Automated A/R: how accounts receivable automation works
Automated A/R, accounts receivable automation, means software handles the routine steps between a sale and the money on your bank account: invoices created and delivered, reminders sent on time, incoming payments matched to the right invoices, interest calculated, and the exceptions handed to a person. Done well, it shortens the time customers take to pay and frees finance staff from copying and chasing. This guide covers each step, the EU rules that shape it, how to measure the results and where to start.
It is written for finance managers, controllers and business owners. For the wider picture of automating processes, see our business automation page.
The short version
- Accounts receivable is a chain: invoice, delivery, reminders, payment matching, disputes, collection and reporting. Each link can be automated separately.
- Payment matching and reminders are usually the quickest wins; invoice creation follows where invoices are still typed by hand.
- E-invoicing to the European standard becomes the EU default from 1 July 2030, and several countries require it earlier.
- The Late Payment Directive gives suppliers interest and a fixed compensation sum on late business payments; automation applies them consistently.
- Measure before and after: days sales outstanding, overdue share, unmatched payments and hours spent.
The accounts receivable process, step by step
| Step | Done by hand | Automated |
|---|---|---|
| Customer and terms | Terms agreed by email, kept in people's heads | Payment terms, credit limits and invoicing details stored per customer and used by every invoice |
| Invoice creation | Typed from orders, contracts or time sheets | Created from the order, the contract schedule, the subscription or approved hours |
| Delivery | PDF attached to an email | E-invoice through the network the customer uses, or email and portal for those without one |
| Reminders | Someone remembers to check the overdue list | A friendly note before the due date, reminders after it, at intervals set per customer group |
| Cash application | Bank statement read line by line and matched by eye | Payments matched by reference, amount and payer; only the doubtful ones shown to a person |
| Disputes | Emails between sales, finance and the customer | A case per disputed invoice with the owner, the reason and a deadline; reminders paused meanwhile |
| Collection | Decided case by case | Interest and compensation calculated by rule, escalation to a collection partner after set steps and an approval |
| Reporting | Spreadsheet built at month end | Aging, days sales outstanding and forecast of incoming cash updated daily |
Invoices that start in the right place
Most receivables problems start at the invoice: a wrong price, a missing purchase order number, a wrong address, an invoice sent weeks after the delivery. Each one is a reason for the customer to pay late. Automated A/R creates the invoice from the source of truth, the order, the contract's billing schedule, the subscription or the hours approved in the project system, with the customer's required references taken from the customer record. Invoices go out the day the work is delivered, not when someone has time, and an invoice that fails a check, for example a missing purchase order number for a customer who requires one, stops for correction instead of going out wrong.
E-invoicing: the EU direction
Electronic invoices, structured data that the customer's system can read without retyping, are replacing PDFs. Public bodies in the EU must already be able to receive e-invoices that follow the European standard EN 16931, under Directive 2014/55/EU. The next step is in the VAT rules. Council Directive (EU) 2025/516 of 11 March 2025, known as VAT in the Digital Age or ViDA (read 11 November 2026), changes the VAT Directive in stages:
- Since 14 April 2025, Member States may require businesses established in their territory to issue electronic invoices for domestic supplies without a special authorisation, and may remove the need for the recipient's acceptance.
- From 1 July 2030, invoices are to be issued as electronic invoices by default, following the European standard, and cross-border supplies between businesses inside the EU come with digital reporting; for those supplies, the invoice must be issued no later than 10 days after the chargeable event.
- Member States that already had a domestic real-time reporting system in place before 1 January 2024 must align it with the EU requirements by 1 January 2035.
For accounts receivable, that means invoices built as data from the start, with every field the standard and each customer's country require, and delivered through the e-invoicing networks your customers use. A receivables process designed around PDFs and email will need rebuilding; one designed around structured invoices is ready.
Reminders and the late payment rules
Reminder sequences are where automation pays back fastest, because consistency matters more than wording. A customer who always gets a reminder on day one past due learns to pay on time. The rules behind the sequence come from the contract and the law. In the EU, the Late Payment Directive 2011/7/EU (read 11 November 2026; in force, implemented in each Member State's law) sets the framework for business-to-business and public sector transactions:
- Statutory interest for late payment is at least the reference rate plus eight percentage points (Article 2).
- Where interest becomes payable, the supplier is entitled to a fixed sum of at least EUR 40 as compensation for recovery costs, on top of the interest (Article 6).
- Payment terms agreed between businesses should not exceed 60 calendar days unless expressly agreed and not grossly unfair to the creditor (Article 3(5)); without an agreed date, interest runs 30 days after the invoice is received.
- Public authorities normally pay within 30 calendar days, and in any case within 60 (Article 4).
An automated system applies these consistently: it calculates interest from the due date with the right reference rate for the period, adds the compensation sum where the company decides to claim it, and leaves the choice of when to waive them with a person, because customer relationships matter more than a few euros. Each reminder records what was sent, when and to whom, which is what a collection partner or a court will ask for.
Cash application: matching payments to invoices
Cash application is often the most manual step left. Customers pay several invoices at once, pay partial amounts, deduct a disputed item, use the wrong reference or pay from a parent company's account. Automated matching works in layers. Payments carrying a structured reference, such as the international RF creditor reference or a national reference number, match exactly. Others are matched by amount, payer and invoice numbers found in the payment message, and combinations of open invoices that add up to the amount paid. Bank statements in the ISO 20022 format used by European banks, the camt.053 and camt.054 messages, carry these details in structured fields, which makes the matching far more reliable than reading a PDF statement. What still does not match goes to a person with the most likely candidates shown, and every manual decision can become a new rule.
Disputes and collection
A disputed invoice should stop the reminders, not be chased with them. The system opens a case with the reason, the owner in sales or operations, and a deadline, pauses the reminder sequence for that invoice, and resumes it when the case is resolved. Credit notes and corrections are issued from the same case. For unpaid invoices that pass the last reminder, the system prepares the file for a collection partner, with the invoice, the delivery evidence and the reminder history, and a person approves the hand-over. Customers who are habitually late can be moved to shorter terms or prepayment, a decision the data now supports.
Predicting late payment, with care
With a history of invoices and payments, a model can estimate which invoices are likely to be paid late, so reminders and personal follow-up go where they matter, and the cash forecast becomes more accurate. For business customers this is ordinary credit management. For individual consumers, more rules apply: decisions based solely on automated processing that significantly affect a person fall under Article 22 of the GDPR, and under the EU AI Act, AI systems used to evaluate the creditworthiness of natural persons or establish their credit score are listed as high-risk in Annex III, with those obligations applying from 2 December 2027. A prediction that only orders the work queue is a different matter from one that refuses a customer credit, and the design should keep that line clear. Our guide to types of analytics explains the difference between predicting and deciding.
Measuring the results
Measure before anything changes, then compare. The usual figures:
- Days sales outstanding (DSO): receivables divided by revenue for a period, multiplied by the days in it. It shows how long, on average, money takes to arrive.
- Overdue share: the part of receivables past due, by age bucket such as 1 to 30, 31 to 60 and over 60 days.
- Automatic match rate: the share of incoming payments matched without a person.
- Invoice errors: credit notes and corrections as a share of invoices sent.
- Time spent: hours a week on invoicing, matching and chasing.
Buy, configure or build?
Start with what you already have. Many ERP and accounting systems include e-invoicing, reminder sequences and bank matching that are only partly switched on, and configuring them is the cheapest step. Dedicated accounts receivable automation products, such as HighRadius or Upflow, add collections workflows, customer portals and forecasting on top of an ERP. Custom work pays off where invoices are created in several systems, where matching rules are specific to your customers and banks, or where a group of companies needs one receivables process across different systems. Then the right solution is often a connecting layer, built on the systems' interfaces as our API integration page describes, rather than a new finance system. Where screens without an interface must be used, software robots can fill the gap; see our guide to the benefits of RPA.
How to start
- Map the process. Where each invoice is created, how it is sent, how payments arrive and who does what, with volumes.
- Measure the baseline. The figures above, for the last six to twelve months.
- Fix the invoice first. References, data quality and timing; every later step depends on them.
- Automate matching and reminders. The quickest wins, measured within weeks.
- Then e-invoicing, disputes and forecasting, in the order your customers and countries require.
How we help
At DT Nova we build the software parts of automated A/R: invoice creation from your order, contract and project systems, e-invoice output to the European standard, payment matching from ISO 20022 bank statements, reminder and dispute workflows, and the reports finance needs, connected to your ERP or accounting system and hosted in an EU region in your company's account. For finance systems more broadly, see financial software development and document workflow automation. For the order-to-invoice system behind receivables, see ERP systems for small business.
Questions people ask
What is automated A/R?
Automated accounts receivable means software handles the routine steps between a sale and the money on the bank account: creating and sending invoices, sending reminders, matching incoming payments to invoices, calculating late payment interest and flagging the cases that need a person. Staff spend their time on disputes and difficult customers rather than on copying and chasing.
Which part of accounts receivable is best to automate first?
Usually cash application, matching bank payments to open invoices, and reminders. Both are high-volume, rule-based and easy to measure. Invoice creation is next if invoices are still typed from orders, contracts or time sheets. Collections and dispute handling benefit from automation of the routine, with people kept on the decisions.
What does the EU late payment directive allow a supplier to charge?
Under Directive 2011/7/EU, when a business customer pays late, the supplier is entitled to statutory interest of at least the reference rate plus eight percentage points, and to a fixed sum of at least EUR 40 as compensation for recovery costs, unless the contract lawfully sets other terms. Business payment terms over 60 days must be expressly agreed and not grossly unfair, and public authorities normally pay within 30 days. Each Member State's law sets the details.
When does e-invoicing become mandatory in the EU?
The ViDA directive, Council Directive (EU) 2025/516, makes electronic invoices to the European standard the default from 1 July 2030, with digital reporting for cross-border business transactions inside the EU. Since 14 April 2025, Member States may also require e-invoices for domestic transactions without asking for special permission, and several are introducing their own mandates earlier. Check the rules in each country you invoice.
Do we need new software to automate A/R?
Not always. Many ERP and accounting systems have receivables features that are not fully used, and dedicated A/R automation products exist. Custom work pays off where invoices come from several systems, where payment matching rules are company-specific, or where customers, contracts and collections do not fit a product. It is often a connecting layer rather than a replacement.
Sources
- Directive 2011/7/EU on combating late payment in commercial transactions, Articles 2 to 6 (read 11 November 2026)
- Council Directive (EU) 2025/516 as regards VAT rules for the digital age, Articles 1, 5 and 6 (read 11 November 2026)
- Directive 2014/55/EU on electronic invoicing in public procurement
- Regulation (EU) 2024/1689, AI Act, Annex III point 5(b), with dates as amended (checked 11 November 2026)