Three-way matching confirms that an invoice agrees with a purchase order and a goods receipt. An invoice audit confirms that the charge itself is contractually correct and that the service being billed still exists. The two do different jobs, and recurring services such as telecom, wireless and utilities fall through the gap between them because they generate no purchase order and no receipt to match against.
This is why organizations with mature accounts payable automation still find six-figure billing errors when someone finally audits their carrier invoices. The AP system was never wrong. It processed, coded and paid exactly what it was designed to process, code and pay. It simply had no mechanism to ask whether a circuit billed at a location closed eighteen months ago should have been on the invoice at all.
Key Takeaways
- Three-way matching validates process integrity. An invoice audit validates charge legitimacy. Neither substitutes for the other.
- Recurring services have no purchase order and no goods receipt, so the match has nothing to compare against and defaults to approval.
- The reference data for auditing recurring spend is an inventory of record, and it has to be built and maintained rather than generated by a transaction.
- Two-way matching, used widely for recurring invoices, checks the invoice against the purchase order only, which removes the delivery check entirely.
- The practical fix is a validation layer between invoice receipt and AP entry, not a replacement of the AP system.
What Three-Way Matching Checks
Three-way matching is a control designed for procured goods. It compares three documents and blocks payment where they disagree.
| Document | Answers the question | Created by |
|---|---|---|
| Purchase order | What did we agree to buy, at what price, in what quantity? | Procurement, before delivery |
| Goods receipt | What actually arrived, and how much of it? | Receiving, at delivery |
| Supplier invoice | What is the supplier charging us? | Supplier, after delivery |
When all three agree within tolerance, the invoice pays. When they do not, an exception routes for review. It is an effective control against duplicate billing, quantity inflation, price variance against an agreed purchase order, and paying for goods never received. It is a control on the transaction.
Three-way matching asks whether the invoice matches the paperwork. An invoice audit asks whether the paperwork was ever right.
Where the Match Breaks for Recurring Services
A monthly telecom, wireless or utility invoice has a fundamentally different shape from a purchase order for a thousand laptops. There is no discrete order event, no delivery, and no receipt. Organizations typically respond by using a blanket purchase order for the annual spend, or by dropping to two-way matching, or by exempting the category from matching altogether and routing invoices straight to an approver.
| Matching approach used for recurring services | What it still catches | What it cannot catch |
|---|---|---|
| Blanket purchase order plus three-way match | Spend exceeding the annual blanket amount | Any error inside the blanket, which is where nearly all of it lives |
| Two-way match, invoice against purchase order | Gross price variance against the order | Services that no longer exist, rate reversion, misapplied surcharges |
| Non-purchase-order invoice with approval workflow | Whether a named person clicked approve | Everything, unless that person reads line items against a contract |
| Variance thresholds against prior month | Large sudden jumps | Errors that have been billing steadily for years, which look like the baseline |
That last row is the quiet one. Variance-based controls define correct as consistent with last month. A circuit that has been billing for a disconnected service since 2023 is perfectly consistent every month, so it never triggers an exception. Consistency is not accuracy.
What an Invoice Audit Adds
An invoice audit substitutes different reference data. Instead of a purchase order and a receipt, it validates against the contract, the rate table and an inventory of what services actually exist.
| Three-way match | Invoice audit | |
|---|---|---|
| Question asked | Does this invoice agree with what we ordered and received? | Is this charge contractually correct for a service that exists? |
| Reference data | Purchase order, goods receipt | Contract and rate table, inventory of record, tax jurisdiction rules |
| Reference data source | Generated automatically by the transaction | Built manually, then maintained through every change |
| Granularity | Invoice or line level against order lines | Individual charge level, including taxes and surcharges |
| Catches | Duplicates, quantity and price variance, undelivered goods | Ghost services, rate reversion, ex-employee lines, misapplied fees, unapplied credits |
| Outcome when it fails | Payment blocked | Dispute filed with the supplier and pursued to credit |
The critical row is the third. Three-way matching works at scale because the purchase order and the receipt are produced as a by-product of buying and receiving. Nothing produces a telecom inventory as a by-product. Somebody has to construct it from carrier records and keep it current through every move, add, change and disconnect, which is the entire reason telecom expense management exists as a separate discipline rather than an AP module.
How RadiusPoint Closes the Gap
RadiusPoint operates the validation layer that sits between invoice receipt and accounts payable entry, delivered through ExpenseLogic, its proprietary cloud-based platform. ExpenseLogic maintains the contract rate table and the inventory of record, tests every invoice line item against both before the invoice reaches AP, and routes exceptions to RadiusPoint analysts who file disputes directly with carriers and utility providers. Validated charges are allocated to cost center, location and general ledger account, then delivered into the client’s ERP and accounts payable systems as a coded file. The AP system continues to do what it does well, which is process, approve and pay, and it receives invoices that have already been proven correct.
The design point is that this is additive rather than a replacement. Organizations do not rip out AP automation to audit telecom invoices. They insert a category-specific validation step ahead of it.
A Worked Comparison
Consider a single monthly carrier invoice containing a data circuit at a branch office that closed the previous year, a wireless line belonging to an employee who left in March, and a rate that reverted to list price when the master agreement renewed.
- Under three-way matching against a blanket purchase order: the invoice total sits inside the annual blanket, so it matches and pays. Three errors survive.
- Under two-way matching: the invoice is compared to the blanket order value. No line-level rate check exists, so the reverted rate passes. Three errors survive.
- Under variance monitoring: the closed-site circuit and the ex-employee line have billed consistently for months, so no variance is flagged. The rate reversion may show as a modest increase, and whether it is investigated depends on the threshold. Two to three errors survive.
- Under a line-item invoice audit: the circuit fails the inventory check because the site is closed, the wireless line fails because the employee record is terminated, and the rate fails against the contracted rate table. Three disputes are filed, and the underlying records are corrected so the charges do not recur.
Every control in the first three scenarios worked exactly as designed. Designed correctly is not the same as designed for this.
Why the Gap Persists in Well-Run Finance Functions
This is not a maturity problem. Organizations with clean controls, tight month-end close and well-configured AP automation carry the same exposure, and the reasons are structural rather than procedural.
| Structural cause | Consequence |
|---|---|
| Ownership is split | IT owns the service, finance owns the invoice, procurement owns the contract. Nobody owns the reconciliation between them. |
| The invoice is large and the lines are small | A six-figure monthly invoice is reviewed at total level. The error is a small recurring circuit charge inside four thousand line items. |
| Errors are stable | Anything that has billed consistently reads as the baseline, and baselines are not questioned. |
| The reference data does not exist | Even a diligent reviewer cannot validate a charge without knowing what services should be there. |
| Controls are designed for fraud and duplication | Both are real risks, but neither describes a service that was correctly ordered, correctly billed, and should have been disconnected two years ago. |
The last row is the important one. The dominant failure in recurring service spend is not an incorrect charge. It is a correct charge for something that is no longer needed, which no matching control is designed to detect because from the supplier’s side nothing is wrong.
What to Do About It
The practical steps are unglamorous and sequential.
- Identify which spend categories are exempt from meaningful matching. In most organizations this is telecom, wireless, utilities, waste, freight and some facilities services. Together they are usually a larger share of spend than anyone expects.
- Establish reference data for the largest of them. An inventory of record is the prerequisite. Without it, no validation is possible regardless of tooling.
- Insert validation before AP, not after. Catching an error after payment converts it into a recovery problem with a dispute window attached. Catching it before payment is simply a corrected invoice.
- Measure the right thing. Track line items validated as a share of total, disputed dollars filed versus credited, and inventory accuracy. Recovery dollars alone will flatter year one and alarm year two.
- Decide who operates it. The work is ongoing and specialist. Our guide to outsourced telecom expense management covers the build-versus-buy decision, and invoice auditing services covers how providers differ by category.
For background on the matching controls themselves, the general accounts payable literature is thorough and freely available, and the Institute of Internal Auditors publishes guidance on control design and testing that applies directly. For the mechanics of the telecom-specific audit, see telecom audit services.
Frequently Asked Questions
What is the difference between an invoice audit and three-way matching?
Three-way matching compares an invoice against a purchase order and a goods receipt to confirm the transaction is consistent. An invoice audit compares the charges against contracts, rate tables and a record of what services exist, to confirm the charges are legitimate. Matching is a payment control; auditing is a billing accuracy control.
Does three-way matching work for telecom invoices?
Not meaningfully. Recurring telecom services generate no discrete purchase order or goods receipt, so organizations use blanket orders, two-way matching or approval-only workflows. All three pass line-level errors through unexamined.
If our AP automation is strong, do we still need invoice auditing?
Yes, for recurring service categories. Strong AP automation ensures invoices are processed correctly and efficiently. It does not verify that a billed service still exists or that the rate matches a contract, because it has no reference data for either.
What is two-way matching?
Two-way matching compares the invoice against the purchase order only, omitting the goods receipt. It is commonly applied to services and recurring charges where there is nothing to receive, which removes the delivery verification step entirely.
Can we build an inventory of record ourselves?
Yes. It requires obtaining customer service records from each carrier under a letter of agency, reconciling them against invoices and site lists, and then maintaining the result through every move, add, change and disconnect. The construction is a project. The maintenance is the hard part.
Where should the validation step sit in the process?
Between invoice receipt and accounts payable entry. Validating before payment turns an error into a corrected invoice. Validating after payment turns the same error into a dispute against a finite carrier window.
Does this apply to utility and waste invoices as well?
Yes, and for the same structural reason. Utility and waste invoices bill for recurring service with no purchase order or receipt, and their reference data is a tariff schedule and a meter or container inventory rather than an order document.