What Is Invoice Processing?

By Sharon Watkins, Founder and CEO, RadiusPoint · 2 September 2026 · 12 min read

Invoice processing for telecom and utility spend is the six-station run that takes a billing account number from receipt to a coded pay-or-hold decision. A shared AP mailbox that keys a header total does not do that work. The bill can still pay a circuit that died last quarter.

Invoice processing is the operating sequence that receives a vendor invoice, captures every line, tests those lines against live inventory and contracted rates, codes the general ledger, and either pays the clean lines or holds the exceptions. Generic accounts-payable software parses a PDF. This page is the Telecom Expense Management (TEM) and Utility Expense Management (UEM) version of the job: RadiusPoint analysts working inside ExpenseLogic against carriers, energy providers, and wireless accounts. It is not an OCR buyer’s guide, and it is not a retelling of invoice-audit services.

Perry D. Wiggins, writing in CFO.com from APQC’s database of 1,485 organizations, put top-quartile AP cost at $2.07 per invoice or less, the median at $5.83, and the bottom quartile at $10.00 or more. Those are cross-industry supplier invoices. A telecom or utility invoice that fails inventory match is not a $2.07 problem. It is a billed service that may not exist. RadiusPoint’s published path is two-day invoice processing on ExpenseLogic, with named analysts on the exceptions.

Key Takeaways

Invoice processing for TEM and UEM is a six-station run: receive, capture, inventory, rate, allocate, and pay or hold. Header OCR stops at station 2.
APQC, via Perry D. Wiggins in CFO.com, puts median AP cost at $5.83 per invoice across 1,485 organizations, with the top quartile at $2.07 or less and the bottom at $10.00 or more.
RadiusPoint’s published FAQ path is two-day invoice processing. ExpenseLogic stores the BAN, the service ID, and the GL code on the same record.
Processing is the run from inbox to GL. An invoice audit is the test of whether the bill is true. They share a file. They are not the same page.
A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one after the processed file and the inventory disagreed. Processing produced the file. The fail produced the cash.

The Short Version

Invoice processing for TEM and utility spend is a six-station run from BAN receipt to a coded pay-or-hold. If you cannot name the service ID, the contracted rate, and the hold queue, you are keying bills, not processing them.

Invoice processing is the run from inbox to GL
How is invoice processing different from an invoice audit?
The Six-Station Invoice Run
How much should a telecom or utility invoice cost to process?
Why do carrier and utility invoices break generic AP matching?
What two-day processing looks like on ExpenseLogic
Processing, allocation, and the accrual file

The Six-Station Invoice Run. Processing is the run from inbox to GL. Audit is the test of whether the bill is true.

Invoice processing is the run from inbox to GL

Invoice processing for telecom and utility spend is the monthly run that turns a carrier invoice into a coded general-ledger file. A repository that stores PDFs is useful for audit later. It does not tell accounts payable whether this month’s MRC still belongs to a live circuit inside ExpenseLogic. The operating object is the invoice line, not the folder.

RadiusPoint has sold this as software plus people since 1992. ExpenseLogic is the platform. Named analysts work every line against contracted rates and against inventory, rather than sampling. That model is the commercial page for telecom expense management. This article is the processing layer sitting under that service: how the BAN lands, how the file is built, and how a hold is a feature.

Generic AP pages teach receipt, OCR, two-way match, and payment. They treat a telecom invoice like a box of copier paper. The paper has a PO. The circuit has a service ID, a tariff or MRC, a location, and a disconnect duty. If your process ends when the PDF is parsed, you have finished the short station and skipped the long ones.

How is invoice processing different from an invoice audit?

Invoice processing is the operational run that receives, captures, codes, and pays or holds every TEM and utility invoice line. An invoice audit is the test that scores those same lines against contract, inventory, and usage so a fail can be disputed. They share a file. They do not share a job description, a KPI, or a page on this site.

The old guide on invoice audit owns the method for catching errors. Invoice auditing services is the commercial offer. Invoice audit versus three-way match owns the comparison with PO matching. This page owns the six stations that have to run even when the audit is quiet. You can process a clean bill. You cannot audit a bill you never ingested.

A three-way match asks whether PO, receipt, and invoice agree. A TEM or UEM invoice often has no PO. The “receipt” is a live circuit, a spinning meter, or a mobile line on an HR roster. Processing that still pretends the PO is the third document will code a total and miss the dead ID. RadiusPoint’s run keeps the ID on the line before anyone touches the GL.

If a team says they “process and audit” as one verb, ask which queue holds the exceptions. If there is no hold queue, they are paying to clear the inbox. That is processing with the audit switched off.

The Six-Station Invoice Run

The Six-Station Invoice Run is RadiusPoint’s map of a TEM or utility invoice from inbox to GL, and generic AP OCR stops at parse. Station 1 receives the BAN. Station 2 captures every line. Station 3 tests inventory. Station 4 tests rate. Station 5 allocates. Station 6 pays the clean lines and holds the rest. That six-station map is the first information-gain element on this page.

RadiusPoint stores the invoice image inside ExpenseLogic and retains vendor, BAN, service ID, period, and amount on the same record. An analyst does not re-key a header to make AP’s calendar look busy. The run is the product.

A pass is six stations populated. A parsed PDF with none of those stations after capture is not a pass. Utility Expense Management (UEM) runs the same six stations at meter level, not account level. Wireless runs them at phone number and Employee ID.

Six stations. Generic AP OCR stops at parse. RadiusPoint runs all six.

How much should a telecom or utility invoice cost to process?

A telecom or utility invoice should be judged on whether the six stations finished, not on whether AP beat $5.83. APQC’s median of $5.83, top quartile of $2.07, and bottom quartile of $10.00 measure generic supplier invoices across 1,485 organizations, as Perry D. Wiggins reported for CFO.com. Those quartiles are still the figures 2026 AP automation summaries repeat. They do not measure a BAN with 400 circuit lines.

RadiusPoint does not publish a dollar-per-invoice processing fee on this page. The published operating fact is two-day invoice processing, claimed on the company FAQ, run by named analysts on ExpenseLogic. That is the TEM version of cycle time: receipt to a coded file, with holds parked. It is not a promise that every carrier PDF becomes a $2.07 event.

A carrier invoice that fails station 3 is not a cheap process problem. It is a billed service that may not exist. Wiggins also split industries: distribution and transportation sat at $1.14 at the median, consumer products at $4.58, public sector at $9.43. Telecom and utility invoices behave more like the complex end of that list, because the third document is inventory, not a packing slip.

This APQC-versus-TEM comparison is the second information-gain element on this page. Category AP cost is a useful ceiling for paper and PO invoices. It is a misleading target for a wireless BAN.

Why do carrier and utility invoices break generic AP matching?

Carrier and utility invoices break generic AP matching because the third document is live inventory, not a purchase order, on that ID. The unit price sits on a service ID that changes when people, sites, and circuits move. Two-way match can agree that the vendor and the total look familiar. Four hundred lines can still be wrong.

A MACD that closed in the field and never hit the invoice is the classic break. The processing run has to see last cycle’s disconnect before it codes this cycle’s MRC. A vacant meter is the UEM version: the site is closed, the tariff is not. Vacant utility cost recovery is what you do after processing keeps presenting the same account. A wireless line that outlived the employee is the mobility version. Processing that cannot see the HR roster will keep coding the MRC to a cost center that no longer has that person.

Taxes, surcharges, and credits sit on the same invoice as the MRC. Generic OCR is built to find a total. RadiusPoint’s capture station is built to keep those as separate lines so station 4 can score the rate and station 6 can hold a tax that does not belong. How to audit a utility bill owns the meter-level test. This page owns the fact that the test never starts if the bill never left the inbox as lines.

Vendor format drift is not a side quest. Carriers change PDF layouts. Portals timeout. EDI feeds drop a BAN. Station 1 is a receipt discipline: one inbox per BAN, daily missing-bill reporting, and a named owner when the file does not land. Without that, AP discovers the invoice when the late fee does.

What two-day processing looks like on ExpenseLogic

Two-day invoice processing on ExpenseLogic is RadiusPoint’s published cycle from receipt to a coded file, with named analysts closing exceptions instead of AP keying headers. Day one is receive and capture. Day two is inventory, rate, allocate, and the pay-or-hold split. Clean lines move. Dirty lines stay visible.

RadiusPoint is ISO 9001 certified since 2002. Amalgam Insights named RadiusPoint a Distinguished Vendor on the 2024 TEM Vendor SmartList. The Capterra listing sat at 4.8 from 31 reviews through December 2025. A capability statement and the about page carry the firm facts. Credentials tell you the operator is real. The six stations tell you the invoice is being used.

The published proof sits downstream of a processed file that failed a later test. A Fortune 100 manufacturer recovered $450,000 in telecom refunds in year one, then $850,000 in ongoing annual savings, a $1.3 million year-one impact. Inventory work recovered $174,000 in re-credits when services did not match the bill. One line of unneeded toll-free numbers ran $18,000 a year. Contract rate optimization recovered $120,000 a year. Those are GREEN figures from RadiusPoint’s proof library. They are not a processing-fee menu. They are what happens when stations 3 and 4 are allowed to fail in public instead of disappearing into a paid total.

You keep budget approval. RadiusPoint keeps the queue. A letter of agency is what lets RadiusPoint pull the invoice or talk to the carrier when station 1 needs a portal and station 6 needs a dispute. Scope it. A read-only billing grant is not ordering rights.

Processing, allocation, and the accrual file

Invoice processing is unfinished if the validated line has no cost center, and it is dishonest if a late bill has no accrual. Station 5 applies location, department, and GL to a validated line that already passed inventory and rate.

A telecom accrual file is what finance books when the BAN did not land in time. Paying a guessed total in week four so the close looks clean is how last year’s error becomes this year’s budget.

Allocating telecom and utility costs across departments is the downstream job once the line is correct. Split-billing a circuit across cost centers is a processing rule, not a spreadsheet afterthought. Closed-location exception reports are a processing output: the site is in the real-estate feed as closed, the invoice is still in station 1. A multi-location client stopped $1,500 a month, $18,000 a year, on utilities at closed locations. That number is GREEN. It only appears after processing keeps the location on the line.

Daily missing-bill reporting belongs in station 1, not in a month-end panic. RadiusPoint’s TEM build includes that report. The data a TEM provider needs before day one is the BAN list, the inventory, the GL map, and the HR or site feed that stations 3 and 5 will use. If onboarding skips those, you have bought OCR. The TEM implementation timeline is the calendar for standing the six stations up. The station names do not change because a tool vendor sold you capture.

Organizations implementing TEM typically see 15 to 30 percent cost reduction in year one. That range is a category observation, not a RadiusPoint guarantee. The operating fact on this page is narrower. If station 6 has no hold queue, you will pay the 15 to 30 percent right back out.

APQC measures generic supplier invoices. A telecom or utility invoice that fails inventory match is a billed service that may not exist.

How we researched this

We fetched the live RadiusPoint invoice-processing page on 2 September 2026 and compared it with generic AP and OCR explainers. Those pages own capture, two-way match, and cost-per-invoice. They do not own a six-station run built for BANs, circuit IDs, meters, and mobile lines, and they do not split APQC’s $2.07 / $5.83 / $10.00 quartiles (Perry D. Wiggins, CFO.com, 1,485 organizations) from a TEM two-day path. Proof numbers come only from the RadiusPoint Master Intelligence 2026 GREEN list and hedged AMBER category ranges. No affiliate relationships. No named-competitor ranking.

FAQ

Can OCR software replace a TEM invoice processor?

OCR can capture a header and many line fields. It cannot, by itself, prove a circuit is still live, score an MRC against a contracted rate table, or hold a tax line while an analyst files. RadiusPoint’s work starts where the parse would have succeeded and the inventory would still have failed. Buy capture if you need capture. Do not call capture a six-station run.

Who should own invoice processing when IT and facilities both buy services?

Finance should own the dollar decision and the GL. IT or facilities should confirm the service is still needed. A named operator should keep the BAN inbox and the hold queue. RadiusPoint will be that operator on an ExpenseLogic engagement. If three departments can buy and nobody can say which BAN is late, you do not have invoice processing. You have three inboxes.

Do we pay exceptions to hit the close, or hold them?

Hold them. Station 6 exists so the close can book an accrual on a late or disputed BAN instead of paying a guessed total. RadiusPoint’s two-day path is built to get clean lines into the file fast enough that the hold queue is a real queue, not a graveyard. Paying to clear exceptions teaches the vendor that the error posts.

How long should we keep telecom and utility invoices?

Keep the image, the line file, and the exception log for the same retention window your auditors already require for AP, commonly three to seven years in the U.S. ExpenseLogic stores the image against the service ID so a later dispute still has the line, not a box of paper. Retention is not processing. Processing is what makes the retained file worth opening.

Does invoice processing include wireless bills?

Yes. Wireless invoices run the same six stations at phone number and Employee ID. Managed mobility services is the service wrap around that run: staging, help desk, and offboard. This page owns the invoice path, including wireless BANs that land next to wireline and utility files in the same month-end.

What to do before the next invoice cycle

Pick one carrier BAN and one utility account. Write the six stations down the left side of a page. Fill what last month’s file actually contains. If capture has a total and inventory has a blank, that is the operating gap. RadiusPoint will fill those stations for a managed ExpenseLogic engagement. Every cycle you pay without them is a cycle the $10.00 invoice can keep.

Latest Updates

2 September 2026: In-place AEO rewrite of the live invoice-processing URL. Stats limited to GREEN and hedged AMBER: APQC $2.07 / $5.83 / $10.00 from Perry D. Wiggins in CFO.com (1,485 organizations), industry medians $1.14 / $4.58 / $9.43, RadiusPoint two-day processing (FAQ), Fortune 100 $450,000 / $850,000 / $1.3 million, $174,000 re-credits, $18,000 toll-free, $120,000 rate optimization, closed locations $1,500 / $18,000, category 15 to 30 percent hedged, ISO 9001 since 2002, Capterra 4.8 / 31, Amalgam Insights 2024 Distinguished Vendor. Distinct from Invoice Audit 1-3. Slug unchanged.

References

Metric of the Month: Accounts Payable Cost | Perry D. Wiggins, CFO.com, APQC data from 1,485 organizations
Telecom Expense Management Services | RadiusPoint
Utility Expense Management | RadiusPoint
Managed Mobility Services | RadiusPoint
ExpenseLogic | RadiusPoint
Invoice Auditing Guide for SMBs and Enterprises | RadiusPoint
Invoice Auditing Services | RadiusPoint
Invoice Audit vs Three-Way Match | RadiusPoint
The MACD Process in Telecom Expense Management, Explained | RadiusPoint
Vacant Cost Recovery: The Utility Bills Nobody Is Watching | RadiusPoint
How to Audit a Utility Bill for Errors | RadiusPoint
Why Your TEM Provider Asks for a Letter of Agency | RadiusPoint
What a Telecom Accrual File Is, and How Finance Teams Build One | RadiusPoint
Allocating Telecom and Utility Costs Across Departments | RadiusPoint
The Data a TEM Provider Needs Before Day One | RadiusPoint
How Long a Telecom Expense Management Rollout Actually Takes | RadiusPoint
Capability Statement | RadiusPoint
About RadiusPoint | RadiusPoint
Sharon R. Watkins | RadiusPoint
ExpenseLogic reviews | Capterra

Disclaimer

This article is general information for finance, IT, procurement, and facilities teams processing telecom, utility, and wireless invoices. It is not legal, tax, or accounting advice. Outcomes cited are from specific RadiusPoint client engagements already in the published proof library and are not a guarantee of future results. Category-level ranges from APQC and from TEM industry research are hedged and are not RadiusPoint promises. Invoice processing on this page is distinct from RadiusPoint’s Invoice Auditing Services, telecom audit services, and invoice-audit-versus-three-way-match pages.

Invoice Processing for Telecom and Utility Spend