Claims that paythemselves out.
Snap a receipt in any currency. It converts to your office's base currency, routes to the approvers your rules choose, and settles straight through payroll — no spreadsheet in the middle, no chasing anyone for a signature.
A closer look
Claims in 5 parts.
Straight from the running product — what an administrator sets up, and what everyone else does with it.
Every claim in the organisation, by batch
Stepped by month and filtered by department, team or country. Each batch carries its pending count and its total, so the queue can be worked from the top rather than opened one claim at a time.
HR admin's view
Limits enforced at the door
Medical, travel, meals, mileage, training, entertainment and any custom type you add. Each carries a per-transaction cap, a per-period cap, and whether a receipt is required — enforced on submission, not discovered at audit.
HR admin's view
The rules, set once
A monthly cut-off, how far back a receipt may be dated, and the HR and Finance groups that can sit in an approval flow. Different flows for different roles or named people, plus a default catch-all — decided the moment a claim is raised.
HR admin's view
The approver's queue
Claims waiting on this person, grouped by batch — a trip's expenses advance together as one unit rather than trickling through one line at a time.
Manager's view
Payment requests, same rails
Spend that isn't a reimbursement — a supplier invoice, a deposit — routes through the same approvals and lands with the same finance stage.
HR admin's view
What's inside
Everything the claims module does for you.
Snap and submit
Photograph the receipt, pick a category, done. The receipt stays attached and viewable in the browser.
Multi-currency native
Spend in yen, bill in dollars — every claim converts to the office's base currency at submission.
Approval flows that match
Different flows for different roles or people, with a default catch-all — the claim finds its own path.
Thresholds and caps
Per-claim limits and per-period submission caps are enforced at the door, not discovered at audit.
Batches move as one
Submit a trip's expenses together and the batch advances through approvers as a single unit.
Paid with payroll
Approved claims land in the month's payroll run — one payment, one payslip line, no second transfer.
How it runs
Three steps, start to finish.
Snap the receipt
From a phone, in any currency, seconds after the meal ends.
It routes itself
Your rules pick the approvers; each one clears it in a tap, in order.
It pays out with payroll
The approved amount joins the next run and appears on the payslip.
Claims is one of nine modules, already working together.
One login, one people record, no re-keying between systems — and a team who sets it up with you.