Goods Receipt and Invoice Differences in Utility Purchasing
A receipt-invoice difference needs a factual explanation before it needs a correction. Review what was ordered, what arrived and what the supplier billed as separate questions.
Goods Receipt and Invoice Differences in Utility Purchasing
Distinguish a quantity discrepancy from a price discrepancy and from a timing difference. Each points to different evidence and may involve a different owner.
Distinguish the physical event from the accounting record of that event. Goods may have arrived without a complete receipt record, or a document may have been entered before the receiving team has resolved a discrepancy. Ask the operational owner to confirm what actually happened. A matched set of system references is useful evidence, but it should not replace the underlying receiving or service confirmation.
Put the method into practice
- Compare purchase order, receipt and invoice references.
- Confirm the physical delivery with the receiving team.
- Route the difference according to its cause.
Follow a purchasing item across the whole process before blaming one stage. The requisition, purchase order, receipt, invoice and payment can each contain a different part of the explanation. Keep their references connected in the review. A discrepancy that appears in finance may have started with an unclear description or an incorrect quantity much earlier.
An illustrative situation
A supplier may invoice the full order while only part has arrived. That is different from an incorrect unit price on a complete delivery, even if both create a blocked item.
Give exceptions a specific route rather than a general instruction to contact purchasing. Quantity differences, price questions, missing approvals and supplier-master changes need different owners. Include enough context for the next person to act without repeating the investigation. This reduces the temptation to bypass a control simply because the queue is difficult to understand.
The mistake worth avoiding
Do not enter a balancing receipt solely to clear an invoice. The receipt should reflect an actual confirmed event.
Evaluate a proposed improvement using both routine and awkward purchases. A stocked item, a non-stock item and a service can create different handoffs. Include partial delivery, cancellation and a returned item in the test set. A process that handles only the cleanest purchase is not ready to be treated as the standard for all utility work.
Check the surrounding process
Compare like with like when reviewing maintenance costs. A planned estimate, a purchase commitment and a posted actual amount do not describe the same stage of activity. Keep them distinct in the discussion and explain the date of the information. Otherwise an apparent saving may simply be an invoice that has not arrived, or an apparent overrun may reflect a changed scope.
Measure data quality through the decisions and processes it supports. A completeness percentage can look impressive while a small number of wrong relationships causes repeated corrections. Track the errors that interrupt work or undermine reporting, and prioritize those causes. Avoid collecting additional fields solely to improve a dashboard statistic.
Separate preparation, review and resolution in the status record. A task can be prepared but not reviewed, or reviewed with open questions. Calling all of those states complete removes useful information. Define the evidence required for final acceptance and keep unresolved items assigned to someone who can actually make the next decision.
The next practical step
Keep a discrepancy record with the evidence, cause, agreed resolution and affected documents.
Related reading
Service Entry Evidence for Utility Contractors; Utility Materials Master Data: Avoiding Duplicate Items; Utility Inventory Count Differences: Finding the Cause.