Key Takeaways
- Transformance’s AI agents build on Acumatica, which applies payments to open invoices, automatically if you choose, keeps an Application History and prepares dunning letters by level (Acumatica ERP help, 2026).
- Acumatica’s help says to apply open payments, prepayments and credit memos before preparing dunning letters: cash application comes first in AR collections.
- AI agents add remittance reading, matching, deductions, AR collections follow-up and cash forecasting; ClearMatch auto-matches 95% of payments (Transformance customer data, 2026).
- Transformance connects to Acumatica through its integrations hub; Acumatica stays the system of record, and a person approves every posting.
- Full rollout takes up to 4-8 weeks, a proof of value runs 4-5 weeks on one entity, and your IT team may be involved.
In This Article
- Key Takeaways
- How do AI agents build on Acumatica’s accounts receivable?
- What does Acumatica already do in accounts receivable?
- Where do AR teams on Acumatica spend manual time?
- Which AR tasks do AI agents take on for Acumatica teams?
- Why does Acumatica put payments before dunning, and how do agents help?
- How does data flow between Acumatica and Transformance?
- How does onboarding work for an Acumatica team?
- What does a worked example look like on Acumatica?
How do AI agents build on Acumatica’s accounts receivable?
Transformance’s AI agents read remittances, propose how each payment is applied, work deductions and follow up on overdue invoices, while Acumatica keeps the books and a person approves every posting.
AR task by AR task: what Acumatica does, what agents add, who approves
Acumatica terms are taken from Acumatica’s site and help portal (accessed October 2026); form names and options vary by release and configuration.
Transformance connects to and works with Acumatica through its integrations hub (which ERP systems Transformance integrates with); this page is about what Acumatica teams add on top.
Takeaway: Acumatica keeps the books and the AR functions; agents prepare the work around them, and a person signs off.
What does Acumatica already do in accounts receivable?
Acumatica records payments and applies them to open invoices, manually or automatically, keeps each application in the payment’s history, and prepares dunning letters by level for overdue documents.
On the product page. Acumatica’s accounts receivable page lists “Generate and deliver invoices and statements”, “Apply payments automatically to open invoices” and “Monitor customer aging and maintain complete audit trails” among its AR functions (Acumatica, 2026).
Payments and Applications. A payment or prepayment is recorded on the Payments and Applications form and applied, fully or partially, to open documents on the Documents to Apply tab; the Available Balance box shows what is not yet applied. Released application records move to the Application History tab, “where you can view (but not modify) the list of the applied documents”. If a released application was wrong, Reverse Application on that tab reopens the payment and the invoice for a new application (Acumatica ERP help).
Automatic application. Per customer, the Auto-Apply Payments check box makes the system apply each newly released payment “to any outstanding documents of this customer”. In bulk, the Auto-Apply Payments process runs for selected statement cycles, sorts open invoices, debit memos and overdue charges “in ascending order by due date” and applies open payments one by one. Payments linked to a sales order or on hold are left out (Acumatica ERP help).
Dunning letters. With dunning by document, a first-level letter is generated once a document’s days past due exceed the level’s Days Past Due, and each released letter raises the document’s level by one; the last level carries a Final Reminder check box. Letters are Draft or Released, can carry a dunning fee, are printed or emailed, and can be prepared on an automation schedule. A person can exclude a document from dunning with Revoke (Acumatica ERP help).
Takeaway: Acumatica already applies, records and reminds; agents work alongside those functions.
Where do AR teams on Acumatica spend manual time?
The manual hours sit around the payment: remittances that arrive by email or PDF, payments that name particular invoices, short pays that need a reason, and follow-up behind every letter.
This is the same AR work in every ERP:
- Remittances outside the ERP. Payment advice arrives by email, PDF or customer portal, and someone has to read it first (where remittances come from).
- One payment, 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, September 2026, US). One payment often settles several invoices the bank line does not name.
- No usable reference. A payment that says only “PAYMENT” waits for someone to find the customer and the invoices (matching a payment with no reference).
- Short pays. A freight, damage, pricing or promotion deduction needs a reason before it is settled or disputed (partial payments and deductions).
- Behind the letter. The work is choosing whom to call first, logging promises to pay and handling the disputes letters bring back.
Industry patterns add to this: freight and damage deductions for distributors (wholesale distribution), down payments and milestones for machinery makers (machinery receivables).
The Hackett Group’s Bryan DeGraw said “a surprising number of organizations are accepting automation rates below 40%, taking up to three days to post payments, and carrying up to 6% of unapplied cash” (The Hackett Group, 2025; no 2026 figure found). More on clearing an unapplied cash backlog.
Takeaway: the manual hours sit in the documents and the follow-up around the ERP.
Which AR tasks do AI agents take on for Acumatica teams?
Agents take on five jobs on a Customer 360 view of each customer: remittance reading, cash application, deductions, AR collections and cash forecasting, and a person approves every posting.
- Remittance reading. DocSense reads remittances in any format with over 97% extraction accuracy across 100+ document types and 170+ languages, with no templates to configure (how AI reads remittance advice).
- Cash application. 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; ClearMatch).
- Deductions. ClaimIQ identifies deductions with 97% accuracy in under 15 seconds each (manual: 45 minutes), sorts them into six categories and auto-validates about 40% of trade deductions by rules (ClaimIQ).
- AR collections. CollectPulse actions 100% of overdue invoices within 24 hours (manual teams: 30-40%), Vero handles 60-80% of routine touches, and DSO comes down 8-12 days on average. 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 follow-up (CollectPulse).
- Cash forecasting. CashPulse reaches 90-95% forecast accuracy out to 90 days, and the first 13-week forecast is ready in 2-4 weeks.
When a payment does not match, Vero investigates the exception from Customer 360, its working memory per customer, and fetches internal and external information to find more matches. It proposes the application with the evidence, and a person approves.
Takeaway: agents do the reading, matching, chasing and sorting; people keep the decisions.
Why does Acumatica put payments before dunning, and how do agents help?
Acumatica’s help says to apply open payments, prepayments and credit memos before preparing dunning letters; agents keep that order for payments that arrive without a clean reference.
The dunning help page says: “Before you start preparing dunning letters, make sure that customers do not have open payments, prepayments, and credit memos that can be applied against outstanding documents” (Acumatica ERP help). Acumatica gives the same advice for statements: apply open payment documents first “to avoid incorrect calculation of aged balances”, and a statement cycle can be set to warn you when open payments remain (Acumatica ERP help).
The reason: an invoice that is paid but still open because its payment is unapplied looks overdue to the dunning run, and the customer gets a reminder for money already sent.
Acumatica’s automatic application follows a rule: open documents by due date. When the remittance names other invoices, or the payment carries no reference, the agent proposes the application the customer meant, and a person approves it before dunning runs (how external systems clear open items).
A cleaner dunning day on Acumatica in 5 steps
- Payments arrive. Bank lines reach the account, and remittances land in the shared mailbox or a customer portal.
- Agents propose. Agents read the remittances and propose how each payment and prepayment is applied; payments with no reference are investigated from Customer 360.
- A person approves. Proposals are approved within thresholds by amount, entity and customer, and the approved applications are written to Acumatica.
- Acumatica prepares the letters. Dunning letters are prepared for the documents that are genuinely overdue, as Acumatica’s own help sequence describes.
- Follow-up runs on what is open. Prioritised contacts, calls and promise-to-pay tracking, with a person handling escalations (how AI automates AR collections; designing a B2B dunning cadence).
Takeaway: apply first, then dun; agents make that order hold for the payments that need a remittance to place.
How does data flow between Acumatica and Transformance?
Transformance connects to Acumatica through its integrations hub, reads customer, invoice, open-item, bank and remittance data, and writes clearing postings and journal entries back once a person approves them.
What moves. Transformance reads customer master data, open items, invoices, journal entries, bank statements and remittances, and writes clearing postings, journal entries and ERP updates, including reversals, after a person approves (what AR automation reads and writes).
Which route. The integrations hub connects by API, files, database, mailbox or Transformance’s own on-premises agent, which only connects outward. The method follows your Acumatica environment and is agreed in the connection step, and your IT team may be involved (custom ERP connections). How your Acumatica companies and branches are read is agreed in the same step.
Who controls postings. A 4-level approval model (read, recommend, execute, post) keeps 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).
Where data lives. Data stays 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: Acumatica stays the system of record; Transformance writes only what a person approved, and logs why.
How does onboarding work for an Acumatica team?
Onboarding runs as one shared project: the integrations hub builds and tests the Acumatica connection in a standardized process, and full rollout takes up to 4-8 weeks.
The integration process has six steps: discover, map, build, test, schedule and monitor. AI agents in the integrations hub run those steps, from mapping your Acumatica data to testing the connection on your own transactions and watching each scheduled run, and a person approves every change that reaches your Acumatica system or production (the agent-run integration platform).
The onboarding hub keeps the plan, test scenarios, parallel run and sign-offs in one place for both teams, through hypercare. A proof of value runs 4-5 weeks on one entity.
What your team brings:
- A contact who owns your Acumatica AR setup and knows its release.
- IT for the connection route and the security review.
- Bank statements, or access to them, for each bank account in scope.
- The mailboxes and portals where remittances arrive.
- Your auto-apply and dunning settings, and the approval thresholds finance wants.
Data access, the security review and the approval rules shape the timeline most (what IT does in a rollout; implementation time).
Takeaway: a standardized process, one entity first, and a person’s approval on every change.
What does a worked example look like on Acumatica?
A common AR case in distribution and manufacturing, two of the industries Acumatica serves, is a payment whose remittance names specific invoices; the example below shows how agents and a person handle it.
Acumatica’s industry navigation lists Distribution, Manufacturing and Professional Services among many industries, including Lumber and Building Materials (Acumatica, 2026).
Illustrative example: a building-products distributor on Acumatica. Names and amounts are fictional.
A customer has four open invoices: INV-1001 for $7,800.00 (due August 15, disputed over damaged goods), INV-1014 for $12,300.00 (due September 2), INV-1022 for $9,150.00 (due September 20) and INV-1030 for $6,400.00 (due November 20). A payment of $21,450.00 arrives with the bank text “PAYMENT”, and the customer’s remittance email names INV-1014 and INV-1022.
- By due date. Applied oldest due date first, the payment would close INV-1001 and INV-1014 and leave INV-1022 open at $7,800.00 for the next dunning run.
- The remittance. DocSense reads the email and pairs it with the bank line.
- The proposal. ClearMatch proposes applying $12,300.00 to INV-1014 and $9,150.00 to INV-1022, with the remittance as evidence; Vero notes that INV-1001 is the disputed invoice.
- The approval. The AR lead approves, and the application is written to Acumatica.
- The dunning run. INV-1014 and INV-1022 are closed. INV-1001 stays open for the dispute, and the AR lead decides whether to exclude it from dunning while it is resolved; INV-1030 is not yet due.
The arithmetic: $12,300.00 + $9,150.00 = $21,450.00; by due date, $21,450.00 less $20,100.00 leaves $1,350.00 for INV-1022, so $7,800.00 stays open.
Takeaway: the rule and the remittance can point at different invoices; the agent brings the remittance, and a person decides.
Who Transformance is for
- ERPs: Acumatica and other ERPs through our integrations hub.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- 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: payments first, then dunning, with agents doing the reading
Acumatica applies payments, keeps their history and prepares dunning letters by level. AI agents add the reading, matching, deductions and follow-up around those functions, so the payments-first order holds even when a remittance names other invoices.
Nothing posts without a person’s approval. Start with cash application on one entity; Book a Call to plan it with your Acumatica team.
Key terms
- Cash application: matching incoming payments to the open invoices they pay and clearing them in the ERP.
- Remittance advice: the payer’s note of which invoices a payment covers and why amounts differ.
- On-account cash: money received but not yet applied to a specific invoice.
- Short pay: a payment below the invoiced amount, often because the customer took a deduction.
- Dunning: the staged reminders sent as an invoice passes its due date.
- Payment reconciliation: checking that payments and the items they settle agree.
Related guides
- Which ERP systems does Transformance integrate with?
- What AR automation reads from and writes to the ERP
- Who approves what when an AI agent works in your ERP
- How onboarding to Transformance works, kickoff to go-live
- What does IT need to do when you roll out AR automation?
- Wholesale distribution: cash application and deductions
Frequently Asked Questions
Does Transformance work with Acumatica?
Yes. Transformance connects to Acumatica through its integrations hub, reads AR data and writes approved postings back; Acumatica stays the system of record. The route follows your environment and is agreed in the connection step.
Which Acumatica release, edition or hosting does it need?
The connection method follows your Acumatica environment, so bring your release, edition and hosting to the first call; the details are agreed in the connection step.
How is this different from Acumatica’s auto-apply payments?
Acumatica’s automatic application works through open documents by due date. Agents add remittance reading and investigation for payments that name specific invoices or carry no reference, and a person approves each application.
How long does implementation take on Acumatica?
Full 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; the connection is one step inside that plan.
Is Transformance a fit for our size, entities 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.
Does Transformance post to Acumatica without approval?
No. Every clearing posting, journal entry and reversal is validated and approved by a person within your thresholds before it reaches Acumatica, and the audit trail records who approved it.
What does AI for Acumatica 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 for your Acumatica setup.
Acumatica is a trademark of Acumatica, Inc. Transformance is not affiliated with or endorsed by Acumatica, Inc.
