The network TPA summary: total TPAs, billed volume, admin fees, days-to-pay

What this header is

The TPAs page is where Verinode HQ rolls up every third-party administrator (TPA) your franchisees deal with, one row per TPA across the whole network rather than one row per franchisee relationship. A TPA is the company a carrier hires to actually process and pay a claim on its behalf, so a TPA relationship carries both a payment cycle, like a carrier does, and an administrative fee that a carrier relationship typically does not. The header at the top of the TPAs page, the hero, is a single glance at the network's overall standing with TPAs: how many TPAs the network deals with, how much has been billed and collected through them, what they charge to administer that volume, and whether they pay on a reasonable clock or drag their feet.

Verinode does not negotiate TPA fees or chase payment on your behalf. It reads the jobs, invoices, and payment records franchisees have already recorded, rolls them up nightly into a network-level summary, and lays out the pattern. Leadership decides what to do with it: an admin fee worth questioning, a payment cycle worth watching, or nothing at all if the numbers look healthy.

This article covers the header only. The rows beneath it (Slowest Payers, Broadest Network Footprint, Heaviest Pushback, and the full TPA list) are their own surfaces and are not covered here.

Where to find it

Open Accounts from the HQ sidebar, at hq.verinode.ai/tpas. Accounts sits in the Revenue band of the sidebar, alongside Reputation and Sales & Marketing. It carries three pills across the top of the page, in a rounded capsule strip: Carriers · TPAs · Commercial. TPAs is the second pill; clicking it is a real navigation to /tpas, not an in-page swap, so a bookmark or a shared link always opens straight to this page with the TPAs pill already highlighted. Carriers and Commercial are separate surfaces with their own rows and their own version of this header.

The header is the first thing on the page, above the Slowest Payers, Broadest Network Footprint, Heaviest Pushback, and All TPAs rows further down.

How the numbers get here

Nothing on this header is entered directly by HQ. Every figure is rolled up nightly from franchisee-recorded jobs, billing, and fee terms into a network-level summary table, one row per canonical TPA, so the same TPA recorded with slightly different spellings by different franchisees still rolls up to a single row, not several. HQ never sees which specific franchisee's job produced which dollar; it sees only the TPA-level totals, counts, and averages that summary produces. That privacy boundary is what makes the small-cohort rule described further down necessary.

Reading the headline number

Total TPAs. The large number at the top left is the count of distinct TPAs the network has billed at all, rolled up across every franchisee. This is not a spend figure and not a franchisee count, it is a catalog size: how many separate TPA relationships the network is managing across the board.

Above the number, the eyebrow reads "Network TPAs."

The pill beside the headline

A pill sits beside the headline number showing the count of TPAs served by more than one franchisee, for example "4 multi-franchisee." This is the negotiating-leverage read: a TPA that multiple franchisees already work with independently is one where the network's combined volume gives HQ more standing in any conversation about that TPA's fees or payment practices than any single franchisee has alone.

If the network has zero TPAs with more than one franchisee serving them, the pill reads "No data yet" in a neutral tone instead.

The summary line

Under the headline, a sentence assembles whichever of these facts are available:

• Total jobs, 36 months. How many jobs, across the whole network, have gone through any TPA in the last three years, for example "96 jobs in the last 36 months."
• Jobs, last 30 days, appended when there has been recent activity, for example "· 7 in the last 30d." Omitted when there has been no TPA activity in the last 30 days.
• Top TPA, the name of the TPA with the highest network-wide billed total, for example "· top: Alacrity."
• Hidden count, when the network has TPAs served by only one franchisee, a trailing note reads "N hidden as single-franchisee." See the privacy section below for why.

If the network has zero TPAs recorded, none of this line appears. Instead the panel shows the cold-start empty state described further down.

The three supporting figures

To the right of the headline, three figures sit in a row, each with a label, a value, and a supporting sub-line. They animate in with a brief count-up on page load.

Billed 36mo

What it is. The sum of every TPA's network billed total over the trailing 36 months, the network's full TPA-administered revenue exposure.

What you see. A dollar figure (for example $940k), formatted compactly (millions as "M", thousands as "k"). Underneath, a sub-line shows the network total collected over the same window (for example "$820k collected") when collections data exists, or the plain description "Network total billed" when there is nothing to compare it against yet.

What it means. This is the top-line size of the network's TPA-administered business. Reading billed against collected side by side is the first check on whether the network is actually getting paid what it bills through TPAs, not just billing it.

Avg admin fee

What it is. The average administrative fee TPAs charge across the network, averaged across every TPA that has fee data on file, not weighted by job volume the way days-to-pay is below. One TPA with a single high fee and one with a single low fee pull this average evenly, regardless of how many jobs run through either.

What you see. A dollar figure (for example $180). Underneath, a sub-line reads "Awaiting fee data" when no franchisee has recorded a TPA fee yet, or "Averaged across reporting franchisees" once at least one TPA has a fee on file.

What it means. TPAs typically charge one of three fee structures: a flat dollar amount per job, a percentage of the claim, or a per-claim fee. This figure blends whatever structures your network's TPAs actually use into a single dollar read, so it's a rough temperature check on administrative cost, not a precise like-for-like comparison. For the fee structure behind any individual TPA, see that TPA's own row in the All TPAs list further down the page, where the fee shows with its structure labeled (flat, percentage basis, or per-claim), or open TPA rate transparency for the fuller rate-by-rate read against industry benchmarks.

Avg days-to-pay

What it is. The network-wide average number of days between billing a TPA and being paid, weighted by job volume so a TPA with many jobs pulls the average more than a TPA with few. This is not a simple average of each TPA's own average, it is weighted so the number reflects where the network's actual job volume sits.

What you see. A plain day count (for example 41 days). Underneath, a sub-line reads:

• "Awaiting payment data" when no jobs have recorded a days-to-pay value yet.
• "Inside 30-day target" when the network average is 30 days or under.
• "Across paid jobs" when the average is over 30 days, a plain statement of what the number covers without a judgment call baked into the text.

What it means and its color bands. The pill beside the headline and this figure's color follow the same three-tier tone, based on the network-weighted average:

• 30 days or under reads in the Expand tone (green). The network is being paid inside a healthy, standard window.
• 31 to 60 days reads in the Maintain tone (yellow). Payment is slower than ideal but not yet a structural problem, worth watching.
• Over 60 days reads in the Analyse tone (red). This is a genuine drag on network cash: TPAs taking more than two months on average to pay is worth a direct conversation, either with the slowest TPAs individually (see the Slowest Payers row below the header) or as a policy question for the network as a whole.

When there is no payment data at all, the figure shows as a neutral dash rather than any of the three colors, since there is nothing yet to judge.

Cold-start: no TPA data yet

If the network has zero TPA relationships rolled up anywhere, the headline reads 0, the pill reads "No data yet," and the summary line reads:

"TPA data will appear as franchisees record TPA-administered claims."

All three supporting figures show as zero or dashed placeholders with their own "awaiting data" sub-lines: Billed 36mo shows "Network total billed" with no collected figure, Avg admin fee shows "Awaiting fee data" with a neutral dash, and Avg days-to-pay shows "Awaiting payment data" with a neutral dash instead of a colored number. Nothing is broken, there is simply nothing to roll up yet. This is expected for a newly onboarded network or one where franchisees haven't yet recorded a TPA-administered job in Verinode.

The privacy boundary: single-franchisee TPAs are hidden

Verinode HQ never lets leadership infer a specific franchisee's business from a network aggregate. A TPA worked with by only one franchisee is a special case: showing that TPA's name and figures by itself would tell HQ, by elimination, exactly which franchisee works with it and how much, even though HQ never sees a per-franchisee ledger. That is a privacy leak dressed up as a network statistic.

To prevent it, any TPA row served by too few distinct franchisees is withheld from every TPA-level view on this page, including the rows beneath the header (Slowest Payers, Broadest Network Footprint, Heaviest Pushback, All TPAs). This guard applies to networks made up of independently owned franchise locations. It does not apply to a network configured as a single legal entity operating multiple locations, where there is no separate-owner privacy boundary to protect in the first place, every TPA row is visible regardless of how many locations serve it.

When TPAs are withheld this way, the summary line adds the trailing note "N hidden as single-franchisee" so leadership knows the visible rows reflect a filtered catalog, not the network's complete TPA list. The network-wide totals in the three supporting figures (billed, collected, the admin fee average, and the weighted days-to-pay average) are computed across every TPA the network has, hidden or not; only the identifying rows further down the page draw from the filtered set.

How to use this header

1. 1Check total TPAs and the multi-franchisee pill first. They tell you the shape of the network's TPA book, broad and diffuse, or concentrated on a handful of shared TPAs.
2. 2Read billed against collected in the same glance. A large gap between the two is worth a look at the Slowest Payers row and the individual TPA rows in the full list further down.
3. 3Weigh the avg admin fee against what those TPAs are actually collecting for the network. A rising average fee against flat or falling billed volume is worth a fee-terms conversation, ideally armed with the industry comparison on TPA rate transparency.
4. 4Treat avg days-to-pay as the network's collective pulse, not a single TPA's report card. If it reads Analyse (red), open the Slowest Payers row to see which specific TPAs are driving it before drawing conclusions about the whole network.
5. 5Watch the hidden count over time. As it shrinks, more of the network's TPA relationships are shared across franchisees, which is what makes network-wide TPA conversations meaningful in the first place.

A different question: the industry-wide Carriers & TPAs benchmark

The header described in this article answers "how is our network doing with the TPAs our franchisees actually work with." A separate surface, the Carriers & TPAs tab on the Benchmarks page (hq.verinode.ai/benchmarks), answers a different question: how does any TPA in Verinode's industry-wide research catalog behave across the whole market, independent of whether your network works with it at all. That tab draws on anonymized peer benchmarks contributed network-wide, not on your franchisees' own billing history. See Carriers & TPAs tab in network view for that surface.

Related articles

• The Accounts cluster: Carriers, TPAs, and Commercial
• Reading the carrier network header
• TPA rate transparency
• HQ overview
• Network health
• HQ benchmarks

Data sources