Key Takeaways
- Transformance’s AI agents start from six data sets, each with a named owner on your team.
- A proof of value runs on one entity with read-only ERP access; write access comes with the rollout.
- Export every file at one key date and tie the open items list to the receivables control account before you send it.
- The answer key, your team’s own matches for a past period, turns the test from a demo into a measurement.
- Tolerances, reason codes, the posting approver and the exception owner are part of the data request.
In This Article
- Key Takeaways
- What data does an AR automation vendor need to start?
- What is the minimum for a proof of value, and what do you add for rollout?
- What goes on the full data request checklist?
- How do you export the open items list from your ERP?
- Which bank statements and remittances do you need to provide?
- Which decisions and rules count as data?
- How do you hand over data safely?
- How does Transformance collect this data in onboarding?
- What if the data is not clean?
What data does an AR automation vendor need to start?
Transformance’s AI agents start from six data sets you hand over: your open items, the customer master, bank statements, sample remittances, your past matches and your posting rules.
What to hand over: six data sets, why, and who provides them
No public standard or 2026 benchmark exists for this list; it is a practical request, not an ERP vendor requirement.
Where the rules leave a payment open, Vero, Transformance’s AI agent, investigates from Customer 360 and proposes a match with its evidence; a person approves. What the platform reads and writes in production is in the ERP data guide.
Takeaway: ask for the data in week 0; the date is set by your side of the project.
What is the minimum for a proof of value, and what do you add for rollout?
A proof of value runs on one entity with read-only ERP access; the rollout adds every entity, write access for postings, and the rules and approvers that govern them.
A proof of value is a time-boxed test on one entity’s live data that ends in a go/no-go decision against criteria agreed at the start (how long AR automation implementation takes).
With Transformance, the ERP stays read-only during testing, and write access starts at rollout. Our times, side by side: the ERP connection typically takes 2-3 days for production ERPs, and your IT team may be involved; a proof of value runs 4-5 weeks on one entity; a full rollout takes up to 4-8 weeks (Transformance customer data, 2026).
Takeaway: keep the read request and the write request separate, so the second never holds up the first.
What goes on the full data request checklist?
Fourteen items, each with its fields, period, reason and owner; the first ten, plus a draft of your posting rules, are enough to start a proof of value.
Data request checklist for an AR automation proof of value and rollout
Periods are typical requests to agree per entity, not a Transformance minimum. For item 10, write down how you count a match rate today (auto-match rate definitions).
Six steps before anyone exports a file:
- Fix one key date and one entity.
- Tie the open items list to the control account at that date.
- Export the answer key for the history period.
- Collect the worst remittances first.
- Write down the posting rules; name the approver and exception owner.
- Grant read access; credentials go into a secure slot, never into an email.
Takeaway: one key date, one entity, one folder.
How do you export the open items list from your ERP?
Export the open items at one stated key date, with their reference fields, and check that the total equals the receivables control account at the same date.
Three lists that get confused. The open items list shows every uncleared item at a key date. A “customer list” means master records or balances per customer, so say which. A trial balance shows balances per ledger account.
Reference fields are the most common gap. Customers quote their own PO number, so export the reference fields with the document number, so a payment that quotes a PO number can be matched (where each ERP keeps open items).
The tie-out. The sub-ledger total must equal the receivables control account at the same key date. Usual causes of a gap: a different date on each report, payments posted in a later period, balances carried forward by hand.
Illustrative example: open items total $4,812,300, the control account $4,826,050. The $13,750 gap is one payment: the list was run for April 2, the balance for March 31. Rerun the list at March 31 and they agree.
Takeaway: an open items list that does not tie to the ledger is the first thing to fix, not the last.
Which bank statements and remittances do you need to provide?
Provide the statements of every bank account in scope for the same period as the payment history, plus remittance samples from your top payers, including the worst formats.
Bank statements. Send camt.053, MT940, BAI2 or CSV as your bank delivers them (how these files feed cash application). For history, ask your bank for its process for historical statements. For the ongoing feed, EBICS, SFTP, bank APIs, files and a mailbox are all routes Transformance can connect (how to connect bank statements).
Remittances. Collect emails, PDFs, portal downloads and EDI 820 files, including scanned and foreign-language ones. 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). Other sources: systems besides the ERP that feed AR.
The answer key. Most requests leave it out: your team’s matches for the same period. Most of it sits in the clearing documents of item 2; add what the ERP does not hold, such as on-account cash resolved by hand. The test is measured against it (how to test AR automation before go-live).
The mailbox. If remittances arrive by email, the mailbox owner grants consent. Vero connects to the shared AR inbox, classifies emails by intent and sends routine replies within rules you set; the rest goes to a person (AI triage of a shared AR inbox).
Takeaway: send the ugly remittances first.
Which decisions and rules count as data?
Your posting rules and roles count as data: tolerances, write-off limits, reason codes, accounts for differences, discount treatment, and who approves postings and owns exceptions.
Eight decisions belong in the request, each with an owner:
- Payment-difference tolerance and write-off limit (controller).
- Reason codes and accounts for differences, bank charges and currency (controller).
- Early-payment discount treatment (controller).
- Short payments and deductions: who works them (deductions lead).
- Unapplied and on-account policy (AR lead).
- Posting approver per entity (finance sponsor).
- Exception owner for payments the rules leave open (AR lead).
- Approval thresholds by amount, entity and customer (controller and finance sponsor).
A correct match can still fail at posting: the ERP rejects a write into a locked period, above a tolerance or against a blocked item.
In Transformance, administrators configure these rules and finance users approve. The approval model has four levels (read, recommend, execute, post), with a person signing every ERP posting (approval thresholds for AI agents), and the audit log records who approved what.
Takeaway: if nobody can answer who approves a $4,000 difference (an illustrative amount), the data request is not finished.
How do you hand over data safely?
Grant read access first, send only the fields needed, keep data in your own region, and enter credentials into a secure slot, never into an email.
- Read first. The ERP stays read-only during testing; write access is a separate request at rollout.
- Only listed fields. The customer master carries bank details and contacts: name an owner for the extract and leave out unlisted fields.
- Your region. Customer data is hosted in your own region; VPC deployment is available (data in your region).
- Access and records. Users sign in via SSO/SAML, role-based access control decides who sees what, and a full audit trail records every action.
- No training. No customer data is used to train models; Transformance is GDPR compliant.
- Credentials. They go into a secure slot in the onboarding hub, with IT in the loop, and are never sent by email.
- Security review. Start it at contract signature (what IT needs to do).
Takeaway: credentials never travel by email.
How does Transformance collect this data in onboarding?
Transformance runs onboarding as one shared project in its onboarding hub: prefilled questionnaires, data requests with templates and instant file checks, balance and bank statement checks, and guided connection setup with your IT team.
- One shared project: every request shows whose turn it is.
- Prefilled questionnaires: your team confirms what is known instead of retyping it.
- Instant checks: each upload is checked for completeness, format and coverage on arrival; you see the result right away and can check again after a fix.
- Balance checks: balances and bank statements are reconciled so nothing is lost between your ERP and the platform.
- Guided connections: ERP, bank and mailbox connections are set up step by step with your IT team.
- Integration agents: they read your system documentation and setup answers, propose field mappings, draft workflows, run the test plan and report (how AI agents build and test an ERP integration).
Transformance builds, runs, monitors and fixes the connections; you approve access and production changes, and a person approves everything that reaches you or production. A standard hypercare period, extra support right after go-live, follows go-live.
Takeaway: a gap shows up on the day of the upload, not at the go/no-go.
What if the data is not clean?
Start anyway on one entity, log what the checks find, and first fix the causes that block matching: duplicate customers, missing payer bank accounts and empty reference fields.
Transformance flags bad master data, such as missing payer links, wrong bank details and duplicates, and proposes fixes; where you have agreed to write-back, approved fixes go to the ERP, and a person approves each one. See master data cleanup before cash application and how to clear an unapplied cash backlog.
Takeaway: data quality is a finding of the proof of value, not a reason to delay it.
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 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: one key date, one entity, named owners
A working data request names the file, fields, period and owner of each item, ties open items to the ledger, includes the answer key and writes down the posting decisions. Book a Call to set up the checklist for your ERP and first entity.
Key terms
- Cash application: matching payments to the invoices they pay.
- Sub-ledger: the item-level receivables record that the control account totals.
- Remittance advice: the customer’s notice of which invoices a payment covers.
- Bank reconciliation: checking the ledger’s cash against the bank statement.
- Master data management: keeping customer records correct and unique.
- On-account cash: a payment posted to the account but not to an invoice.
Related guides
- Which ERP systems does Transformance integrate with?
- How do you test AR automation before go-live?
- How do you connect bank statements to cash application?
- What master data cleanup comes before automating cash application?
- What does IT need to do when you roll out AR automation?
- How long does AR automation implementation take?
- What is the ROI of accounts receivable automation?
Frequently Asked Questions
What data does an AR automation vendor need to start?
Six data sets: open items at a key date, the customer master, bank statements, sample remittances, your team’s matches for a past period, and your posting rules.
What is the difference between an open items list, a customer list and a trial balance?
An open items list shows uncleared items at a key date and ties to the receivables control account; a customer list means master data or balances, so say which; a trial balance shows balances per ledger account.
Which ERPs can you take the data from, and what if ours has no API?
Transformance runs in production with customers on SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 Finance & Operations and Business Central and Odoo, and supports Oracle and Infor. If a system has an API, a database, a file drop or a mailbox, it can be connected (custom or legacy ERPs).
Do we need to share data for all entities and every payment?
No. A proof of value runs on one entity; the rollout adds the rest. Transformance works for companies from under 1,000 to over 100,000 payments a month, including multi-entity groups.
How long do the connection, the proof of value and the rollout take?
The ERP connection typically takes 2-3 days for production ERPs, 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 (Transformance customer data, 2026).
Can you work with personal data in a test?
Yes, under your data-protection rules: data is hosted in your region, no customer data is used to train models, and you decide which fields to send.
What does it cost to get started?
It depends on scope and the number of entities; there is no standard figure. Book a Call to scope your first entity.
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.




