Guides › Claims
Sending a claim
Set it up once
- Settings, then Send claims to. The address that reimburses you. This is per account, so it is yours and nobody else's.
- Settings, then Reporting period. Choose the window you actually claim over: daily, weekly, every two weeks, twice monthly, monthly, quarterly or yearly.
- Send automatically, if you would rather not have to remember.
Changing your claim period changes nothing that is already recorded. Trips and receipts keep their dates and keep whether they have been claimed. Only which of them fall inside "this period" moves.
Automatic sending
The claim goes out from 6am on the morning after your period ends. Settings shows the exact date of the next one, so a quiet Monday is a fact rather than a worry.
An automatic claim will not go out while trips are still sitting in your Inbox. Unsorted trips are not on the claim, so sending it anyway would email a claim that is short by those miles, and the next period would never look back for them. Refusing is recoverable. A quietly short claim already sitting in Accounts is not. Clear the Inbox and it sends.
Sending it yourself
The Report tab sends the period you are looking at, whenever you want. You can step back through previous periods with the arrows.
If any of that period has already been claimed, the button becomes Resend. That sends a copy: it says so in the subject, it marks nothing as newly submitted, and nobody gets paid twice for it.
Checking one arrived
Settings, then Sent claims, lists every claim this account has emailed and what happened to it. Each row is honest about how much its status is worth, because "opened" is an inference rather than a receipt, and chasing a payment on the strength of a misread status wastes your morning.
Looking at a claim before it goes
Report has a View claim report option that renders exactly what your accounts team will see, including periods you have already sent. Worth doing once, early, so you know what you are asking someone to approve.
Still stuck? Ask us, or use Help inside the app.