Home › Guides

Receive supplier e-invoices without losing AP controls

A structured invoice can arrive correctly and still charge for goods you never received. It can also duplicate a PDF already entered by an AP clerk. Treat delivery as the start of the buyer's process.

Receipt, approval and payment are separate controls Recommended AP controls. A technical response is not commercial approval or authorization to pay. Receipt, approval and payment are separate controls Recommended AP controls. A technical response is not commercial approval or authorization to pay. Receive and retain Original document and delivery evidence Identify and match Supplier, duplicate and order checks Review tax evidence Eligibility and correct accounting period Approve and post Commercial decision and controlled journal Authorize payment Separate bank and payment controls Reconcile and retain Invoice, posting, payment and exceptions

Diagram: Receipt, approval and payment are separate controls. Recommended AP controls. A technical response is not commercial approval or authorization to pay.

Use this guide to turn incoming documents into approved liabilities and controlled payments. Start with the inbound AP control worksheet. Adapt its checks to your buying process and country rules. The workflow below is a recommended control design, not a statement that every jurisdiction requires every approval.

Assign AP as the case owner. Procurement resolves order and price questions, the receiving team confirms quantities, the tax owner approves deduction treatment, and treasury controls payment release. The integration team resolves missing or unreadable documents. Name a person for each role, including a substitute.

Keep separate decisions for separate evidence

Record the incoming document's technical result separately from its purchasing, tax and payment decisions. Avoid one checkbox called "approved" that hides all four.

A technical check establishes whether a document conforms to the applicable format and rules. A commercial check establishes whether your business owes the amount. A tax review establishes the evidence, treatment and claim period. Payment authorization establishes that an approved liability may be included in a payment run to the approved beneficiary.

Set clear release conditions for each decision. If your ERP posts a liability before commercial approval, keep the payment block until the dispute is resolved. If it records an invoice in a staging register first, reconcile that register to posted liabilities. Neither design removes the need to track unresolved documents.

HMRC describes reliable business controls that connect an invoice to the underlying supply using orders, delivery records and independent evidence. It also gives examples of authorization controls. Those principles support retaining purchasing controls after the document channel changes. HMRC, electronic invoicing notice, section 4.4.

Capture the original before transforming it

Save the received structured file, relevant attachments, source channel, arrival time and external identifier. Link the readable rendering to the same case. Preserve the original even if you map descriptions, tax codes or units into ERP fields.

Create a receipt record before attempting automated posting. Give it an internal case ID that survives retries and supplier corrections. A failed conversion must leave an accessible exception rather than a document that appears received at the provider but disappears from AP.

Record the intended buying entity. A network connection used by several group companies does not make their liabilities interchangeable. If the supplier named the wrong buyer, retain the document and request the appropriate correction. Do not repair the legal buyer by editing only the ERP copy.

Treat a supplier's bank instruction as a proposed change. Route it through your existing beneficiary-change approval before payment. Structured data reduces rekeying; it does not authorize a new bank account.

Check duplicates across all receiving channels

Compare incoming records against the staging register, posted invoices, earlier payments and open correction cases. Include the supplier's verified identity, invoice number, currency, amount and date. Use external IDs where available, but do not assume two channels share one identifier.

When an XML invoice and PDF refer to the same charge, link both to one liability. Preserve the duplicate arrival as evidence and stop the second posting. Do not delete a suspected duplicate until AP has checked whether it is a separate installment or valid adjustment.

Handle recurring invoices carefully. Equal amounts and similar descriptions do not prove duplication. Conversely, adding a space to an invoice number must not bypass your review. Keep the supplier's original number and a separate comparison value if your matching process normalizes text.

If a duplicate has already posted, follow your controlled reversal process. Reconcile tax, supplier balance and any payment effect. A payment block alone leaves an overstated liability.

Match the invoice to the purchase

Match the buying entity, supplier, purchase order, currency, price, quantity and receipt evidence. Use line-level matching when the invoice contains items with different outcomes. Record approved tolerances and who can override them.

For services, use the agreed acceptance evidence instead of inventing a goods receipt. The contract owner might confirm a completed milestone or approved time record. For a non-PO invoice, route the expense to the person authorized to accept the charge and assign its accounting treatment.

If an order number is missing, investigate before declaring the charge invalid. You may owe the supplier even though the invoice requires administrative clarification. Keep commercial liability and document completeness visible as separate questions.

Where both parties support it, use the agreed business-response process to communicate the result. Peppol Invoice Response supports states and reasons for business processing, including queries and rejection. The specification recognizes that the same issue can lead to different responses under different buyer processes. OpenPeppol, BIS Invoice Response. Confirm the provider's released profile and receiving capability before relying on that channel.

Decide the tax treatment before claiming

Check the document requirements, supplier status relevant to the transaction, business purpose and deduction restrictions. Record the approved claim period. Keep the expense-accounting decision separate from input-tax eligibility.

Singapore's input-tax conditions include the business and supply requirements and supporting documentation. IRAS also distinguishes import-permit evidence from the supplier invoice and cautions against a duplicate claim on the same import. IRAS, conditions for claiming input tax.

Japan provides another reason to retain a country-specific tax check. Its general input-credit evidence requirements include books and qualifying invoices or records, with defined exceptions. Japan NTA, Tax Answer 6496. Apply the current local rules rather than treating successful network validation as a tax entitlement.

If a supplier's registration changes, record the effective date and investigate the actual supply. Do not apply the supplier's current status indiscriminately to every historical invoice. Escalate uncertain documents to the tax owner and prevent an unsupported automatic claim. Decide any necessary liability or expense accrual separately.

Work a disputed invoice delivered twice

Consider this synthetic example in one fictional currency with a fictional 10% tax rate. The company buys 100 units at 20 net each. The purchase order is 2,000 net. The warehouse accepts 90 units and reports the remaining ten as not delivered.

The supplier sends invoice A-440 for 2,000 net, 200 tax and 2,200 gross through the network. A PDF copy reaches the AP mailbox the next day. Both arrivals concern one invoice. AP links the PDF to the existing case and blocks a second liability.

The company uses a policy that posts the original supplier invoice to a blocked liability while a documented quantity dispute remains open. This is an example policy, not a universal accounting instruction. Procurement confirms that the ten missing units will not be supplied and obtains an authorized credit note for 200 net, 20 tax and 220 gross.

AP preserves the original invoice and posts the credit note against it. The supplier balance is now 2,200 minus 220, which equals 1,980. Net purchase cost is 1,800 and tax is 180. The receiving evidence agrees with 90 units multiplied by 20.

Assume the tax owner confirms that the documents support the full 180 input claim in this period under the fictional rules. Treasury can release 1,980 after the commercial approval and beneficiary check. The case contains two invoice arrivals, one original liability and one credit adjustment. It does not contain two payable original invoices.

If the supplier disputes the shortage, keep the case open with the procurement owner. Decide whether to accrue, post, withhold or make a permitted partial payment under the contract and local rules. Do not fabricate a supplier credit note just to clear the matching exception. Preserve the value in dispute and the undisputed amount separately.

Handle failures that arrive after approval

If the credit note is unreadable, create a document exception and retain the original arrival. Obtain a valid copy through the agreed channel. Do not close the supplier dispute because an email says a credit was sent.

If the original invoice has already been paid, the credit creates a recoverable amount or supplier credit under the approved accounting policy. It does not by itself prove that cash returned. Track the refund or offset separately and confirm its effect on tax.

If the supplier sends a replacement invoice while the original remains active, link both to the same case and obtain the required adjustment evidence. Use the correction guide to coordinate the document chain.

At close, compare provider arrivals with receipt cases, cases with postings, and postings with payment status. Investigate accepted documents missing from AP and AP documents absent from the expected source. Use the reconciliation guide for the period-level evidence.

Release and close the case

Close the AP case when the original and related documents are retrievable, the buying entity and supplier are confirmed, duplicates are resolved, and commercial approval is evidenced. Record the tax decision, posting IDs, payment authorization and any outstanding refund or offset.

Keep an exception open if a required decision is still missing. Assign the next action and date rather than allowing a case to remain indefinitely "on hold." Review unresolved age and value with procurement and the tax owner.

Before automating further, test the controls against the disputed-invoice example, a changed supplier registration and a repeated delivery. Verify your actual ERP edition and provider behavior. The master-data readiness guide and Peppol implementation checklist provide the setup checks that support this daily process.

Source verification date: 17 October 2026.

Worksheet: Inbound AP control and exception worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use one receipt case for each supplier charge, with linked records for repeated arrivals and adjustments. Follow the inbound AP guide.

Identify the receipt

Preserve the original before mapping. Link repeated PDF and XML arrivals to the same case when they represent one invoice.

Record separate decisions

For each decision, record outcome, reviewer, date and evidence. Use a precise pending or exception state when a decision is incomplete.

  1. Technical validity and successful import: ____
  2. Buying-entity and supplier identity match: ____
  3. Duplicate review across receipt, posting and payment populations: ____
  4. Order, price, quantity and receipt match, or authorized non-PO approval: ____
  5. Tax-document eligibility, claim amount and claim period: ____
  6. Accounting posting and any accrual or adjustment: ____
  7. Payment authorization and approved beneficiary: ____

Do not release payment because technical validation passed. Record supplier bank changes in the separately approved master-data process.

Open an exception

Preserve the distinction between an administrative query and a dispute over the underlying supply. Do not create an invented supplier credit to clear a match.

Check the synthetic quantity dispute

The guide assumes a fictional 10% tax and a policy of posting disputed invoices to a blocked liability.

For a real case, record the applicable accounting and tax policy before using this sequence.

Close or carry forward

AP decision and date: ____

Tax decision and date: ____

Payment authorization and date: ____

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.