
An ERP dashboard can tell a buyer exactly where an invoice sits. The supplier who issued it usually cannot see any of that, so they email or call to ask. Real-time invoice tracking only earns its name when both sides are looking at the same record, not two private ones.
Key takeaways
Real-time invoice tracking has a quiet problem: most of it is only real-time for one party. The buyer's finance team can see an invoice move through capture, coding and approval inside their ERP or accounts payable inbox the moment it happens. The supplier who sent that invoice sees none of it. They know they submitted something, and after that they are guessing, which is why so many finance inboxes fill up with a version of the same question: when will I be paid?
The fix is not tracking invoices faster (most teams already do that on their own side). It is tracking them as one shared status rather than two separate views that happen to describe the same document. That is what good real-time invoice tracking looks like end to end, and it is one of the things a connected accounts payable network is built to provide.
How can I track invoice status in real time?
For most suppliers today, the short answer is that they cannot, not directly. They can track their own outgoing invoice (sent, maybe acknowledged), but the buyer's internal workflow (approval queues, scheduled payment runs, exception holds) sits behind a wall the supplier has no view into. Where real-time tracking exists, it almost always exists for the buyer alone.
That is the gap a shared payment record is built to close. Rather than the supplier inferring status from silence or a forwarded email, both sides read from the same record: received, approved, scheduled, paid, or disputed. Accounting Links maintains that record as part of its accounts payable network, and both the buyer and the supplier see it update at the same moment, because it is one entry, not two.
What does better visibility into invoice status and payment timelines actually change?
It changes who has to chase, and how often. Buyer-side visibility already exists in most modern accounting systems and ERPs. Supplier-side visibility, historically, has not, and that gap is where the cost sits: not in processing time, but in the enquiry volume it generates.
Every 'has my invoice been approved yet' email costs someone time on both ends: the supplier chasing, and the finance team stopping what they are doing to check and reply. Multiply that across a supplier base of any size and it becomes a meaningful, if rarely measured, drain on an AP team's week. Shared status does not just make suppliers feel informed. It removes the reason for the enquiry to exist in the first place, because the answer is already visible without asking.
There is a knock-on effect on disputes, too. A large share of payment disputes are not disagreements about the invoice itself; they are disagreements about what happened to it. A supplier who believes an invoice was never received, when it was in fact received and is sitting in an approval queue, will raise a dispute that a shared status would have prevented. When both sides can see 'received' and 'approved' logged with a timestamp, there is far less room for that kind of dispute to start.
Real-time invoice tracking is bigger than one dashboard
Real-time invoice tracking is one input into a wider payment behaviour data set, not the whole story. Status tells you where an invoice is; the pattern of statuses over months tells you how a business actually pays. If you want the argument for continuous, always-current AP rather than batch cycles, see Continuous AP: monthly cycles vs real time; if you want the case for visibility across the whole procure-to-pay chain rather than just the invoice stage, see Procure-to-pay visibility.
How to track real-time invoice approval status?
Approval status is the single most requested piece of information suppliers do not have, so it is worth being specific about what 'tracking' it actually requires. It needs a status that updates the moment an approver acts, not a batch update at the end of the day, and it needs that status visible to the supplier without a support ticket or a phone call. Inside a shared payment record, an invoice moving from 'received' to 'approved' is one event, logged once, seen by both parties immediately. There is no second system to reconcile and no lag between what the buyer's approver just did and what the supplier can see.
The cost nobody puts on a spreadsheet
Late payment is a well-documented cost to UK small businesses. Research cited by the Department for Business and Trade puts the average loss to SMEs at around £22,000 a year, and separate Federation of Small Businesses analysis links roughly 50,000 business closures annually to late payment (GOV.UK: crack down on late payments in major support package for small businesses). Those figures are usually read as a case about payment speed. They are just as much a case about payment visibility: a supplier who cannot see that a payment is scheduled has no way to distinguish 'this will be paid on time' from 'this has gone quiet', and reacts to both the same way, by chasing.
This is also where payment practices reporting and the fair payment code intersect with tracking. The Fair Payment Code, run by the Small Business Commissioner, awards bronze, silver or gold status to businesses that demonstrate consistently fair and fast payment practices, with gold aimed at making 30-day payment the norm (Small Business Commissioner: the Fair Payment Code). Reporting on that record depends on the underlying data being reliable and current. A business whose invoice status lives in email threads and someone's memory has a much harder time evidencing its actual payment behaviour than one whose status is logged in a shared, timestamped record. Shared invoice tracking is not a compliance feature, but it makes compliance and reporting considerably easier to stand behind.
It is worth being clear about what this is not. The UK's move towards mandatory e-invoicing via Peppol, due from April 2029 according to HMRC's transformation roadmap update, will eventually standardise how invoice data is exchanged between systems. That is a useful direction, but it is a separate question from whether a buyer and supplier can see the same status today, and it is not a substitute for shared visibility in the meantime. Treat it as context for where invoicing is heading, not as something to wait for. For the fuller picture on the mandate itself, see The UK has chosen Peppol for e-invoicing.
What this looks like in practice
On Accounting Links, a supplier submits an invoice through a verified profile and sees it move through received, approved, scheduled and paid in the same view the buyer's finance team is looking at. If a buyer flags a dispute or an exception, that status is visible too, rather than surfacing as a delayed or missed payment with no explanation attached. Buyers get the fraud and verification benefits of a supplier verification network; suppliers get an answer to 'when will I be paid?' before they have to ask it.
If you run accounts payable and want your suppliers asking fewer status questions, see how the shared record works. If you are a supplier tired of chasing buyers for an answer, see what changes on your side.
Sources
