UAE eInvoicing AP three-way matching: purchase orders, goods receipts and duplicate payment controls
Published · Official source links reviewed in the project as of 22 October 2026; relevant amendment text separately reviewed on 23 October 2026 · 13 min read
A supplier invoice can arrive through an electronic exchange successfully and still be wrong for payment. Perhaps the supplier billed 100 units when only 80 arrived. Perhaps the agreed price was AED 45 but the invoice says AED 54. Or perhaps the same invoice entered the payable ledger twice through different channels. These are procurement and payment-control problems, not merely electronic document-delivery problems.
This guide explains how an accounts payable (AP) team can compare a purchase order, evidence of receipt and a structured Electronic Invoice before authorising payment. It concentrates on the controls after intake, rather than repeating our Recipient obligations guide, invoice intake workflow or discrepancy workflow. All figures in the examples below are illustrative, not statutory thresholds.
1. Legal requirements versus recommended AP controls
Verified regulatory context: Article 6(3) of Ministerial Decision 243/2025 requires a Recipient to process Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System. Article 6(7) addresses fulfilment of Article 6 obligations through appointment of an Accredited Service Provider. Decision 197/2026 amends the underlying decision. The Ministry of Finance eInvoicing programme provides the official programme context.
Recommended business control, not an asserted eInvoicing law: three-way matching, duplicate-payment scoring, internal approval matrices, exception queues, payment holds and the illustrative tolerances below are operational safeguards. We have not identified a provision in the verified eInvoicing decisions that universally requires every buyer to use three-way matching or a particular approval threshold. An invoice being received through the system does not, by itself, establish that goods were received, prices were agreed or a bank transfer is approved.
Businesses should separately assess VAT, accounting, contractual, procurement and record-retention requirements with qualified advisers. For the official implementation timetable see Decision 244/2025 and its Decision 66/2026 amendment; this page does not attempt to restate category deadlines.
2. Define the three records before matching
The purchase order (PO) records what the buyer authorised: supplier, contracting entity, item or service, agreed quantity, unit price, currency, delivery terms and relevant tax treatment. A PO is not proof of delivery. The goods receipt or service acceptance record records what was actually delivered or accepted, including the date, quantity, condition, receiving employee and any rejection. A delivery note alone may be insufficient if nobody verified it.
The supplier invoice records what the supplier requests to be paid. The AP team should retain the structured document identifier and exchange references supplied by its system or provider alongside the accounting record. The document's exchange status and the internal payment status must remain separate fields. The official MoF Electronic Invoicing Guidelines provide programme guidance; this article does not claim that every proposed ERP field is mandatory under that document.
For non-PO expenditure such as utilities, subscriptions or emergency services, create an explicitly approved alternative control using a contract, service confirmation and delegated budget approval. Do not fabricate a PO or mark a nonexistent goods receipt as complete just to clear an exception.
3. Match at line level, not only invoice total
Start with the supplier and purchasing legal entity, then locate the correct PO and receipt. Compare item identifiers or descriptions, units of measure, quantities, unit prices, discounts, currency, tax amounts and totals. Where a single PO has several deliveries, match each invoice line against the remaining accepted quantity, not the original PO quantity. Where several invoices draw down the same PO, subtract previously invoiced and approved quantities to avoid overbilling.
A useful control calculation is available billable quantity = accepted quantity minus quantity already invoiced and approved, adjusted for returns or corrections. For price checks, compare the invoice unit price with the agreed price after documented discounts and authorised amendments. A total-only check can conceal a price overcharge offset by an unrelated undercharge. Differences in units, such as boxes versus individual pieces, require an approved conversion factor rather than an arbitrary numerical comparison.
Store the comparison result for each line: exact match, within approved tolerance, unmatched receipt, unmatched PO, quantity excess, price variance or ambiguous supplier identity. An invoice may contain both matched and disputed lines; whether partial payment is permitted is a contractual and company-policy decision, not a feature assumed to exist in the eInvoicing exchange.
4. Example: a partial delivery and quantity mismatch
Illustrative case A: A buyer orders 100 office chairs at AED 300 each. The warehouse accepts 80 chairs and records 20 as not yet delivered. The supplier invoices 100 chairs for AED 30,000 before any tax adjustments. The accepted quantity supports only AED 24,000 at the agreed price. The remaining AED 6,000 is unsupported by the receipt.
AP should hold the unmatched portion or the entire payment according to company policy, link the invoice to the 80-unit receipt, and ask procurement to confirm whether the missing 20 units are in transit, rejected or cancelled. If the supplier corrects the billing, keep the original invoice, relevant credit note or replacement documentation, communication and resolution history together. Do not silently alter the received structured invoice to make it match the PO. For correction concepts and limits of verified Article 6 rules, see the credit notes and price adjustments guide.
5. Example: an incorrect price despite full delivery
Illustrative case B: A service PO authorises 40 hours at AED 250 per hour. The project owner confirms all 40 hours, but the invoice uses AED 275 per hour. The invoice is AED 11,000 while the approved baseline is AED 10,000, a difference of AED 1,000 before any applicable tax adjustments.
Receiving the service does not approve a higher rate. AP should check for an authorised change order dated and approved under company policy. If none exists, record a price exception and route it to the contract owner. Avoid letting the person who requested the service approve an undocumented rate change and release the payment without independent review. If a valid contract amendment exists, update the controlled PO reference and preserve the amendment evidence rather than bypassing the match.
6. Design duplicate-invoice and duplicate-payment checks
Run duplicate checks before posting and again before generating a payment file. Exact matching can use a normalised supplier identifier, purchasing entity, supplier invoice number and document type. Normalisation should remove harmless spacing and case differences without destroying meaningful punctuation or leading zeros. A second, risk-based check can compare amount, currency, invoice date, PO, receipt, supplier bank account and similar invoice-number patterns.
Never rely on invoice number alone: different suppliers may reuse the same sequence, while one supplier may send a corrected document or a credit note that legitimately references an earlier invoice. Conversely, a repeated invoice can arrive under a different internal import ID. Preserve both the source document identity and any ERP posting ID. A duplicate flag is a reason for investigation, not automatic proof of fraud or an instruction to delete a valid record.
Illustrative case C: Supplier A sends invoice INV-1048 for AED 8,500. It enters through the ASP feed and is also manually keyed from an emailed copy. The records have different ERP document numbers but share supplier identity, invoice number, currency and gross amount. The second entry should be held while AP determines whether it represents the same liability. If one entry has already been paid, block another payment, document the investigation and use a controlled accounting correction where appropriate.
7. Separate approval of purchases, invoices and payments
Segregation of duties reduces the chance that one person can invent a supplier, approve a purchase, confirm delivery, change bank details and pay the resulting invoice. A workable division assigns supplier-master changes to an authorised data owner, purchase approval to a budget holder, goods receipt to a receiving team, invoice matching to AP and payment release to a separate treasury or finance approver.
Small organisations may not have enough employees for complete separation. Compensating controls can include independent periodic reviews, dual authorisation for bank-detail changes, restricted system permissions and a second person's review of payment batches. Record who performed each action and when. These are recommended governance measures; they are not represented here as a universal approval matrix imposed by the UAE eInvoicing legislation.
Bank-detail changes deserve special handling. Verify a request using an independently known contact channel, not solely the email or telephone number supplied in the change request. Hold the first payment after a high-risk change until the verification record is complete. Compare the final payment file with the approved payable register and investigate any additions, altered beneficiaries or changed amounts.
8. Establish tolerances without hiding material errors
Define tolerances by purchase category, risk and delegated authority. For example, a company might allow a small rounding difference on low-value supplies but require explicit approval for every rate change on consulting services. Tolerances should be documented, periodically reviewed and applied consistently. There is no verified UAE eInvoicing rule in the cited decisions setting the illustrative thresholds below.
An internal policy could treat a rounding difference of AED 1 as low risk while escalating a 5% unit-price increase, but those figures are examples only. Evaluate both percentage and absolute differences: a 1% variance on a large contract may be more significant than a 10% variance on a minor purchase. Never automatically waive a discrepancy simply because a total falls below a threshold if the supplier identity, bank details or receipt evidence is suspicious.
Maintain a record of policy version, exception reason, override approver and the underlying calculation. Review frequent tolerance overrides by supplier and employee. Repeated small exceptions may reveal a systematic mapping error, outdated contract pricing or intentional splitting of invoices to evade approval limits.
9. Manage exceptions through a controlled queue
Give each mismatch a unique case identifier, owner, severity, opening date and next action. Typical categories include missing PO, missing receipt, excess quantity, wrong unit price, incorrect supplier, duplicate candidate, disputed tax treatment and unresolved credit note. Assign procurement to commercial terms, receiving teams to quantities, tax specialists to tax questions and AP to ledger reconciliation. An exception should not disappear merely because the invoice is older than a target date.
Set internal service targets based on business needs and supplier agreements, not on invented statutory acceptance or payment deadlines. Keep technical document statuses separate from commercial acceptance, invoice booking and payment approval. If the document itself requires correction, follow the established supplier and ASP process; our exception handling FAQ and discrepancy workflow cover those branches in more detail.
Where a credit note arrives, link it to the original liability and check whether it reduces an open balance or relates to an amount already paid. Prevent both a supplier refund and a deduction from a later payment from clearing the same adjustment twice. For recurring problems, update supplier onboarding checks and the PO master data rather than repeatedly applying manual overrides.
10. Keep an audit trail that reconstructs the decision
An auditor or internal reviewer should be able to reconstruct why a particular invoice was paid, held or corrected. Preserve the original structured document and its reference, the PO version, accepted receipt or service confirmation, matching results, exception communications, credit-note links, approval history, payment batch reference and bank confirmation where available. Use access controls and retention settings consistent with applicable requirements and company policy.
The record-keeping discussion in our archiving guide addresses the verified Article 11 context following Decision 197/2026. This article does not invent a separate legal retention period for PO matching evidence. The audit readiness checklist helps teams review completeness, while the month-end reconciliation guide addresses ledger-to-document differences.
For management reporting, consider the proportion of invoices matched automatically, unmatched quantity and value, duplicate candidates investigated, overrides by reason, average exception age and payments released after supplier-master changes. Measure resolved cases separately from cases merely closed administratively. A dashboard should improve investigation, not encourage staff to clear legitimate exceptions without evidence.
11. Implement and test the control before go-live
Map the current PO, receipt, invoice and payment data sources. Identify who owns supplier identifiers and how one invoice is represented across the ASP feed, integration layer and ERP. Agree a duplicate key and define what happens when a field is missing. Design a controlled fallback for genuine non-PO invoices. Test with finance, procurement, warehouse, IT and treasury rather than treating this as an AP-only software configuration.
Use realistic test cases: partial deliveries, multiple receipts for one PO, split invoices, wrong currencies, changed prices, credit notes, repeated imports, leading-zero invoice numbers, supplier bank changes and payment-file resubmissions. Confirm that an exchange retry does not automatically create a second payable. Record expected and observed outcomes, owners and defects. Our go-live testing checklist, master data guide and supplier onboarding guide provide companion implementation steps.
12. Frequently asked questions
Is three-way matching legally mandatory for every UAE Electronic Invoice?
Not on the basis of the verified eInvoicing provisions cited here. It is a recommended internal control. Other laws, contracts or sector rules may impose separate requirements that need independent assessment.
Can we pay an invoice before all goods have arrived?
That depends on the contract, authorised advance-payment arrangements and company policy. A partial-delivery mismatch should not be concealed by falsely marking the receipt complete.
Does a successful ASP exchange status mean the invoice is approved for payment?
No. Technical exchange and internal commercial approval are different decisions. Keep them as separate statuses and require the applicable internal checks before release.
What if a supplier sends the same invoice twice?
Flag the candidate using supplier identity and document references, investigate whether it is a true duplicate, and prevent a second payable or payment while the case is unresolved. Preserve evidence rather than deleting records without a trace.
How should a credit note affect the match?
Link it to the relevant original invoice and PO or receipt adjustment. Recalculate the remaining liability and verify whether the original invoice has already been paid. Follow the documented correction process instead of editing the source document silently.
What about subscriptions and other non-PO purchases?
Use a documented alternative such as contract verification, service-owner acceptance, budget approval and independent payment release. Label it as a non-PO exception rather than manufacturing missing evidence.
Are our tolerance percentages prescribed by the Ministry of Finance?
No such universal percentages have been verified in the referenced eInvoicing decisions. Tolerances in this article are illustrative policy choices and should be approved internally.
13. Official sources and unresolved questions
Primary official references: MoF Decision 243/2025; MoF Decision 197/2026; MoF Decision 244/2025; MoF Decision 66/2026; MoF programme hub; MoF amendment announcement; FTA awareness announcement. The source links provide regulatory context, not government endorsement of the matching methodology.
Not confirmed: This guide has not verified any mandatory UAE eInvoicing three-way-match algorithm, government-prescribed duplicate-detection key, invoice acceptance/rejection deadline, universal payment-approval threshold, supplier bank verification procedure or required ERP matching fields. Do not infer such rules from our examples. Verify technical capabilities with your ASP and the current official specifications, and check contractual, tax and accounting questions with appropriate professionals.
Disclaimer: This is an educational operational guide, not legal or tax advice. It distinguishes cited regulatory provisions from recommended internal controls. Requirements and guidance can change; consult current official publications and qualified advisers before making compliance decisions.