Accounts receivable is often the most underestimated source of financial risk in a business. Invoices go out, payment delays creep up, DSO quietly climbs, and working capital tightens — all before anyone pulls the alarm.
In 2025, the average DSO for mid-market companies in Europe reached 65 days, with a peak above 70 days in August. According to Coface’s 2025 European Payment Survey, 86% of businesses reported experiencing late payments that year, and 39% described their cash position as “significantly impacted.” The average payment delay reached 14.1 days in the first half of 2025 — a record high across European markets, according to Altares.
The ERP sits at the center of the solution. Not because it can change customer payment behavior on its own, but because it already holds every piece of data you need: invoices, due dates, received payments, sent reminders, outstanding balances by customer. The question is whether you are actually using that potential.
Accounts Receivable and DSO: The Underestimated Financial Health Barometer
The Real Cost of One Extra DSO Day
DSO (Days Sales Outstanding) measures the average time between issuing an invoice and collecting payment. The base formula:
DSO = (Accounts Receivable Balance / Net Revenue) × Number of Days in the Period
To calculate the financial impact of one additional DSO day:
Cost of 1 DSO Day = Annual Net Revenue / 365 × Financing Rate
For a mid-market company with €20M in revenue and a 4% financing cost: one extra DSO day equals roughly €2,200 in annual financing charges. Over 10 additional days of delay, that is €22,000 in pure financing cost — before factoring in default risk. At the 14-day average payment delay observed across European markets in 2025, the annual excess financing cost for that same company exceeds €30,000.
What Your ERP Already Knows
The aged receivables report is the most consulted report in any AR (Accounts Receivable) module. But it is often misused: pulled out at the end of a treasury meeting, skimmed quickly, and filed away until next month.
Yet your ERP records everything:
- Invoice issue dates and due dates calculated per the negotiated payment terms
- Actual payment dates and variances against the due date
- Reminders already sent, if the dunning module is configured
- Open bank reconciliation items and disputes logged per invoice
This data allows real-time calculation of DSO by customer, segment, sales rep, or region. The problem is not a lack of data — it is the absence of a workflow that turns data into action.
The Risk Reality in 2025
The pressure on corporate cash flow is documented and worsening. According to the Coface 2025 survey, 42% of reported late payments are directly linked to customers’ own financial difficulties — meaning that managing credit risk upfront, before extending payment terms, is as important a line of defense as chasing invoices after the due date. Billions in trade payables are at elevated risk across European markets, with downstream employment impacts in the hundreds of thousands.
The legal maximum payment term for B2B transactions across the EU is generally 60 days from invoice date, with individual member states setting stricter rules in certain sectors. A DSO of 65 days already exceeds the contractual limit for a large share of the customer base.
Configuring the Accounts Receivable Module in Your ERP
Payment Terms and Due Dates: The Foundation
Configuring payment terms is the most neglected step in any ERP implementation. Teams import the existing customer file, set a default delay, and move on.
In practice, payment terms must be configured at the individual customer level (or by segment) and must exactly reflect what is in the contract:
- Net 30: payment due 30 days from invoice date
- Net 30 EOM: 30 days plus time to end of calendar month
- Net 60: the standard maximum B2B term in most EU jurisdictions
- Cash on first order: for new customers with an unknown risk profile
The ERP must automatically calculate the due date at invoice issuance and trigger an alert at D-5 if payment has not yet been received. This configuration takes half a day. The ROI is immediate.
Risk Classes and Credit Limits
Credit management starts before the sale — not after the unpaid invoice. In your ERP, every customer must have a credit limit (authorized outstanding balance) and a risk class.
Internal scoring: based on behavioral history in your ERP. A customer who consistently pays at 45 days against a 30-day contractual term deserves a different risk class than one who pays on time. The ERP can calculate this score automatically if payment terms are properly filled in.
External scoring: leading ERP vendors offer connectors to credit rating agencies — Coface, Dun & Bradstreet, Creditsafe, Experian. The goal is to enrich the customer record with an independent rating that complements your own payment history.
Automatic order blocking: when the outstanding balance exceeds the authorized credit limit, the next order is blocked in the ERP until the credit manager approves it. This workflow is native in SAP, Oracle, and Dynamics 365. It is often activated but rarely calibrated correctly due to poor initial configuration.
Customer Data to Prioritize Enriching
The quality of credit management depends directly on the quality of the customer master data in the ERP. Critical fields that are often missing:
- Company registration number (VAT ID, EIN, or equivalent): essential for connecting to external scoring services
- Separate billing email from the commercial contact: the invoice must reach the customer’s accounting department, not the sales contact who signed the contract
- Accounts payable contact at the customer: name and direct line. Often missing on 60–70% of customer records — yet this is the person who actually releases payments
- Validated credit limit: not a default value inherited from the historical file, but a limit approved by the credit manager based on a recent analysis
Automating Dunning: The 5-Level Workflow
Dunning — the systematic follow-up on overdue invoices — is the most ROI-positive automation your ERP can deploy. The principle: at each overdue threshold, a defined action triggers automatically. Here is the standard 5-level structure to configure.
Level 1 — Day 0: Invoice Delivery Confirmation
When the invoice is issued, an automated email goes out with the PDF attached and a summary of payment terms. Objective: ensure the customer received the invoice and knows the due date. Low friction, but highly effective at eliminating the “we never received the invoice” excuse.
Level 2 — 5 Days Overdue: Friendly Reminder
Automated personalized email with a summary of the invoice, amount, missed due date, and ideally a link to an online payment portal. Tone: courteous, no mention of penalties. For major accounts, this level can be replaced by a phone call from the credit manager.
Level 3 — 15 Days Overdue: Formal Notice
Firmer email with a reference to contractual terms and a mention of applicable late payment penalties. If the ERP is connected to a certified electronic registered mail service (DocuSign, Maileva, or equivalent), this level can trigger an automatic send.
Level 4 — 30 Days Overdue: Formal Demand
Formal email explicitly stating the penalties that apply. In most EU jurisdictions, statutory late payment interest applies automatically under commercial law — typically the ECB reference rate plus 8 to 10 percentage points, plus a fixed recovery fee. At this stage, the tone shifts to collections mode.
Level 5 — 45 Days Overdue: Legal Transfer
Automatic transfer of the file to the legal team or a collections agency. In the ERP, the invoice is reclassified as a doubtful receivable and can trigger an accounting provision.
Exception Rules to Configure Without Fail
Automation without exceptions means triggering dunning at the worst possible moment. Critical rules:
- Suspend on open dispute: the ERP must be synchronized with the CRM to detect active claims. Sending a payment reminder the day a customer is waiting for resolution of a delivery problem guarantees a refusal — and damages the relationship.
- Suspend for insolvency proceedings: administration, receivership — reminders become pointless and potentially illegal.
- Differentiated workflows by segment: a large enterprise does not get the same automated treatment as a small business. Most ERPs allow the creation of separate dunning workflows by customer category.
ERP Modules for Credit Management in 2026
SAP S/4HANA: Credit Management (FIN-FSCM-CR)
The market reference. Strengths: real-time dynamic scoring, native connectors to Coface and Atradius, workflow for validating blocked orders (the credit manager receives an alert and approves directly from their interface), dashboard with a consolidated view of outstanding balances. The functional depth requires serious configuration: budget 3 to 6 weeks of setup to fully exploit the module.
Microsoft Dynamics 365 Finance: Customer Credit Management
Native module in D365 F&SCM with credit limits per customer and per group, alerts at multiple thresholds (50%, 75%, 100%), configurable hierarchical escalation, and integration with the Collections module for dunning. Workflows can be extended via Power Automate for complex cases.
Sage Intacct / Sage X3: Credit Risk Management
Authorized exposure per customer, risk codes (A, B, C, D), configurable reminders with email templates, multi-criteria aged receivables. Sufficient for most mid-market companies. Primary limitation: integrating external scoring typically requires a complementary tool such as Sidetrade or Creditsafe.
Access Group / IRIS: Accounts Receivable
Well-suited to UK mid-market companies already within the Access ecosystem. Configurable reminder workflows, aging reports, and credit limit management with order-hold capability. Analytics are robust for the segment; complex external scoring integrations may require add-ons.
Odoo 17: Follow-up (Free Native Module)
Simple, configurable without development, included in the licence, suited to companies processing fewer than 200 invoices per month. Clear limitation: no external scoring integration, no behavioral prediction, dunning workflow less configurable than SAP or Dynamics.
Predictive AI and Specialized AR Tools: What Changes in 2026
Sidetrade: AI Behavioral Scoring
Sidetrade does not replace the ERP — it connects to it (SAP, Oracle, Sage, Dynamics) to enrich the AR module. Its value: predicting the probability of payment at 30, 60, and 90 days per customer, by crossing internal data (payment history in your ERP) with external signals (company news, weak sector signals, external credit scores). The credit manager prioritizes follow-up on high-risk customers before they become overdue.
Esker: Order-to-Cash Platform
Esker covers the full O2C cycle with an AI-first approach. On the AR side: outbound invoice automation, personalized dunning, and automated payment reconciliation (cash application). The last item is often the fastest ROI lever: for a company processing 500 invoices per month, moving from manual reconciliation to 85–95% automation represents 30 to 40 hours of accounting work saved each month.
Chaser and Quadient AR (formerly YayPay): SaaS Alternatives for Mid-Market
For companies whose ERP lacks a powerful AR module, SaaS tools like Chaser or Quadient AR integrate via API with most mid-market ERPs. They provide configurable dunning workflows and DSO dashboards without requiring a heavy implementation project.
AR KPIs to Track in Your ERP
An effective AR dashboard tracks at minimum these indicators:
DSO (Days Sales Outstanding): the baseline metric, to be tracked as a weekly trend and benchmarked against your sector.
Best Possible DSO: DSO calculated assuming all customers pay exactly on their contractual due date. The gap versus actual DSO indicates the improvement potential available without changing payment terms.
CEI (Collection Effectiveness Index): (Opening Balance + Invoiced − Closing Balance) / (Opening Balance + Invoiced − Current Receivables) × 100. A CEI of 100% means everything collectible was collected. Most mid-market companies sit between 80 and 95%.
Doubtful Receivables Rate: provisioned receivables as a percentage of revenue. Warning signal above 1–1.5% for standard B2B activity.
Top 10 Overdue Debtors: risk concentration view. If 3 customers represent 70% of overdue balances, the collections strategy must start with those three accounts.
Dunning Automation Rate: percentage of reminders sent automatically by the ERP versus manually. A rate below 60% signals a dunning workflow that is poorly configured or being bypassed.
Pragmatic Roadmap to Reduce DSO
If your accounts receivable is largely manual today, here is a realistic sequence:
Weeks 1 and 2: enrich the customer master data (billing email, AP contact, exact payment terms per customer). This data cleanup work conditions everything that follows.
Weeks 3 and 4: configure the 5-level dunning workflow in your ERP. Budget 2 to 3 days of configuration for an experienced implementer.
Month 2: activate credit limits and risk classes. Train sales teams on the blocked-order validation workflow.
Month 3: measure impact. Compare DSO and CEI before and after. If results are positive, consider integrating external scoring (Coface, Dun & Bradstreet, Creditsafe) or a specialized AR tool (Sidetrade, Esker).
Full configuration of the AR module in a mid-market ERP takes 4 to 6 weeks of setup. The return on investment is visible from the second month if the baseline data is clean.
To explore the broader cash flow impact, see our analysis on ERP and predictive AI for working capital optimization and our monthly ERP close checklist which integrates DSO among the key control KPIs. Download our ERP evaluation grid — 30 criteria on a 100-point scale — to benchmark AR modules across leading vendors side by side.
