Expense data is finance data. Every claim below maps to code you can ask us to walk you through — we count it rather than estimate it.
Every record belongs to one organization, enforced at the model layer rather than in each query. 20 models carry the tenant scope, so a missing WHERE clause cannot leak another company's data.
Audit records cannot be edited or deleted — the model raises on update, delete and destroy. Approvals, settlements and expense changes write to it from 12 places in the application.
Authorization is decided by 20 policy classes, not by hiding buttons. A statement can only be submitted by the person it belongs to, and is visible to an approver only when it is routed to them or they already acted on it.
Submitting a statement locks it and every expense inside it. Values stop being editable at the moment they enter the approval chain; returning it to draft is itself a recorded action.
Runs on dedicated infrastructure in the United States. Receipt images are stored in object storage in the US West region, and the database streams continuously to backup rather than relying on nightly dumps.
Claimbook implements a SOX-style audit trail. It has not been through an external SOC 2 or SOX audit, and we don't describe it as certified. If your auditor needs evidence, we will walk them through the controls and the log.
Setup is included — we configure your approval chain before your team logs in.
Talk to us