Solution · Finance Operations
AI for finance operations where nothing executes without approval
RoleAxis agents never act on their own. Every finding becomes a draft in an approval queue; a named person approves or rejects it; only an approved draft is written to your system, and only for the action types the connector supports. Drafts of 20,000 SAR or more need an owner. Tax rates, tax filings, bank and IBAN details, closed periods and the chart of accounts can never be drafted at all. Every transition is an append-only audit row with an exception code, and the monthly value statement adds up only what was approved.
Nothing executes without approval.
What it does
- Executes on approvalApproval queue
draft → pending approval → approved → executed. A draft can be rejected at any point; nothing skips a state.
- Executes on approvalOwner sign-off on large amounts
Any draft at or above 20,000 SAR needs an owner-level approval, whatever the action type.
- Executes on approvalBlocked outright
Tax rates and filings, bank/IBAN edits, closed-period edits, chart-of-accounts changes: refused before a draft exists.
- Executes on approvalAppend-only audit log
Every draft, decision and execution is a row that is never edited or deleted, with who, when and a named exception code.
- Executes on approvalMonthly value statement
Riyals protected, chased and governed, by month and by skill; counted only from approved actions, with 'protected' explicitly not meaning 'saved'.
“Executes on approval” writes to your system once approved; “Recommends” records the decision for your team to act on; “Planned” is not built and does not run.
How approval works here
Two approval levels exist today: any approver on the tenant, and owner-level for high-value drafts. A 'second, independent approver' for material or multi-location changes is classified and shown in the draft's note but is not mechanically enforced yet, we say that here rather than imply it. If a write to your system fails after approval, the failure is logged, the draft stays approved, and approving again retries; nothing is executed twice.
Connector note
Writes exist today on Odoo only (holds, activities, transfers, RFQs). On Qoyod every approval is recorded and the accountant applies it by hand; that connector is read-only.
- Finding
- Payment reminder for overdue invoice QINV-1042
- Amount
- 15,800 SAR chased
- Decision
- Accountant approves the reminder
- Result
- Reminder placed on the invoice as a to-do for your team to send; 15,800 SAR chased on the value statement; audit row FIN-PAYMENT-HOLD
Questions
Can an agent be given autonomy for small amounts?
Not today. Every action type waits for a human approval. The assessment's 'limited autonomy' class describes what a task could tolerate, not a mode the product has.
Who sees the audit log?
Your tenant's users, in the dashboard; the RoleAxis owner console for support. Rows are never edited or deleted, and one tenant can never read another's.
Is RoleAxis certified (ISO 27001, SOC 2)?
No, not yet. Credentials are encrypted at rest and tenants are isolated by design and by test, and we would rather say plainly what is not certified than imply it.
Credentials encrypted, tenants isolated, owner sign-off above 20,000 SAR, tax and bank changes never drafted, an append-only audit log. The full list, with what enforces each item: security and control →