Slowest Payers: where the network's cash gets stuck

What this row is

Slowest Payers is the payment-risk row on the Accounts page: a ranked list of the carriers taking the longest to pay across your whole network, average days-to-pay, worst first. Where the page header above it gives you one weighted number for the entire network (see Reading the carrier network header), this row breaks that single number apart and names which specific carriers are actually driving it.

Verinode does not chase carriers for payment or negotiate terms on your behalf. It reads the jobs and payment history your franchisees have already recorded, rolls them up by carrier across the network, and surfaces the ones whose payment cycle is running long. Leadership decides what to do with that: a direct conversation with a specific carrier, a network-wide policy on which carriers to keep writing for, or nothing at all if the numbers look fine.

Where to find it

Open Accounts from the HQ sidebar (Revenue band), at hq.verinode.ai/carriers. The page opens on the Carriers pill of a three-pill strip, Carriers · TPAs · Commercial. Slowest Payers is the first row of tiles below the header, above Broadest Network Footprint, Heaviest Pushback, and All Carriers further down the same page.

How a carrier gets on this list

A carrier qualifies for this row on two conditions:

1. It has at least one recorded days-to-pay value. A carrier with jobs on file but no days_to_pay recorded on any completed job never appears here, no matter how much business it does with the network. It shows up instead in the header's total-carrier count and in the All Carriers row further down, just without a days-to-pay figure.
2. It clears the network's privacy floor. Carriers served by too few distinct franchisees are withheld from every carrier-level row on this page, including this one, so that a single carrier's figures can never be traced back to one franchisee by elimination. See the privacy section below.

Among the carriers that clear both, Verinode ranks by network-wide average days-to-pay, slowest first, and shows up to six. This is not a list of every slow carrier, it is the worst six, meant to be scanned in one glance rather than sorted or paged.

What each tile shows

Every tile in this row carries four pieces of information:

• Days figure ("52 days"): the carrier's own network-wide average days-to-pay, weighted across every franchisee that bills it.
• Headline: the carrier's name.
• Sub-line: how many franchisees serve this carrier, for example "3 franchisees serving" (or "1 franchisee serving" when only one, in networks where that's allowed to show at all, see below).
• Meta line: the carrier's total billed over the trailing 36 months, for example "$210k billed 36mo," when that figure exists. If billing data isn't available for the carrier, the meta line is left blank rather than showing a placeholder.

Tiles in this row render larger and more visually assertive than the rows below it (Broadest Network Footprint, All Carriers), a deliberate "this needs a look" treatment consistent with how Verinode flags anything that reads as a risk rather than a routine ranking.

The accent logic: 60-day and 45-day thresholds

The row itself uses a simple two-way accent:

• Over 60 days average: the tile's accent renders in Analyse (Ember Red). This is the network's own read of a genuinely slow carrier, one whose payment cycle is dragging past two months on average.
• 60 days or under: the tile's accent renders in Maintain (Hard Hat Yellow). Because this row only ever shows the network's six slowest carriers to begin with, even the "yellow" tiles here are already among the worst in your book, they simply haven't crossed the 60-day line.

There is no green tier inside this row. A carrier paying quickly enough to read green never ranks slow enough to make this list in the first place; green readings live on the header's network-wide average and on the individual carrier detail (below).

Tapping a tile opens that carrier's detail view, a modal overlay on the same page (with a full-page version at hq.verinode.ai/carriers/[id] as a fallback if you land on a direct link). The detail view repeats the same days-to-pay figure with a third tier added, because a single carrier's own number can be genuinely healthy in a way the row above it, by design, never shows:

• Over 60 days: red (Analyse), same as the row.
• Over 45, up to 60 days: yellow (Maintain), a "worth watching" read that sits below the row's 60-day cutoff.
• 45 days or under: green (Expand), reading as within normal network terms.

In other words, the row you land on first is a coarse triage (slow enough to make the list, or not), and the detail view one tap away is the finer read that actually distinguishes a carrier that's merely a little slow from one that's genuinely healthy.

The privacy boundary

Same guard as the rest of the Accounts page: a carrier served by only one franchisee is withheld from this row (and every other carrier-level row) in networks made up of independently owned locations, because showing that carrier's days-to-pay by itself would tell HQ, by elimination, which franchisee it belongs to. This does not apply to networks configured as a single legal entity operating multiple locations, where every carrier row is visible regardless of how many locations serve it.

When carriers are withheld this way, the header's summary line carries a trailing note ("N hidden as single-franchisee") so leadership knows the visible rows are a filtered set, not the network's complete slow-payer list. Qualitatively: the fewer franchisees sharing a carrier, the more likely that carrier sits below the visibility floor and simply won't appear here yet, regardless of how slow it actually pays.

What it needs to populate

This row needs one specific thing recorded that a lot of the rest of the Accounts page doesn't: days_to_pay on completed, billed jobs. A franchisee can bill a carrier, get paid, and close the job out without ever recording how many days that took, in which case the job counts toward billed and collected totals elsewhere on the page but contributes nothing to this row or to the header's network-average days-to-pay figure.

Empty state

If no carrier in the network has a recorded days-to-pay value at all, the row reads:

"Payment-cycle data appears once franchisees record days_to_pay on completed jobs."

This is not a broken page. It means every franchisee in the network has either not billed a carrier job yet, or has billed and been paid without recording how long it took. As franchisees start closing that field out on completed jobs, carriers begin appearing here in the order their average days-to-pay data accumulates.

How to use it

1. 1Scan this row before any network-wide carrier or vendor conversation. It's the fastest read on which specific counterparties are actually dragging the network's cash cycle, rather than the header's single blended average.
2. 2Tap a red tile first. Anything over 60 days average, across enough franchisees to clear the privacy floor, is a genuine collections drag worth a direct conversation with that carrier or a policy question about continuing to write for them.
3. 3Tap through to the carrier's detail view before drawing conclusions. The three-tier read there (green under 45, yellow 45 to 60, red over 60) tells you whether a "yellow" tile in this row is borderline-fine or actually close to the red line.
4. 4Cross-check against Billed 36mo on the same tile. A slow carrier that represents a small slice of network billing is a different priority than one that's both slow and heavily used.
5. 5If the row looks thin or empty, that's a data-completeness gap, not a compliment. Push franchisees to record days_to_pay on completed jobs so the network's actual payment risk becomes visible.

Related articles

• Reading the carrier network header, the network-wide average and pill this row's own figures roll up into.
• Carriers & TPAs tab in network view, the industry-wide benchmark read on carrier payment speed, independent of your own network's billing history.
• HQ overview, orientation to the HQ sidebar and what each section covers.
• Network health, the HQ command home this section sits alongside.
• HQ benchmarks, the seven-tab industry benchmark hub.
• HQ compliance, for network-wide standards conversations this row can feed into.

Data sources