Hermes reconciles SaaS books with human review
Satva Solutions reports a Hermes accounting experiment that extracted statements, prepared Zoho Books entries and corrected tax and matching errors under human review.
satvasolutions.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Prepare draft reconciliation using authorized documents and live settings. Show payable totals, source statements and unmatched items, then wait for my accounting review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Satva Solutions
- Original account
- Read the source ↗
- Published
- 2 Jun 2026
- Source link checked
- 15 Oct 2026
- Reported result
- Satva Solutions reports a Hermes accounting experiment that extracted statements, prepared Zoho Books entries and corrected tax and matching errors under human review.
- Human involvement
- An accountant-managed parallel organization and operator review catch posting and reconciliation errors. Tax and final accounting judgments remain human.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Hermes reads financial documents and extracts structured transactions.
- The operator corrects payable amounts and ensures bank data reaches Zoho.
- Matching rules are tightened and unresolved entries become exceptions.
Satva Solutions documents a Hermes accounting experiment for a Singapore SaaS business. The operator kept separate accountant-managed and agent-managed Zoho Books organizations for comparison. Hermes generated Python clients for official APIs and connected Gmail, Aspire statements, Stripe and Telegram.
The agent extracted 89 statement transactions and prepared vendor entries. Human inspection caught a material error: it posted a bill's subtotal rather than the amount payable. After correction, the agent restored the tax-inclusive payable. It also initially left bank transactions in a local staging file instead of importing them into Zoho.
Reconciliation exposed another failure when a matching amount led to a transaction thirty days away. The operator required date proximity, amount, vendor and the correct statement, leaving an unresolved Shopify item as an exception. Receipt chasing was changed from 43 separate requests to a weekly summary per cardholder.
The useful result is a recurring workflow with explicit corrections and exception review. The reported time reduction is an estimate, not an independently measured accounting outcome. Tax treatment, unusual transactions and final review remain with people.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: satvasolutions.com · Satva Solutions
Frequently asked questions
What error affected vendor bills?
The agent initially posted a subtotal instead of the full payable.
Was every amount match accepted?
No. Date and statement checks left a Shopify item unresolved.
Are the time savings independently measured?
No. The source presents estimates from this experiment.
More details
Remaining steps
- Receipt requests are consolidated for human review.
About this account
Hermes generated API clients, extracted statement transactions, prepared vendor entries, imported bank data after correction and compared records for reconciliation.
Firsthand account opened and read. Outcome is source-reported, not independently reproduced. Suggested prompt written by Agents In Use. Recovered with web after local 406. Company attribution; estimates and accounting judgments are not independent audit results.
Credit: Satva Solutions
Source published 2 Jun 2026
Source checked 15 Oct 2026
Tools and topics
Hermes Agent · Zoho Books · Gmail · Stripe
Hermes Agent · Zoho Books · Gmail
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.