By Sharon Watkins, Founder and CEO, RadiusPoint
Controllers use a TEM GL interface file to turn a month of audited telecom charges into one pre-coded batch the ERP can post in minutes, instead of a stack of invoices someone keys by hand. The file is the finished output of telecom expense management (TEM): every charge has already been checked line by line, mapped to a general ledger account, and tagged to a cost centre. By the time it reaches your close, the coding decisions are done and the disputes are flagged. What lands in the ERP is a reviewed subledger feed, not a pile of PDFs.
Key takeaways
- The GL interface file is the audited product of TEM, not an invoice dump. Each line carries the billing account number, service period, amount, GL account, and cost centre.
- It belongs early in the close, after the audit finishes and before journals lock, so telecom posts alongside every other subledger.
- Clean lines flow straight through; exception lines route to an accrual or a hold, so one disputed charge can’t stall the close.
- RadiusPoint generates the file from ExpenseLogic after line-item audit, so your team posts a reviewed file rather than coding carrier bills.
The short version: an audited, pre-coded GL file lets you post telecom like any other subledger. Clean lines flow through, exceptions get handled on the side, and the work that makes the file trustworthy (the audit and the coding) happens before it ever reaches your ERP.
What’s Actually Inside a TEM GL Interface File
A TEM GL interface file lists every audited telecom charge with its billing account number, service period, amount, GL account, and cost centre for posting.
Start with the fields, because they’re what make the file postable. Each row typically carries the billing account number (BAN), which is the carrier’s account identifier and the anchor for tracing a line back to its source invoice. Alongside it sit the service period the charge covers, the audited amount, the GL account it maps to, and the cost centre or allocation string your organization uses to push spend to the right department, location, or entity.
The file separates into two kinds of rows, and controllers should treat them differently. Clean lines are charges that passed audit and matched contract, plan, and inventory. They’re ready to post with no human touch. Exception lines are charges that failed a check: a rate that doesn’t match the agreement, a service billed after disconnection, a new line nobody ordered, a credit still pending. These don’t get suppressed. They get marked so finance can decide whether to accrue, hold, or post with a note.
Where the GL File Lands in Your Close Calendar
Controllers load the GL file early in the close, after the audit finishes but before journals lock, so telecom posts with other subledgers on time.
Timing is where a good file earns its keep. Telecom is a recurring, high-volume expense that arrives on the vendor’s schedule, not yours, so it has a habit of showing up late and forcing a last-minute manual journal. Placing the feed deliberately fixes that. Below is a Close-Calendar Placement Map most finance teams can adapt to their own cycle.
| Close stage | What happens with the TEM feed |
|---|---|
| Before close opens | Audit completes on the prior month’s invoices; the GL file is generated and delivered to finance. |
| Early close | Clean lines import and post to the telecom accounts and cost centres; the file is balanced to source invoices. |
| Mid close | Exception lines are reviewed; late or disputed charges are accrued or held with a documented reason. |
| Before journals lock | Telecom subledger ties out; any adjusting entries are booked and the version is archived. |
| Post close | Resolved exceptions and vendor credits carry into the next period’s file. |
Handling Accruals and Exception Lines Without a Pile of Manual Journals
Clean lines post straight to the general ledger; exception lines route to an accrual or hold, so the close isn’t blocked by one disputed charge.
This is where the interface and the accrual do different jobs, and it’s worth being precise. The interface file is the posting mechanism for real, audited spend in the period. An accrual is your estimate for spend that belongs to the period but isn’t cleanly billable yet, usually because an invoice is late or a charge is under dispute.
A well-built feed supports both. Clean lines give you the confirmed base. Exception lines give you the accrual candidates, already itemized, so your accrual isn’t a round-number guess. Instead of accruing “telecom, roughly the usual,” you accrue the specific held lines with their amounts and reasons attached. When the dispute resolves or the credit posts, it flows through a later file and the accrual reverses against something concrete.
Balancing matters here too. Before anything posts, the file should tie to the source invoices it was built from, so the total you book reconciles to what carriers actually billed, net of audited adjustments. That reconciliation is what lets you sign the close knowing the telecom line is defensible, not approximated. RadiusPoint’s invoice auditing services are what produce that audited base in the first place, which is why the exception lines are trustworthy rather than arbitrary.
The Controls That Keep the TEM Feed Trustworthy
Feed controls cover versioning, balancing to source invoices, restricted access, and a named coding owner, so the file you post is the file you audited.
A GL feed is only as good as the controls around it, because it writes directly into your books. Use a TEM Feed Control Checklist and run it every period:
- Versioning. Every generated file is versioned and archived. If a correction is needed, you produce a new version rather than editing the posted one, and you can always show which file backed which journal.
- Balancing. The file totals reconcile to source invoices and to the amounts audited before import. No line posts that can’t be traced to a BAN and a service period.
- Access. Only named roles can generate, approve, and import the file. The person who audits isn’t automatically the person who posts.
- Coding owner. One owner is accountable for the GL account and cost-centre mapping. When the mapping changes, that owner signs off before the next file uses it.
The mapping itself is set up once and maintained deliberately, not reinvented monthly. Most of that structure gets defined during onboarding, when your chart of accounts and cost-centre logic are captured. If you want to see what that setup involves, RadiusPoint documents the inputs in its TEM onboarding data requirements, and the sequence in its TEM implementation timeline.
How RadiusPoint Produces a GL-Ready File from ExpenseLogic
RadiusPoint produces the file inside ExpenseLogic after line-item audit, mapping each charge to your chart of accounts, so your team posts instead of coding.
Here’s the part that separates a real GL feed from a spreadsheet export. RadiusPoint audits every invoice line first: rate against contract, service against inventory, plan against usage. Only then does ExpenseLogic assemble the audited charges into a file coded to your GL accounts and cost centres. The output is GL-ready because the review and the coding are already finished by the time it’s generated.
ExpenseLogic covers telecom, wireless, and utility expense management (UEM) on one platform, so the same audited-then-coded logic applies across all three categories and lands in a consistent file rather than three different formats. That single unified feed is easier to control and easier to reconcile.
And it’s software plus people, not software alone. The platform builds and balances the file, but a RadiusPoint analyst works the account, resolves disputes with carriers, and confirms the exception lines make sense before the file reaches finance. Automation handles the volume; a named human handles the judgment. That combination is what lets your controller treat telecom as a clean subledger instead of a monthly investigation.
Frequently Asked Questions
Is the GL interface file the same as an accrual?
No. The interface file posts confirmed, audited spend for the period. An accrual estimates spend that belongs to the period but isn’t cleanly billable yet. The file’s exception lines feed the accrual, so your estimate is itemized rather than a round number.
Doesn’t AP automation already do this?
AP automation routes and pays invoices, but it approves recurring telecom charges by default because there’s usually no purchase order or goods receipt to match against. It doesn’t audit the line against contract, plan, or inventory. The TEM feed adds that audit and the GL coding before anything posts.
What happens when our GL structure or cost centres change?
The coding owner updates the mapping and signs off before the next file uses it. Because the mapping lives in ExpenseLogic and is versioned, the change is applied once and carries through every future file, rather than being re-keyed each month.
Who signs off on the cost-centre coding?
A single named coding owner on the finance side is accountable for the GL account and cost-centre mapping. RadiusPoint proposes the mapping from your chart of accounts during onboarding, and your owner approves it, so accountability stays in-house.
How far before close should the file arrive?
Ideally before the close opens, so clean lines post early and exceptions get worked mid-close rather than at the deadline. The earlier the audited file lands, the less telecom shows up as a last-minute manual journal.
The Verdict
A TEM GL interface file is what lets a controller stop treating telecom as a monthly fire drill and start treating it as a subledger. Audited lines, pre-coded to your accounts and cost centres, post like everything else. Exceptions get accrued or held with specifics attached. The file balances to source and stays versioned, so the close is defensible. RadiusPoint builds that file from ExpenseLogic after a real line-item audit, which is the difference between posting numbers you trust and coding invoices you hope are right. If you’re evaluating whether a provider can deliver a genuinely GL-ready feed, the questions to ask a TEM provider are a good place to start.