Match construction invoices to purchase orders and delivery receipts without hiding exceptions

Define the review you are performing

Start with the supplier, project, purchase-order reference, invoice reference and period. Identify whether the review concerns a particular delivery, a partial invoice or a cumulative account. A comparison can be mathematically correct while answering the wrong question if its scope is not clear.

Use the organization’s actual purchasing and accounts-payable process. Identify who confirms receipt, who resolves commercial terms and who authorizes accounting or payment actions. The coordinator should be able to route an exception without assuming that possession of three documents grants all of those authorities.

Keep the current invoice’s review separate from the supplier’s overall balance. Prior invoices, credits or another project’s documents may need reconciliation, but they should not be silently folded into a single line match. Preserve the source relationship and the question the responsible reviewer is being asked to resolve.

Understand what the three records contribute

Sage 200’s product help distinguishes matching an invoice to a purchase order from matching it to both the order and goods-received records. That is a bounded software example of two-way and three-way matching. Its settings and item rules are not universal accounting instructions for every contractor.

The purchase order supplies the actual ordered scope and commercial basis. The receipt record supplies the relevant reported receipt. The invoice supplies what the vendor has billed. Keep those source statements distinct instead of replacing them with a single quantity that hides where a disagreement began.

A receipt can still leave condition, technical acceptance or another required review unresolved. Likewise, a matched invoice may still require the organization’s posting and payment approvals. The useful comparison preserves what each source establishes and leaves other decisions with their actual responsible people.

Sources: Sage 200: Recording invoices for purchase orders and receipt matching

Confirm identity, versions and line mapping

Check the supplier and project references, PO and amendment version, receipt identifiers and invoice number or version. Preserve original files and corrections. A later scan of the same invoice should not become another payable item merely because it has a different filename.

Map the actual lines and item scope. A supplier may group several ordered items, use a different description or bill freight separately. Record the relationship and unresolved mapping question rather than forcing a line match based only on a similar total.

Where one invoice relates to multiple orders or deliveries, preserve the allocation basis and review owner. Do not apply the full invoice to each order or infer a split from round numbers. The next reviewer should be able to identify which quantity and charge belongs to which source record.

Compare the relevant quantities and units

Record ordered quantity, relevant cumulative receipts, quantities on this invoice and any earlier invoicing that affects the comparison. Use the actual unit basis. A pallet, box, piece, length or area can describe different quantities; do not invent a conversion to make the columns agree.

For partial deliveries, retain each receipt’s identity and source. A cumulative total should be traceable to the component records without counting a duplicate scan twice. A missing receipt means the evidence is unresolved; it does not by itself prove that the vendor failed to deliver.

Keep returns, rejected items and replacements linked to their actual sources and review state. A physical return, promised credit and posted credit are different events. Do not subtract an unconfirmed return or assume a replacement can be counted as an additional accepted purchase without the responsible review.

Review the commercial basis separately

Use the actual authorized PO or other applicable commercial source for the comparison. Check currency, unit price, quantity basis, stated charges, discounts and exclusions. A rate from an old order or a different project should not be applied simply because it is already in the spreadsheet.

Microsoft’s Dynamics 365 Finance guidance provides a product example of quantity and price matching under configured policies and tolerances. That illustrates why the actual organization’s settings matter. Do not copy a vendor example’s tolerance percentage into a contractor’s process or treat it as an industry standard.

If a rate or charge is disputed, preserve both sources and route the question to the responsible purchasing or commercial owner. A coordinator can calculate a conditional difference while leaving the actual resolution open. Correct arithmetic does not establish an agreed contract adjustment or approved credit.

Review fixed charges separately from quantity extensions. A freight line may apply to a delivery or order under its own actual terms, while tax, discounts and other adjustments can have different bases. Keep the relevant source and reviewer question visible. Do not spread every fixed charge across units merely to make the unit price agree, or subtract the same charge both in the rate comparison and in a separate exception. Reconcile the conditional line subtotal to the actual invoice total and explain every excluded item before handing the packet to accounts payable.

Sources: Microsoft Dynamics 365 Finance: Three-way matching policies

Worked example: separate a ten-unit question from a price question

All records and amounts below are fictional. PO-741 orders 100 units at $28 each. The relevant receipt sources total 80 units. Invoice I-541 bills 90 units at $30 each, or $2,700. The exercise assumes no earlier invoices for this first comparison and excludes taxes, freight and other adjustments.

Using the stated receipt quantity and original PO rate gives a conditional comparison of 80 × $28 = $2,240. The $460 difference can be separated into ten billed units without a receipt source in the packet, at the invoice’s $30 rate, or $300, plus a price difference of $2 on each of the 80 receipt-supported units, or $160.

That decomposition avoids counting the same price difference twice. The receipt gap needs its actual receiving source, and the price gap needs the commercial basis. Neither is automatically a proven overcharge, approved deduction or payment amount. The actual reviewer resolves the facts and required action.

Ask the owner of the specific exception

For the ten-unit question, ask receiving or the designated site owner for the relevant source record or clarification. Identify the order, invoice line, quantity and existing receipts. A general request to resend all delivery paperwork can produce duplicates while leaving the specific gap unanswered.

For the $2 price question, ask the responsible purchasing owner whether an authorized amendment or other applicable source changes the rate. Keep the answer and version linked. The receiver may know what arrived without having authority to decide the supplier’s commercial terms.

Preserve conflicting accounts instead of overwriting one with the latest reply. If the supplier supplies another delivery reference, link it for review. If the office reports that the order changed, retain the actual amendment source. The comparison should show what remains unresolved after each response.

Do not confuse received quantity with unbilled quantity

Earlier invoices can change the quantity available for a current comparison. In a separate fictional variation, the same cumulative 80 received units already have 30 units recorded on an earlier invoice. The remaining quantity for this simplified receipt-allocation exercise is 50 units, subject to the actual review of those records.

At the fictional original $28 rate, 50 units correspond to $1,400 before excluded charges and other decisions. This variation is separate from the first example’s no-prior-invoice assumption. Do not apply both scenarios at once or subtract a paid amount from a quantity column.

Keep quantities allocated to earlier invoices traceable to their sources, whether those invoices are posted, disputed or awaiting another step. The actual accounting process determines how those states affect the review. A receipt total should not silently authorize repeated billing of the same goods.

Recalculate only after preserving the new basis

Suppose the responsible commercial reviewer supplies an actual authorized amendment confirming $30 per unit for the fictional scope. Retain that source and identify the comparison version. At 80 receipt-supported units, the conditional amount becomes $2,400, leaving a $300 quantity-evidence question against the $2,700 invoice.

The new rate resolves only the rate basis under that variation. It does not supply the missing ten-unit receipt, establish quality acceptance or authorize payment. Keep the remaining exception visible and route it to the appropriate source owner.

If a replacement invoice arrives, retain the original and its supersession relationship. Confirm the current supplier reference and whether the accounting team must take a separate action. Do not simply replace the attachment and assume that an earlier posted or reviewed record has changed everywhere.

Hand the reviewer a clear comparison and source pack

Provide the source index, line mapping, conditional calculation, unresolved questions and relevant responses. Identify the packet version and what changed since the last review. The responsible person should be able to reconstruct the comparison without searching an unlabeled email history.

Record the actual disposition and its scope. A reviewer may accept a source, request another record or authorize a particular accounting action. Preserve that decision rather than translating every response into approved for payment. Keep posting, credit application and payment references distinct where the process requires them.

Use exception counts as coordination measures. A packet with one remaining receipt question is different from a fully resolved commercial review. A clean spreadsheet does not prove that the supplier account is reconciled or that every condition for payment has been met.

Use the free PO / receipt / invoice comparison register

The blank CSV includes supplier and project, order and version, invoice identity, line mapping, receipt sources, quantities and units, earlier allocations, commercial rate source, conditional amount, exception type, responsible owner, review outcome and separate accounting references. Keep sensitive payment information in the approved controlled destination.

Enter the main fictional example and check the $2,700, $2,240 and $460 values. Then test the separate prior-invoice variation and the authorized-rate variation. Preserve their assumptions and sources so another reviewer does not accidentally combine incompatible scenarios.

Pilot one supplier invoice with purchasing, receiving and accounts payable. Ask each person to identify the question they own and the evidence needed to resolve it. Clarify unit definitions, duplicate handling and decision boundaries before expanding automated reminders across the full supplier roster.

Coordinate invoice-document exceptions with Buildalytic

Buildalytic’s custom-workflow page describes requests, logged follow-up, waits and named approval steps. Bring a redacted invoice, PO and missing-receipt or price question to a demo. Ask how the request reaches the responsible site or purchasing contact and how its response stays linked to the packet.

Demonstrate a receipt gap, a commercial amendment awaiting review and a replacement invoice with a superseded version. Confirm the supported document connections, permissions and accounting handoff for your setup. The workflow should keep those paths distinguishable rather than presenting every reply as a match.

The useful demonstration shows source traceability and next-action ownership. Accounting policy, commercial resolution, posting and payment authority remain with the responsible people and systems. The fictional calculations do not claim recovered overcharges, automated payment approval or a verified customer result.

Sources: Buildalytic custom construction workflows