What you're actually approving
A Spool and a receipt, signed, and verifiable offline by anyone.
For buyers
Pay for what actually counted.
Reconcile every vendor against the rules you agreed and the evidence you already trust. See the exceptions, the corrections, the accepted count, and the payable amount.
01
The approval record
Partial credit, held uncertainty
92 of 100 reads as 92. What cannot be verified stays uncertain instead of quietly passing.
One lifecycle across all your vendors
Claimed, accepted, rejected and needs review, the difference and why, grouped by reason, as a CSV or a booking row. The same lifecycle whoever sent the invoice.
- Northstar AI: 92 accepted, 8 rejected
- Atlas Support: 47 accepted, 3 need review
- Juniper Data: 100 accepted
When a number moves
The correction chain shows the earlier receipt, the new one, and why it changed.
A place to send the uncertain ones
Acceptance Reviews: one link, one deadline, one named person.
02
Questions buyers ask
We trust our vendor's dashboard.
A dashboard is the vendor's count on the vendor's rules. A receipt is signed against rules both sides agreed, and anyone can verify it.
This slows approvals down.
It is the reconciliation you already do by hand, produced automatically in a format AP reads.
If a vendor disputes, who wins?
The agreement does. Dispute Resolution freezes the disputed value and resolves to a superseding receipt both sides can point at.