Features
Part of Reading accounts receivable as a beginner bookkeeper: aging, payments and credit notes
Accounts receivable trends 2027: reminders and matching
Accounts receivable trends 2027: payment links settle invoices, reminders chase by themselves, and matching plus exceptions replace keying receipts.
The invoice used to be a document. It is turning into a message, and the difference is what most of the change in receivables comes down to.
A document is sent, read by a person, keyed into someone else's system, approved, and paid by a separate act. A message arrives in the customer's system already structured, is matched to their order automatically, and can be paid from inside it.
Every stage in between is where invoices get stuck, and every one of those stages is thinning out. What follows is what accounts receivable trends 2027 mean for the work, and where the dates behind them come from.
Where the 2027 date comes from
Structured invoices are already compulsory in some countries, and those mandates are what put a year on this change. Italy's SdI network has required them for business-to-business invoices since 2019; Belgium requires them between businesses from 2026; France phases its mandate in across 2026 and 2027; and Germany's obligation to issue them starts in 2027. The messages travel over the Peppol network and follow the European standard EN 16931, and the EU's VAT in the Digital Age package points the same way.
The United States has no federal business-to-business e-invoicing mandate, so 2027 is not a US filing deadline. The part of the change a US small business meets first is the part its software brings: a payment link on the invoice, reminders that send themselves, receipts matched by rule instead of by hand.
What to take away
- Chasing is shrinking as a job and allocation is growing as one. The effort that used to go into phone calls now goes into working out what a net settlement actually paid.
- Automatic matching is confident and sometimes wrong. The customer ledger needs a human check it did not need when a person keyed every receipt.
- Whatever changes in how invoices travel, the entry is unchanged: income when the work is done, receivable until the money lands, bank when it does.
Payment moves onto the invoice
An invoice that carries a payment link is settled by a click, often before the customer's own accounts process has seen it. Three consequences for the bookkeeper.
Net settlement splitting
- Processor pays net amount
- Bank line shows processor name
- Receivable was gross
- Gap is a fee, a cost
- Split before allocating
First, money arrives from a processor, not the customer, so the bank line shows a net amount and the processor's name. The receivable was for the gross, so the gap is a fee, which is a cost.
The settlement needs splitting into the two before it can be allocated. A business that matches the net deposit to the invoice and writes off the difference has hidden its payment costs in its sales.
Second, one settlement can cover several invoices from several customers, netted against refunds issued the same day. The processor's own report, not the bank feed, is the document to reconcile from.
Third, the invoice date and the payment date get closer together, which is good for cash and does nothing at all to the question of when the sale was earned. That question is settled in the revenue recording guide and it does not move.
Reminders send themselves
Automated reminders take the routine chase off a person's desk: a note before the due date, another on it, another a week after. This removes the category of late payment that was only ever forgetfulness, and it does so for every customer at once.
It cannot tell a disputed invoice from a forgotten one. A reminder sent to a customer who raised a query sounds like a business not listening. A sequence of them can turn a small dispute into a lost account.
The dispute flag on the customer ledger was once a courtesy; now it is the switch that stops the machine, so keep it current.
The second thing automation cannot do is escalate. The human part of the ladder in the accounts receivable overview starts where the reminders stop, and it starts sooner in calendar terms than it used to, because the easy cases have already been cleared.
Cash matching becomes a suggestion
Receipts are now matched to invoices by rules: same amount, same reference, same customer name. Most of the time the rule is right. When it is wrong it is wrong silently, because the bank reconciles either way.
Rule match vs human check
Automatic rule
- Round sum
- Matches one invoice
- Duplicate customer
- Lands on wrong account
- Parent company
- Sits unallocated
Human control
- Round sum
- Spots three covered
- Duplicate customer
- Ledger agreed to control
- Parent company
- Aged report read
A round sum payment is matched to the one invoice of that amount, not the three it covers. A customer with two accounts in your ledger, set up twice, has receipts landing on the wrong one.
A payment from a parent company is matched to nothing and sits unallocated while the subsidiary's invoices are chased.
The control that catches all three has always existed: the customer ledger agreed to the control account, and the aged report read by a person who knows the customers.
The difference: it used to check human keying. Now it checks a rule that keys a thousand times without tiring.
Subscription income makes the receivable and the sale the same event
Recurring billing raises the invoice, collects the payment by direct debit or stored card, and records both in one pass. There is often no receivable at all in the old sense, because the money is taken on the invoice date.
What there is instead is the failed collection: the expired card, the canceled mandate, the insufficient funds. These do not appear as aged invoices. They appear as exceptions in the billing system, and if nobody owns that exception list, revenue is being recognized on sales that were never collected. The exception list is the new aged report.
There is also the reverse problem. Money taken in advance for a full year is not a year of income the day it arrives, but a liability that releases as the service is delivered. Billing systems know this rule, but bank-feed bookkeeping does not.
How an advance payment is treated for tax is a further question, handled differently under different methods, so start with IRS Publication 538, the federal guide to accounting periods and methods.
Invoice finance moves inside the ledger
Offers to advance money against unpaid invoices now arrive inside the accounting system, with the amount available computed from the ledger itself. The mechanics vary and are a matter for the contract. Read an offer of this kind beside the plainer forms of business funding before taking it.
The bookkeeping shape is consistent: the advance is borrowing, secured on the receivable, not a payment of it. The invoice stays open until the customer pays, the advance sits as a liability, and the fee is a cost.
A business that records the advance as the customer's payment has overstated its collections and understated its debt in one entry. The effect on the cash flow statement is that a financing inflow appears as an operating one.
Structured invoices and identifiers
In a growing number of places, invoices are moving from PDFs to structured messages exchanged between systems. That is what the Peppol network carries and what the European standard EN 16931 defines; in other places the invoice stays a PDF but has to carry identifiers the tax administration requires on the document.
Whether any of it applies to you, and on what timetable, is set by your jurisdiction's authority, and no guide written for somewhere else can tell you. In the United States there is no federal business-to-business e-invoicing mandate and no federal deadline, which is why the useful preparation here is your data rather than a compliance calendar.
What is worth doing regardless is making sure your customer records already carry the details a structured invoice would need: legal entity name, registration numbers where they exist, the customer's own reference conventions. That data costs nothing to hold and saves a scramble if a requirement arrives.
What the job looks like now
| Used to take most of the time | Takes most of the time now |
|---|---|
| Keying receipts from the bank statement | Checking that automatic matches are right |
| Phoning customers about forgotten invoices | Handling disputes and failed collections |
| Producing the aged report | Reading it, and the exception list beside it |
| Chasing the missing purchase order number | Getting the customer master data right so the invoice matches on arrival |
| Working out who paid | Working out what a net settlement paid for |
The skills in the right column are judgment skills, and they sit on top of the same method described in the bookkeeping foundations guide. What to ask of a system before trusting it with any of this is covered in the guide to accounting software.
