Reimbursements
Reimbursements are how an employee claims back money they spent out of their own pocket. Anyone can file a claim, their supervisor approves it, and Treasury pays it out. Unlike petty cash there is no float to replenish β the employee is simply paid back.
Overview
There are two ways in:
- Treasury β Reimbursements β the Treasury panel, where the people who pay claims review them and track each one's payment. Needs the reimbursement access permission.
- Reimbursements (from your own dashboard widget or
/reimbursements) β your own claims. Every employee has this; no special permission needed.
Both open the same claim detail page; you simply see different actions on it depending on your role.
Filing a claim
A claim has a short description and one or more expense lines β one line per receipt or invoice. For each line you record what it was for, the category, the date on the receipt, the amount, and (when the receipt shows them) the vendor's name, tax ID and tax invoice number.
You can attach a photo or scan of the receipt to a line. If you upload the receipt first, ANTE reads it and fills the line in for you; you can correct anything before saving.
Once a receipt is attached, click its file name to open the photo full-screen and double-check it before you submit the claim.
The total is calculated from the lines β you never type it.
If a line's receipt date is in the future, ANTE refuses to submit the claim β a receipt cannot be issued tomorrow, so correct the date before you can continue.
If a receipt date is over a year old, ANTE doesn't block you β some late filings are legitimate β but before submitting it shows a Check these receipt dates dialog naming each old-dated line, since a wrong year is the most common receipt mistake. Choose Go back to fix a date, or File anyway to submit as it is.
When a receipt has no year printed on it, ANTE fills one in for the line automatically β from the photo's own date when it can read one, otherwise from today's date β and shows a note under the date explaining where the year came from, so you can check it before submitting.
A line's VAT amount must be less than that line's amount β ANTE won't save a claim if any line's VAT is equal to or greater than the expense itself.
Linking meetings for context
While filing a claim you can link meetings from your own calendar as context for an expense β for example, "this dinner was for these client meetings." It's optional, and it never blocks you from filing.
Automatic linking
Once a line has a date β usually filled in for you the moment you attach a receipt photo, since ANTE reads the date off it β ANTE looks at your own calendar for meetings on that day. If there are none that day, it falls back to the day before instead (never a mix of both).
Meetings held at a real place are preferred. A meeting that is only a video-call link (Google Meet, Zoom, Microsoft Teams) is never attached for you automatically β a video call is a weaker explanation for a restaurant bill than a meeting with an actual venue β but you can still add one yourself in the picker if it applies.
Up to 3 meetings are linked automatically (10 in total per claim). They appear as removable chips, each showing the meeting's title, date, and where it came from. A banner above them explains which day they were pulled from, with Review (opens the picker to look them over) and Undo (removes what was linked automatically) actions.
The moment you remove a chip or confirm the picker yourself, ANTE stops auto-suggesting meetings for the rest of that claim β from there, linking is entirely up to you.
Adding meetings by hand
Click Add meetings to open a picker over your own calendar.
The picker lets you:
- Search your meetings by title
- Widen or narrow the date range (it opens on the days around your claim's expense dates, and stays editable for a claim filed weeks late)
- See at a glance whether each meeting was In person or Online, and where it came from β your internal ANTE calendar, Google Calendar, or a governance Meeting
Tick up to 10 meetings in total and click Link meetings to confirm.
The claim description
As soon as meetings are linked, ANTE writes the claim's Description for you as a short phrase drawn from them. While that stands you can Rewrite it (ask ANTE to write it again) or Clear it. The moment you type your own words into the field, they're yours β ANTE never overwrites anything you've typed.
Where linked meetings show up later
Any meetings linked to a claim also appear on its detail page, in a Linked meetings section with each meeting's title, time, location, and source β visible to anyone who can open the claim, including its approver.
The approver also sees them without opening the claim: the reimbursement's approval task shows a count of linked meetings and their titles alongside who requested the claim and its amount.
Expense line details
Open a claim to see each expense line laid out as its own block, in the order it was filed. Every field captured on that line is shown: the description, category, and amount, plus the transaction date, vendor name, vendor TIN, vendor address, tax invoice number, VAT amount, and withholding tax β whichever of these the receipt had.
If a receipt photo was attached, it appears as a thumbnail β click it (tap it on the mobile app) to open it full-screen, then click it again or press Esc to close. A line filed without a receipt shows No receipt attached instead. A line ANTE filled in automatically from the receipt photo is marked AI-filled.
Claim status
| Status | Meaning |
|---|---|
| Pending Approval | Waiting for your supervisor to decide |
| Awaiting Payment | Approved β Treasury has not paid it yet |
| Paid | Released to the employee |
| Rejected | Turned down, with a reason |
| Cancelled | Withdrawn by the filer before approval |
While a claim is still Pending Approval the person who filed it can cancel it.
Account coding
If your company uses Multibook, every line on a claim is quietly assigned a GL account behind the scenes as soon as it's filed β you never see this as the filer. ANTE tries, in order: an AI suggestion (reading the line's description, category, and vendor against each account's guideline), a keyword match on the line's category (automatically choosing the taxed or untaxed version of an expense type based on the VAT captured on the receipt, when your company's Multibook publishes both), and finally the company's fallback expense type. A line can be left uncoded if none of these resolve it.
People with the reimbursement release permission (the same one needed to pay a claim) see an Account coding section on the claim detail page while it is still Pending Approval. Each line shows:
| Field | Description |
|---|---|
| Current coding | The GL account currently assigned to the line, with a badge showing how it got there β AI suggested, Keyword, Fallback, Accountant, or Uncoded |
| GL account | A picker to change the line's account, listing each Multibook expense type as account Β· expense type (tax) |
Change any lines that need it and click Save coding. Once the claim is approved, the coding becomes part of the books, so get it right beforehand β the section no longer appears after that.
The account picker needs your own Multibook connection (My Profile β Connections), the same as Sync to Multibook below. If your company doesn't use Multibook, or your own connection isn't linked, you still see each line's current coding, just without a way to change it here.
This section is for claims approved in ANTE. A claim approved in Multibook was already pushed there at filing, so Save coding on it is refused β correct its lines in Multibook during its own approval instead.
Approval
When you file a claim it goes to your direct supervisor as an approval task. If you have no supervisor on record, the claim is approved automatically.
Your company can choose which approval flow reimbursements follow under Settings β Workflows β Reimbursement Workflow β either the built-in single-supervisor flow or a custom multi-stage one. Approvers get 24 hours by default before the task is flagged as overdue.
The tagged approver for the claim's current stage β or a full-access administrator β sees Approve and Reject buttons right on the claim detail page while it is Pending Approval. Nobody else does: the person who filed the claim never sees these buttons, and neither does anyone whose turn hasn't come up yet.
- Approve decides the current stage. Once the claim clears its last approval stage, ANTE automatically generates the Request for Payment that pays it back β see Paying a claim below.
- Reject opens a dialog asking for a reason (shown to the employee) and is required before you can submit. Rejecting at the approval stage is terminal β unlike sending a task back for revision, the claim is turned down outright and the employee must file a new claim; there is nothing to resubmit.
Paying a claim
Once a claim is approved, ANTE automatically generates a Request for Payment to pay the employee back β the supervisor's approval already authorized the spend, so this request needs no further approval and is created ready to release right away. Treasury pays the claim by releasing that request from Treasury β Payables β Request for Payment, not from this page.
The reimbursement list's Release status column, and the same field on the claim detail page, show that request's live status β For Releasing, Payment Released, Rejected, or Cancelled β so you can see where a claim's payment stands without leaving this page.
If the Request for Payment is rejected or withdrawn, the claim is rejected too automatically, with the same reason β there is nothing extra to do. In the rare case an approved claim is left showing a Release status of Rejected or Cancelled, a Reject button appears on the claim so Treasury can clear it.
This hand-off is for claims ANTE itself owns the books for. A claim approved in Multibook, or any other claim with no linked Request for Payment, still pays directly from this page β Treasury sees two actions:
- Pay out β choose the fund account the money comes from. The balance is deducted and the payment is posted to the books.
- Reject β decline the claim at the payment stage, with a reason.
Working with Multibook
If your company uses the Multibook ERP, reimbursements can flow into it so nobody types the same expense twice. There are two ways this is set up, chosen by an administrator on Settings β Multibook:
- Approved in ANTE (the default) β everything above works exactly as described, and an approved claim can additionally be pushed to Multibook by hand. That is the Sync to Multibook section below.
- Approved in Multibook β the claim goes into Multibook the moment you file it, and Multibook's own approvers decide it. See When Multibook approves further down.
Companies that do not use Multibook are unaffected by any of this.
Sync to Multibook
Used when approval happens in ANTE. An approved claim is pushed into Multibook as an Expense Reimbursement (ERCM110) document.
Before you can use it
- An administrator has set up Multibook under Settings β Cloud Credentials, including a write API key.
- You have linked your own Multibook account under My Profile β Connections. The document is created as you in Multibook, so your own login is used β never a shared account.
- You have the reimbursement release permission (the same one needed to pay a claim).
Doing it
Open the approved claim and choose Sync to Multibook.
The dialog asks for:
| Field | What to choose |
|---|---|
| Expense document type | The Multibook document type, e.g. the one your company uses for expense reimbursements |
| Multibook employee | The employee record in Multibook the claim is filed for |
| Document description | Pre-filled as Reimbursement <Month Year> - <expense types>; edit it if you need to |
| Account (per line) | A picker for each receipt line, listing each Multibook expense type as account Β· expense type (tax) β pick by the GL account it books to |
ANTE suggests everything it can work out on its own β the employee, the description, and the account for each line. A line already coded in Account coding keeps that decision; anything else falls back to a keyword match on the line's category. Anything ambiguous is left blank for you to choose.
Submit for approval in Multibook is ticked by default, which files the document for approval straight away. Untick it to leave the document as a draft you can still edit in Multibook.
After syncing
The claim shows the Multibook document number, along with who synced it and when, and the Treasury list gains a Multibook column showing the same number. The Sync to Multibook button disappears β a claim can only ever create one Multibook document.
If a sync fails, the claim shows a Multibook sync failed banner naming the reason and what to do next, and the filer is notified with the same next step. Which button appears depends on what went wrong:
| What went wrong | Button | What it does |
|---|---|---|
| Multibook rejected the claim's own data (a value it doesn't accept) | Correct and refile | Cancels this claim and reopens the filing dialog pre-filled with the same receipts, expense lines, and meetings, so you only fix what was wrong |
| The company's Multibook setup, your own Multibook connection, or Multibook itself was the problem | Retry | Re-queues this same claim once the underlying problem is fixed β nothing is re-typed |
Only the person who filed the claim sees these buttons, and only while the claim is still Pending Approval. ANTE checks Multibook before creating anything on a retry, so a failed attempt can never leave you with the same expense filed twice.
Receipts
Any receipt files attached to the claim's expense lines are copied onto the Multibook document automatically, appearing under its Attach section β you don't need to attach them again by hand. This is best-effort: if a particular file can't be copied (for example it's unusually large, or was removed from ANTE), the document is still filed without it.
As the manual expense reimbursement process requires, Accounting still attaches the Expense Reimbursement Form in Multibook before posting the document.
If something is missing
| Message | What to do |
|---|---|
| "Connect your Multibook accountβ¦" | Link your Multibook account under My Profile β Connections |
| "Your Multibook connection is read-onlyβ¦" | An administrator needs to add a Multibook write key in Settings β Cloud Credentials; reconnect afterwards |
| "β¦accounting periodβ¦ is not open" | Correct the date named in the message, or ask your Multibook administrator to open the current accounting period in Multibook |
| "β¦requires a departmentβ¦" | Ask an administrator to set the default department under Settings β Multibook β Departments |
| "β¦is a grouping level, not an actual departmentβ¦" | Ask an administrator to pick a leaf (actual) default department under Settings β Multibook β Departments |
| "β¦the tax invoice number is β¦ characters, but Multibook accepts at most 20β¦" | Shorten the tax invoice number on the expense line named in the message β Multibook accepts at most 20 characters β and sync again |
| Any other message from Multibook itself | Multibook refused the document β the text explains what it objected to (for example an employee with no approval route set up) |
When Multibook approves
If your administrator has set Approved in: Multibook, filing works a little differently:
- You must link your Multibook account first. The document is created in Multibook as you, so the filing form asks you to connect your account before you can start. There is a Connect button right in the form.
- You never pick an expense type or GL account. Just fill in the description, category, date, and amount as usual β ANTE codes each line's account automatically (AI, then keyword matching, then the company's fallback expense type) the moment you file, before the document reaches Multibook. If no rung can resolve a line, filing fails and tells you what to fix (usually asking your administrator to set a fallback expense type or an account guideline).
- You never pick a department either. ANTE sends the Multibook department an administrator set under Settings β Multibook β Departments. There is nothing for you to do here unless filing fails asking for one.
- The tax invoice number on each line is checked before filing reaches Multibook. Multibook accepts at most 20 characters for it β a longer number is refused right when you submit, naming the expense line so you can shorten it and file again.
- Receipt files on your expense lines are attached automatically. Anything you uploaded to a line rides along onto the Multibook document β see Receipts.
- The claim goes straight to Multibook when you submit. No approval task appears in ANTE; Multibook's own approvers decide it, exactly as if you had typed it into Multibook yourself.
- The claim shows its Multibook document number and follows Multibook's progress. ANTE checks with Multibook each time you open the claim, so the status catches up on its own β there is nothing to press. It stays Pending Approval until Multibook fully approves it (both the manager and accounting stages), at which point it becomes Awaiting Payment and you are notified.
- If Multibook sends the claim back, it stays Pending Approval in ANTE and you are notified. Sending back is not a rejection β amend the expense document in Multibook and re-submit it there, and ANTE will follow it through to approval.
- If Multibook keeps refusing the filing with an internal error β rather than a normal rejection message β ANTE stops retrying after 3 attempts, notifies you, and shows the same Multibook sync failed banner described above with Correct and refile, since this usually means a value on the claim is not accepted there rather than a passing outage. A genuine outage gets Retry instead, and ANTE keeps retrying that automatically for longer before giving up and asking you to retry by hand.
- If your own Multibook sign-in is the problem β ANTE cannot even reach Multibook under your connection β it gives up sooner than either case above, after 2 attempts, since retrying a broken connection can't fix it. You are notified and shown the same Multibook sync failed banner asking you to reconnect your account under My Profile β Connections, then use Retry.
- Withdrawing and rejecting happen in Multibook. Once the document is in Multibook, ANTE will not let you cancel or reject it β do that in Multibook so both systems agree.
- Paying out still happens in ANTE. Because Multibook has already recorded the accounting, ANTE only records the cash movement β so the claim must be paid from a fund account that is not mapped to a GL account. If you see a message about that, pick a different account or ask your accountant which one to use.
If filing is blocked
If you haven't linked your own Multibook account yet, the "New Reimbursement" form shows Connect your Multibook account instead of the form, with a Connect Multibook button right there.
If you have linked your account but submitting still fails β for example none of a line's coding rungs could resolve an account β the form shows the reason Multibook (or ANTE's coding step) gave, and the claim is not filed. Fix what it names (often asking your administrator to set a fallback expense type) and try again. The same common Multibook messages listed under Sync to Multibook β If something is missing β a closed accounting period, a missing department, or a department that's a grouping level β can also show up here, since filing straight to Multibook goes through the same checks.
"Still being filed in Multibook"
Occasionally a filing is interrupted before ANTE learns whether Multibook accepted it β a dropped connection at exactly the wrong moment. The claim then shows Still being filed in Multibook.
Do not file the claim again while this shows. ANTE re-checks with Multibook every time the claim is opened, and resolves it by itself: if the document did reach Multibook, the claim adopts it and carries on; if Multibook confirms it never arrived, the claim is released so you can file it again. Filing a second copy in the meantime is the one thing that produces a duplicate expense.
Related pages
- Request for Payment β where Treasury releases the payout an approved claim automatically generates
- Settings β Multibook β where an administrator chooses ANTE- or Multibook-approved filing
- Settings β Cloud Credentials β where Multibook is configured for the company
- My Profile β Connections β where you link your own Multibook account