Bank lines matched to your books — without letting AI write.
Raven ingests your bank statement, matches each line to the right Zoho invoice or bill, and drafts the entry. Deterministic code posts it only after you approve. You stay the checker.
The intelligent part can never act on its own.
Moving money is exactly where a black box is unacceptable. Raven splits the work across three roles, and only the deterministic writer ever touches Zoho — after a human approves.
- Maker · AI
- Reads the statement, finds the right invoice or bill, drafts the entry.
- Writer · Code
- Tested, deterministic code posts the change to Zoho. The model never has a write path.
- Checker · You
- Nothing is written until you approve. Full trail of who approved what.
Mode-aware, dedup-safe.
The parser knows the difference between NEFT, IMPS, IFT and UPI and extracts the right fields per mode. Dedup is UTR-preferred, raw-description normalised, and decimal-precision-stable — so re-uploading a statement never creates a duplicate, even if the bank reformats their export.
Counterparty matching normalises vendor and customer names across formats, so "ACME FOODS PVT LTD" and "Acme Foods Private Limited" resolve to the same Zoho contact.
Built for Indian banks. Adapters in flight.
The parser interface is built once. Each new bank is a per-bank adapter — a description parser plus a statement layout — not new architecture.
The other surfaces it leans on.
See reconciliation run on a real statement.
We'll walk you through the maker-checker flow on a live example.