The Invoice That Never Arrived
You closed the books on Tuesday. Everything you had was reconciled, every invoice you received was categorized, every payment matched a bill. Two weeks later a vendor emails asking about a past-due amount for a service you use every month, and you realize the June invoice was never sent. Or it was sent and it never landed. Or it landed and it got stuck in a shared inbox that nobody sorts.
The reconciliation did not catch it. The reconciliation could not catch it. Every review process a small business runs at month-end is designed to check the invoices that are there. The problem is the ones that are not.
Why Missing Is Harder Than Wrong
Errors in an invoice you received are relatively easy to catch. The amount is wrong, the vendor is wrong, the terms are wrong, the line items do not match the delivery. Any of these show up when someone looks at the invoice. It is a comparison problem, and comparison is what accounts payable is built to do.
Absence does not fail a comparison. There is nothing to compare against, because the invoice is not there. The only way to notice an invoice is missing is to remember that one usually arrives, and then notice that it did not this month. That is a memory task, not a checking task, and human memory is the weakest link in any monthly close.
The result is a specific kind of leak that shows up in three places.
- Accruals get missed. If the invoice never arrives, the expense never posts. Your P&L looks better than reality for a month or two, and then the vendor catches up and hits you with several months at once.
- Vendor relationships drift. The vendor is watching their aging report. You are not on it because you never got the bill. They start assuming you are a slow payer, and the next quote comes in less friendly.
- The close eats extra days. When the missing invoice finally surfaces, it has to be back-dated, journalized, and reconciled to a period that is already closed. That is hours of catch-up work every time.
The Four Places Missing Invoices Actually Hide
Missing invoices are almost never truly missing. They are somewhere. The four common somewheres cover most of what a small business hits.
- A shared inbox nobody sorts. The invoice went to accounts@yourbusiness or a similar catch-all address that gets fifty other messages a day. It is not lost. It is buried under promotions and vendor newsletters and password resets.
- A personal inbox at a former employee. The vendor still has an old contact address on file. The person who used to check that inbox left in April. Everything routed to them still is.
- A change of billing platform on the vendor's side. The vendor moved from emailed PDFs to a portal login. You have not created the portal login yet. The bill sits in a portal you have not logged into.
- The vendor forgot to send it. This happens more often than owners expect, especially with small vendors on manual invoicing. Nobody on their side generated the invoice this cycle.
Each of these is fixable once you know to look. The problem is you do not know to look until the vendor calls, which is usually two to three months later.
average cost to process a single invoice manually at companies without best-in-class AP automation (Ardent Partners AP Metrics That Matter 2025)
Manual accounts payable is expensive per invoice you receive, and even more expensive for the invoices you do not receive, because the cost of chasing a missing one after month-end includes back-dating, adjusting entries, and often a phone call to a vendor whose next quote is now less friendly.
What a Baseline of "What Usually Arrives" Does
The way to catch a missing invoice is to know what should have arrived. Every recurring vendor has a rhythm. The rent invoice arrives between the twenty-fifth and the thirtieth of the month. The internet bill arrives on the fifth. The linen service bills every other Friday. The pattern is stable, and stable patterns are exactly what a baseline is built to remember.
A working baseline flags four things, all of them absences.
- Recurring vendor did not invoice this cycle. The linen service usually bills every other Friday. Two Fridays have gone by. Where is it?
- Cycle length changed. The invoice arrived, but it covered a shorter or longer period than usual. Sometimes this is a genuine change. Often it is a vendor catching up after a missed cycle you did not notice.
- Vendor went quiet after regular activity. The freelancer who invoiced every month for six months has not invoiced in two months. Either the relationship changed and you know it, or the invoice is stuck.
- Amount is far from the running average. The invoice arrived, but the amount is a third of usual or three times usual. That is a signal worth reading before it hits the pay run.
Doing this for the top ten vendors on a quarterly basis is possible by hand. Doing it for every vendor continuously is the kind of work a document and invoice processing agent is built to do in the background, with any flagged absence showing up in a queue that a human confirms before any action is taken.
The bookkeeper cannot catch this because the bookkeeper's job is to reconcile what came in. The owner cannot catch this because the owner is not looking at vendor cycles individually. The absence gets caught only by a system whose job is specifically to remember what usually arrives and flag what did not.
Why the Close Cannot Fix It
A common reaction is to say the fix belongs in the close checklist. Add a step: "check for missing invoices." Two problems.
First, the close is already the longest week of the month. Half of small teams that aim for a three-day close actually take six or more days because catch-up work always expands. Adding a manual review across every recurring vendor at the end of the month makes the close longer, not shorter, and the review is exactly the kind of task that gets skipped when the close is running behind.
Second, the close catches missing invoices too late. By the time you notice at close, the vendor already has two weeks of aging on their side. The point of a continuous baseline is to notice within a day or two of the expected date, when the fix is a quick email to the vendor and not a back-dated journal entry.
The close is the wrong place for this work. The right place is a continuous process that runs after every document is ingested, notices what is missing against expectation, and shows the human the list before it becomes a month-end scramble.
What to Do Next
You do not need software to see whether this is a real leak for you.
- Pull your last twelve months of vendor payments. For each recurring vendor, count how many months they were paid. If any vendor shows fewer months than expected, you have already found one. Reach out and reconcile.
- Set up a single-vendor watch. Pick the recurring vendor most likely to slip and put a calendar reminder two days after their usual invoice date. Manual, but a real signal.
- Take the AI Readiness Assessment. Four minutes, no signup. It puts a dollar figure on what missing invoices are quietly costing your close and shows whether a document agent watching your vendor cadence would pay for itself in a single quarter.
The invoice you paid twice gets a headline. The invoice that never arrived does not, because nothing failed a check that was never run. That is why it costs more over a year than the duplicate ever will. Catching it does not require distrust of your vendors or a rebuild of your accounting system. It requires a piece of the workflow that remembers what usually arrives, notices when it does not, and puts the absence in front of a human while the fix is still a two-minute email.
Written by
Michael Sweeting
Is your business leaking revenue?
Take our free 4-minute assessment to find out exactly how much you're losing to manual processes, and get a personalized action plan to fix it.
Start Your Free Assessment