Your customer placed the order. You delivered. You invoiced. And yet — the cash still isn’t in your account. In B2B, this gap between delivery and payment routinely locks up 30 to 90 days of working capital. For a mid-size company with €10M in annual revenue, each extra day of DSO represents roughly €27,000 of working capital tied up in receivables: cash you cannot invest, repay, or distribute.
The Order-to-Cash (O2C) cycle is the end-to-end process from customer order to cash receipt. The ERP is the only tool capable of orchestrating this cycle from start to finish — provided you activate the right modules and configure the right workflows. This guide shows you how.
The Order-to-Cash Cycle: 7 Steps from Order to Payment
The O2C cycle breaks down into seven sequential steps. Each one can generate delays, errors, or bottlenecks that mechanically inflate your DSO.
- Quote and commercial validation: quote creation in the CRM or ERP, approval by the sales rep, customer acceptance.
- Order entry: order recorded in the ERP, stock availability check or production capacity confirmation.
- Customer credit check: verification of the approved credit limit, automatic hold if the ceiling is exceeded.
- Fulfillment and shipping: picking, packing, delivery note generation, physical dispatch or service delivery.
- Invoicing: automatic invoice generation from the delivery note, transmission to the customer (PDF, EDI, or Peppol depending on the country).
- Collections and follow-up: tracking due dates, sending reminders, managing disputes and credit notes.
- Cash application and matching: receipt of payment, automatic reconciliation against the open invoice, closure of the receivable.
Where Does the O2C Cycle Leak Time?
In most mid-market companies, payment delays come not from the customer but from internal process failures. The most common causes:
- Late invoicing: the invoice is issued 5 to 10 days after delivery, which mechanically pushes back the due date.
- Unresolved disputes: a disputed invoice stays open until settlement — often several weeks.
- Manual reminders arriving too late: without an automated workflow, follow-up depends on a credit manager’s availability and typically lands after the due date.
- Manual cash application: incoming payments are manually matched, causing posting delays and phantom open items in the AR aging.
- No credit hold: orders are shipped to customers who already have overdue invoices, compounding exposure.
Common Bottlenecks in Mid-Market Companies
Companies running without a fully integrated ERP — or with a poorly configured one — typically lose 10 to 20 additional days versus their theoretical O2C process. The most documented bottlenecks: invoicing not automated from the delivery note, absence of a structured dunning workflow, and bank reconciliation done weekly instead of daily.
DSO: Definition, Calculation, and European Benchmarks by Industry
The DSO Formula and How to Read It in Your ERP
DSO (Days Sales Outstanding) measures the average number of days it takes to collect payment after invoicing.
Standard formula:
DSO = (Outstanding receivables at calculation date / Revenue for the period) × Number of daysWorked example: If your outstanding receivables at 30 September are €1,200,000 and your quarterly revenue is €3,000,000: DSO = (1,200,000 / 3,000,000) × 90 = 36 days.
Most mid-market ERPs (SAP Business One, Sage X3, Microsoft Dynamics 365, Access Financials, Unit4) calculate DSO automatically in the receivables management module. Configure the calculation on a rolling 90-day basis to avoid quarter-end distortions.
European Industry Benchmarks: Indicative Reference Points
Payment timelines vary significantly across industries. Based on European payment observatory data:
| Sector | Target DSO | Observed DSO |
|---|---|---|
| B2B distribution | 30–40 days | 45–55 days |
| Manufacturing / industrial | 40–50 days | 55–70 days |
| B2B services | 45–55 days | 60–80 days |
| Construction / infrastructure | 55–70 days | 75–100 days |
These gaps between target and observed DSO represent your improvement headroom. A B2B services company at 65 days actual DSO with a 15-day gap versus target has significant trapped liquidity to recover.
Regulatory note: EU Directive 2011/7/EU sets a statutory payment deadline of 30 days between businesses, with a maximum contractual term of 60 days. Late payments entitle the creditor to statutory interest plus a flat-fee compensation of €40 per unpaid invoice (UK equivalent under the Late Payment of Commercial Debts Act: £40–£100 depending on invoice value). Member states can impose stricter limits: France caps B2B payment terms at 60 calendar days or 45 days end of month.
The Working Capital Impact of High DSO
The financial cost of excessive DSO is routinely underestimated. A concrete example:
- Mid-size manufacturer: €15M annual revenue, current DSO 62 days, target DSO 45 days.
- 1 DSO day = €15,000,000 / 365 = €41,100 of working capital tied up.
- 17-day gap = €698,700 of liquidity locked in receivables.
At a short-term financing cost of 4%, this gap represents roughly €28,000 in avoidable annual interest expense — before accounting for the write-off risk on aged receivables.
According to Allianz Research’s June 2025 Working Capital Report, global working capital requirements reached 78 days in 2024 — a post-2008 record — with 44% of companies reporting DSO above 60 days. Europe recorded a deterioration of +4 days over three consecutive years.
Key ERP Modules for Automating Order-to-Cash
Automated Customer Credit Scoring
The credit check step is the most neglected in mid-market companies — yet it is the first line of defence against bad debt.
Modern ERPs support integration with third-party credit scoring APIs (Dun & Bradstreet, Creditsafe, Coface, Experian) directly within the customer master. The mechanism:
- When a new customer account is created, the system queries the API and retrieves the financial rating and recommended credit limit.
- This limit is synced into the Order Management module.
- The rating is refreshed automatically on a configurable schedule (weekly, monthly).
The benefit: credit decisions are no longer based on sales intuition but on current financial data.
Credit Limit Management and Automatic Order Holds
Automatic order holds for customers exceeding their credit limit are standard functionality in SAP S/4HANA, Sage X3, Microsoft Dynamics 365, and most mid-market ERP platforms. However, they are frequently disabled by sales teams to “avoid blocking deals.”
Best practice: configure an approval workflow rather than a hard block. The sales rep receives an alert and can submit a credit exception request to the CFO, who approves or rejects with one click from the ERP interface. Resolution time drops from several days to a few hours.
Automated Dunning Workflows
Dunning is the structured process for chasing overdue receivables. A well-configured ERP workflow automatically triggers:
- Day +1 past due: payment reminder by email (neutral tone, invoice reference and payment details).
- Day +8: first reminder (polite tone, mention of applicable late payment charges).
- Day +15: second reminder (firm tone, online payment option or instalment plan offered).
- Day +30: formal demand letter with automatic document generation.
- Day +45+: handover to external collection agency or legal escalation.
The most overlooked configuration parameter: segment dunning sequences by customer tier. A longstanding enterprise account should not receive the same Day +8 reminder as a first-time buyer. ERPs allow you to create distinct dunning profiles by customer category, sales territory, or credit risk class.
Intelligent Cash Application: Automated Payment Matching
Manual reconciliation of incoming bank transfers is one of the most time-consuming tasks in accounts receivable. Payments arrive without invoice references, with partial amounts, incomplete remittance details, or as lump-sum wires covering multiple invoices.
Modern ERPs integrate AI-powered cash application modules: the algorithm analyses bank transfer descriptions, payment history, expected amounts, and automatically suggests matching. The most advanced systems (SAP S/4HANA, Oracle Fusion Cloud, Sage Intacct) achieve automatic matching rates of 70–90%, reducing manual work from several hours per week to a handful of edge-case reviews.
Real-Time Credit Manager Dashboard
A credit manager working without a live dashboard is flying blind. The ERP receivables module must expose in real time:
- AR aging: balance by aging bucket (0–30 days, 31–60 days, 61–90 days, >90 days) by amount and invoice count.
- Exposure by customer and by sales rep: to identify risk concentration and hold sales teams accountable.
- CEI (Collection Effectiveness Index): measures the percentage of collectable receivables actually collected on time.
- Bad Debt Ratio: share of receivables written off — monitor monthly.
- Automated alerts: triggered when a customer breaches a defined exposure or aging threshold.
Without this dashboard, the credit manager spends their time extracting data. With it, they manage by exception.
Connecting a Specialist Collections Tool to Your ERP
Esker, YayPay, HighRadius: When to Go Beyond the Native Module?
ERP native collections modules cover standard requirements. But for companies with high receivables volumes (>500 open invoices per month), multiple chronically disputed customers, or dedicated credit teams, specialist solutions deliver additional value:
- Esker Order Management / AR: comprehensive document platform, structured dispute management, predictive dashboards. Reference solution for mid-market and enterprise.
- YayPay (by Quadient): AI-driven collections automation, customer payment portal, two-way ERP sync. Popular with US and UK mid-market companies using Sage, NetSuite, or Dynamics.
- HighRadius: enterprise-grade AR automation suite covering cash application, credit management, and collections. Integrates with SAP, Oracle, and major ERP platforms.
The threshold for switching to a specialist tool: when your credit manager spends more than 50% of their time managing exports, manual emails, and Excel files rather than resolving complex cases.
Integration Architecture: REST APIs and Bidirectional Sync
The connection between an ERP and a collections tool relies on three data flows:
- Export from ERP to tool: open invoices, customer exposure, payment history, billing contact details.
- Return from tool to ERP: payment promises recorded, disputes opened, partial payments accepted, customers referred to legal.
- Webhook triggers: real-time alerts (invoice overdue, payment received, credit limit reached) without waiting for the next batch import.
Synchronisation must be bidirectional and at minimum daily. Unidirectional or weekly integration generates duplicate reminders and data conflicts that damage customer relationships.
Case Study: A Food Distribution Company Cuts DSO from 58 to 42 Days in 12 Months
Context and Initial Problem
A European food distribution business (€28M revenue, 400 active B2B customers, running Sage X3) had a DSO of 58 days at the start of the project. The credit manager was manually processing 350 to 400 reminders per month via spreadsheets and email. Disputes were tracked in email threads; partial payments were matched once a week. The result: AR working capital exceeding €4.5M and 3% of receivables written off each year.
Solution Deployed
The company activated three components on its existing Sage X3:
- Sage X3 native dunning module with three differentiated reminder profiles (key account, standard distributor, occasional customer).
- Dun & Bradstreet API integration for credit scoring and monthly credit limit refresh.
- Esker AR connection for complex dispute management and an online payment portal for customers.
The project ran for 4 months (configuration + training) at a total budget under €40,000.
Results After 12 Months
- DSO reduced from 58 to 42 days: 16 days recovered.
- Working capital released: 16 × (€28,000,000 / 365) = approximately €1.2M of liquidity unlocked.
- Bad debt ratio down from 3% to 1.1%.
- Time spent on manual reminders: reduced by 80% (the credit manager now handles exceptions, not volume).
Project ROI was achieved in under 3 months.
Checklist: 10 O2C KPIs to Monitor in Your ERP
Here are the 10 metrics to configure in your Credit Manager dashboard:
| Metric | Formula / Definition | Alert Threshold |
|---|---|---|
| DSO (Days Sales Outstanding) | (Receivables / Revenue) × 90 | > Sector target DSO |
| CEI (Collection Effectiveness Index) | Collections / (Collections + End-of-period overdue balance) × 100 | < 80% |
| Bad Debt Ratio | Write-offs / Annual revenue × 100 | > 1% |
| % Disputed invoices | Disputed invoices / Total invoices issued × 100 | > 5% |
| Aging 0–30 days | Receivables 0–30 days / Total exposure | < 60% = monitor |
| Aging 31–60 days | Receivables 31–60 days / Total exposure | > 25% = act |
| Aging 61–90 days | Receivables 61–90 days / Total exposure | > 10% = alert |
| Aging > 90 days | Receivables > 90 days / Total exposure | > 5% = high risk |
| Automatic matching rate | Auto-matched payments / Total incoming payments × 100 | Target: > 70% |
| Average invoicing lag | Days between delivery and invoice dispatch | > 3 days = anomaly |
The tenth metric — average invoicing lag — is the one most often overlooked. Yet it is the fastest, cheapest lever available: invoice on the day of delivery, not at week-end or month-end.
To go further on treasury management in the ERP, read our complete guide on SEPA Instant Payment and its treasury impact, our article on reverse factoring and supply chain finance to round out your short-cycle financing strategy, and our ERP monthly close checklist to ensure the data quality your receivables reporting depends on.
