Accounts payable trends: the shifts that matter

Payables was built on a sequence: you order, the supplier invoices, someone approves, you pay. Every control in the function assumes that order, and the biggest change in the function is that the order is breaking down.

A subscription charges the card on file; the invoice arrives afterward, if at all. A marketplace deducts its fees before payment reaches you, and a supplier's invoice arrives as a structured message already matched to a purchase order nobody remembers raising.

The sequence remains in the ledger, because the entries have not changed. But the events no longer arrive in it.

What to take away

Payment first, invoice later

The largest single change is the card on file. Software, services, advertising, storage: charged monthly to a company card, with an invoice generated somewhere in the supplier's portal that nobody downloads.

For the bookkeeper, the payment is a bank line with a merchant name and nothing else.

Two consequences follow: first, the cost is real and needs recording in the month the service was consumed, invoice or no invoice, as the expense recording guide sets out.

Second, the missing invoice will be asked about at year end and at any tax review. The routine now includes fetching invoices from portals rather than waiting for them.

The control that used to live in approval before payment moves to review after it. Somebody has to look at the list of recurring charges, periodically, and ask whether each one is still wanted. That review is the new purchase order.

Capture is nearly free

Photographing a receipt, forwarding an email, or letting a supplier push an invoice straight into the ledger has removed most of the keying. With it has gone most of the transposition errors and most of the lost paper.

What has replaced them is the confident duplicate. The same invoice arrives by email and through a portal and is captured twice, with identical dates and amounts, and nothing about either capture looks wrong. Or it is captured once from the supplier's email and again when the statement arrives with the same invoice listed on it.

Duplicate detection by invoice number and amount catches most of it, provided the supplier's invoice number is captured accurately and the same supplier is not set up twice under slightly different names. Both of those are master data problems, and master data is now the front line of payables control.

Coding becomes a suggestion

Captured invoices arrive with a proposed account, learned from what was done last time for this supplier. It is usually right. It is wrong in exactly the cases that matter: the supplier who sells both materials for jobs and consumables for the workshop, the courier whose charge is sometimes inbound freight on stock and sometimes outbound delivery to a customer.

A human coding by hand asks what this invoice was for. A rule asks what the last one was for. The account definitions written against the chart of accounts are the only thing that lets a reviewer say the suggestion is wrong, and they matter more now than when a person made every choice.

Approval moves to a phone

Approval workflows route an invoice to whoever ordered the thing, who taps approve on a phone between meetings. This is faster than a paper trail and it removes the invoice stuck in a tray for a month.

It also changes what approval means. An approver who sees an amount and a supplier name, with no purchase order or delivery note, only confirms the invoice looks plausible. The three-way match, order to receipt to invoice, must be rebuilt in the system or it quietly stops existing.

For a small business that never had a formal match, the practical version is that the approver confirms the goods or service arrived, and the workflow records it.

Payment runs come from the ledger

Payments are now initiated from inside the accounting system: pick the invoices due, approve the run, and the bank executes it. The days of retyping supplier bank details into a banking portal are ending, and with them a category of error.

The master data risk replaces the retyping risk. Bank details on the supplier record now decide where every payment goes, so changing that record changes where the money goes.

The control is simple and non-negotiable. Verify any change to a supplier's bank details by calling a number you already had, never one from the email requesting the change, and log who made it.

Payment timing also becomes a setting. A run configured to pay everything on entry pays early by default; a run configured to pay on due date pays on terms. Neither is right in every case, and the accounts payable overview covers the decision.

A large payer must answer the same question in writing. The federal government is the clearest example: in 1982 Congress passed the Prompt Payment Act to require federal agencies to pay their bills on a timely basis, to pay interest penalties when payments are made late, and to take discounts. In most cases, when an agency pays a vendor late, it must pay interest. Those rules read as a checklist of decisions a payment run setting quietly makes for you: when to pay, when a discount is worth taking, and what lateness costs.

That decision is now made once in a setting, not each time a person writes a check. It needs to be made deliberately.

Suppliers send structured invoices

In a growing number of jurisdictions invoices are moving from documents to structured messages, sometimes through mandated networks, sometimes with required identifiers. What applies to you, and by when, is set by your own authority; do not adopt a date or a format from a guide written for somewhere else.

The European Union shows the timetable such a shift follows. Its VAT in the Digital Age (ViDA) package was adopted on 11 March 2025 and will be rolled out progressively until January 2035. Since it entered into force on 14 April 2025, member states can introduce mandatory e-invoicing under specific conditions, and from 1 July 2030 digital reporting requirements based on e-invoicing take effect for cross-border business-to-business supplies. A US business that sells into the EU will meet those rules through its customers before it meets any domestic mandate.

The preparation costs nothing: accurate legal names and registration details on every supplier record, and tax shown separately on every entry rather than buried in a gross figure.

Add a filing convention that lets any entry find its document for as long as it has to be kept. For federal tax, the IRS sets that period; its Publication 583 says that if you have employees, you must keep all employment tax records for at least 4 years after the date the tax becomes due or is paid, whichever is later. The IRS applies the same discipline to its own files through its records schedules. Those are the same disciplines described in the bookkeeping foundations guide, and they are what a structured invoice will need if one arrives.

Where the control has gone

The function has not become easier. It has moved from doing to checking, and the checks need setting up, which is what to ask of any package before trusting it, as the guide to accounting software sets out.

Common questions