One expense policy, checked on the phone and the server.
Caps per line, per day and per month, receipt flags and approval levels. The rep's phone and the server run the same check, so they always agree.
SyncedThe phone and the server cannot disagree.
The verdict a rep sees is computed on their phone by the same rules the server applies when the claim is sent. A rep is never told a line is fine on the phone and refused at submit.
Each category can carry a cap per line, per day and per month, a receipt threshold, and a rule that the line must name who it was for. Dates in the future are refused, and dates outside the claim month are flagged.
Warnings never block.
A cap breach blocks the claim until it is fixed. A missing receipt or an out-of-period date is a warning: the claim still goes, and the approver sees the flag. Anything unclear defaults to a warning, because the person out of pocket is the rep.
Policies are versioned by date.
Each policy version has a date it starts judging claims, so a change next month does not re-judge last month's spending. A new account starts with categories named for your industry and one approver, the claimant's manager, and you add limits as your finance team sets them.
Questions people ask.
What does a new account start with?
Which problems stop a claim from being sent?
Can category names match our own terms?
Works well with.
Expense claims
A monthly claim, built line by line from the field, with the policy verdict shown before it is sent and a clear status after.
Read moreExpense approvals
Managers see waiting claims oldest first, with the lines, the total and every policy flag, and approve, send back or reject with a note.
Read moreSee it on your own team.
Tell us your fleet and we will size a proposal. Complete roll-out may take up to 4 months, counted from signed requirements and first payment.