Supplier Invoice Currency Mismatch Rate

A supplier quotes an invoice in one currency while the purchase order or vendor record expects another, and the mismatch may be legitimate, such as a contract amendment, or a data-entry error that changes the payable amount. Supplier invoice currency mismatch rate measures how often this exception appears among invoices checked.

Separate invoice currency from functional currency, since every foreign-currency invoice can be correctly recorded in the buyer's functional currency and the metric concerns agreement between commercial documents, not the mere presence of a foreign currency. Choose the authorised reference, because the signed contract, approved purchase order and accepted amendment may each specify a currency, and an old vendor default should not override a newer binding agreement.

Check the contract version, since an amendment may change the billing currency from a named effective date and the delivery or service period should be reviewed before marking an invoice wrong. Check the supplier entity too, because a parent group may have subsidiaries that invoice in different currencies and the invoice must be matched to the correct legal supplier and purchase order.

Define the eligible population by including supplier invoices subject to a purchase order, or describe a separate rule for non-purchase-order invoices, and count credit notes and intercompany items separately where needed. Set the unit of counting, since one invoice with five mismatched lines should generally count once in an invoice-level rate while a line-level metric answers a different question.

Store an ISO currency code or another explicit agreed identifier, because dollar signs are ambiguous across countries. Distinguish billing from settlement, since a contract may allow invoices in one currency and bank payment in another at an agreed conversion rule, and those are different controls.

If the invoice and purchase order currencies differ, stop automatic matching and seek the agreed source before payment rather than silently converting one side. Preserve the original currency amount as issued and record any accounting conversion separately, which keeps the commercial claim traceable.

Track the initial submission, because counting only unresolved invoices understates how often mismatches occur, and also report how many were corrected before posting, deduplicating documents so a revised invoice that replaces the original does not create an extra exception. Classify the cause, since common causes include stale purchase order settings, supplier template errors, an unrecorded contract amendment or the wrong supplier entity, and assess materiality by reporting count and value separately because a small invoice can still reveal a recurring control gap.

Review the matching workflow, since automation that treats a currency mismatch as a numerical variance may approve a document on a misleading converted value; under IFRS, IAS 21 addresses initial recognition and later translation of foreign-currency monetary items, but its accounting rate guidance does not decide which invoice currency the supplier was entitled to use. Use a clear exception route in which the supplier corrects the invoice or an approved purchase order change is obtained, and avoid paying first and fixing evidence later.

Monitor trends by supplier, buyer and category, because a cluster in one region may indicate a configuration problem rather than widespread supplier noncompliance. Treat the rate as a control signal, not proof of overbilling, and resolve the document hierarchy and contract terms before judging whether the supplier made an error.