Automation
Automate finance without losing control
Automation in JiriBooks follows one model: trigger, condition, action, approval, audit. Rules assist the people responsible for the numbers; they never post value on their own.
01
The automation model
Every rule passes the same five stages.
- Trigger
- Condition
- Action
- Approval
- Audit
02
Example rules
What businesses automate first.
- Invoice overdue → send reminder
- Large expense → request approval
- Bank transaction → suggest category
- Low cash balance → alert owner
- Customer above credit limit → flag transaction
Status
What is live today, and what is not
Capability status
- Live
- Implemented and available to every account today.
- Beta
- Implemented and usable, still being refined with early customers.
- Early Access
- Available on request to selected businesses.
- In Development
- Actively being built for an upcoming release.
- Planned
- On the product roadmap, not yet started.
Every JiriBooks page reads capability status from one central source, so a capability is never described as available in one place and planned in another.
Keep exploring