Why some carriers are aggregate-only: the privacy boundary

What this page is

Verinode HQ is the network intelligence layer that sits above the franchisees, locations, or members already running their own book of business in Verinode IQ. Accounts > Carriers is where HQ leadership sees the network's posture toward every insurance carrier its franchisees serve: how much is billed and collected, how fast each carrier pays, and how much of the supplement work it cuts. It answers "how is Carrier X treating our network," not "how is Franchisee Y doing with Carrier X." That second question belongs to the franchisee, not to HQ, and it is exactly the line this article is about.

HQ is not a job-management, CRM, or accounting tool, and it never becomes one on the Carriers page. Franchisees own their own business data. HQ only ever sees what has been rolled up into network-level counterparty rows, and even those rows are withheld when showing them would let HQ work out, by elimination, which single franchisee is behind a number. The rest of this article walks through exactly where that line sits: what gets hidden, what gets shown only as a network total, and what changes depending on the kind of network you run.

Where to find it

Open Accounts from the HQ sidebar, then the Carriers pill (the tab strip reads Carriers · TPAs · Commercial) at hq.verinode.ai/carriers. Carriers, TPAs, and Commercial are the revenue-in side of the network: carriers pay after a claim, TPAs administer claims on a carrier's behalf, and Commercial clients pay directly. This article covers Carriers; the same privacy boundary applies to TPAs.

Clicking any carrier tile opens the carrier detail card as an overlay on top of the Carriers page. A direct link to /franchise/carriers/[id] opens the same detail view.

The K-anonymity guard: why some carriers never show up

Every carrier row on this page starts life in a nightly network rollup, one row per carrier, counting how many of your franchisees have served it. A carrier that only one franchisee in your network has ever billed is a special case: showing that carrier's numbers to HQ would tell HQ exactly which franchisee they came from, just by process of elimination, no matter how the row is labeled. So Verinode suppresses it. A carrier only earns a visible row, tile, or ranking slot once more than one franchisee in your network has served it.

This is the K-anonymity guard, and it applies uniformly across every ranked list on the page: Slowest Payers, Broadest Network Footprint, Heaviest Pushback, and the full All Carriers list. A single-franchisee carrier simply does not appear in any of them. It is not greyed out or blurred, it is absent, the same way it would be absent from a list of "carriers two or more of your team have dealt with."

What HQ still sees. The hero panel at the top of the page counts every suppressed carrier without naming it. Its summary line ends with a note like "N hidden as single-franchisee" whenever cohortSuppressedCount is greater than zero, so HQ knows the long tail exists without HQ ever learning which carrier, or which franchisee, sits behind it. The network totals above that line (total carriers billed, total jobs, network average days-to-pay) are computed across every carrier row your franchisees have, including the suppressed ones. Hiding a row from the ranked lists never shrinks the network total. Suppression only ever removes the ability to see which carrier a number belongs to when that carrier's identity would leak a single franchisee's business.

If you land on a suppressed carrier by direct link. Because a suppressed carrier can still be reached by URL (a bookmark, a link shared before it dropped below the threshold, a link from an email digest), the detail card does not error out. It opens, shows the carrier's name and Verinode Score (those are never gated), and in place of every dollar figure shows this exact text:

Aggregate-only view. This carrier is currently served by fewer than 2 franchisees in your network. Per-carrier metrics are suppressed to protect operator privacy.

No billed amount, no days-to-pay, no satisfaction rating, no supplement data, and no per-franchisee list render underneath that message. As soon as a second franchisee starts billing that carrier, the guard lifts on its own and the full detail card appears at the next nightly refresh.

The entity-model fork: whose data can be named

Not every HQ network is the same shape, and Verinode treats two shapes differently. Your network's entity_model setting decides which one applies:

• same_entity: a single-owner, multi-location business (an enterprise buyer, a PE-backed platform that owns its locations outright). HQ is the business here. There is nothing to anonymize because HQ already owns the underlying data.
• independent_operators: the default, and the safer posture. This covers franchises, associations, and buying groups where each location is an independently owned business that happens to share a network. HQ sees the network's aggregate performance and compliance posture, never one member's private numbers, because HQ is not that member's owner.

New networks start on independent_operators and have to be explicitly moved to same_entity. This fork changes three things on the Carriers page, each a little differently:

1. 1Franchisee display names. Anywhere a franchisee or location name would render next to a number (per-franchisee participation, per-location pushback, per-location line-item cuts), same_entity networks see the real name. independent_operators networks see a stable anonymized label instead, formatted as Franchisee #XXXX, built from a short suffix of that franchisee's internal ID so the same franchisee always gets the same label across the page without ever surfacing their actual business name.
2. 2Per-location supplement pushback. The "Pushback by location" list on a carrier's detail card, which breaks supplement denials out location by location, only renders real rows for same_entity networks. For independent_operators networks, the whole list is replaced with one disclosure line: "Per-location supplement detail is shown only for networks that own their locations' data. Your network sees the aggregate above." The aggregate figures above it (denial rate, cut dollars, response time) still show, because those are network totals, not one member's private data.
3. 3Per-location line-item cuts. The same fork applies one level deeper, inside "What [Carrier] cuts across your network" (see the next section). Each canonical line item's per-location breakdown is populated only for same_entity networks. independent_operators networks get the identical disclosure line at the bottom of that section instead.

What does not change. The per-franchisee participation list on a carrier's detail card (which franchisees have billed this carrier, their job counts, their billed and collected dollars, their days-to-pay, and their satisfaction rating) still renders a row per contributing franchisee in both entity models, as long as the carrier itself has cleared the K-anonymity guard above. The only difference is whether that row is labeled with a real name or an anonymized Franchisee #XXXX tag. That list is the one place per-franchisee dollar figures do appear to HQ, gated on the carrier having enough franchisees serving it that no single row could be reverse-engineered back to one business by elimination.

The re-identification floor on line-item cells

A carrier can clear the top-level K-anonymity guard (two or more franchisees serving it overall) and still have individual line items that don't. "What [Carrier] cuts across your network," on the carrier detail card, breaks the carrier's supplement cuts down to canonical line items, roofing tarp, water mitigation equipment, drywall replacement, and so on, each with its own count of how many franchisees actually submitted that specific line to that carrier.

That per-line count can be smaller than the carrier's overall franchisee count. A carrier five of your franchisees bill overall might have only one franchisee who has ever submitted a particular specialty line item to it. Showing that line's cut rate and dollars would identify that one franchisee by elimination, even though the carrier as a whole is visible. So the line-item guard runs independently, at the line level: a canonical line only appears in this section once at least two franchisees in your network have submitted it to that carrier. Lines that don't clear it are simply left out of the list, the carrier's other, better-populated lines still show.

Each line that does clear the guard shows:

• Cut rate and Cut (dollars), how often and how much this carrier cuts on that specific line.
• A fixability read: Fixable or Negotiable (worth re-arguing, documentation or pricing) versus Structural (a coverage or policy position, not worth fighting the same way). This is the section's headline number too, an "addressable share" that tells HQ how much of the total pushback is worth fighting versus how much is a fixed cost of doing business with that carrier.
• A network-vs-industry comparison, in points, showing whether your network is cut harder, softer, or in line with the national rate on that line, alongside the industry observation count where one exists.
• For same_entity networks only, a per-location breakdown: "Cut by X of Y locations," with a plain read underneath: all locations cut reads as "systematic across your network," one or two cutting out of many reads as "isolated, likely a submission-quality gap." That is the tell for whether a denial pattern is the carrier's policy or a coaching opportunity at one location, and it is exactly the detail withheld from independent_operators networks for the reasons above.

Reading the Carriers home page

Hero. The eyebrow reads "Network carriers" over a count of every carrier your network has an active rollup for. Its pill reads either "N multi-franchisee" (carriers two or more franchisees serve) or "No data yet." Underneath, three secondary figures: Billed 36mo (with collected dollars beneath it, or "Network total billed" if none), Jobs last 30d (with the 36-month total beneath it), and Avg days-to-pay, colored green inside a 30-day target, yellow up to 60 days, red beyond that. If no carrier has billed yet, the page reads: "Carrier data will appear as franchisees complete and bill insurance jobs."

Slowest Payers. Carriers ranked by average days-to-pay, worst first, red above 60 days and yellow above that but improving. Each tile shows the day count, the carrier name, how many franchisees serve it, and dollars billed over 36 months. Empty state: "Payment-cycle data appears once franchisees record days_to_pay on completed jobs."

Broadest Network Footprint. Carriers ranked by how many franchisees serve them, the procurement-leverage view: the more locations dealing with one carrier, the more standing HQ has to negotiate terms. Empty state: "Network footprint by carrier will appear once franchisees register their carrier relationships."

Heaviest Pushback. Carriers ranked by cut dollars, then by denial rate, the carriers costing the network the most in denied supplements. Each tile shows cut dollars, the carrier name, the denial rate as a share of supplement dollars, a 30-day trend when it is moving up, and franchisee count. Empty state: "Supplement denial data appears once franchisees record supplements with carriers across the network."

All Carriers. Every visible carrier, sorted by dollars billed over 36 months, up to 18 tiles. Each shows dollars billed (or "No billing"), franchisee count, job count, days to pay, and average satisfaction rating where available. Empty state: "No carrier relationships rolled up yet. Data appears after the next nightly aggregation."

Reading the carrier detail card

Clicking a tile opens the carrier's detail card. At the top: the carrier's name, an eyebrow reading "Insurance carrier · N franchisee(s) serving," the date of its last completed job, and the Verinode Score with its label and, if the score is still being established, a provisional badge. If no score exists yet, this reads "Not yet rated by operators."

Below that (once the carrier has cleared the K-anonymity guard):

• Billed · 36mo, with collected dollars beneath it, or "Collection pending" if nothing has been collected yet.
• Avg days to pay, colored the same way as on the home page.
• Collection rate, collected dollars as a percentage of billed dollars.
• Avg satisfaction, out of 10, with the count of peer ratings behind it, or "No ratings yet."
• Jobs · 36mo and Jobs · last 30d as plain rows, the second flagged "Active inflow" when nonzero.

If the carrier has recorded supplement activity, a Supplement pushback block follows: denial rate (as a share of supplement dollars), cut dollars over 36 months (with submitted dollars beneath), average response time, and the 30-day trend in points. Underneath, a plain-language sentence compares your network's denial rate to the national rate for that carrier, for example naming how many points harder or softer your network is cut than the industry average, or that it is in line.

After that comes the per-location pushback list or its aggregate-only disclosure (see the entity-model fork above), then "What [Carrier] cuts across your network" (see the re-identification section above), and finally Per-franchisee participation: every franchisee that has billed this carrier, their job counts, dollars billed, days to pay, and rating, one row per franchisee (real name or anonymized, per the entity-model fork). If no franchisee has billed this carrier yet, it reads: "No franchisee jobs on file with this carrier yet. Rows populate after the nightly aggregator runs."

Best-practice example

Say HQ opens Accounts > Carriers and sees "State Farm" sitting at the top of Heaviest Pushback with a high denial rate and a climbing 30-day trend. Opening the tile shows the network-wide numbers plus the industry comparison line, State Farm is cutting this network several points harder than the national average. Scrolling to "What State Farm cuts across your network" shows the addressable share is high, most of the pushback is documentation or pricing that can be re-argued, not a fixed policy position. If this is a same_entity network, the per-location breakdown shows the cuts are concentrated at two locations rather than systemic, pointing HQ at a coaching conversation, not a carrier-relationship conversation. If this is an independent_operators network, HQ sees the same aggregate numbers and the same addressable-share read, but stops there: it takes the pattern to the affected franchisees directly rather than naming which one is driving it, because that call belongs to the members, not to HQ.

Related help articles

• /help/hq-overview
• /help/network-health
• /help/hq-benchmarks
• /help/hq-compliance
• /help/hq-report-library

Data sources