Jump to a section
A correctly priced invoice can sit unpaid because the customer portal expects a purchase order line number. The sales team had the PO in an email, fulfilment delivered the order and billing entered only the header reference. The rejection starts upstream of accounts receivable.
Test one order as the buyer would
Compare invoice instructions with the actual PO. Check the buyer entity, PO number, line reference, authorised quantity and remaining value. If one PO covers several shipments, track the amount already billed. Ask who can issue an amendment before billing a delivery that exceeds the remaining authority.
Retain the submission evidence
Store the portal acknowledgement or rejection alongside the invoice. Assign the missing information to its owner and retain the corrected submission reference. Reviewing rejection reasons by buyer can show where a small change in order-entry instructions would prevent repeated manual follow-up.
The field validation stage in eInvoice360 is a practical place to check the PO references the buyer expects.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



