Key Takeaways
- Transformance’s AI agents work from eight kinds of system besides the ERP, and its integrations hub connects them: if a system has an API, a database, a file drop or a mailbox, it can be connected.
- The feeds carry four kinds of data: the money (bank, lockbox, processors), its explanation (EDI, portals, mailbox), the invoice (billing) and the customer context (CRM).
- An unmatched payment is usually a missing input, not a weak matcher: the payment sits in the bank file while its explanation sits in a mailbox, a portal or an EDI file.
- Connect in the order money, explanation, customer: the bank first, then the remittance mailbox, then EDI, then portals, then CRM and billing.
- Every feed needs a named owner, a system of record for each field and an alert when it stops delivering.
In This Article
- Key Takeaways
- Which systems besides the ERP feed accounts receivable?
- What does AR get from the bank, and what does it not?
- What can EDI give accounts receivable, and how does it connect?
- What do customer portals and shared mailboxes add?
- What should the CRM, billing systems and payment processors give AR?
- Which sources should you connect first?
- Who owns each connection, and what must you agree?
- How does Transformance work with these sources?
Which systems besides the ERP feed accounts receivable?
Agents like Transformance’s Vero draw on eight kinds of system besides the ERP: bank, lockbox, EDI, customer AP portals, shared mailboxes, CRM, billing systems and payment processors.
Systems besides the ERP that feed accounts receivable: data, connection, owner and what breaks
An AR data source is any system other than the ERP that supplies something cash application, AR collections or dispute work needs: the money, its explanation, the invoice or the customer context. The ERP stays the system of record for open items; the others feed it or sit beside it. The connection and failure columns are our reading from implementations, not survey results.
This page is the map. Bank channels are in how to connect bank statements to cash application, remittance in depth in where remittance advice comes from, and the ERP half in what AR automation reads from and writes to the ERP.
Takeaway: list the eight rows for your own company before you judge any matcher; most gaps are rows nobody connected.
What does AR get from the bank, and what does it not?
The bank gives AR proof that money arrived, as a statement line with an amount and a reference, but not the list of invoices the payment covers.
The statement arrives over EBICS, bank SFTP, a bank API or the ERP’s bank interface, as camt.053, BAI2 or another format (bank statement formats for cash application). The explanation usually travels separately unless the payer sends structured remittance data.
In the US, ACH carried 41% of B2B payments by count in 2024 and checks 13%, down from 32% in 2015 (Federal Reserve Bank of Cleveland, 2026). So most payments first show up in the bank feed, while checks and their paper remittance reach AR through the lockbox file, whose layout differs by bank.
What breaks: a statement that arrives late, twice or cut short looks exactly like unapplied cash.
Takeaway: the bank tells you money came in; plan from day one where the explanation will come from.
What can EDI give accounts receivable, and how does it connect?
EDI gives AR structured documents from a customer’s system, most often the EDI 820 remittance advice, through your ERP’s EDI layer, an EDI provider or a direct partner link.
The EDI 820 is the X12 payment order or remittance advice transaction set; REMADV is the EDIFACT remittance advice message. Nacha describes the CTX format as an ACH credit or debit that supports up to 9,999 addenda records, so a full ANSI ASC X12 message or UN/EDIFACT payment information can be sent with the entry (Nacha ACH Guide for Developers, 2026); its rules name the 820 as one such message (Nacha, 2013). Otherwise it arrives over the EDI connection and is tied to the payment by a reference.
An EDI integration is an agreed route plus a mapping. The route is usually an EDI provider’s value-added network, a direct AS2 link or SFTP; the set-up adds a partner profile, credentials and the mapping between the partner’s documents and your ERP. EDI also brings invoices (810 or INVOIC) and order data. Each trading partner’s implementation guide decides the codes and document numbers, so mapping is done partner by partner.
What breaks: a customer quotes its own document numbers instead of yours; an advice arrives without its payment, or the reverse; a partner changes EDI provider and the feed goes silent.
Takeaway: for payers who already send EDI, the 820 is the cleanest explanation you can get; map it per partner and watch for silence.
What do customer portals and shared mailboxes add?
Customer AP portals add invoice and payment status that exists nowhere else, and a shared AR mailbox carries the remittances, disputes and promises to pay that never reach the ERP.
Portals. Each customer’s AP portal is its own system, read portal by portal, and owned by whoever keeps the supplier account, usually billing or AR. A rejected invoice shows up in the portal long before it shows up as overdue, which is why the AP portal checklist starts there. Portal notifications and exports often land in the mailbox or a file drop.
The shared mailbox. The published AR address collects remittance emails and attachments, dispute notices, requests for invoice copies, promises to pay and address changes. It is a data source with a permissions question.
For Exchange Online, Microsoft documents that a permission granted to an application “can be paired with a scope of access (resource scope) to specify which mailboxes an app can access”, and that organization-wide grants in the identity service still apply on top, so they have to be removed for the scope to take effect (Microsoft Learn, 2026). Ask your mail administrator to scope any application to the AR mailboxes only.
Vero connects to the shared AR mailbox and classifies each email by intent: remittance, dispute, promise to pay or query. It drafts replies and sends routine ones itself, such as invoice copies, within rules you set; everything else goes to a person, and bank-detail changes, credit-note or refund requests, write-offs and legal wording always do (how AI triages a shared AR inbox). Customers grant consent for the remittance and collections mailboxes during onboarding, and the health of each connection is tracked.
Takeaway: portals hold status you cannot see elsewhere, the mailbox holds explanations; scope the mailbox before you connect it.
What should the CRM, billing systems and payment processors give AR?
The CRM should give AR the customer hierarchy and account owner, billing systems the invoices created outside the ERP, and payment processors the detail behind each payout.
CRM. A CRM-to-ERP integration should give AR parent and child accounts that match the ERP’s customer hierarchy, the account owner to ask when a payment is unclear, and contacts for AR collections. It breaks on duplicate customers and different IDs. The fix is one agreed customer ID and a system of record per field: the ERP for open items and bank details, the CRM for the account owner. Transformance flags bad master data, such as missing payer links, wrong bank details and duplicates, proposes fixes, and writes approved fixes back to the ERP where you have agreed to write-back; a person approves (master data cleanup before cash application).
Billing, subscription and e-commerce systems. Invoices and credit notes created outside the ERP must be in the ERP, or visible to AR, before the payment arrives; otherwise a correct payment looks like unapplied cash. E-invoicing networks are one more invoice source of this kind (e-invoicing and cash application).
Payment processors. A processor’s payout is one transfer to your bank that can bundle many card and online payments, net of fees and refunds. The processor’s payout report lists the transactions inside it, which turns one bank line back into many customer payments. Your own customer payment portal, if you run one, adds commitments and disputes entered by customers.
Takeaway: the CRM tells AR who the customer is, billing what was invoiced, and the processor what one deposit contains.
Which sources should you connect first?
Connect the sources that carry the money first, then the ones that explain it, then the ones that describe the customer: bank, remittance mailbox, EDI, portals, then CRM and billing.
- Bank: the payment exists only there.
- Remittance mailbox: it explains most payments that arrive without a usable reference.
- EDI for the payers who already send it: structured advices need mapping, not reading.
- Portals for your largest portal customers: status and remittance found nowhere else.
- CRM hierarchy: it links payers to the group and the account owner.
- Billing systems and processors: if invoices or payouts sit outside the ERP.
This order is our reading; your data is the test. For your 20 largest payers, note which source explains each payment and connect the one that explains the most cash first.
Takeaway: money, explanation, customer; then let your 20 largest payers overrule the order.
Who owns each connection, and what must you agree?
Every feed needs a named owner, a system of record for each field and a way to notice when it stops delivering.
Six things to name for every feed:
- Owner: a named person and a deputy, not a team name.
- System of record: which system wins for each field when two disagree.
- Missing-feed alert: how you notice that a statement, an EDI file or a mailbox stopped delivering, and who is told.
- Permission scope: an application sees only the accounts, mailboxes or folders it needs, and the grant is reviewed.
- A real sample: one week of your own files, emails or advices run through the connection before go-live (how to test AR automation before go-live).
- Change contact: who learns when a customer changes portal, EDI provider or remittance address.
Takeaway: a feed without a named owner is a feed nobody notices when it stops.
How does Transformance work with these sources?
Transformance connects the feeds around your ERP through its integrations hub: if a system has an API, a database, a file drop or a mailbox, it can be connected.
That covers every row of the table, each by the route it offers: API, file drop, database, mailbox, or an outbound-only on-premise agent for systems behind your firewall (what an agent-run integration platform is). Transformance’s integration agents read the system documentation and your setup answers, propose field mappings, draft the workflows, run the test plan and report, and draft plain-language explanations when something fails. A person approves every change that reaches your systems or production. Transformance builds, runs, monitors and fixes the connections; your team approves access and production changes. ERP, bank and mailbox connections are set up step by step with your IT team in the loop, and credentials go into dedicated secure slots, never by email.
On top of the feeds, Transformance reads remittances in any format with over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration (Transformance platform data, 2026). ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes, and nothing posts without human sign-off (Transformance customer data, 2026). When a payment does not match, Vero, Transformance’s AI agent, investigates from Customer 360, fetches information from internal and external sources to find more matches, and proposes a match with the evidence; a person approves.
Timing. For the ERPs in production with our customers, the ERP connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs in 4-5 weeks on one entity, and a full rollout takes up to 4-8 weeks (Transformance customer data, 2026). Which other feeds join, and in what order, is agreed with your IT during onboarding (what data an AR automation vendor needs to start).
Takeaway: with every feed connected, the agent sees the payment, its explanation and the customer at once, and a person still approves what posts.
Who Transformance is for
- ERPs: SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo, all running in production with customers; Oracle and Infor supported; plus other ERPs and the systems around them through our integrations hub.
- 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: name the sources, then the owners, then connect in order
List every system that feeds your AR, give each a named owner and a system of record, and connect them in the order money, explanation, customer. This week, write the eight-row table for your own company, mark the rows nobody owns and run the 20-largest-payers test to pick the first connection. Book a Call and bring the table.
Key terms
- EDI 820: the X12 payment order or remittance advice transaction set.
- EDI: the exchange of business documents between trading partners in agreed standards.
- Remittance advice: the message that tells you which invoices a payment covers.
- Lockbox: a bank service that processes checks and paper remittances and delivers a file.
- camt.053: the ISO 20022 XML end-of-day bank statement.
- Cash application: matching incoming payments to open invoices.
Related guides
- Which ERP systems does Transformance integrate with?
- What does AR automation read from and write to the ERP?
- Where does remittance advice come from, and how do you capture it?
- How do you connect bank statements to cash application?
- How can AI triage a shared accounts receivable inbox?
- How does AI read remittance advice and match payments?
Frequently Asked Questions
Which systems besides the ERP feed accounts receivable?
The bank and lockbox, EDI, customer AP portals, shared AR mailboxes, the CRM, billing systems and payment processors. Each supplies the payment, its explanation, the invoice or the customer context.
What is an EDI 820, and is it a payment?
An EDI 820 is the X12 payment order or remittance advice transaction set: it explains a payment but is not the money. Under Nacha’s rules it can travel inside the addenda of an ACH CTX payment, or separately over an EDI connection.
How does an EDI connection to a customer work?
You agree a route with the trading partner, such as an EDI provider’s network or a direct AS2 or SFTP link, then map the partner’s documents to your ERP. Codes and document numbers follow each partner’s implementation guide.
Can an application read a shared AR mailbox safely?
Yes, if your mail administrator scopes the application to the named mailboxes and removes any organization-wide grant that would override the scope.
Which ERPs, company sizes and payment volumes does this work for?
Transformance runs in production with customers on SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations, Business Central and Odoo; Oracle and Infor are supported. It serves companies with 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month.
How long does it take to connect these systems?
For the ERPs in production with our customers, the ERP connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs in 4-5 weeks on one entity, and a full rollout takes up to 4-8 weeks (Transformance customer data, 2026).
What does it cost to connect the sources around the ERP?
It depends on scope and the number of entities, so there is no single figure. Book a Call and we scope your sources, ERPs and entities 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.




