Customer Receipt Allocation Ledger

How to use Customer Receipt Allocation Ledger

Enter invoice charges and date-ordered receipts. Either name exact invoice applications or use oldest-due-first for that customer; preserve each application, outstanding balance and excess receipt amount without posting to an account.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Enter invoice charges and date-ordered receipts. Either name exact invoice applications or use oldest-due-first for that customer; preserve each application, outstanding balance and excess receipt amount without posting to an account.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–200 invoices and 0–199 receipts, at most 200 records together and 500 actual applications. Each record has a distinct ID within its kind. Dates are Gregorian 1900–9999; issue dates and receipts are on/before asOf, with due dates not earlier than issue.
• Amounts are positive exact cents up to 1,000,000,000. Receipts are processed in nondecreasing date order, source order on equal dates. Applications require the same customer, an already-issued invoice and sufficient invoice/receipt balances. Explicit mode can leave a deliberate unapplied credit.
• Unapplied credit stays on that receipt and is not automatically reused later. No FX, discounts, tax, write-offs, credit-note netting, reversal, payment verification, automatic bank matching, posting, collection advice, transfer or customer contact.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.