AI that matches invoices but cannot approve its own payments
Accounts payable workflow · working prototype
The question
AI can read an invoice and match it to a purchase order quickly and accurately. The reason finance teams hesitate is not accuracy. It is control: what stops the AI, or someone talking to it, from approving a payment it should not?
I built this prototype to show one answer to that question, so that clients can see the control model working before they trust it with real money.
How it works
The design separates what the AI is good at from what it must never be allowed to decide.
- The AI reads the invoice and matches it against the purchase order
- Approval limits are checked by fixed rules that run outside the AI, so no prompt or conversation can change them
- Anything within the limit is posted; anything over it stops and waits for a named approver to sign
- The approver’s authority is itself signed and verifiable, not a setting the AI can read and reinterpret
- Every step is written to an audit trail, with personal data hashed rather than stored in the clear
Why it matters
The same pattern applies to any consequential decision you might want AI to help with: the AI prepares, a rule decides whether a person is needed, and the person decides. It is how I design every AI step in a client roadmap.
Built with
Node and TypeScript with no runtime dependencies, Ed25519-signed authority, SQLite audit ledger, Anthropic API with an offline deterministic fallback for testing
Have a challenge like this one?
A free 20-minute conversation about your business, what is getting in the way, and what it would take to fix it.