Cash application exceptions: the records that show how a short payment was resolved

Short answer

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.

Visual briefFull-size diagram
Stacked bars: three invoices totaling $52,000.00, a single payment of $50,250.00 that leaves $1,750.00 short on the third invoice, and the gap closed by an approved credit memo for $1,750.00.
Illustrative short payment: one remittance, three invoices, one deduction resolved by credit memo.

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.

RecordSystemPart of the exception it shows
Bank statement entryBank feed or bank portalThe initial problem: cash that does not equal the open items
Remittance adviceEmail, EDI or customer portalThe customer's stated intent and any deduction code
Matching decisionERP settlement recordHow the cash was split across invoices, and by whom
Deduction or dispute caseERP case module or trackerThe investigation, routing and supporting evidence
ApprovalWorkflow or emailWho authorized the outcome, against which limit
Credit memo, rebill or repayment requestERPThe authorized action that closed the balance
Reason code and closed balanceERPThe 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.

InvoiceAmount dueAmount paid per remittanceDifferenceRemittance note
7711$23,400.00$23,400.00$0.00None
7712$16,350.00$16,350.00$0.00None
7716$12,250.00$10,500.00$1,750.00Deduction: damaged on arrival
Total$52,000.00$50,250.00$1,750.00One 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 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 and freight audit exceptions cover neighboring records, and the industries hub lists more.

Go deeper on cash application exceptions

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, check the company against who qualifies, and keep the program terms at hand when you introduce the AR director or CFO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Are unapplied-cash reports enough on their own?

Rarely. An unapplied-cash report shows that money sat unmatched, not why or how it was resolved. The value is in the remittance, the matching decision, the deduction case and the credit or rebill that closed it.

Do customer remittances belong to the company?

The company received them in the course of its own business, but they name customers and can fall under confidentiality terms in customer contracts. That is why the rights review, not the partner, decides what can be included and how it is de-identified.

Does a treasury systems advisor need to be involved after the introduction?

Only if the company wants it. Once the decision-maker is introduced, SourceX works with the company directly; the partner's credit depends on the first valid introduction and the company's verified application, as set out in the terms.

Sources

  1. learn.microsoft.com/en-us/dynamics365/finance/accounts-receivabl…
  2. learn.microsoft.com/en-us/dynamics365/finance/accounts-receivabl…
  3. iso20022.org/iso-20022-message-definitions
  4. x12.org/products/transaction-sets
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment