Segregation of duties
Build roles from individual permissions, then require approval before money moves.
- Permission-level custom roles
- Approval workflows on spend
- Warehouse and branch scoping
- Session controls and 2FA
For larger organisations
Governance, integration and control at scale
Custom roles, approval chains, period locks, a complete audit trail and a REST API that lets WisoBooks sit inside the systems you already run.
Custom
Roles & policies
Full
Audit trail
REST
API & webhooks
Overview
What a finance director asks first
Scale changes the questions from 'can it invoice' to 'can it be controlled and audited'.
- Who can approve what, and can we prove it later
- Can we stop edits to a period we have already reported on
- Does it feed our data warehouse and our other systems
- Can we segregate data by entity, branch and warehouse
Audit and close discipline
Every posting is traceable to a document, a user and a moment in time, and closed periods stay closed.
- Immutable double-entry ledger
- Reversal-based corrections, never silent edits
- Period locking with override permission
- Activity log across the tenant
Integrate, do not re-key
A documented REST API, API keys, OAuth applications and webhooks connect WisoBooks to the rest of your stack.
- OpenAPI spec and interactive docs
- API keys and OAuth2 apps
- Webhooks on document events
- Bulk export of reports and journals
FAQ
Questions, answered
Can we run several entities?
Yes. Each legal entity runs as its own tenant with its own base currency and chart of accounts, and users can be given access to more than one.
How is our data isolated?
Every record is scoped to a tenant at the data layer, and access is enforced on the server for every request, not just hidden in the UI.
Do you support single sign-on?
Two-factor authentication is built in today. Talk to us about SSO requirements for your rollout.
Can we export everything?
Yes. Reports, journals and master data export to CSV, Excel and PDF, and the API exposes the same data programmatically.