What does a remittance advice that disagrees with the ledger look like?
A freight forwarder receives a payment whose remittance lists four invoices, but a credit note and a dispute flag change what can be applied. The analyst must apply, hold and explain.
A freight forwarder's finance team receives `RCPT-5208` for 12,400.00 from a retail importer. The attached remittance advice lists four invoices, `INV-3301`, `INV-3302`, `INV-3305` and `INV-3309`, with amounts that total 12,400.00.
The open-items record shows something different. `INV-3302` was reduced two weeks earlier by `CN-0177` for 900.00, so its balance is 2,100.00, not the 3,000.00 on the advice. `INV-3309` is in dispute, flagged by operations as a damaged container claim, and rule `POL-DISP-02` forbids applying cash to a disputed invoice without the claims owner's sign-off.
The receivables analyst works through it. Invoices 3301 and 3305 match the advice and are applied. For `INV-3302` the analyst applies 2,100.00 and notes that 900.00 of the receipt now has no home. For `INV-3309` the analyst does not apply and requests sign-off from the claims owner. The unallocated 900.00 and the amount intended for the disputed invoice are placed in suspense against the importer's account, and the importer is told what was applied and what is held.
**Consequence.** The importer's statement shows the held amount as unallocated cash, so the credit control team does not chase invoices that have in effect been paid.
**What it teaches.** A generated record set for this case needs a remittance that disagrees with the ledger, a credit note that changes a balance, a dispute flag, a policy rule that blocks an action, and a suspense outcome. Any one of these alone would make the task much easier.
A good generated case combines a conflicting remittance, a changed balance, a blocking rule and a suspense outcome in one record set.
- Audience:
- Model labs
- Content type:
- Scenario
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- Can a release encode an organisation's allocation policies as well as transactions?
- What would a generated task for an insurance short-pay look like?
- What do the record schema and links look like in JSONL?
- What can a generated dataset for matching payments to obligations contain?
- Which record types should I request for a simulated payment matching environment?
- Can a release include tolerances, write-off limits and approval rules?