bb-backoffice-payments

Apply FIFO accounting rules to reconcile order-payment ledgers via Prisma transactions.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill bb-backoffice-payments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-backoffice-payments
Source: https://github.com/valentinmathey/Skills-Back-Automation/tree/main/skills/bb-backoffice-payments
Command: npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill bb-backoffice-payments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill manages and reconciles customer cash flows by applying First-In-First-Out (FIFO) principles to orders and payments through the PaymentApplication model, ensuring accurate balances derived from AccountMovement records.

Core Features & Use Cases

  • FIFO-based linking of orders and payments to resolve mismatches in customer accounts.
  • Partial settlement support across multiple debts, reflecting oldest obligations first.
  • AccountMovement as the single source of truth for client balances, with deterministic, auditable updates via Prisma transactions.

Quick Start

Run the FIFO-based reconciliation for all open orders and payments to update balances.

Frequently Asked Questions about bb-backoffice-payments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reconcile partial order payments using FIFO accounting rules?

To reconcile partial order payments using FIFO accounting rules, you apply the First-In-First-Out principle to link payments to the oldest outstanding obligations, resolving mismatches by updating account balances via the PaymentApplication model.

How does FIFO payment settlement handle multiple debts across customer accounts?

FIFO payment settlement handles multiple debts by systematically applying payments to the oldest obligations first. This resolves partial settlements across accounts by ensuring deterministic, auditable updates through AccountMovement records.

Can I enforce atomic transaction updates for backoffice payment reconciliation in Prisma?

Yes, you can enforce atomic transaction updates for backoffice payment reconciliation in Prisma. The reconciliation logic specifies dependencies on Prisma transactions to validate movements and enforce atomic updates across the ledger.

What is the PaymentApplication model used for in backoffice ledger management?

The PaymentApplication model is used for linking orders and payments in backoffice ledger management. It applies FIFO principles to resolve mismatches, ensuring accurate client balances are derived from AccountMovement records.

How do I ensure AccountMovement records act as the single source of truth for client balances?

To ensure AccountMovement records act as the single source of truth for client balances, you execute FIFO-based reconciliation for all open orders and payments, validating movements and enforcing deterministic, auditable updates through Prisma transactions.