What a TPA cuts across your network: line-item pushback (fixable vs structural)

What this section shows

A TPA's overall denial rate, the headline number in Supplement Pushback, tells you a TPA is cutting hard. It does not tell you where to spend your next conversation with that TPA, or whether the pattern is one location's documentation habit or the TPA's standing posture. Line-item pushback breaks the overall cut down to the canonical service line, the specific scope of work, so you can see which lines this TPA cuts hardest, how much of that cutting is realistically worth re-arguing, and whether it shows up at every location serving that line or just one.

This is the deepest layer of a TPA's detail view. It reads: here is what this TPA cuts across your network, line by line, and here is how much of that cut you could plausibly get back.

Verinode does not file the dispute or draft the argument. It reads the supplements and decisions that have already flowed in from your franchisees' jobs, resolves each line item to a canonical service code, and surfaces the pattern. Your team decides which fights are worth having.

Where to find it

Line-item pushback lives inside a TPA's detail view, not on the main TPAs page itself.

1. 1Open Accounts from the HQ sidebar under the Revenue group. That link lands on the Carriers tab.
2. 2Click the TPAs pill to switch to hq.verinode.ai/tpas.
3. 3Click any TPA tile, in the hero row, Slowest Payers, Broadest Network Footprint, Heaviest Pushback, or All TPAs. Clicking opens the TPA detail overlay rather than navigating away.
4. 4Scroll down inside the overlay, past the Verinode Score and the billed / days-to-pay / collection-rate / avg-fee KPIs, past Supplement Pushback, and (on networks where it applies) past Pushback by location. The line-item section sits below all of that, under the heading "What [TPA Name] cuts across your network."

The same section, with identical mechanics, appears on a carrier's detail view, reading "What [Carrier Name] cuts across your network." See Line-item pushback on a carrier if you're comparing a carrier and a TPA side by side, everything in this article applies the same way there.

The headline: total cut and addressable share

Above the line list sits one sentence that frames everything below it. It reads two ways depending on what data is available:

• "[TPA] has cut $X off your network's supplemented lines." The total dollar amount this TPA has cut across every canonical line with data, not just the lines listed below.
• "Y% of that pushback is addressable (documentation or pricing you can re-argue), the rest is structural policy."

This second sentence is the point of the whole section. Not every dollar a TPA cuts is fair game to fight. Verinode classifies each denial reason behind a cut as either something you can push back on, missing documentation, a pricing dispute, an omitted photo, or something you generally cannot, a coverage exclusion, a depreciation schedule, a policy limit the TPA is simply administering on the carrier's behalf. The addressable share is the percentage of classified cut dollars that fall into the fightable bucket, calculated across every one of this TPA's lines with data on file, not just the six or so lines the section happens to display. That is a deliberate choice: the headline should reflect the TPA's full pattern, not just its biggest lines.

The per-line list

Below the headline, up to six canonical service lines are listed, the ones with the largest dollar amount cut, largest first. A line only earns a spot if the TPA has actually cut something on it, lines with zero cutting don't appear here even if the TPA processes them. Each line is a single row with several pieces of information stacked together.

Line name and volume. The bold text at the top of the row is the canonical service name, for example "Water mitigation, Category 3" or "Drywall removal and replacement." Underneath it, in smaller type:

• Line count, how many individual line items on jobs across your network resolved to this canonical service, for example "142 lines."
• Location count, how many of your franchisee locations have submitted this line item through this TPA at all, for example "9 locations."
• An Early signal chip, when it appears (see below).
• The top denial reason for this line with this TPA, for example "Missing moisture readings," followed by a fixability tag in parentheses:

- (Fixable), shown in Expand green, denials rooted in documentation or process, the kind a better submission fixes. - (Negotiable), shown in Maintain yellow, denials that are arguable but require actual back-and-forth, pricing disagreements, scope disputes. - (Structural), shown in muted gray, denials rooted in the policy itself, coverage exclusions, depreciation, limits. These are not going to move no matter how good the paperwork is.

Cut rate and cut dollars, at the right edge of each row:

• Cut rate, the percentage of this line's submitted dollars that this TPA cut, for this canonical line specifically. Shown in Ember Red once it reaches 40% or higher.
• Cut, the actual dollar amount cut on this line, shown on wider screens.

Network vs. industry. Underneath the row, when Verinode has enough industry reference data for this line, a sentence compares your network's cut rate on this specific line against the national cut rate for that same line:

• "[X]pp harder than the industry ([Y]% cut rate nationally, [Z] obs)." in Ember Red, when your network is cut harder than the industry average by more than one percentage point.
• "[X]pp softer than the industry ([Y]% cut rate nationally)." in Expand green, when your network does better than the industry average by more than one point.
• "In line with the industry ([Y]% cut rate nationally)." when the gap sits within a point either way.

This is the line-level version of the same comparison the top of the overlay shows for the TPA's overall denial rate. It matters more here because it isolates the comparison to one specific scope of work rather than blending everything the TPA touches, "harder on drywall" is a more useful fact than "harder overall."

Systematic vs. isolated. On networks where per-location detail is unlocked (see below), a final line under each row reads how widely this cutting is spread:

• "Cut by N of M locations: systematic across your network." when every location serving this line has had it cut through this TPA. This reads as the TPA's posture, not a submission-quality problem at any one franchisee.
• "Cut by N of M locations: isolated, likely a submission-quality gap." when only one location (or none) among several is getting cut. This reads as a coaching opportunity at that one location, not a fight with the TPA.
• No qualifying phrase when the pattern falls in between, more than one location cut but not all of them, just the raw "Cut by N of M locations" count.

This is the single most actionable read on the section: a systematic cut is worth raising with the TPA relationship directly, a documentation standard, a photo checklist, a moisture-reading protocol, whatever the top denial reason implies; an isolated cut is worth a one-on-one conversation with that franchisee about their submission process.

The "Early signal" chip

A line can wear an Early signal chip next to its location and line counts. This means the line has enough locations and enough line items behind it to clear Verinode's minimum privacy floor for publishing a network-wide number at all, but not yet a wide enough sample to be a statistically settled rate. Treat an early-signal line as directional: worth watching, not yet worth walking into a TPA conversation and citing as a hard number. As more locations submit more of this line item through this TPA, the sample grows and the chip drops off once the line is well established. Verinode does not expose the specific location or line-item counts behind this threshold, only the qualitative early-versus-settled distinction.

Per-location detail: who is actually eating the cut

Whether you see named locations behind each line depends on your network's entity model, the ownership structure Verinode has on file for your group:

• Multi-location and enterprise networks (locations you directly own and operate) see the full per-location breakdown behind every line, which of your locations are getting this line cut through this TPA, and at what rate and dollar amount each.
• Franchise associations and cooperatives (independently owned member businesses) see the network aggregate only. A note at the bottom of the section reads: "Per-location line detail is shown only for networks that own their locations' data. Your network sees the aggregate above." This is the same privacy boundary that runs through every part of HQ: franchisees own their own business data, and HQ never gets a name-level view into an independently owned member's numbers just because they're part of your network.

Even on networks with per-location detail unlocked, an individual line's location breakdown only ever shows once enough distinct locations are behind it to protect any single franchisee from being identifiable by elimination. A line submitted by too few locations to clear that floor is left out of the six lines shown entirely, not shown with a thin, de-anonymizing breakdown.

How to use this in a real conversation

A practical sequence:

1. Check the addressable share in the headline. A TPA at 60%+ addressable is worth investing conversation time in; one at 15% addressable is mostly administering carrier policy you will not move.
2. Scan for lines marked systematic. Those are candidates for a network-wide documentation standard, a template photo checklist, a required moisture-reading protocol, whatever the top denial reason implies, rather than a per-job fight.
3. For lines marked isolated, take it to that one franchisee. It is very likely a submission-quality gap at that location rather than a TPA-wide problem, and the fix is training, not escalation.
4. Use the network-vs-industry line to gauge how hard to push. A line where your network is running well harder than the industry average is where the TPA has room to soften; a line already in line with the industry is a weaker argument.
5. Treat Early signal lines as a heads-up to watch, not yet as ammunition, they firm up as more locations submit that line item through this TPA.

Empty states

The whole section is absent, not blank, when a TPA has no canonical-line cut data on file. There is no dedicated "no line-item data yet" message inside the overlay; the layout simply skips from whatever section comes before it straight to Per-franchisee participation. As franchisees bill more jobs through this TPA and Verinode's nightly aggregator resolves more line items to canonical service codes, lines populate on their own, no manual entry required.

If a line clears the network-level floor for appearing at all but your network is in the association or cooperative model, you will see the line and its headline numbers, just without the per-location names, per the disclosure above.

Related reading

• TPAs overview, the full TPAs page this detail view opens from.
• Line-item pushback on a carrier, the same mechanics on the carrier side.
• HQ TPA rate transparency, how your network's accepted TPA rate terms compare against the industry.
• Verinode HQ overview
• Network health
• HQ benchmarks
• Broadcasting to your network

Data sources