The same dual-control workflow your auditor expects, without the three-day setup. Here’s what each step looks like in the product.
A maker fills in the receipt — pick the organization, list the line items, choose the payment mode. Drafts auto-save, so nothing is lost if the page reloads. When the receipt is ready, the maker hits Submit and it enters the review queue.
Checkers in the same organization see the receipt in their queue. They open it, eyeball the line items, and either Approve or Reject with a reason. Rejection reasons are kept as history — old reasons are never overwritten when a maker resubmits.
Once approved, the receipt is immutable. No edits. The status flips to APPROVED, the approver is recorded, and an audit-log row is written. If the receipt is paid later, an admin can flip the payment status — but the receipt itself stays sealed.
Approved receipts export to a clean PDF — the organization's name, address, GSTIN, PAN, CIN are baked in. Filenames are sanitized. The route honours If-None-Match, so re-downloads of an unchanged receipt return 304 instantly.
You don’t have to wire any of this. It’s how the product runs from day one.
Members are scoped per organization. A checker in Org A can't see Org B's receipts — not via the list, not via direct id lookup, not via the export endpoint.
Every receipt action is recorded. Rows are never edited or deleted; the log is your forensic record if a customer disputes something.
Login, signup and OTP endpoints are throttled per IP per minute. Brute-force attempts return 429 with a Retry-After hint.
Sign up free, create an organization, walk through the four steps in your own browser.