Transaction Review Agent
Surfaces ledger exceptions and prepares evidence-backed coding suggestions.
Ledger noise becomes a short exception queue.
This live workflow uses a prepared transaction batch. In an installation, it can read approved ledger, bank-feed and expense records.
Test it live- 01TransactionsLedger, bank feed and receipts
- 02Transaction AgentNormalizes records and evidence
- 03Exception checksFinds duplicates, gaps and unknown vendors
- 04Accountant reviewConfirms treatment and posting
- 05Prepared outcomeA focused review queue
- Your Supabase project
- No pooled client database
- Human approval before action
- No model call needed
Under the hoodSee the systems, storage and control points+
Example client installation
- 01Firm sourceLedger or expense system
- 02Scoped connectorReads the approved transaction batch
- 03Transaction packageNormalizes records and evidence
- 04Rules engineRuns duplicate, category and value controls
- 05Safety checksLocks every ledger change
- 06Firm-owned SupabaseStores the result and run trace
- 07Named reviewerApproves, edits or rejects
Your operational data stays in your firm-owned database. This workflow runs on explicit rules and sends no client data to a model. No final action happens until a named person approves it.
Test the full workflowTest the agent live
Take one record set through the full workflow.
The rules do the predictable work. Every final action still waits for a person.
Ledger batch→Exception rules→Posting review
Items waiting in this agent’s lane.
1in queue
1need human review
| Subject | Agent summary | Confidence | Age | Status | Open |
|---|---|---|---|---|---|
| Riverbend Retail · August transaction review | 2 transactions need accountant review | 99% | 6d | high priority | View → |
How it connects
Supabase stores the workflow records. The server reads only this agent’s lane and turns it into the queue above. Completed rows open this agent’s compact owner view and inspectable run trace.
Test it live