Key Takeaways
- Remittance advice has eight sources: two travel inside the payment, six arrive separately and need their own intake route and owner.
- ACH carried 41% of US B2B payments by count in 2024, up from 25% in 2015 (Federal Reserve Bank of Cleveland, 2026), and an ACH CCD payment supports only 80 characters of remittance information (ASC X9, 2022), so a long invoice list travels separately.
- A separate advice can only be applied automatically when it shares a linkage key with its payment: a payment reference first, then payer, total and date.
- Capture fails at the source: an advice sent to a salesperson, a portal nobody downloads, a new PDF layout or an advice with no key.
- Transformance reads remittances in any format with over 97% extraction accuracy and no templates, and ClearMatch auto-matches 95% of payments (Transformance platform and customer data, 2026).
In This Article
- Key Takeaways
- Where does remittance advice come from, and what does each source carry?
- Which sources arrive inside the payment, and which arrive separately?
- How do you capture each source?
- How do you tie a separate remittance advice to its payment?
- How does an ERP take a remittance advice in?
- What breaks remittance capture, and how do you spot it?
- Illustrative example: one Monday, five payments, five sources
- How does Transformance capture remittance advices?
Where does remittance advice come from, and what does each source carry?
Remittance advice comes from the payer’s accounts payable team and reaches you by eight routes, each with its own delivery, format and level of detail.
Remittance advice sources: who sends them, what they carry and how to capture each
Remittance advice is the message that tells you which invoices, credit memos and deductions a payment covers. The bank statement proves the money arrived; the advice explains what it was for.
The columns follow the three dimensions in the US standards body’s ISO 20022 Remittance Content Market Guide (ASC X9, IR 01-2022, 2022): delivery (inside the payment or separate), format (structured or free text) and content. Content comes in four tiers: tier 1 is document number, date, amount due and amount paid; tier 2 adds discounts and adjustments; tier 3 adds invoicer and invoicee; tier 4 adds line items. X9 warns that ignoring any of the three “can lead to missing the true cause of problems”. The tier per source is our reading of typical practice, not a measured distribution.
The bank file alone rarely carries enough. By count, ACH carried 41% of US B2B payments in 2024 and checks 13%, against 25% and 32% in 2015 (Federal Reserve Bank of Cleveland, 2026). B2B volume on the ACH network grew almost 10% in 2025 to close to 8.1 billion payments (Nacha, 2026). An ACH CCD payment “only supports 80 characters of remittance information in an addenda” (ASC X9, 2022), so a long invoice list has to travel separately; how much room each bank field has is set out in how AI reads remittance advice.
This page covers sources and capture. Field-level bank file structure is in the BAI2, camt.053 and MT940 guide, and the case where nothing usable arrives is in how to match a payment with no reference.
Which sources arrive inside the payment, and which arrive separately?
Two of the eight sources travel inside the payment, bank reference text (including ISO 20022 data) and an EDI 820 on a CTX payment; the other six arrive separately.
Inside the payment. First, the reference field you already import with the bank statement; in an ISO 20022 payment message it can hold structured remittance data. Second, the EDI 820, the X12 payment order / remittance advice transaction set: the Federal Reserve’s Fundamentals of Financial EDI (FedPayments, 2021) shows a CTX payment carrying the 820 in its addenda records.
Separate from the payment. X9 names “emails, portals, and other electronic means”, and notes that a stand-alone ISO 20022 remittance message “can also be used for payment types that do not support remittance data, for example, card payments” (ASC X9, 2022). Attachments, lockbox stubs and paper complete the list.
For every separate source, the advice and the money can arrive on different days, through different teams, and they only meet through a key both carry.
A pattern to check for: teams watch the source they can see, usually the AR inbox, and treat the rest as exceptions. Large customers often pay through portals or EDI, so they get the weakest coverage. Pull unapplied cash by customer and see whether your 20 largest payers sit at the top.
How do you capture each source?
Capture each source where it enters your company, with one owner and one route per source, and normalize everything to the same fields before any matching starts.
Seven steps to set up remittance capture
- List your 20 largest payers and the route each one uses: bank text, email, attachment, EDI, portal, lockbox or paper. Owner: AR lead.
- Publish one AR address and a short note on what an advice must contain: payer, payment date, total, invoice numbers, amount per invoice, discounts and deductions. Owner: AR lead with sales.
- Set up the bank and lockbox feeds your ERP imports, and confirm the reference arrives untruncated. Owner: treasury and finance systems.
- Put a named owner and a daily schedule on every portal and every EDI connection. Owner: AR team.
- Extract every source into the same fields (X9 tier 1 and tier 2) and keep the original document next to the extracted fields. Owner: AR operations.
- Define the linkage key (payment reference, then payer plus total plus date window) and what stays pending. Owner: AR lead.
- Measure the share of payments with a captured advice within one business day, payments waiting for an advice and advices without a payment, and review every low-confidence read. Owner: AR lead.
Whatever the source, extract the same fields: payer, payment date and total, document numbers, amount paid per document, discounts, deductions and credit memos. Where the customer quotes its own PO or document number, keep a mapping table to your invoice numbers.
Three source-specific rules matter most. EDI is parsed, not read, and trading-partner guides for the 820 use different code values, so check each payer’s guide before trusting a field. Email body and attachment are read together, because the short-pay reason often sits only in the body while the invoice table sits in the PDF. Portals need a named person with a working login, or the export simply does not happen.
Customers send advices to whichever address they already have, often a salesperson. Print one AR address on every invoice and statement. How the document is then read and matched is covered in how AI reads remittance advice and matches payments.
How do you tie a separate remittance advice to its payment?
Use a linkage key that both carry, a payment reference or payer, amount and date, and keep an advice without a payment pending, never posted.
X9 states the rule plainly: “When remittance data is sent separate from the payment, there must be a linkage identifier in the payment and separately sent remittance data to match the remittance data with the payment in an automated fashion for cash application” (ASC X9, 2022).
Our guidance on keys, strongest first:
- A unique payment reference carried in both: end-to-end ID, ACH trace number, check number or the payer’s payment run number.
- Payer plus exact total plus a value-date window: works when a payer sends one payment a day; fails when it sends three of the same amount.
- Payer plus invoice numbers: the fallback when the totals differ because of a deduction or discount.
For euro receipts, the European Payments Council’s SEPA instant credit transfer guidelines (EPC121-16, the 2025 version in force since 5 October 2025, issued in 2024) list the ISO 11649 structured creditor reference. When that reference is present, “the Debtor PSP is not obliged to validate the reference information” (EPC, 2024). Print the reference on the invoice, and expect it to arrive unvalidated.
The advice is not the payment. An advice that arrives before the money stays open until the bank line appears; an advice for a payment that never arrives is a question for the customer, not a posting. Instant payments tighten the timing further (instant payments and cash application). When neither an advice nor a usable reference arrives, see how to match a payment with no reference.
How does an ERP take a remittance advice in?
An ERP keeps the advice next to the open items it will clear. SAP’s documented mechanism stores payment advice notes in an advice note database used to clear open items.
SAP’s library describes the standard process in “Entering Payment Advice Notes per EDI (FI-AR-AR-P)” (SAP Library, NetWeaver 7.0 help, undated): advice notes can arrive from a business partner by EDI, and “Payment advice notes are stored in the advice note database and can then be used to clear open items.” The company code is derived from the partner’s bank details or from an external-name assignment in Customizing. The page belongs to an older release, so check your own release’s documentation for the current transactions and apps.
The bank statement line brings the money, the advice note brings the list of documents, and the clearing posting closes the customer’s open items against both. Three things can stop that in a live system (our practitioner reasoning, not a sourced list):
- A blocked document. The invoice in the advice carries a payment block or sits in dispute, so the clearing proposal stops at that line.
- A locked period. The value date falls in a closed posting period, so the clearing is rejected or has to be moved to an open period.
- A residual item. The advice pays $9,880 against a $10,000 invoice and the $120 difference has no reason code, so it stays open as a residual item until someone classifies it (illustrative amounts).
This page documents one ERP on purpose. Posting and clearing in each ERP are covered in how payments post and clear open items from an external system, and the SAP side of the connection in the SAP S/4HANA integration guide.
What breaks remittance capture, and how do you spot it?
Capture breaks at the source: an advice sent to the wrong address, a portal nobody downloads, an unseen layout or an advice that cannot be tied to one payment.
Eight gaps that stop an advice from being captured, and the fix at the source
The rows are patterns, not measured shares. X9 covers two directly: the linkage identifier, and “a parent company making payments for subsidiaries” that has to say whom it pays for (ASC X9, 2022).
Four signals to pull from your own data (our guidance, not benchmarks):
- Unapplied cash by customer, sorted by amount.
- Payments waiting for an advice for more than two business days.
- Advices without a payment for more than five business days.
- The share of payments matched on the bank reference alone.
E-invoicing and ISO 20022 improve the data that can travel, but they do not deliver an advice a payer never sends (e-invoicing and cash application). The unapplied cash that capture gaps leave behind is the subject of how to clear an unapplied cash backlog.
Illustrative example: one Monday, five payments, five sources
On an illustrative Monday, five customers pay a US distributor by five routes; with an owner on each route, all five advices are captured and one goes to a person.
Distributor A is fictional and every amount is illustrative, in USD:
The five payments total $153,740. Four advices tie out to the cent. The fifth lists three invoices of $12,400, $9,080 and $6,500, which sum to $27,980, $500 more than the wire. The difference is classified as a short pay and goes to a person with the email as evidence.
Capture finished before the matching question started. Without a portal owner, the hospital group’s $41,000 would have sat unapplied until someone logged in.
How does Transformance capture remittance advices?
Transformance reads remittances in any format with over 97% extraction accuracy and no templates; ClearMatch auto-matches 95% of payments, and a person approves anything that posts.
DocSense reads remittances with vision language models, not OCR plus regex: over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration, so a new layout is read on the first attempt (Transformance platform data, 2026). A PDF, a spreadsheet or a scanned stub is read as a page, tables included.
ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes, with 100% posting validation; nothing posts without human sign-off (Transformance customer data, 2026). ClearMatch works on the bank statement lines your ERP has imported and the remittances read by DocSense, and writes clearing postings back after approval.
For the exception, such as a payment with no advice or a short pay like the one above, Vero, the AI agent, investigates from Customer 360, its memory of each customer. It fetches information from internal and external sources to find more matches and proposes with the evidence attached. A person approves, and postings follow your approval thresholds.
Transformance works with customers across Europe, the United States and Australasia, including Syngenta, Eberspächer and PwC.
Who Transformance is for
- ERPs: teams whose cash application clears in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).
Conclusion: give every remittance source an owner before you tune the matching
Capture decides how much cash application runs without a person: list your sources by customer, give each an owner and a key, and measure coverage before tuning any matching rule.
Start with your 20 largest payers and the route each one uses. Then measure, for four weeks, the share of payments with a captured advice within one business day; that is our definition, not a benchmark. For the cash that capture gaps have already left behind, see the unapplied cash backlog guide; for the bank-side half of the input, see the bank file formats guide; and for the full rollout, how to automate cash application with AI.
Key terms
- Remittance advice: the payer’s message listing which invoices, deductions and credit memos a payment settles.
- EDI 820: the X12 payment order / remittance advice transaction set, often carried with an ACH CTX payment.
- Lockbox: a bank service that collects check payments and sends their remittance data as a file with images.
- Cash application: matching incoming payments to the open invoices they settle.
- SEPA: the euro payment scheme, whose transfers carry one short remittance field.
- camt.053: the ISO 20022 XML end-of-day bank statement that brings the bank reference into the ERP.
Related guides
- Which ERP systems does Transformance integrate with?
- What does AR automation read from and write to the ERP?
- How do payments post and clear open items from an external system?
- How does the SAP S/4HANA integration work?
- Why does unapplied cash pile up, and how do you clear the backlog?
- How does AI read remittance advice and match payments?
- Rule-based vs AI cash application
Frequently Asked Questions
What is remittance advice, and is it proof of payment?
Remittance advice tells you which invoices, credit memos and deductions a payment covers. It is not proof of payment: the bank statement is the record that the money arrived, so an advice without a bank line stays pending.
Where does remittance advice come from?
It comes from the payer’s accounts payable team. It arrives inside the payment (bank reference text, an EDI 820 on a CTX payment, ISO 20022 data) or separately by email, attachment, customer portal, lockbox stub or paper.
How do you capture remittance advice from email?
Publish one AR address, state what the advice must contain, and read the email body and the attachment together, because the short-pay reason is often only in the body. Keep the original email with the extracted fields.
Which ERPs does Transformance work with for remittances?
Transformance runs in production with customers on SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations, Business Central and Odoo, and supports Oracle and Infor.
Is this for a company of our size and payment volume?
Transformance is built for mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities, and for volumes from under 1,000 to over 100,000 payments a month.
How long does it take to start reading remittances?
The ERP connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs 4-5 weeks on one entity, and a full rollout takes up to 4-8 weeks.
What does it cost?
Cost depends on scope and the number of entities, from cash application alone to the full order-to-cash, so there is no figure on this page. Book a Call and we scope it with you.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
