Delegate expense approval to AI agents.
You want to automate expense approvals, but you can't hand an AI unlimited authority. With Lemma, "limit ¥100k," "budget category," and "team scope" become a scoped delegation verified at runtime, so the agent approves autonomously inside that scope and escalates to a human outside it.
Three voices from the front line.
- Accounting / finance
“We want to automate expense approvals, but handing over unlimited authority is a real risk”
- Legal / internal control
“We want the AI's approval-authority scope kept in an auditable form”
- Digital transformation
“We want to cut approval turnaround from 24h to instant”
Hand over the source, or just the facts?
Nothing changes on the floor. Everything changes for the receiver.
① Your team just saves, as always.
- The usual step
- Fill in the record and save
- On save
- A proof is attached (API, behind the scenes)
- The document itself
- never sent
② They just open a link.
- Proven fact
- within scope, the AI may approve
- expense data and the approval authority itself
- not shown
- Login / keys
- not needed
- The document stays private — the record itself is never sent or disclosed.
- Independent verification — the receiver just opens a link. No account, no keys.
- Edits are detected — even a one-character edit fails verification.
The finance team issues a signed delegation with a spend ceiling, categories, scope and validity. Before approving, the agent verifies it stays within that scope at runtime — auto-approving inside it and escalating to a human outside it. Without disclosing the approval authority itself, the fact "approved within an authorized delegation" can later be independently verified.
See the technical details ↗Why the usual methods fall short.
Only work that needs all three at once — pass without exposing, independent verification, tamper-evidence — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-evident | What happens |
|---|---|---|---|---|
| Access control / permissions | △ | ✗ | ✗ | “Someone inside could have edited it” remains possible |
| Masking / redacted copies | △ | ✗ | ✗ | Redaction work grows; the original is still unproven |
| Encrypt and store / send | ✓ | ✗ | ✗ | To verify, the receiver needs it disclosed after all |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ | The receiver just opens a link |
How it works — and how to start.
We help design disclosure scope and retention, run the PoC, and support production.
Start with a 30-minute call.
Tell us one workflow stalled on expense-approval automation, in the first 30 minutes. No disclosure of approval authority required.
Find the case that matches your industry and problem
Browse all 36 use cases →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.