Supplier invoice without a project reference: route the exception before posting

A supplier invoice can be technically valid yet impossible to allocate to the right site. Without a project, purchase order or named requester, finance has to search messages and ask several people. The delay affects payment and weakens project cost reporting. A controlled exception queue keeps the invoice intact, identifies the business owner and records the reference before approval or posting.

Keep the received document unchanged

Store the structured invoice, readable representation, attachments and receipt status together. Do not edit the supplier’s original file to insert an internal project code. Record internal enrichment as separate metadata with its own author and timestamp.

Belgian B2B invoices within scope have used structured e-invoicing since January 2026. Technical receipt does not prove that the buyer can allocate or approve the cost.

Search reliable matching signals

Compare supplier, invoice date, amount, delivery address, purchase order, delivery note and named contact. Look at open orders and recent receipts. Use several signals rather than matching only on a familiar supplier name.

A supplier serving multiple sites needs a stronger match than a vendor used by one project. If evidence remains ambiguous, keep the exception open.

Assign one business owner

Route the invoice to the project manager, buyer or requester most likely to recognise the purchase. State the exact question: which project, which order and whether the goods or service were received. Set a response date before the payment deadline.

Do not broadcast the invoice to a large group. Wide requests dilute accountability and expose commercial information unnecessarily.

Validate the commercial basis

Once a project is proposed, compare quantity, unit, price and delivery evidence. Check whether the purchase was authorised and whether a dispute or back-order exists. A project code alone does not make the invoice payable.

If the supplier should have included a customer reference, record that feedback for the next order and invoice instruction.

Approve and code only after resolution

Apply project, cost category and tax treatment through the normal finance controls. Preserve who supplied the missing reference and which evidence supported it. If no project applies, use a deliberate overhead route instead of forcing the cost into the busiest site.

Keep rejection, query and approval states distinct so finance can see what blocks payment.

Reduce repeat exceptions

Report suppliers, teams and order types that frequently lack a reference. Improve purchase-order instructions, delivery capture and supplier master data at the source. The useful metric is not how quickly finance guesses a project, but how many invoices arrive ready for correct first-pass allocation.

Read also supplier invoice project coding and connect purchasing and projects in Enfin.