Strict tenant isolation
PostgreSQL forced RLS and API authorization keep users inside their own tenant data boundary.
Start with the data boundary
Every save and change leaves evidence you can trace
Each company has its own data boundary. From originals and hashes to approval and revision, the system retains evidence that can be checked later.
Protection is part of every step, not an add-on
Approved originals are locked for retention
Approved receipts and their original assets are locked to prevent deletion, replacement or unrecorded rewriting.
Originals and hashes are retained
File type, size, SHA-256, upload time and AI results remain available to verify evidence origin.
Records and originals back up together
PostgreSQL records and MinIO originals follow one backup process to reduce evidence inconsistency.
The evidence chain continues from upload to export
Upload
Original page order, file type, size and hash are retained.
Review and revision
Finance changes keep before-and-after differences with time.
Approval and payment
Approval and payment become traceable business records.
Reports and audit packages
Originals, data, alerts and audit history can be exported securely.
An audit needs more than a total
An audit evidence package keeps original multi-page files, data summaries, AI results, revisions and download history in one checkable context.
- Original multi-page files and page order
- Data summaries, hashes and AI results
- Revision, approval, payment and download history
Keep a complete basis for every future expense review
Build a traceable company record from the first receipt.