Disputes desks staff up and down with volume, and the people who look at a dispute file — clerk, analyst, approver, sometimes the shipper — are not the people who should be paying per login. So D&D Pilot meters shipments.
The unit
One Dispute File is one shipment analysed end to end: timeline, clause check, computed versus invoiced, missing-evidence list, letter draft. It covers up to fifteen documents; each additional ten is half a file. Pay as you go is USD 6 a file; annual plans include a monthly pool and bill overage at a lower rate.
Pre-screen at a tenth
Rating a statement line against the contract uses only the invoice's own dates, so it is cheap, and it should be run on every line — that is the point. A tenth of a file per line means a 200-line statement is twenty files' worth, and opening a full file for a flagged line credits its pre-screen cost.
Re-runs are free
Disputes unfold over weeks: the carrier replies, the trucker produces an EIR, customs sends the release notice. Charging for each re-run would make desks hesitate to add evidence or respond to a rejection, which is exactly backwards. Any re-run on the same shipment within thirty days is free.
Model tokens as a separate line
The language model's cost appears as model_access_usd at the provider's list price — or zero with your own key. It keeps the file price stable when model prices move, and it lets finance see exactly what the AI part cost.
On the Google Cloud invoice
Annual plans bill once at purchase through Marketplace; included files are netted in the workspace and only overage is reported hourly as dispute_files. Both meters appear as separate line items on your existing Google Cloud invoice and count toward commitment. Every unit carries a request id so the invoice can be reconciled against the tracker.
Recovery-share
Audit firms and large 3PLs can take a lower platform fee plus a share of credited amounts, reconciled monthly against the tracker. It aligns us with the thing you are measured on.