Vendor Bills Not Linking to Purchase Orders: A Bookkeeper's Guide

When you enter a vendor bill and the matching purchase order stays open, the ledger tells you something is wrong before the month-end does. The PO is a commitment record, not a ledger posting, so nothing in the trial balance flags the mismatch. You find it in the open-PO report, usually when a supplier chases a payment you already made.

Is it a workflow issue or a data issue?

Most of the time the bill is fine and the linkage is what failed. The commonest cause in Enterprise with Enhanced Inventory Receiving turned on is sequence. With EIR active, receiving and billing are deliberately separated: goods arrive on an item receipt, and the bill comes later against that receipt. If you enter the bill directly and skip the receipt step, the PO never closes because the system is waiting for a receipt transaction that does not exist.

Test the sequence before anything else. If the file uses EIR, check whether an item receipt exists for that PO. If it does not, the open PO is your answer, and the fix is ordinary bookkeeping: record the receipt, then bill against it.

How the fault shows up in the close

An open PO against a paid bill distorts your commitment reporting. Accruals at period end rely on the open-PO list to capture received-not-invoiced items. A PO that should have closed makes the accrual look larger than reality. A PO closed by a receipt with no bill makes it look smaller. Both are cut-off errors, and both surface as reconciliation surprises when the supplier statement arrives.

Run the open-PO report against the accounts payable ageing before you close. Any PO whose goods are on the shelf and whose bill is in the ageing is a linkage failure, whatever caused it.

Telling a posting mistake from data damage

A workflow error is consistent and explainable: it happens on specific transactions where the sequence was broken. Data damage behaves differently. The symptoms are erratic. A bill entered against a PO posts to the wrong account, the PO shows closed with no bill behind it, or the same entry works in one file and fails in another.

The clean test is to reproduce the entry in a sample company file. If the same steps link the bill to the PO there, the procedure is sound and the working file is suspect. That is the moment to stop entering transactions and start preserving evidence.

What to preserve before anyone touches the file

Once you suspect damage, freeze the file. Take a full backup, note the file's size and modified date, and write down exactly which transactions misbehaved. Do not run repair utilities on the only copy. Keep the backup somewhere separate from the working file, because a rebuild that goes wrong can leave you with two damaged files and no clean history.

Where bookkeeping ends and repair begins

Verify and Rebuild utilities exist, and they sometimes resolve minor inconsistencies. But repeated verification failures, transactions that change on their own, or a list that corrupts again after a rebuild are repair work, not bookkeeping work. At that point the right move is a specialist. See our QuickBooks data repair service for damaged company files, and keep your verified backup untouched until the file comes back.

The bookkeeper's job in this scenario is diagnosis and evidence. Establish whether the sequence was broken, prove whether the file is at fault, and hand over a clean backup with a written description of the symptoms. That is what makes the repair fast and the close recoverable.