# Cash application exception records | SourceX

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

The records that explain a cash application exception are the ones that show the mismatch and the decision that resolved it: the bank entry, the remittance advice, the matching decision in the ERP, the deduction or dispute case, the approval at the right level, and the credit memo, rebill or repayment that closed the balance. Together they connect an initial problem to an authorized action and a checked result, which a matching rule alone never records.

Cash application looks mechanical until a payment does not equal the open items. Then a person reads a remittance, decides how to apply the money, opens a case and chases the difference. This guide shows which records capture that judgment, works one Illustrative short payment from bank credit to closed invoice, and lists what a treasury systems advisor can note without handling any of it.

## What counts as a cash application exception?

Any receipt that cannot be matched to open invoices automatically and in full. The common shapes are a short payment, an overpayment, a payment with no usable reference, and one payment spread across several invoices with a deduction on one of them.

Each shape leaves a slightly different trail, but the core records are the same. The bank statement entry, often delivered as an ISO 20022 camt.053 statement message, reports the booked credit. The remittance advice says what the customer intended, and it may arrive as an X12 820 transaction, a portal download or an email. The ERP holds the matching decision. Everything after that, the case, the approval and the closing document, is where the exception is actually handled.

## Which cash application exceptions records help a company explain how exceptions were handled?

The ones that show the arithmetic of a mismatch and the decision that resolved it. A short payment across several invoices is the classic case, because a matching rule alone cannot close it.

| Record | System | Part of the exception it shows |
|---|---|---|
| Bank statement entry | Bank feed or bank portal | The initial problem: cash that does not equal the open items |
| Remittance advice | Email, EDI or customer portal | The customer's stated intent and any deduction code |
| Matching decision | ERP settlement record | How the cash was split across invoices, and by whom |
| Deduction or dispute case | ERP case module or tracker | The investigation, routing and supporting evidence |
| Approval | Workflow or email | Who authorized the outcome, against which limit |
| Credit memo, rebill or repayment request | ERP | The authorized action that closed the balance |
| Reason code and closed balance | ERP | The checked result |

An unapplied-cash report alone shows that money sat unmatched, not why or how it was resolved. The value is in the chain.

### Illustrative short payment, worked through

A 410-person building products manufacturer receives one ACH payment of $50,250.00 from a regional distributor (customer C-2207). Three invoices are open for that customer.

| Invoice | Amount due | Amount paid per remittance | Difference | Remittance note |
|---|---|---|---|---|
| 7711 | $23,400.00 | $23,400.00 | $0.00 | None |
| 7712 | $16,350.00 | $16,350.00 | $0.00 | None |
| 7716 | $12,250.00 | $10,500.00 | $1,750.00 | Deduction: damaged on arrival |
| Total | $52,000.00 | $50,250.00 | $1,750.00 | One payment, three invoices |

What a person did, in order:

1. **May 2.** The bank statement shows a booked credit of $50,250.00 with a short reference, not invoice numbers.
2. **May 3.** The remittance arrives separately by email and lists the three invoices and a deduction code on 7716.
3. **May 3.** The cash applier settles 7711 and 7712 in full and applies $10,500.00 to 7716, leaving $1,750.00 open.
4. **May 4.** A deduction case is opened and routed to the sales operations team with the remittance attached.
5. **May 11.** Proof of delivery shows damage noted at receipt; the sales manager recommends a credit.
6. **May 13.** The AR director approves a credit memo for $1,750.00, above the specialist's approval limit.
7. **May 14.** The credit memo is applied to 7716, the invoice closes, and the case is marked resolved with a reason code.

That is the full shape of an exception record: an initial problem, an authorized action approved at the right level, and a checked result (a zero balance on all three invoices).

## Why the manual decision is the valuable part

The ERP behavior in step 3 is standard, and that is the point. In Dynamics 365 Finance, for example, a partial payment partially settles an invoice, which stays open with a balance, and the amount to settle can be set by hand. Without a settlement priority, automatic settlement picks transactions by due date. Left to the default, the cash could have gone to the oldest invoices first and hidden which one the customer actually disputed.

The case would also look different if the deduction were invalid. Then the outcome is a rebill or a repayment request, and the correspondence records the argument. Both branches, accepted and rejected deductions, are what make the history instructive: they show the same starting problem leading to different authorized actions for documented reasons. That is the kind of work record AI agents need, as [why AI agents need work data](/proof/ai-agents-need-work-data) explains.

## What a partner can note, and what stays unknown

Note the exception shapes the company handles, roughly how many deduction cases it opens a year, which systems hold remittances, cases and approvals, and how many years can still be joined. Do not collect remittances, bank statements or case exports: they name customers and may fall under confidentiality terms in customer contracts.

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. The AR director or controller usually knows coverage; the company's counsel decides what customer contracts allow; the CEO, or the owner-CEO in an owner-run company, authorizes a licensing discussion. Whether buyers want this record set, what the rights review concludes and how much de-identification is needed stay unknown until SourceX reviews it. The [accounts receivable dispute resolution page](/data-types/accounts-receivable-dispute-resolution-process) and [freight audit exceptions](/data-types/freight-audit-exceptions) cover neighboring records, and the [industries hub](/industries) lists more.

## Go deeper on cash application exceptions

- [Cash application exceptions records across systems](/guides/cash-application-exceptions-records-across-systems) is a field map of how bank feed, remittance and ERP records join.
- [Who can license cash application exceptions records](/questions/who-can-license-cash-application-exceptions-records) answers which finance decision-maker to introduce.
- [Preserve cash application exceptions records](/guides/preserve-cash-application-exceptions-records) is an inventory checklist for a cash application vendor switch.
- [Cash application exceptions referral brief template](/resources/cash-application-exceptions-referral-brief-template) gives a fill-in introduction note.

## 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 a client's deduction cases can still be traced from bank credit to closed invoice, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and keep the [program terms](/terms) at hand when you introduce the AR director or CFO.

## Sources

- 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
- https://www.iso20022.org/iso-20022-message-definitions?search=camt.053
- https://x12.org/products/transaction-sets
- https://refer.sourcex.si/terms
