Key Takeaways
- Vero, Transformance’s AI agent, reads the remittance behind each payment and proposes which open invoices in ByDesign it clears; ClearMatch auto-matches 95% of payments (Transformance customer data, 2026), and a person approves every posting.
- ByDesign already imports bank statements, creates payment allocations, holds unreferenced receipts as payments on account and runs dunning from a dunning strategy (SAP documentation, 2026).
- The manual time sits around those functions: one transfer for many invoices, the remittance that arrives a day later, cash discounts and short pays that need a reason, and the follow-up behind each dunning letter.
- Transformance connects to SAP Business ByDesign through its integrations hub; rollout takes up to 4-8 weeks (Transformance customer data, 2026), and your IT team may be involved.
- Nothing posts to ByDesign without human sign-off, within approval thresholds by amount, entity and customer.
In This Article
- Key Takeaways
- How can AI agents help SAP Business ByDesign teams automate AR?
- What does SAP Business ByDesign already do in order-to-cash and AR?
- Where do AR teams on ByDesign spend manual time?
- Which AR tasks do AI agents take on for ByDesign teams?
- How does data flow between ByDesign and Transformance?
- How does onboarding work for a ByDesign team?
- Who is this a fit for, and what does a day look like?
How can AI agents help SAP Business ByDesign teams automate AR?
Agents like Transformance’s Vero take on the work around each payment: reading remittances, proposing matches, prioritizing AR collections and sorting deductions. ByDesign stays the system of record; a person approves.
AR task by AR task: what ByDesign does, what agents add, who approves
ByDesign column: SAP documentation, accessed November 6, 2026 (sources in this section and the next). Transformance figures: 24 hours from Transformance customer data, 2026; 90-95% forecast accuracy from Transformance platform data, 2026.
What payment allocation means. Payment allocation in ByDesign is the step that assigns an incoming payment or bank statement line to the customer, invoices or other items it settles. Agents prepare the allocation proposal; a person approves it.
How SAP positions ByDesign. SAP describes Business ByDesign as a single cloud ERP for fast-growing midsize businesses, with pre-built processes from finance and sales to product management and purchasing (SAP, 2026). Its features page also covers running operations across several legal entities, currencies and accounting principles (SAP, 2026). ByDesign is its own product with its own objects, distinct from SAP S/4HANA and SAP Business One, which has its own page.
How Transformance connects. Transformance connects to SAP Business ByDesign through its integrations hub (all ERPs we connect to). ByDesign already records the payments and runs the dunning cycle; this page is about what AR teams add on top.
Takeaway: ByDesign keeps the books and the AR functions; agents take on the reading, matching and chasing around them.
What does SAP Business ByDesign already do in order-to-cash and AR?
ByDesign imports electronic bank statements, creates payment allocations from them, clears payments on account by a clearing strategy and runs dunning cycles from a dunning strategy.
As SAP documents it (all sources accessed November 6, 2026):
- Bank statements. The electronic bank statement function posts incoming and outgoing payment items automatically, for cash allocation and reconciliation, and updates the cash position (SAP Help Portal, ByDesign 2408 Integration Scenarios).
- Payment allocation. Once a bank statement is entered and posted, payment allocations are created, reachable from the statement or in the Payment Management work center. An allocation posts when the open amount is zero; differences can go to a payment on account, bank charges and interest, or another allocation (SAP KBA 1739844).
- Receipts without a reference. A transfer with no document reference and no matching rule for analyzing memo lines can be allocated to the customer as a payment on account, for example by its IBAN. Whether the on-account clearing then posts automatically depends on the business partner’s clearing strategy; “Create Manual Clearing Task If Overpaid” (or “If Underpaid”) raises a manual task instead (SAP KBA 3578582).
- Payment advices. A payment advice recorded in ByDesign is allocated automatically when its advice ID reaches the bank statement line unchanged (SAP KBA 2373026).
- Dunning. Dunning strategies are set in Business Configuration and assigned to companies or customers. Dunning runs are scheduled under Periodic Tasks in the Receivables work center, and proposals appear in the Dunning view. For a customer with a dunning block (reason and expiry date in the financial data), proposals stay blocked for release (SAP KBA 2034715). Selected dunnings can be released in bulk with Execute Dunning in Background (SAP KBA 2721471), and the dunning letter can go straight from ByDesign to the customer by email.
- Interfaces. SAP lists standards-based web services and file exchange, with scenarios for bank statements, bank payment advices, importing remittance advices, payment files, a lockbox file upload for US checks, inbound journal entries, business partner master data and OData APIs for reports and business objects (SAP Help Portal, ByDesign 2408 Integration Scenarios).
Takeaway: ByDesign already covers the statement, allocation, clearing and dunning steps; agents build on them rather than replace any of them.
Where do AR teams on ByDesign spend manual time?
Manual time collects around the payment: working out which invoices a transfer pays, chasing the remittance, resolving cash discounts and short pays, and following up each dunning letter.
This is the same AR work every ERP team has. On ByDesign it shows up in five places.
One transfer, many invoices. ACH carried 41% of US B2B payments by count in 2024, up from 25% in 2015, while checks fell from 32% to 13% (Federal Reserve Bank of Cleveland, 2026; US). One electronic payment often settles several invoices, and only the remittance says which. It tends to arrive after the cash, as an email, PDF or portal export, and until then the amount waits on account (where remittance advice comes from, matching a payment with no reference).
Cash discounts and short pays. When a customer takes the early-payment discount after the window, or deducts for a pricing difference, the payment no longer equals the invoice less the discount. The gap needs a reason and evidence before it posts (automating partial payments and deductions).
Retail customers. A food, beverage or consumer goods business selling to grocery and drugstore chains sees debit notes, pricing deductions and compliance fines, and checking them takes longer than the matching (food and beverage deductions, retailer debit notes, OTIF and compliance fines, grocery order-to-cash, reason codes).
Behind the letter. The dunning run creates proposals from your dunning strategy. The work around it is deciding whom to call first, recording promises to pay and pausing reminders while a dispute is open.
The group subsidiary. If your ByDesign team works in a subsidiary, the parent often wants the numbers on the group calendar while the local team is lean (order-to-cash across legal entities).
Takeaway: the manual work sits where documents from outside ByDesign, remittances, debit notes and customer replies, have to be read and judged.
Which AR tasks do AI agents take on for ByDesign teams?
Agents take on four jobs: cash application (ClearMatch), AR collections (CollectPulse), deductions (ClaimIQ) and cash forecasting (CashPulse), all working from a Customer 360 view of each customer.
Cash application. DocSense reads remittances from email, PDF, portal or EDI with over 97% extraction accuracy across 100+ document types and 170+ languages, with no template set-up (Transformance platform data, 2026). ClearMatch auto-matches 95% of payments, runs end to end in under 8 minutes and validates 100% of postings; nothing posts without human sign-off (Transformance customer data, 2026). See how AI reads remittance advice and ClearMatch.
Exceptions. When a payment does not match, Vero investigates from Customer 360, its working memory for each customer (payment history, open items, past deductions), fetches internal and external information and proposes a match with the evidence; a person approves (clearing an unapplied cash backlog).
AR collections. CollectPulse actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams, and Vero handles 60-80% of routine touches. DSO comes down 8-12 days on average (Transformance customer data, 2026). The AI calling agent makes 15-20 calls an hour in 70+ languages, identifies itself as AI at the start of every call, and captures 3x more promises to pay than manual work (how to prioritize AR collections with AI, CollectPulse).
Deductions. ClaimIQ identifies deductions with 97% accuracy (Transformance platform data, 2026), in under 15 seconds each against 45 minutes manually, and sorts them into six categories (ClaimIQ).
Cash forecasting. CashPulse reaches 90-95% forecast accuracy out to 90 days (Transformance platform data, 2026), and the first 13-week forecast is ready in 2-4 weeks (Transformance customer data, 2026).
Vero also runs in Microsoft Teams, where many AR teams already work together.
Takeaway: start with cash application alone, or run all four jobs on the same ByDesign connection.
How does data flow between ByDesign and Transformance?
Transformance reads customer data, open items, invoices, journal entries, bank statements and remittances, and writes approved clearing postings, journal entries and reversals back to ByDesign.
What is read and written. Reads cover customer master data, open items, invoices, journal entries, bank statements and remittances; writes cover clearing postings, journal entries and ERP updates, including reversals, after a person approves (the ERP field map).
How ByDesign exposes data. In SAP’s documentation, ByDesign offers web services, OData APIs and file exchange (listed above). That describes ByDesign, not which route Transformance uses; the route follows your environment. The connection is scoped on ByDesign’s own objects, not from an SAP S/4HANA template (how external systems post payments and clear open items).
Routes. The integrations hub connects through an API, files, a database, a mailbox, or Transformance’s own agent in your data center, which only connects outward. The route is agreed with your ByDesign team. If your group runs several ByDesign companies, name each one when you scope the rollout.
Control. Transformance runs a 4-level approval model (read, recommend, execute, post) with a human in the loop for every ERP posting. Thresholds are set by amount, entity and customer; administrators configure the rules and finance users approve. The audit log stores the timestamp, what the system did, what the user did, who approved, the input and the confidence (approval thresholds for AI agents).
Data. Data is hosted in your region, VPC deployment in your own cloud is available, sign-in runs through SSO/SAML with role-based access control, and no customer data is used to train models (how AI agents access ERP data safely).
Takeaway: ByDesign keeps the open items and the postings; Transformance keeps the evidence, the approvals and the log.
How does onboarding work for a ByDesign team?
Rollout takes up to 4-8 weeks and your IT team may be involved; a proof of value runs 4-5 weeks on one entity (Transformance customer data, 2026).
The onboarding hub and the integrations hub follow one standardized process: discover, map, build, test, schedule, monitor. A person approves every change that reaches ByDesign or production.
What your team brings:
- a ByDesign contact, and IT for the route;
- bank statements, or access to them, for each bank account in scope;
- the mailboxes and portals where remittances arrive;
- the dunning strategies you use today;
- the approval thresholds finance wants, per entity.
Data access, the security review and the approval rules shape the timeline more than the connection does (how long AR automation implementation takes).
Takeaway: line up the contacts, bank data, mailboxes and thresholds before kickoff, and the rollout follows the standard steps.
Who is this a fit for, and what does a day look like?
SAP lists professional services, manufacturing and wholesale distribution as industries with dedicated ByDesign functionality; this page is written for AR teams in group subsidiaries and wholesale.
SAP shows that functionality on the ByDesign features page (SAP, 2026); cash application in wholesale distribution covers the wholesale process on any ERP.
From a payment on account to cleared invoices in 4 steps:
- The payment is allocated to the customer in ByDesign as a payment on account; depending on the clearing strategy, a manual clearing task opens.
- Transformance reads the remittance and proposes, with the evidence, which invoices the payment clears and how to treat the discount and the deduction.
- A person approves the proposal within the thresholds finance has set.
- The approved clearing posts to ByDesign; the deduction goes to its owner as a dispute case.
Illustrative example: a foodservice distributor. Names and amounts are fictional.
The US distribution subsidiary of a foodservice group receives an ACH payment of USD 61,480.00 with a truncated reference that matches no invoice. The AR specialist allocates it to the customer as a payment on account. The next morning the customer’s remittance arrives as a portal export listing nine invoices totaling USD 62,550.00:
- five invoices of USD 8,600.00, 7,900.00, 6,400.00, 5,800.00 and 4,300.00, together USD 33,000.00, paid with a 2% early-payment discount of USD 660.00;
- four invoices of USD 9,200.00, 7,750.00, 6,180.00 and 6,420.00 with no discount, and a USD 410.00 pricing deduction taken on the USD 9,200.00 invoice.
DocSense reads the export. ClearMatch proposes clearing all nine invoices, with the discount as its own line. ClaimIQ identifies the USD 410.00 deduction, sorts it into a category and opens a dispute case with the invoice and the remittance line attached. The amount is above this entity’s threshold, so the AR lead approves in Microsoft Teams. ByDesign clears the invoices, and sales checks the pricing difference.
The arithmetic: 62,550 less the 660 discount and the 410 deduction gives 61,480, the amount received.
Takeaway: the payment on account is where the day starts; the remittance and one approval close it.
Who Transformance is for
- ERPs: SAP Business ByDesign and other ERPs through our integrations hub; in production with customers on SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 and Odoo; Oracle and Infor 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: ByDesign posts, agents read and propose, you approve
SAP Business ByDesign already imports bank statements, allocates payments, clears them by your clearing strategy and runs dunning. AI agents take the work around those steps: reading remittances, untangling multi-invoice payments, explaining deductions and following up overdue invoices, with a person approving every posting. Transformance works with customers across Europe, the United States and Australasia; Book a Call to scope one ByDesign company first.
Key terms
- Cash application: matching incoming payments to the open invoices they pay and posting the result.
- Remittance advice: the payer’s note that says which invoices a payment covers and why amounts differ.
- On-account cash: customer money posted to the account but not yet matched to an invoice.
- Cash discount: a discount a customer may deduct for paying within a set period.
- Dunning: the staged reminders sent as an invoice passes its due date.
Related guides
- Which ERP systems does Transformance integrate with?
- What ERP data does AR automation read and write?
- How AI reads remittance advice and matches payments
- Cash application in wholesale distribution
- How do food and beverage makers automate AR on their ERP?
- How can wholesale distributors automate AR on their ERP?
Frequently Asked Questions
Does Transformance work with SAP Business ByDesign?
Yes. Transformance connects to SAP Business ByDesign through its integrations hub. The route (API, files, database, mailbox or an on-premises agent that only connects outward) follows your environment and is agreed with your ByDesign team.
How long does it take to roll out with ByDesign?
Rollout takes up to 4-8 weeks, and your IT team may be involved; a proof of value runs 4-5 weeks on one entity (Transformance customer data, 2026).
Does a person approve what is posted to ByDesign?
Yes. Nothing posts to ByDesign without human sign-off. Approval thresholds are set by amount, entity and customer, administrators configure the rules, and finance users approve.
Is Transformance a fit for our size and payment volume?
Transformance is built for mid-market to large enterprises with 250 to 2,000+ employees, including groups with several entities, and for volumes from under 1,000 to over 100,000 payments a month.
Can we keep the ByDesign dunning run?
Yes. Agents work alongside the tools you run today, and which dunning steps move to agents is scoped with you, from cash application alone to the full order-to-cash.
What does AI for ByDesign accounts receivable cost?
It depends on scope and the number of entities, for example cash application alone or the full order-to-cash. Book a Call and we scope it with you.
Is our ByDesign data used to train models?
No customer data is used to train models. Data is hosted in your region, with VPC deployment, SSO/SAML and role-based access control available.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Oracle, NetSuite, Odoo, Infor and SAP Business One 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.
