Don't let ERP complexity delay financial transformation: 5 AR gaps to fix

Most ERPs do exactly what they're built to do: record transactions and close the books. What they were never built to do is run Accounts Receivable, the actual work of turning an invoice into cash: reviewing credit, sending and confirming invoices, chasing payment, applying cash, and resolving deductions.

None of these five processes were ever fully owned by the ERP. And if you're running more than one, through an acquisition, a regional entity, or a migration still in progress, the gap only gets wider.

Closing that gap doesn't mean waiting for a bigger ERP project. It means connecting the Accounts Receivable work that happens around whatever ERP landscape you already have: SAP, Oracle, Microsoft Dynamics, or all three at once. Here are the five places that gap shows up in Accounts Receivable, and how finance teams are already closing each one.

Credit: the decision that shapes everything after it

When review criteria shift depending on who's looking, and risk visibility has gaps, the cost doesn't stay in credit. It shows up later, as a delayed order or an account that should never have cleared.

A single governed view of risk, pulled from every ERP instance instead of reconciled by hand, lets credit teams decide with more confidence and less back-and-forth between systems. AI adds a forward-looking piece too, forecasting a customer's likely exposure days before an order is at risk of being blocked, so analysts get a window to adjust a limit or flag collections before the order actually stalls.

That's a large part of what TEC saw once credit reviews stopped depending on manual cross-checks: open account credit application turnaround dropped from 7–10 days to 3–4 days.

Read the Case Study: How TEC Streamlined Credit and Collections

Invoicing: where the cash clock actually starts

An invoice sent isn't the same as one received and confirmed, and that gap is where a lot of AR friction begins. Fragmented delivery means collections inherits a relationship that's already confused, and disputes surface early over something as simple as "we never got this."

Traceability from generation to acknowledgment, regardless of which ERP the invoice came from, removes most of that friction before it ever reaches collections. It also gives every team — not just AR — the same status to work from.

Lennox EMEA felt a version of this gap directly. Running three ERPs, including SAP, their previous solution wasn't well connected to any of them, and the disconnect showed up well beyond invoicing alone. Once information was centralized across all three systems, every team working from that shared status noticed the difference:

"One of the first benefits Lennox EMEA noticed once the Esker solutions were implemented was the visibility that the unified platform brings. All information is centralized, which provides every team using the solutions to be fully equipped to promptly reply to inquiries from suppliers, customers and internal stakeholders."

Collections: turning data into a priority list

ERPs show how old a balance is. Turning that into a clear sense of who to call first, and why, is a different story. That judgment usually lives in spreadsheets and institutional memory, inconsistent by design, and gone the day an experienced collector moves on.

A shared, prioritized view, fed by every ERP a company runs, replaces that guesswork with something collectors can actually rely on, regardless of who owns the account. AI strengthens it further: predicting which invoices are genuinely at risk of late payment, and surfacing customers whose behavior is starting to shift before a balance turns into something worth escalating.

Northfleet set out to implement a collections solution that would integrate directly with their ERP rather than sit next to it. The result showed up directly in the health of their receivables: the share of balances in the current, bucket rose from 70% to over 95%, easing cashflow strain and strengthening the company's financial stability

"Implementing Esker Collections Management wasn't just about automation; it was about creating a systematic approach that scales. We're now prepared for continued growth."

TEC saw a similar shift on the collections side: DSO down by an average of 10 days, and the volume of inbound calls and emails from customers chasing status dropped from as many as 15 a day to just 1–2.

Cash application: where AI earns its keep quietly

Payment matching is still the most manual, thankless part of AR — and exactly the kind of repetitive work that's safe to hand to AI, as long as it's embedded rather than bolted on. Partial remittance details, several payment channels, and, for teams on more than one ERP, payments that need to be matched against open items sitting in different systems entirely: none of it needs to sit in a queue by default.

Centralizing that matching logic above the ERP layer means it works the same way regardless of which system the invoice or the open item lives in. AI does a lot of the reading here too: pulling data from a remittance advice, or from payment details written directly into an email thread, and using it to match automatically.

That's also where cash visibility improves fastest. Finance sees what's cleared in near real time instead of waiting for month-end and teams running this well see auto-match rates climb above 90%, with unapplied cash cut by as much as 95%.

If you're running SAP, this is worth seeing rather than reading about: watch how a prebuilt connector automates cash application inside SAP.

Deductions: when they stall, it's rarely about the claim itself

Resolving a deduction usually means pulling in sales for context and service for history. When those teams aren't working from the same facts, or are pulling data from different ERPs entirely, resolution stretches from days into weeks, and revenue leakage sits quietly in between.

A shared workflow with visible ownership, built on top of whatever ERPs are in play, is what "connected departments" looks like in practice. With the help of AI, the claim itself gets routed and classified automatically, whether it's a pricing dispute, a missing product, a promotional deduction, or a mixed claim with more than one issue, instead of waiting for someone to triage it manually. From there, finance, sales and service work the same case with the same context, and resolution speeds up because nobody's chasing information across departments.

TEC's experience with disputes reflects the same shift: once the process ran on a shared, ERP-agnostic workflow, resolution time dropped by 88%. Eagle Foods saw a comparable result from the connected-departments side specifically: open deductions cut by 80%.

The connected layer, in practice

None of these five gaps close by replacing the ERP, or by automating one step in isolation. What closes them is a single layer across the whole AR cycle: credit, invoicing, collections, cash application and deductions, all working from the same customer data, on top of SAP, Oracle, Microsoft Dynamics or any combination of them, without disturbing the systems of record underneath.

This is exactly the space Esker's Accounts Receivable solution suite was built for: one unified view of AR execution across complex, multi-system landscapes, with standardized processes, shared customer context across every team that touches AR and real-time cash visibility instead of a picture that's only accurate at month-end.

Embedded throughout that layer is Esker Synergy AI, handling the parts of the AR cycle that used to eat the most time: forecasting credit exposure, prioritizing collections, reading and matching remittance data, classifying claims. It's built into the workflow itself, not a separate tool teams have to remember to open.

Your ERP will always hold the record. That part isn't changing. What can change now is how fast the work around it turns into cash, without waiting on whatever's next for the ERP itself.

See more results like these. Explore our full library of case studies to see how other finance teams are closing these gaps today, or get in touch to talk through what this could look like for your team.

Already on the SAP S/4HANA roadmap? Migration timelines don't have to put AR modernization on hold. Get the ebook: Unlocking AI-Orchestrated Finance During the Transition to SAP S/4HANA. 

Interested in learning more ?

Contact us now to see how Esker's solutions can help your business

Get started