Topic Pillar

PO Matching

Purchase order matching sounds straightforward until invoices arrive with quantity variances, partial deliveries, or split line items across multiple POs. For construction and wholesale businesses, these edge cases are the rule, not the exception. This pillar covers where PO matching workflows break in real Xero and MYOB environments, what two-way matching misses, and how teams build tolerances and exception rules that actually stick.

5 articles | Maintained by Pulsify

What this pillar covers

  • Two-way PO matching in Xero and MYOB: how it works and where it fails
  • Construction-specific PO matching challenges: progress claims and retentions
  • Tolerance rules, partial matching, and exception handling
  • Building scalable PO matching workflows for high-volume operations

All articles in this pillar (5)

Browse by category →

Frequently asked questions

What is the difference between two-way and three-way matching?
Two-way matching compares the invoice to the purchase order. Three-way matching adds the goods receipt. Two-way suits businesses that check price and quantity against the PO before payment without a separate receipting step.
Why does PO matching break in practice?
It breaks on the edge cases: quantity variances, partial deliveries, and line items split across multiple POs. Header totals can match while the lines do not, so matching only the totals lets overcharges through.
What are tolerance rules in PO matching?
Tolerance rules set how much an invoice can differ from the PO before it is flagged, for example a small percentage on price or quantity. They let minor, expected differences pass while genuine variances are held for review.

Ready to automate your AP?

Go beyond capture and basic workflows. Pulsify codes, validates, routes, and syncs every invoice automatically.