Line-item pushback: what a carrier actually cuts, and what's worth fighting

What this section shows

A carrier's overall denial rate tells you a carrier is tough. It does not tell you where to spend your next negotiation. Line-item pushback breaks that overall number down to the canonical service line, the specific scope of work, so you can see which lines a carrier cuts hardest, how much of that cutting is actually worth re-arguing, and whether the pattern is one location's documentation problem or a network-wide carrier posture.

This is the deepest layer of the Carriers section. It reads: "Here is what State Farm cuts across your network, line by line, and here is how much of that cut you could realistically get back."

Verinode does not file the dispute or draft the argument. It reads the claims, 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 carrier's detail view, not on the main Carriers page itself.

1. 1Open Carriers from the HQ sidebar (hq.verinode.ai/carriers). This is the first pill in the Accounts cluster (Carriers · TPAs · Commercial).
2. 2Click any carrier tile, in the hero row, Slowest Payers, Broadest Network Footprint, Heaviest Pushback, or All Carriers. Clicking opens the carrier detail overlay rather than navigating away.
3. 3Scroll down inside the overlay, past the Verinode Score, the billed/collection/days-to-pay KPIs, Supplement pushback, and (on some networks) Pushback by location. The line-item section sits below all of that, under the heading "What [Carrier Name] cuts across your network."

The same detail overlay and the same line-item section appear on a TPA's detail view (from the TPAs pill), reading "What [TPA Name] cuts across your network." Everything below applies identically to both.

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:

• "[Carrier] has cut $X off your network's supplemented lines." The total dollar amount this carrier has cut across every canonical line with data, not just the lines shown 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 carrier 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 addressable share is the percentage of classified cut dollars that fall into the fightable bucket, calculated across all of this carrier's lines with data on file, not just the six or so lines the page happens to display. That is a deliberate choice: the headline should reflect the carrier's full pattern, not just the 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. 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, e.g. "142 lines."
• Location count, how many of your franchisee locations have submitted this line item to this carrier at all, e.g. "9 locations."
• An "Early signal" chip, when it appears (see below).
• The top denial reason for this line with this carrier, e.g. "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 carrier cut, for this canonical line specifically. Shown in Ember Red when 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 is within a point either way.

This is the line-level version of the same comparison you see at the whole-carrier level in Supplement Pushback. It matters more here because it isolates the comparison to one specific scope of work rather than blending everything the carrier touches, "harder on water mitigation" 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. This reads as a carrier 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 carrier-wide fight.
• 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 page: a systematic cut is worth escalating at the network level (a template fix, a documentation standard, a conversation with the carrier's claims leadership); 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 to clear Verinode's minimum privacy floor for publishing a network-wide number, but not yet enough to be a statistically settled rate. Treat an early-signal line as directional: worth watching, not yet worth walking into a carrier negotiation and citing as a hard number. As more locations submit more of this line item to this carrier, 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/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, 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 is only ever shown 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 carrier at 60%+ addressable is worth investing negotiation time in; one at 15% addressable is mostly enforcing 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 carrier problem, and the fix is training, not escalation.
4. Use the network-vs-industry line to decide how hard to push. A line where you are running well harder than the industry average is where the carrier 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 will firm up as more locations submit that line item to this carrier.

Empty states

The whole section is absent, not blank, when a carrier 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 with this carrier 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/cooperative model, you will see the line and its headline numbers, just without the per-location names, per the disclosure above.

Related reading

• Verinode HQ overview
• Network health
• HQ benchmarks
• Broadcasting to your network

Data sources