Product · Approvals and audit
Every proposal goes to the right person by rules you write. Every decision is sealed in a record you can show your auditor.
Join the waitlistControl, written down
An accounting firm already has rules for who signs what. Qestra turns them into code, so the same case reaches the same person every time, and nobody has to remember.
01 · Approval rules
Decide who approves what by client, company, amount, account or agent. Routing is plain code you can read and test. No AI model ever chooses who approves.
02 · The decision
What the agent found, why, and the change it proposes, shown as now and suggested side by side. One button fixes it. Nothing is written to the client's system until you approve.
03 · The audit trail
Every proposal, approval, change and posting goes into one trail. Each entry is sealed to the one before, and the chain is checked every night. Change one entry and it shows. Not even we can edit it.
04 · Periods
Once a period is closed, nothing can write to it. Reopening needs a request and an approval, and both are on the record. When someone is away, their duties pass to a colleague you choose.
No, never. The approval engine always sends an agent's proposal to a person.
Partners, and the people they give the right to. Rules can differ per client and company, and every change is versioned and logged.
Who or which agent did what, when and why, which rule sent it to whom, and a fingerprint of the evidence. Not a copy of the ledger.
No. Events are only ever added, each one is sealed to the one before it, and the whole chain is checked every night.
They hand the work to a colleague with the same authority, or the rule sends it to its backup. The handover is logged too.
Early access
Join the waitlist and see Qestra on companies like yours.