When a vendor’s insurance lapses, the liability lands on you.
Statum is an AP agent that safeguards your business from compliance risk. It chases expiring insurance renewals and halts payments to non-compliant vendors — before the money leaves.
- Reads the folder your certificates already arrive in
- Never moves money. No banking credentials, no payment permissions
- Sits alongside QuickBooks, NetSuite, Bill.com and Ramp
Certificate of Liability Insurance
ACORD 25Northline Mechanical LLC
Vendor 2117 · Toledo, OHRidgeline Industrial Inc.
Issued 01/14/2026Workers’ Comp lapsed 22 days before this payment run.
The expiry date is printed on the insurance certificate — and nowhere else.
Your ERP doesn’t read it. Your AP tool doesn’t read it. The tracking spreadsheet is as current as the last person who had time. This was never a discipline problem — nothing in the stack was built to open a PDF and read a date.
- 15 Jan
Workers' Comp expires
The certificate on file still looks fine. Nothing tells anyone.
- 06 Feb
$84,200 released
Approved on the Friday run, like every other invoice.
- 20 Feb
$31,400 released
Approved on the next run. Nobody has opened the file yet.
$115,600 released against a policy that ended on 15 January.
With the agent, the 6 February run stops and the vendor is asked to renew. Nothing else on the run is touched.
Nothing about your AP process changes. One payment stops.
Statum reads the compliance state of every vendor on the run and holds only the one that fails. Everything upstream stays exactly as it is.
Invoice received
INV-40118 · Northline MechanicalCoded and matched
Job 24-017 · cost code 05-210Approved by AP
K. Alvarez · 06 Feb, 09:14
- General Liability01 Mar 2027
- Automobile Liability01 Mar 2027
- Umbrella Liability01 Mar 2027
- Workers' Compensation15 Jan 2026
$84,200 paused, with the certificate and the expired date attached.
Routed to K. Alvarez and the vendor contactEvery other vendor on the run releases on schedule. Nobody is asked to check anything.
47 of 48 payments · no action takenIt reads your documents. It never touches your money.
Statum holds no banking credentials and no payment permissions. It tells your approver what it found. The approver decides.
It holds no credentials and no permissions
No bank access, no payment rights, and read-only access to your documents. It cannot release, block, or redirect a single dollar.
It reports to the people who act
AP, Procurement, and Finance each see what they own. A held payment reaches the approver, not the whole company.
- 14 Jan · 09:02
Agent read the certificate
COI-2026-0114.pdf · 4 fields extracted - 15 Jan · 00:01
Coverage lapsed
Workers' Comp · Current → Expired - 06 Feb · 09:14
Payment held
INV-40118 · WC-6612840 expired 15 Jan - 06 Feb · 11:40
Reviewed by a person
M. Chen (Finance) · document opened
What a controller asks in the first ten minutes.
- How long does it take to get running?
- You point Statum at the folder, drive, or mailbox your certificates already arrive in. It reads what is there and builds the register itself. No migration, no IT project, nothing for your vendors to log into.
- Do we have to change our AP tool or ERP?
- No. Statum performs one check and hands you the answer. QuickBooks, NetSuite, Bill.com, Ramp, and your approval workflow keep doing exactly what they do today.
- Our certificates are scans and phone photos. Does that matter?
- That is the normal case. Statum reads the document itself rather than relying on structured data, so a scanned fax and a photo taken on a plant floor are both readable. If a document genuinely cannot be read, it is marked unread with the reason and the vendor stays flagged — it is never quietly passed.
- What decides whether a vendor is compliant?
- Your contract terms. You define what each vendor must carry, and Statum compares what it reads on the certificate against that. A missing coverage is treated as seriously as an expired one.
- How established is Statum?
- It is early. There are no customer references, case studies, or usage statistics to show you yet, and inventing them would be the fastest way to lose the kind of buyer this is built for. What exists is the behaviour described on this page, and a walkthrough on your own documents.
Run it on your own vendor folder.
Bring a handful of real certificates, in whatever state they are in. Watch it read them and tell you which vendor it would stop.
Thirty minutes, on your documents.
Read-only throughout.