# Cash application exceptions: system map | SourceX

Canonical: https://refer.sourcex.si/guides/cash-application-exceptions-records-across-systems
Last updated: 2026-11-04

Five linking fields carry a cash application exception from bank to ledger: the amount, value date and payer reference that tie a bank entry to its remittance; the invoice numbers and line amounts that tie the remittance to open items; the settlement ID that records how cash was applied; the case ID that carries a short amount into a deduction investigation; and the credit memo number that closes it. If any one of those fields lived only in a tool the company has retired, the case cannot be rebuilt.

This system map is part of the [cash application exceptions guide](/guides/workflow-cash-application-exceptions), which works through what an exception is and why the manual decision matters. Here the question is narrower: where does each record sit, which key joins it to the next, and who owns it? It is written for systems advisors who need to describe a company's evidence without handling any of it.

## The five systems in one exception

A short payment touches five places, and few companies hold all five in one system:

- **Bank feed.** The incoming credit, often delivered in an ISO 20022 camt.053 statement message. It shows money arrived, not what it was for.
- **Remittance source.** What the customer meant to pay: invoice numbers, amounts and any short-pay codes. It may come as EDI, a PDF, a portal download or the body of an email, and it is often stored apart from the money.
- **ERP receivables.** The open invoices and the settlement that applied cash to them.
- **Deduction or case tool.** The investigation of any short amount: routing, evidence and notes. It may be a module of a cash application tool, an ERP case module or a ticket queue.
- **Approval and credit.** The approval at the right level and the credit memo or corrected invoice that clears what is left, usually back in the ERP.

## Linking keys: system, record, key and owner

| System | Record | Linking key | Owner |
|---|---|---|---|
| Bank feed | Incoming credit | Amount, value date, payer reference | Treasury manager |
| Remittance source | Remittance advice | Payer reference plus invoice numbers and line amounts | AR director |
| ERP receivables | Open invoices | Invoice number | Controller |
| ERP receivables | Settlement | Settlement ID, invoice number, amount settled | AR director |
| Case tool | Deduction case | Case ID quoted on the invoice or settlement note | AR director or sales operations |
| Approval workflow | Approval | Case ID and approver | Controller or AR director |
| ERP receivables | Credit memo or corrected invoice | Memo number referencing the invoice and case ID | Controller |

## Where the joins fail

**Bank to remittance.** The weakest link when remittance arrives separately. Bank references are short and often omit invoice numbers, so the join relies on amount and date plus whatever the person applying cash recorded. If the remittance was parsed by a vendor tool and only the result kept, what the customer originally said is gone.

**Remittance to settlement.** A settlement records where the cash went, rarely why. Microsoft's documentation for Dynamics 365 Finance shows the mechanics: a partial payment leaves the invoice open for the remainder, the amount can be set by hand, and without a priority the automatic run picks by due date. Whenever someone overrode that default, the reason sits in the remittance or a note, not in the settlement row.

**Settlement to case.** Breaks when the case ID was never written on the invoice or settlement, or when the case lives only in a tool being retired.

**Case to credit.** Breaks when the credit posts as a generic adjustment with no reason code or case reference.

## One fully joined case (Illustrative)

Fictional figures for a fictional 300-person food distributor; not a real case or a completed deal. One customer pays two invoices with one electronic credit and deducts a pricing difference.

| Step | Record | Key that joins it to the next | Value |
|---|---|---|---|
| 1 | Bank credit, June 3 | Amount and payer reference | $31,480.00 |
| 2 | Remittance by email, June 3 | Invoice numbers 5520 and 5524 | $18,200.00 and $13,280.00 paid |
| 3 | Settlement S-90311, June 4 | Invoice 5524 left open | $800.00 short on $14,080.00 |
| 4 | Deduction case D-2207, June 4 | Case ID on invoice 5524 | Reason: pricing, promotion not applied |
| 5 | Approval by controller, June 12 | Case ID and approver | Promotion confirmed valid |
| 6 | Credit memo CM-1180, June 12 | Memo references 5524 and D-2207 | $800.00, invoice closed |

The arithmetic holds: $18,200.00 plus $14,080.00 is $32,280.00 due, the customer paid $31,480.00, and the $800.00 gap is closed by the memo. Every key is present, so the chain reads from bank entry to a closed invoice. In a real company, expect gaps, especially at steps 2 and 4; the map shows where.

## Questions to put to the AR director

Fill the map at metadata level with these:

1. Which bank file formats arrive, and are remittances received with the payment or separately?
2. Where are remittance images or files stored, and for how many years?
3. Is the case ID written on the invoice or settlement in the ERP?
4. Does the cash application tool, if any, export matching history and case notes, or only posted results?
5. Are credits coded with a reason and a case reference?
6. Is any system in this chain due to be retired, and when?

Write "unknown" until someone confirms an answer, especially on exports. The [preservation checklist](/guides/preserve-cash-application-exceptions-records) covers a vendor switch, and the [workflow map template](/resources/workflow-map-template-business-records) is a general format for this kind of map. For systems already being shut down, see [application decommissioning](/questions/application-decommissioning).

## Qualification and what stays unknown

The map describes records and owners; it does not decide rights. Remittances and case notes name customers and may fall under confidentiality terms in customer contracts. [Why data rights matter](/proof/why-data-rights-matter) explains why SourceX reviews that first. A similar exception pattern in transport is described on [freight audit exceptions](/data-types/freight-audit-exceptions).

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company. Buyer interest, the rights result, the de-identification needed and any offer stay unknown until SourceX reviews it. The [who can say yes decision tree](/questions/who-can-license-cash-application-exceptions-records) covers whom to introduce.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the map shows a company whose exceptions still join from bank entry to credit memo, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the AR director.

## Sources

- https://refer.sourcex.si/terms
- https://www.iso20022.org/iso-20022-message-definitions?search=camt.053
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/customer-payments-partial-amount
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/automatic-settlement-prioritization
