Cash application exceptions across bank feed, remittance and ERP: a system map of records and linking keys

Short answer

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.

Visual briefFull-size diagram
Five system nodes in a chain, bank feed, remittance, settlement, deduction and credit memo, with linking keys (amount and date, invoice numbers, settlement ID, case ID) dropping onto the connectors to join one Illustrative short payment of $31,480.00.
Illustrative system map. One short payment joined from bank entry to closed invoice by five keys.

This system map is part of the cash application exceptions guide, 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

SystemRecordLinking keyOwner
Bank feedIncoming creditAmount, value date, payer referenceTreasury manager
Remittance sourceRemittance advicePayer reference plus invoice numbers and line amountsAR director
ERP receivablesOpen invoicesInvoice numberController
ERP receivablesSettlementSettlement ID, invoice number, amount settledAR director
Case toolDeduction caseCase ID quoted on the invoice or settlement noteAR director or sales operations
Approval workflowApprovalCase ID and approverController or AR director
ERP receivablesCredit memo or corrected invoiceMemo number referencing the invoice and case IDController

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.

StepRecordKey that joins it to the nextValue
1Bank credit, June 3Amount and payer reference$31,480.00
2Remittance by email, June 3Invoice numbers 5520 and 5524$18,200.00 and $13,280.00 paid
3Settlement S-90311, June 4Invoice 5524 left open$800.00 short on $14,080.00
4Deduction case D-2207, June 4Case ID on invoice 5524Reason: pricing, promotion not applied
5Approval by controller, June 12Case ID and approverPromotion confirmed valid
6Credit memo CM-1180, June 12Memo 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 covers a vendor switch, and the workflow map template is a general format for this kind of map. For systems already being shut down, see 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 explains why SourceX reviews that first. A similar exception pattern in transport is described on 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 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, check the company against who qualifies and read the program terms before introducing the AR director.

  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

Is the ERP enough to rebuild a cash application exception on its own?

Usually not. The ERP keeps the posted result: which invoices were settled and by how much. The remittance that explains the customer's intent and the case notes that explain the investigation often sit elsewhere, and those are the links that break.

Should I ask the company to send a sample remittance to show the format?

No. Ask which format arrives (EDI, PDF, portal download or email body) and where it is stored. A sample names the customer and may be confidential under the customer contract.

What if the cash application tool is being replaced?

Then ask, before the switch, whether its matching history, case notes and remittance images export or only its posted results. Record unknown until the administrator confirms. The preservation checklist for cash application records covers the switch in detail.

Sources

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

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