Signing in with your email and password

This is how everyone reaches the system day to day.

1. Open the app in your browser and go to the sign-in page.
2. Enter your Email and Password.
3. Optionally tick Remember me.
4. Select Login.

What happens next: if your details are correct, you land on your Dashboard. If your organisation requires a new password (see below), you’re taken to the Set your password screen instead. If you belong to more than one organisation with no organisation chosen yet, you’re taken to Select Organisation instead (see below). If your email or password is wrong, a message appears above the Login button and you stay on the sign-in page.

Signing in with your company account (SSO)

If your organisation uses this: some organisations let staff sign in with the same account they already use for their company email or Microsoft 365, instead of a separate password.

1. On the sign-in page, look above the Email/Password form for a button reading Sign in with Microsoft (or another provider your organisation has set up).
2. Select it.
3. You’re sent to your organisation’s own sign-in page to confirm who you are.

What happens next: you’re brought back to the app already signed in, and land on your Dashboard. The Email/Password form on the sign-in page still works even when this button is present. SSO is an extra option, not a replacement.

Setting a new password when the system asks

An administrator can require you to choose your own password the next time you sign in, for example after your account is first created. When this applies to you, signing in with your temporary password takes you straight to a Set your password screen instead of your dashboard, with a notice that reads “Your account requires a new password before you can continue.”

1. Enter a password in New password (at least 6 characters).
2. Re-enter the same password in Confirm new password.
3. Select Set password & continue.

What happens next: your new password takes effect immediately and your temporary password stops working. You’re taken straight to your Dashboard, no need to sign in again.

Forgetting your password

Use this when you can’t remember your password and need to set a new one.

1. On the sign-in page, select Forgot Password?.
2. Enter the email address you sign in with.
3. Select Send reset link.
4. Check your inbox for an email with a reset link, then open it.
5. On the page it opens, enter a new password in New password and again in Confirm new password, then select Update password.

What happens next: after step 3, you’ll see “Check your inbox” whether or not an account exists for that email. That’s normal, and it doesn’t confirm one way or the other, for your security. The reset link expires 60 minutes after you request it. After step 5, you see a confirmation and are returned to the sign-in page automatically after a few seconds.

Choosing an organisation, and switching organisation

If you belong to more than one organisation: your login isn’t tied to a single organisation. The same email and password can give you access to more than one, each with its own claims, categories and people.

Choosing an organisation (first time, or when you have no preference set)

If you sign in and the system can’t tell which organisation you mean, you’ll see a Select Organisation screen listing each organisation you belong to, along with your role in it.

1. Select the organisation you want to work in.

What happens next: you’re taken to its Dashboard. The system remembers this choice, so next time you sign in you’re usually taken straight there without being asked again.

Switching to a different organisation

1. Select your name near the bottom of the left-hand menu.
2. In the menu that opens, select the entry showing your current organisation’s name, labelled Switch organisation.
3. In the Switch Organisation dialog, choose the organisation you want, then select Switch.

What happens next: the page reloads inside the newly selected organisation, and everything you see afterwards (claims, categories, people) belongs to that organisation instead.

Updating your profile and bank details

Use this to correct your name, set a new password without signing out first, or give Finance your bank details for reimbursement.

1. Select your name near the bottom of the left-hand menu, then Edit Profile.
2. On the Profile tab, update your Name. Email, Date of Birth and Department(s) are shown for reference only, so ask your administrator to change these. To set a new password at the same time, fill in Current Password and New Password under Change Password (optional); leave both blank to leave your password as it is.
3. Select the Bank Info tab to enter your Bank Name, Account Number and Account Holder Name. Finance uses these to pay your reimbursements.
4. Select Save Changes.

What happens next: your changes take effect immediately. If you set a new password, use it the next time you sign in. The third tab, Claim for Me, is covered below.

Letting someone claim for you

Use this if you’d like someone else, such as an assistant or a colleague, to enter and submit your claims for you. The claims stay yours: your spending limits and your approver apply, exactly as if you’d submitted them yourself.

1. Select your name near the bottom of the left-hand menu, then Edit Profile.
2. Select the Claim for Me tab.
3. Under People who can claim for me, choose the Person from the list.
4. Optionally pick an End date (optional) after which they can no longer claim for you. Leave it blank to keep it in place until you revoke it.
5. Select Authorise.

What happens next: the person appears in the list, showing until [date] or until revoked, and they’re told in My Feed and by email that they can now submit claims on your behalf. Everything on this tab takes effect straight away, so there’s no Save Changes button; select Close when you’re done. Whenever they submit a claim for you, you’re told in My Feed and by email, and the claim appears in your own My Claims like any other. They can only see and change the claims they entered for you, not your other claims. To see how they make a claim for you, see Claiming for someone else.

To stop someone claiming for you, select Revoke next to their name and confirm. Claims they’ve already entered stay yours, but they can no longer change them.

The same tab also lists People I can claim for: everyone who has authorised you. Select Stop next to a name if you no longer want to claim for that person. An administrator can also set up or remove these authorisations for you.

What the dashboard shows

Your Dashboard is the first thing you see after signing in: a quick summary of your own claims.

• My Claims: a count of your claims that are Submitted, Approved and Rejected.
• AI Insight: a short, plain-language comment on your recent spending, with a Refresh link to regenerate it.
• Spending Limits: a progress bar per category showing how much of your allowance you have left, if your organisation has set any limits that apply to you. If none apply, this area is simply empty.

If you can see the My Reimbursements, All Claims or Reports menu items, your dashboard also shows a Company-Wide section with organisation-level totals, spend by category, and top claimants. This isn’t shown to everyone.

If you can see a Management Dashboard menu item too, it’s a fuller, dedicated version of that same Company-Wide reporting: the same kind of organisation-level figures, with more of them and more ways to break them down, on a page of its own rather than a section of yours.

What happens next: this page is read-only. Use the menu on the left to go to My Claims, My Feed, or wherever you need to work next.

Finding your notifications

Notifications about your claims (for example, a new claim awaiting your approval) collect in My Feed, reached from the left-hand menu. A red badge on My Feed shows how many are unread.

1. Select My Feed in the left-hand menu.
2. Use the All / Unread tabs to filter the list.
3. Select a notification to open the claim it refers to; doing so also marks it as read.
4. If you have several unread notifications, select Mark all read to clear them all at once.

What happens next: notifications you’ve opened lose their unread highlight and no longer count toward the badge on the menu.

One thing worth knowing throughout this guide: most dates you see in the system are shown as DD/MM/YYYY (day/month/year), and that’s the format used consistently in this guide’s own screenshots. A handful of screens instead show a date in whatever format your own browser and operating system are set to, which may or may not be DD/MM/YYYY. A claim’s own Submitted date on its detail page, the date shown on a claim card, and a delegation’s start/end dates are the ones currently affected. So if a date on screen looks unexpectedly different from the rest, that’s why. It isn’t a sign anything is wrong.

Every claim carries a status, shown at the top of the claim page, and moves through these statuses in a predictable way: Draft, Submitted, Approved, Rejected, and Reimbursed. This section explains what each one means and who acts next. Later sections show you the actual screens and buttons.

The dotted arrows only apply if your organisation uses that feature. They’re explained under their own statuses below.

Draft

This is a claim you’ve started but not sent anywhere yet.

• What it means: nobody else can see it. It doesn’t count toward anything until you submit it.
• Who acts next: you.
• What you can still change: everything: title, category, amount, receipts, line items, all of it. You can also delete it.
• Who’s notified: nobody.

Submitted

Your claim has been sent for approval.

• What it means: the claim is locked and waiting on one or more approvers.
• Who acts next: depends on how your organisation has set up approval for that category and amount. Most claims go to a single approver, but if your organisation uses this: a claim can need agreement from more than one person in a group before it moves on, or pass through more than one approval step in sequence. Your claim’s status still just reads Submitted the whole time, even while it’s quietly moving between approvers behind the scenes. If nobody has been set up to approve a claim like this one at all, it still sits at Submitted until Finance or an administrator picks it up directly.
• What you can still change: nothing on the form. If your organisation uses this: you can select Retract to pull the claim back to Draft, edit it, and submit it again from scratch.
• Who’s notified: whichever approver (or approvers) the claim is currently waiting on, by email and in My Feed.

Approved

Your claim has cleared approval and is waiting to be paid.

• What it means: everyone who needed to approve it has done so. Or, if your organisation uses this, the claim was small enough to skip approval altogether and was approved automatically the moment you submitted it.
• Who acts next: whoever handles reimbursement marks it as paid, either on its own or as part of a batch of claims paid together.
• What you can still change: nothing. An approved claim can still be turned down before it’s paid, though, if a problem is found with it.
• Who’s notified: you, as soon as it’s approved.

Rejected

Your claim was turned down.

• What it means: an approver, or Finance if the claim had already been approved, decided not to accept it, and left a reason.
• Who acts next: you. You can fix whatever was wrong and resubmit it, or leave it as is.
• What you can still change: anything, the same as when it was a draft. Resubmitting sends it through approval again from the start, exactly like a fresh submission, including, if your organisation uses this, skipping straight to Approved again if it now qualifies for automatic approval.
• Who’s notified: you, along with the reason it was rejected.

Reimbursed

You’ve been paid for this claim.

• What it means: this is the end of the line for the claim. Nothing more happens to it.
• Who acts next: nobody.
• What you can still change: nothing.
• Who’s notified: you, once it’s marked paid.

Who does what

Row labels above describe a job, not a fixed role name. Your organisation may call the people who do these things something else, or have one person cover more than one of these jobs.

This section covers everything you do as a claimant. That means starting a claim, filling it in, submitting it, and fixing one if it comes back rejected. For what happens to a claim after you submit it, and what each status means, see How a Claim Moves.

Starting a claim from a receipt photo or PDF

This is the fastest way to start a claim. Upload the receipt or invoice and let the system read it for you.

1. Select My Claims in the left-hand menu, then + New Claim.
2. In the Upload Invoices box, drag your receipt or invoice onto it, or select it to browse for the file (JPG, PNG or PDF, up to 10 MB).
3. Wait while it’s read. This takes a few seconds.

What happens next: the file attaches to the claim, and a preview appears alongside the form. Whatever the system can read from it (vendor name and address, date, amount, currency, and any line items) fills in the matching fields for you, and the Category is guessed automatically from the title and line items. Nothing is final, so check every pre-filled field before you submit, especially the amount and date. A scanned PDF, one with no selectable text, is read from the picture of each page, the same way a photo is; only its first three pages are read. Sometimes nothing can be read at all, for example from a blurred or faint scan. When that happens, the file is still attached and marked Extracted in the upload box, but none of the fields actually fill in, so you’ll need to enter them by hand. If the upload itself fails outright, the file’s entry shows as failed instead and nothing is attached; just try uploading it again. (Uploading an invoice from a claim’s own Edit page, instead of here, does tell you directly when nothing could be read from a PDF, and suggests a JPG or PNG instead.)

A small Extract Again link appears once a file is attached, in case you want to re-run the reading on the same file (for example, after uploading a clearer photo of the same receipt). Reading the same file twice gives the same result, so if a field comes out wrong, Extract Again won’t change it: correct it by hand, or upload a clearer copy.

You can add more than one receipt to the same upload box. By default, the toggle above the upload box is set to Split into separate claims, so each file becomes its own claim, in its own tab, and you can review and submit them one at a time or all together. Select Combine into one claim instead to merge every file you add into a single claim. This is useful when several receipts belong to one trip or one expense. A combined claim has one line item per receipt, each with its own file attached, and its total is the sum of those line items. Each of those line items is labelled Invoice 1, Invoice 2 and so on, and has its own Invoice / Receipt No., Company Name, Amount, Transaction Date and Notes, filled in from that receipt where it can be read. Check each one, and use Notes for anything specific to that receipt (for example, who attended). The claim’s own Date of Transaction is then taken from the earliest of those invoice dates and can’t be typed over: to change it, change the date on the invoice itself in Line Items. Extract Again on a combined claim, here or on its Edit page, reads every receipt again and refreshes each one’s own line item; the line items and their files stay as they are. If some receipts can’t be read again, a message says how many, and their line items are left unchanged.

Uploading a Touch 'n Go or other transaction statement

You can upload an e-wallet or card statement (for example a Touch 'n Go eWallet statement) in the same Upload Invoices box. The system recognises it as a statement rather than a receipt and, instead of filling in the form, opens a window listing every transaction it found: date, type (Toll, Parking, Retail and so on), location, transaction number and amount.

1. Tick the transactions you want to claim. Top-ups are shown greyed out and can’t be ticked.
2. Under Create, choose One claim per type (for example, Toll and Parking as separate claims) or One claim for all ticked transactions.
3. Select Create claim (or Create N claims). Each claim opens in its own tab with one line item per ticked transaction, ready for you to check and submit.

Which rows start ticked depends on the statement:

• A photo or scanned statement that you’ve marked with a highlighter: the highlighted rows are found and ticked for you, and rows you’ve crossed out are left unticked. Check them against your copy before you continue.
• Any other statement, including a statement downloaded as a PDF from the app or website: no highlights are picked up (even ones you added in a PDF viewer), so every toll and parking row starts ticked. Untick anything that wasn’t a business trip.

Only the first six pages of a scanned or photographed statement are read. A downloaded PDF statement is read in full, however long it is. If you upload a long statement and the form fills in with nothing (no transaction window appears), split it into shorter date ranges and upload those instead.

Starting a claim from the form

Use this when you don’t have a receipt to scan, or prefer to type everything in yourself.

1. Select My Claims in the left-hand menu, then + New Claim.
2. Leave the Upload Invoices box alone and fill in the form directly, starting with Title.

What happens next: see Filling in the details below for what each field means.

Starting a claim by chatting

Instead of the form, you can describe your expense in your own words and let an assistant turn it into a claim. This page isn’t linked from the menu, so you’ll need its address from your administrator (or your organisation may link to it from somewhere else in the app).

1. Go to the claim chat page.
2. Answer the assistant’s questions about your expense (what it was for, how much, when, and so on) in the message box, and select Send after each one.

What happens next: once the assistant has enough information, it creates a Draft claim behind the scenes and shows you a summary of what it collected. Select Review & Submit to open the claim and check it over. The chat only gets you a starting draft: you still review and submit it the same way as any other claim, and can correct anything the assistant got wrong before you do.

Claiming for someone else

If someone has authorised you to claim for them: you can enter and submit a claim on their behalf, for example for a manager whose receipts you look after. They set this up themselves, in the Claim for Me tab of their profile (see Letting someone claim for you), or an administrator sets it up for them.

1. Select My Claims in the left-hand menu, then + New Claim.
2. At the top of the form, change Claiming for from Me to the person you’re claiming for. This box only appears once someone has authorised you.
3. Fill in and submit the claim as usual.

What happens next: a blue note above the form reads “You are claiming on behalf of [name]. The claim will be theirs: their limits and approver apply.” The claim belongs to them: their spending limits, their departments and branch, and their approver are used, not yours. Choose the person before you start filling in, because once the claim has been saved as a Draft, Claiming for can’t be changed. If you add several receipts as separate claims, each tab has its own Claiming for box.

When you submit, the person you claimed for is told, in My Feed and by email, that you submitted a claim on their behalf. The claim also appears in your own My Claims, tagged For [name], so you can follow it; you’re told in My Feed when it’s approved, rejected or reimbursed. You can edit, submit, retract or delete it the same way as your own claims, but only the claims you entered yourself, not the person’s other claims. On the claim’s page, the Claimant is shown as the person you claimed for, followed by (entered by [your name]).

If the person stops your authorisation, or its end date passes, you can still see the claims you entered for them, but you can no longer change them. You’ll see “Your authorisation to claim for [name] has ended.” instead.

Filling in the details

The claim form is organised into collapsible sections: Claim Details, Custom Fields (if your organisation defines any that apply to this claim), Amount & Currency, Company Information, Line Items, and Supporting Documents. Only one section is open at a time. Select a section’s header to expand it, and its summary (shown when it’s collapsed) gives you a quick look at what’s already filled in without opening it.

Fields in Claim Details, in the order they appear:

• Title: a short description of the expense. Required. Auto-filled from the vendor name if you upload a receipt, but you can always change it. If your organisation has set a title format: the title on a new claim is built for you instead, from your organisation’s pattern (for example your name, the category and the month, such as “John Teh - Entertainment - Oct 2026 (Dinner at ABC)”). The note under the box shows the format. The part in brackets is a short description suggested from the receipt you upload; with no receipt, it’s simply left out. The title keeps itself up to date as you change the category. You can still type over it; the note then reads “Edited by hand.” and a Use format link appears to rebuild it from the format. When claiming for someone else, their name is used.
• Group: if your organisation uses this: which category group this claim’s category belongs to. Required when shown. Pick this before Category, since it determines which categories are offered below it.
• Date of Transaction: when the expense happened, not when you’re filing the claim. Required. On a claim made of several receipts with their own dates (a combined claim, or one created from a statement), it’s set for you to the earliest of those dates and can’t be typed over.
• Category: what kind of expense this is. Required. Select Auto-detect (next to the label) to have it suggested from your Title and any line items you’ve entered. This becomes available once you’ve typed a title. If nothing suitable is found, you’re told to pick manually or check with your administrator. If your organisation uses rate or limit tables for a category: choosing it may add one or more extra dropdowns here, whatever your organisation’s table for that category needs to look up the applicable rate or limit.
• Department / Projects: optional. It defaults to your usual one if you have one; change it if this expense belongs to another department you’re a member of. If you don’t belong to any department, the box tells you so and the claim is submitted without one. Select Refresh next to the label if you’ve just been added to a department and it isn’t listed yet.
• Branch / Entity: optional. Defaults to your own assigned branch or entity if you have one.
• Notes: optional free text for anything else worth recording.

Fields in Amount & Currency (see Claiming mileage if the category you picked is a mileage one, and Claiming in another currency for what the invoice/conversion fields below are for):

• Invoice Amount and Invoice Currency: the amount and currency shown on the actual invoice or receipt. Optional, and filled in automatically from a scanned receipt.
• Conversion Rate: optional. How many units of your claim currency one unit of the invoice currency is worth.
• Claim Amount and Claim Currency: the amount and currency you’re actually claiming. Required. If the invoice currency matches your claim currency, this fills in automatically from the invoice amount.

Fields in Company Information (details about the vendor, mostly filled in from a scanned receipt but all editable):

• Company Name
• Company Address
• Postcode
• State (a dropdown, for a Malaysian address) or State / Province (free text otherwise)
• Country: defaults to Malaysia on a new claim; typing a different country switches State above to free text.
• Tax Invoice / Receipt # / e-Invoice No.

Custom Fields: if your organisation uses this: your administrator can define additional recording dropdowns (for example, which entity or project a claim belongs to). These are for record-keeping only. They don’t affect rates, limits, or who approves the claim. A field marked with an asterisk is required before you can submit. Some fields only apply to certain claims, so which fields appear, and which are required, can change as you pick the Group, Category or Department / Projects in Claim Details. That’s why this section sits right after Claim Details, and why it may disappear altogether for some claims. A field that isn’t shown is never required.

Once you’ve filled in Title, Category and Date of Transaction, you can move between sections freely. The form saves your progress automatically a few seconds after you stop typing, so switching sections or accidentally closing the tab won’t lose your work (see Saving a draft and coming back to it).

Claiming mileage

If your organisation uses this: when the category you pick has a per-kilometre rate configured, the Amount & Currency section replaces the invoice/amount fields above with a Mileage Details box instead.

1. Open Amount & Currency.
2. Fill in Start Location and End Location (optional unless your organisation uses a distance table, see below).
3. Enter Distance (km), and optionally a Description of the trip (for example, “Client visit”).

What happens next: the rate per kilometre is shown at the top of the box, and Calculated Amount updates as you type the distance, and that figure becomes your claim amount. If no rate has been set up for the category, you’ll see a notice to contact your administrator instead of a rate.

More than one trip on one claim

You can put several trips on one mileage claim, for example a week of client visits.

1. Fill in the first trip’s locations, distance and description as above.
2. Select Add under the box. The trip moves into Line Items as a Mileage trip row, and the fields empty, ready for the next one.
3. Repeat for each trip.

The claim amount is then the total of all the trips, shown at the bottom of the box as Total of N trip(s). To change a trip, select its row (or its Edit button) in Line Items; it loads back into the box, where you select Update trip to save the change or Cancel to leave it as it was. Select × on a trip’s row to remove it. If you try to submit while a trip is still sitting in the box, you’re asked to select Add (or Update trip) first, so that it isn’t lost.

Distance tables

If your organisation uses this: Start Location and End Location become dropdowns of your organisation’s usual places. Pick both, and the distance between them fills in for you, with a note saying which distance table it came from; on the trip’s row it shows as Policy distance. A route works in either direction. What you can do next depends on how your organisation has set it up:

• Usually you can still change the distance (it then counts as your own figure), and you can pick Other (type a location) for a place that isn’t listed and type the distance yourself.
• If your organisation only accepts distances from the table, the distance can’t be typed, there’s no Other option, and a route that isn’t in the table can’t be claimed. Ask your administrator to add it.

Adding line items

Line items break a claim down into its individual parts. This is useful for an itemised receipt, or a claim covering more than one thing.

1. Open Line Items.
2. Fill in Description and Amount for each item already listed.
3. Select + Add Item for another row, or the × next to a row to remove it.

What happens next: the Items total at the bottom updates as you go. This is for your own breakdown. It doesn’t need to match your Claim Amount exactly, but a large mismatch is flagged as a warning when you submit (see Submitting your claim). A line item created from a scanned receipt shows a View link to its source image.

Two kinds of line item look different from the plain description-and-amount rows: on a combined claim, each receipt is an Invoice row with its own number, company, date and notes (see Starting a claim from a receipt photo or PDF), and on a mileage claim, each trip is a Mileage trip row that you change from the mileage box (see Claiming mileage).

Attaching supporting documents

Use this for anything beyond the main invoice: a bank statement, a bank-in slip, or an additional receipt.

1. Open Supporting Documents.
2. Drag a file onto the box, or select it to browse for one (JPG, PNG or PDF, up to 10 MB each, up to 5 files per claim, see A file won’t upload if you need to attach a spreadsheet or document instead).

What happens next: each file appears in a list with View and Remove options. Once a claim is submitted, only an administrator can remove an attachment: as the claimant, you can only add or remove files while it’s still a Draft. If you haven’t filled in Title, Category and Date of Transaction yet, attaching a file saves the claim as a Draft first automatically; if those three aren’t filled in, you’re asked to complete them before you can attach anything.

Claiming in another currency

Use this when the invoice or receipt is in a currency different from what your organisation claims in.

1. In Amount & Currency, enter the Invoice Amount and select the Invoice Currency.
2. Enter a Conversion Rate, or select Get BNM Rate to fetch the current rate from Bank Negara Malaysia for that currency.
3. If you fetched a rate, review the figure shown, for example “Invoice Amount × Rate = Converted Amount”, and select Apply to use it as your Claim Amount.

What happens next: the BNM rate is shown with the date it was quoted, alongside the buying and selling rates for reference. Applying it fills in Claim Amount in your claim currency; you can still adjust the figure by hand afterwards if needed.

Which day’s rate you get depends on your organisation’s setting, and a note under Conversion Rate tells you which before you fetch: “Get BNM Rate uses today’s rate.” or “Get BNM Rate uses the rate on the transaction date.” With the transaction-date setting, enter the Date of Transaction first. If BNM published no rate that day (a weekend or public holiday, for example), the last rate before it is used, and the note under the rate says so. If you haven’t entered a date yet, or it’s in the future, the latest rate is used instead.

A rate fetched with Get BNM Rate stays in step with the claim: if you change the Invoice Currency (or, with the transaction-date setting, the Date of Transaction), the rate is fetched again automatically. A rate you typed yourself is never replaced. For a few currencies BNM only publishes today’s rate, so with the transaction-date setting you’ll be asked to enter the rate yourself.

Saving a draft and coming back to it

A claim doesn’t have to be finished in one sitting.

1. Fill in at least Title, Category and Date of Transaction: these are required even to save a draft. Everything else, including the amount, can be left blank for now.
2. Select Save Draft.

What happens next: you’re taken to the claim’s own page, which now shows it as a Draft. The form also saves your progress automatically a few seconds after you stop typing, once the draft exists, so you don’t need to select Save Draft repeatedly. To come back to it later, find it in My Claims and open it. A Draft shows an Edit Draft button to keep filling it in, and a Submit button once you’re ready to send it for approval. See Submitting your claim below for what happens next, and for an important difference between these two ways of submitting.

Checking what’s left of your allowance

If your organisation has set a spending limit on a category, you can see how much of it you have left before you submit.

• On your Dashboard, the Spending Limits section shows a progress bar per category with a limit that applies to you, see What the dashboard shows.
• While filling in a claim, once you’ve picked a Category and entered a Claim Amount, a banner appears near the bottom of the form, above the Submit Claim button, if this claim would approach or exceed the applicable limit, before you even get to Submit.

What happens next: this is informational. It doesn’t stop you from filling in the rest of the claim. See below for what happens when you actually try to submit one that trips a limit.

Submitting your claim, and what the limit warning means

Once a claim is filled in, submitting sends it for approval. See How a Claim Moves for what happens after that.

If you’re submitting a Draft you saved earlier, there are two ways to do it, and they behave differently. Opening the Draft from My Claims and selecting Submit right there on the claim’s own page skips straight to submitting, with no chance to review the warnings described below first. To see them before you commit, select Edit Draft instead and submit from the form itself, as covered here.

1. Select Submit Claim (or Submit This Claim if you have more than one claim open in separate tabs) at the bottom of the form.

What happens next: if nothing looks unusual, the claim is submitted immediately. You may see a brief confirmation with a View claim option before you’re taken to it. Otherwise, a Review Before Submitting dialog appears, summarising everything worth your attention before you go further. You may see one or more of:

• Spending Limit Exceeded or Approaching Spending Limit: this claim would put you over, or close to, a limit your organisation has set for this category.
• Category May Not Match: the claim’s content doesn’t look like it belongs in the category you picked.
• Possible Duplicate Claim: it matches an existing claim of yours closely enough (same amount, vendor, reference number, or attached file) to be worth a second look. On a combined claim, every receipt is checked separately, against your earlier claims and against each receipt inside them, and the message names the receipt that matched, for example “Invoice 2 (Grab, MYR 50.00)”.
• Submission Window Exceeded: the transaction date is further in the past than this category allows for a new submission; a different category may allow more days, fewer, or have no deadline at all. If your organisation still accepts late claims in that category, a Reason for late submission box appears on the form, and you must fill it in before you can submit. Your approver sees the reason. A note under the box tells you if the claim will also go to a different set of approvers because it’s late.
• Amount Mismatch (or Faulty Invoice, if you attached one and it’s the only line item): your line items don’t add up to your claim amount.

Select Proceed Anyway to submit regardless, or Cancel to go back and fix something first. Occasionally your organisation may configure one of these checks strictly enough to block submission outright rather than just warn you. In that case you’ll see an error message instead of this dialog, and you’ll need to change the claim or contact your administrator before you can submit.

Tracking your claim

1. Select My Claims in the left-hand menu.
2. Use the card or table view (a toggle near the top of the list remembers your preference) to browse your claims, each showing its current status.
3. Select a claim’s title (in card view) or its View button (in table view) to open it and see its full detail, including its history of what’s happened to it so far.

What happens next: a claim’s status updates as it moves through approval. See How a Claim Moves for what each one means and who acts on it next. Any warning you saw (and proceeded past) when you submitted stays visible as a small flag on the claim afterwards, so it’s easy to spot which of your claims were flagged for a reviewer’s attention. In table view, a Draft or Submitted claim of yours also shows Edit/Delete or Retract directly in its row, alongside View, so you don’t always need to open it first. A claim you entered for someone else is tagged For [name] (see Claiming for someone else).

On a claim’s own page, selecting View next to its invoice or a supporting document opens the document in a panel beside the claim, so you can read both at once. Select Close document to go back to the single column. On a narrow screen, such as a phone, there’s no room for the panel, so a PDF opens in a new tab and a photo opens on top of the page instead.

Editing a claim before it’s approved

A claim can only be edited freely while it’s a Draft (or, once rejected, see Fixing a rejected claim below). Once submitted, it’s locked until it’s approved, rejected, or (if your organisation allows it) retracted back to Draft.

1. Open the Draft claim from My Claims.
2. Select Edit Draft.
3. Make your changes, then select Save Draft to keep it as a Draft, or Submit Claim when you’re ready to send it for approval.

What happens next: any field can be changed, added to, or cleared: title, category, amount, receipts, line items, all of it. Nothing is sent anywhere until you submit.

Fixing a rejected claim and resubmitting

A rejected claim isn’t final. You can correct whatever the approver flagged and send it through again.

1. Open the rejected claim from My Claims.
2. Select Edit & Re-submit.
3. Read the Rejection reason shown at the top of that page.
4. Make whatever changes address the reason it was rejected, then select Re-submit Claim.

The rejection reason is also recorded lower down on the claim’s own page, under History, if you want to check it without opening the edit page.

What happens next: the claim goes through the same checks and warnings as a brand-new submission (see Submitting your claim above), and moves back to Submitted, starting approval over from the beginning, exactly as if you’d just filed it, including automatic approval again if it now qualifies. If you don’t need to change anything and simply disagree with the rejection, you can still open it and resubmit as-is; there’s no requirement that something be different.

This section is for anyone who gets claims sent to them to approve.

Whether you can approve depends on your permissions, not your job title. If you can see My Approvals in the sidebar, this section is for you. If you can see My Reimbursements, you can also act on the claims Finance handles, including any that nobody else has been asked to review. For what each claim status means and who acts next at every stage, see How a Claim Moves.

Finding claims waiting for you

Claims waiting for your decision collect on one page.

1. Select My Approvals in the left-hand menu. A badge next to it shows how many claims are currently waiting on you. If you were named as an approver individually, rather than through managing a department or branch, this menu item may not appear for you even though claims are genuinely waiting on you. Ask your administrator for the address to go to directly in that case (the screenshot below is exactly this case: an individually named approver, reached directly at that address rather than through the menu).
2. Look under Pending Review. It lists every claim currently waiting on your decision, oldest submission first.
3. Use the card or table view (a toggle near the top of the list) to browse them.

What happens next: select a claim’s title to open it and decide. See Reviewing a claim before you decide below. Once you’ve approved or rejected a claim, it moves out of Pending Review and into Reviewed underneath (collapsed by default). That’s a record of decisions you’ve already made, not something you can act on again from there.

Reviewing a claim before you decide

Before approving or rejecting, open the claim itself and check it properly rather than deciding from the list.

1. From Pending Review, select the claim’s title to open it.
2. Check, in particular:
   • Claim Amount, and, if it was claimed in another currency, the invoice amount and conversion rate underneath it.
   • Claimant. If someone else entered the claim for this person, their name follows in brackets: “(entered by” and then that person’s name. See Claims entered on someone’s behalf below.
   • Category. A Category may not match notice appears if the claim’s content doesn’t look like it belongs there.
   • Any invoice or attachments. Select View to open them. On a computer screen they open beside the claim. See Viewing an invoice beside the claim below.
   • Line Items. A claim that combines several invoices lists each invoice as its own line, with its invoice number (shown as “No.” followed by the number), its date and any notes the claimant added for it. The claim’s Transaction Date is the earliest of those invoices, and underneath it you’ll see the range they span, starting “Invoices”.
   • Any warning banner near the top of the page: an exceeded or approaching spending limit, a late submission (with the claimant’s Reason for it), a mismatched amount, or a possible duplicate. If the claimant proceeded past a particular warning when they submitted, that banner also says so (“Acknowledged by the claimant at submission”). A banner with no such note wasn’t. The same warnings also show as small flags (for example, ⚠ Over limit or ⚠ Possible duplicate) on the claim’s row back in My Approvals, so you can spot a flagged claim before you even open it.
   • If your organisation uses them: a ⚠ Custom rule flagged badge, naming a policy the claim appears to break. See When a claim is flagged by a Custom Rule below.
   • History at the bottom of the page: the full timeline for this claim, including a previous rejection and resubmission, if it’s been through that.

What happens next: this step doesn’t change anything by itself. It’s just what you check before deciding to approve or reject.

Viewing an invoice beside the claim

You can read an invoice or supporting document side by side with the claim’s details, rather than switching between tabs.

1. Open the claim.
2. Select View next to the file under Invoice, or next to any file under Supporting Documents.
3. To put it away, select Close document above it.

What happens next: the page widens into two columns, with the claim on the left and the document on the right. The document stays in view as you scroll down the claim, so you can check each figure against it. Selecting View on another file swaps it in. This only happens on a screen wide enough for two columns, such as a laptop or desktop. On a phone or a narrow window, View works as before: a PDF opens in a new tab and a picture opens over the page.

Approving a claim

Use this once you’ve reviewed the claim and it’s good to go.

1. Open the claim, or find its row in My Approvals.
2. Select Approve.
3. If your organisation requires a comment when approving: the Approve Claim dialog opens. Enter a comment (the claimant will see it), then select Approve. You can’t approve without one. Whether this applies is set by your administrator, not by you.

What happens next: if this is the only approval the claim needs, its status becomes Approved immediately and the claimant is notified right away. Any comment you wrote is added to the claim’s History next to your approval, and included in the claimant’s notification. See Approved. If your organisation uses this: your approval might instead be one of several needed at the current step. In that case the claim stays Submitted, your decision is recorded, and nothing changes for the claimant yet, not until enough other people have also approved. See When a claim needs more than one approval below. A claim can also need to pass through a further step after yours; in that case it simply moves on to whoever is next, still Submitted.

Rejecting a claim and writing a reason

Use this once you’ve reviewed the claim and found a problem with it, or decided not to accept it.

1. Select Reject, from the claim’s own page, or its row in My Approvals.
2. In the Reject Claim dialog, enter a reason. This is required, and the claimant will see it.
3. Select Reject to confirm.

What happens next: the claim moves to Rejected and the claimant is notified immediately, together with your reason. They can fix whatever was wrong and resubmit it. See Fixing a rejected claim and resubmitting. If you can see the My Reimbursements menu, you can also reject a claim that’s already Approved, if a problem turns up before it’s paid. An assigned approver can’t do this once their part is done.

Approving or rejecting several claims at once

When you have a number of claims waiting, you can tick the ones you’ve checked and decide them together, instead of opening each one in turn.

1. In My Approvals, under Pending Review, tick the box beside each claim you want. In the table view, the box in the heading row ticks every claim on the current page. A claim you can’t act on has its box greyed out.
2. A bar appears above the list, showing how many claims you’ve selected and their total. Select Select all (followed by a number, for example Select all 12) to take in every claim you can act on, across all pages, or Clear to start again.
3. Select Approve selected or Reject selected.
4. To approve, check the dialog that opens (headed, for example, Approve 3 Claims). It shows the total, and lists by name any selected claim that carries a warning (for example “over limit” or “possible duplicate”), so nothing flagged slips through unnoticed. If your organisation requires a comment when approving, enter one here: the same comment is recorded on every claim. Then select Approve 3 (or however many you chose).
5. To reject, enter one reason in the dialog (headed, for example, Reject 3 Claims). The same reason is recorded on every claim, and each claimant will see it. Then select Reject 3.

What happens next: the claims are dealt with one after another, and the button counts them off as it goes. Each one is approved or rejected exactly as if you’d done it on its own, with the same notifications, so a claim needing further approvals still moves on to its next step. Open and review each claim first, as described in Reviewing a claim before you decide: selecting them together saves clicks, not checking. When it finishes, a message says how many were approved or rejected. If any couldn’t be, for example because someone else decided it first, the message names each one with the reason, and those claims stay ticked so you can try again or deal with them separately.

Emails you get about claims waiting for you

You are always told inside the app when a claim reaches you. Whether you also get emails about it depends on two settings your administrator chooses for the whole organisation:

• An email for each claim. Normally, every time a claim is sent to you, you get an email about it. For a claim needing only your approval, it includes a one-click approval link (see Approving from an emailed link, without signing in below). Your organisation can switch these emails off, usually because it uses the digest instead. You still get the in-app notification either way.
• A regular digest. If your organisation uses this: on a set schedule (every day, every weekday, or on chosen days of the week, at a set hour), you get one email headed Claims Awaiting Your Approval. It lists every claim still waiting on you, oldest first, with the claimant, amount, date submitted and how many days it has been waiting. Select a claim’s title to open it in the app, or Open My Approvals to see the whole list. If nothing is waiting on you that day, you get no digest.

What happens next: the digest’s links only open the claim; you sign in and decide it as normal. It never approves anything with one click. Someone can still send you a one-off reminder for a particular claim at any time. See Nudging an approver who hasn’t acted.

Approving from an emailed link, without signing in

When a claim needs only one approval from one person, its approver can also act straight from the notification email, without opening the app or signing in at all. You’ll only have this email if your organisation sends an email for each claim, or if someone has sent you a reminder about it.

1. Open the email about the claim, and select its approval link.
2. On the page it opens, review the claim summary shown: title, claimant, department, category, amount, transaction date, and any reference number or notes.
3. If your organisation requires a comment when approving: type it in the Comment box. The button stays greyed out until you do.
4. Select Approve Claim.

What happens next: the page shows “Claim approved” with the claim’s title, and the claimant is notified immediately, exactly as if you’d approved it from inside the app. This page only offers approval. For anything else (rejecting, editing, viewing attachments), it tells you to log in to the app normally instead. Opening the same link again afterwards, or an old one for a claim that’s since been decided some other way, shows “This claim has already been approved” (or rejected, or whatever it now is) instead of the summary. Every link also stops working on its own after 7 days. Past that point, or if the link was never valid, it shows “This approval link is invalid or has expired” instead.

Nudging an approver who hasn’t acted

If you can see the My Approvals menu yourself, or the My Reimbursements menu, you can prompt a claim’s approver directly instead of waiting on them.

1. Open the claim that’s waiting.
2. Select Send Reminder.

What happens next: you see a confirmation naming the approver’s email address, a fresh copy of their one-click approval email is sent to them, and an Approval reminder sent entry, naming who it went to, is added to the claim’s History, visible to the claimant too. If your organisation uses this: Send Reminder isn’t offered at all once a claim needs more than one approval, or more than one approval step. Reminders currently only work for a claim with exactly one approver; contact that person directly instead.

When a claim is flagged by a Custom Rule

This only appears if your organisation has written Custom Rules. See Writing a policy in plain language.

A Custom Rule is a policy your administrator wrote as a sentence rather than as an amount or a period: something like “users below 50 can claim once per year, 50 and above twice a year”. The system checks each submitted claim against those sentences and passes what it found to you.

You may see either of two badges on the claim, and on its row in My Approvals:

• ⚠ Custom rule flagged — the claim appears to break a policy. The reason names which one.
• ⚠ Custom rule check incomplete — the check couldn’t be finished. This is not a finding about the claim; treat it as no information, and review the claim as you otherwise would.

The decision is yours. A Custom Rule never blocks a claim and never rejects one; it only tells you what it noticed. That’s deliberate, because the check is made by reading the policy rather than by counting, so it can be wrong in both directions. Approve if you’re satisfied the claim is legitimate, whatever the badge says; reject if you agree with it. If a flag looks plainly wrong, tell your administrator, since it usually means the policy sentence needs rewording rather than that the claim is at fault.

Claims entered on someone’s behalf

If your organisation uses this: some people are allowed to enter claims for a colleague, for example an assistant entering claims for their manager. The claim still belongs to the colleague, and comes to you for approval exactly as if they’d entered it themselves.

On the claim’s page, Claimant shows the colleague’s name, followed by “(entered by” and the name of whoever actually entered it.

Occasionally the person who entered a claim is also the person who has to approve it. The system lets them approve it, but it doesn’t let it pass unnoticed: once approved, the claim carries a ⚠ Entered and approved by the same person flag. It shows on the claim’s own page, and on its row under Reviewed in My Approvals, so Finance and anyone reviewing the claim later can see it. If that’s you, you also see the claim’s warnings, including any Custom Rule badges, just as any other approver would.

What happens next: nothing changes in how you approve or reject. If you entered a claim for someone and are also its approver, consider asking someone else with approval rights to decide it instead.

Handing over your approvals while you’re away

If you have permission to do this: while you’re away, you can have your approvals go to someone else for a set period, without anyone having to change how claims are routed.

1. Go to your organisation’s Delegations page (this isn’t linked from the menu, so ask your administrator for the address if you need it).
2. Under Create New Delegation, enter the Delegatee User ID of whoever is covering for you. This box’s own placeholder text reads “MongoDB ObjectId”, which is just a technical way of saying it wants that person’s internal user ID, not their name or email. Ask your administrator for it, since it isn’t shown anywhere else in the app. Then set the Start Date and End Date to cover.
3. Select Create Delegation.

What happens next: for the whole date range, every claim that would come to you instead goes straight to your delegate. It appears in their own My Approvals, and they act on it exactly as you would have; you won’t see it in yours while the delegation is active. The delegation itself appears under My Delegations, showing who it’s for and whether it’s currently Active. Select Revoke beside it at any time to end it early and send new approvals back to you immediately. If you don’t revoke it, the same thing simply happens on its own once the end date passes: new claims route straight back to you without any further action. Either way, this only changes where the next claim goes. A claim already sent to your delegate while the delegation was active stays theirs to decide, in their My Approvals, even after you revoke the delegation or its end date passes. It doesn’t jump back to you mid-flight. You can only delegate to someone whose own access already covers everything yours does. The system refuses to create a delegation to someone with less access than you.

When a claim needs more than one approval

If your organisation uses this: some categories are set up to need more than one approval before a claim can move on, either through several people in sequence, or several people agreeing on the same step.

An Approval Progress panel on the claim’s own page shows where it stands:

• Each step is labelled by who it needs, Reporting Manager, Department Lead, Department C-Suite, Department Approvers, Branch Lead, Branch Approvers, or Named Approver, with a Level X of Y count next to the heading showing which step is current. Branch Lead always means the branch’s manager alone. Branch Approvers means the list of approvers your administrator keeps for that branch, separately from its manager. So if a claim from a branch you don’t manage reaches you, it’s usually because you’re on that branch’s approvers list. A step any one of several people can approve is labelled with all of them, for example Reporting Manager or Department Lead. While it waits on more than one person, the claim’s status reads Pending Approval (any one approver). (If both choices turn out to be the same person, it reads Pending Approval by that person, as for any single approver.) The first of them to approve completes the step, and the claim leaves the others’ My Approvals.
• A step that needs more than one person’s agreement shows as Department Approvals (even when the people are a branch’s approvers rather than a department’s), listing each person on it and whether they’ve approved yet or are still Pending, along with how many approvals it needs in total.
• A Late-claims approval chain tag beside the heading means the claim was submitted after its category’s submission window and is following the separate chain set up for late claims, rather than the normal one. See Sending late claims to a different approver.

What happens next: the claim’s status stays Submitted throughout every step. See Submitted. It moves to the next step, or to Approved, only once the current one is satisfied. If you’re one of several people who can act on a step, your approval alone may be enough to complete it, or it may still need one or more of the others to act first, depending on how many approvals that step requires.

This section covers paying approved claims and reporting on spending across the organisation. Access is permission-based, not a fixed role. If you can see the My Reimbursements menu in the left-hand sidebar, the payment tasks below are for you. If you can see All Claims or Reports without My Reimbursements, you can view and export claims but not mark them paid. For what each claim status means and who acts next at every stage, see How a Claim Moves.

Seeing everything waiting to be paid

Every claim that has cleared approval and is waiting to be paid collects on one page.

1. Select My Reimbursements in the left-hand menu.
2. Stay on the Queue tab. It lists every Approved claim not already grouped into a batch, most recently approved first.
3. Use the Period filter to narrow the list by Approval Date or Submission Date, including the same quick presets (This month, Last month, Month to date, Year to date) used elsewhere in the app.

What happens next: select a claim’s title to open its full detail page, same as anywhere else in the app. From here you can pay a claim on its own, pay several at once, or set some aside as a batch. See below. A warning flag on a claim (for example, Amount mismatch) carries over from when it was submitted or approved; select it to see why. You can also select Reject on any claim here if a problem turns up before it’s paid. See Rejecting a claim and writing a reason. The same rules apply here as anywhere else Finance can reject an already-approved claim.

Paying a single claim

1. Find the claim’s row on the Queue tab.
2. Select Reimburse.

What happens next: the claim’s status becomes Reimbursed immediately. See Reimbursed. The claimant is notified right away, and the claim drops out of this queue for good. If someone else entered the claim on the claimant’s behalf, that person is told it’s been paid too. This is the same however the claim gets paid: on its own, with Reimburse Selected, as part of a batch, or through the Excel round trip.

Grouping claims into a batch, and why

Ticking claims and selecting Reimburse Selected on the Queue tab pays every ticked claim immediately, exactly like paying them one at a time, but it keeps no record afterward of which claims were paid together. Use a batch instead when you want that record: to match a set of claims against a single bank transfer or payroll run, to pay them gradually rather than all at once, or to hand the list to your accounting system (see the Excel round trip, below).

1. On the Queue tab, tick the checkbox next to each claim to include. The header checkbox only selects claims on the current page. With a long queue, other pages aren’t included.
2. Select Save as Batch (N).
3. Enter a Batch Name (something that will mean something later, like a date range or payment run) and select Create Batch.

What happens next: the selected claims move out of the Queue tab and the batch appears on the Batches tab as Pending, showing its claim count and total amount. If a claim you ticked was no longer eligible by the time the batch was created (for instance, someone else had already started paying it), it’s left out and you’re told how many were dropped, rather than the whole batch failing. Open the batch at any time to pay some or all of its claims, export it, or cancel it. See below.

Paying some of a batch

Use this when only some of a batch’s claims are ready to be paid, for example, you’ve confirmed some payments went through and are still waiting on the rest.

1. Select the batch’s row on the Batches tab to open it.
2. Tick the claims you want to pay now. Only claims still Approved can be ticked. One that’s already paid, or that was rejected out from under the batch, shows no checkbox.
3. Select Reimburse Selected.

What happens next: each ticked claim is paid exactly like a single reimbursement. The claimant is notified for each one, and anything ticked that turned out to no longer be Approved is skipped and reported rather than causing an error. The batch itself only becomes Reimbursed once every claim inside it has been paid; until then it stays Pending, with the claims you just paid now showing Reimbursed in its list and the rest still waiting. Reopen it later to pay the remainder the same way, or pay everything left in one step. See next.

Paying a whole batch

Use this once you’re ready to pay every remaining claim in a batch at once.

1. Select the batch’s row on the Batches tab to open it.
2. Select Reimburse Batch.

What happens next: every claim in the batch still Approved is marked Reimbursed at once, each claimant is notified, and the batch itself becomes Reimbursed immediately. Unlike paying a batch down gradually (see below), Reimburse Batch closes the batch out regardless of whether every claim in it actually got paid this way (for instance, one already rejected out from under it earlier).

Using the Excel round trip to mark payments made in your accounting system

Use this when you process payments through your own accounting or banking system and want to record which claims were actually paid there, rather than marking each one by hand in the app.

1. Open the batch on the Batches tab.
2. Select Export Excel to download a workbook listing every claim in the batch, its claim details, a Claim Reference, and a Reimbursed column, and save it. If your organisation has switched on choosing a template: an Export Excel box opens first, listing your organisation’s column layouts with the default one already picked (or Built-in columns, if there’s no default). Pick one and select Export. Otherwise the download starts straight away using the default layout.
3. Do your payment run in your own system, then open the saved workbook and mark TRUE in the Reimbursed column for every claim you actually paid. Leave it as FALSE, or blank, for anything not yet paid.
4. Back in the batch, select Upload Reimbursement Excel and choose your edited file.

What happens next: a summary reports how the workbook’s rows were handled:

• Processed: the claim was marked Reimbursed, exactly as if you’d ticked it and selected Reimburse Selected.
• Skipped: nothing changed for that claim, either because you left it unmarked, or because it had already been reimbursed before you uploaded. Re-uploading the same workbook a second time is safe for this reason: a row for an already-paid claim is simply skipped again, never paid twice.
• Failed: the row couldn’t be applied at all, most often because the claim it names is no longer Approved (it was rejected, or paid a different way, in the meantime). The reason is shown next to the row; fix the mismatch and re-upload if you still want to record it this way, or handle that one claim individually from the batch’s own list instead.

As with paying a batch down gradually on its own list (see Paying some of a batch above), a batch you’re working through with the Excel round trip becomes Reimbursed only once every claim inside it shows as paid. Selecting Reimburse Batch instead, at any point, closes it out immediately regardless (see Paying a whole batch above). Don’t rename or reorder the workbook’s hidden Claim ID / Batch ID columns, and don’t mix rows from a different batch’s export into it. Claims are matched back by those columns, not by row position, and a workbook that doesn’t belong to this batch at all is rejected outright before anything is changed. If your organisation uses this: which claim details the workbook includes, and in what order, comes from a column layout your administrator has set up (see Setting the reimbursement report column layout). Without one, you’ll see a standard set of claim details instead. Whether you’re asked to pick a layout each time you export is also your administrator’s choice (the Choose Excel template on export setting, see Organisation settings).

If you pick a layout and someone deletes it before you select Export, the box tells you “That template no longer exists. Pick another and export again.” and removes it from the list. Choose another and export again.

Getting a PDF of a batch

A batch’s detail view also offers Export PDF next to these two buttons: a printable processing report scoped to just that batch’s claims, grouped by claimant with every claim listed underneath. See Producing the processing report below for what that report contains.

1. Open the batch on the Batches tab.
2. Select Export PDF.

What happens next: the PDF is put together in the background, since a large batch with many attachments can take a while. A note under the buttons reads “Generating the batch PDF. Track it under the Reports tab.” You’ll get a notification in My Feed when it’s ready, and selecting that notification takes you straight to it. The PDF is named after the batch.

Finding batch PDFs (the Reports tab)

Every batch PDF generated in your organisation is listed in one place, whoever generated it, so you can pick up a copy a colleague already made instead of generating another.

1. Select My Reimbursements in the left-hand menu.
2. Select the Reports tab, next to Queue and Batches.

What happens next: each row shows the Batch it was made from, its Status, the number of claims (# Claims), when it was Generated, and who it was Triggered by. A PDF still being made shows as Queued or Generating, and the list updates by itself until it’s Ready. Select Download on a ready one to save it. A PDF is kept for 7 days; after that it shows as Expired and can’t be downloaded, so generate a fresh one from the batch if you need it again. A Failed one shows the reason underneath; try Export PDF again.

Cancelling a batch

Use this when a batch was grouped by mistake, or its claims need to be paid a different way.

1. Open the batch on the Batches tab.
2. Select Cancel Batch.

What happens next: the batch is marked Cancelled, and any of its claims not already paid return to the Queue tab, unpaid, exactly as if they’d never been batched. Nothing changes for a claim in it that’s already been marked Reimbursed. A cancelled batch stays on the Batches tab afterward as a record, but nothing more can be done with it.

Seeing every claim in the organisation

Use this to find or check on any claim, not just ones needing your action.

1. Select All Claims in the left-hand menu.
2. Use the status chips, filters, and card/table view toggle to narrow down what you’re looking for. These are the same controls as My Claims, plus organisation-wide Department and Branch filters. See Tracking your claim for how the view toggle and warning flags work.

What happens next: selecting a claim opens its full detail page, same as anywhere else. If you can see the My Reimbursements menu, an Edit button next to a claim in table view also lets you change its status directly. This is useful for correcting a mistake without going through the normal submit/approve/reject/reimburse flow. Choose the new status, give a reason if you’re rejecting it, and select Update Status; the claimant is notified exactly as they would be through the normal flow. Not every change is accepted: the system still enforces which transitions make sense for a claim’s current status, so an option that doesn’t apply may return an error instead of completing.

Building a report

Use this to see totals and breakdowns across claims, by category, department, branch, claimant or month, rather than looking at claims one at a time.

1. Select Reports in the left-hand menu. It opens on the Summary tab.
2. Choose how to group the report, from the row of buttons at the top: By Category, if your organisation uses category groups: By Category Group, By Department, By Branch, By Claimant, or By Month.
3. Optionally, choose a second breakdown from the then by dropdown next to it: another dimension for a nested sub-breakdown with the same figures at each level, or Each Claim to list every individual claim under its group instead of summarising further.
4. Set the Period, a Month, a custom From/To range, or one of the quick presets (This month, Last month, Month to date, Year to date), and which date it applies to (Transaction Date, Submitted Date, or Creation Date).
5. Narrow further with the Department, Branch, Category (and, if your organisation uses category groups: Category Group) and Claimant filters, and the Status chips, as needed.

What happens next: the table below updates as you change any of these, showing one row per group with its claim count, total amount, and a breakdown of how many of those claims are Approved and Reimbursed (each with its own total amount) and Rejected (a count only, since a rejected claim was never paid), plus a Grand Total row at the bottom. Choosing Each Claim as the second breakdown instead lists every claim under its group individually, with its own claimant and date, rather than further totals. A claim made in another currency counts in your organisation’s own currency, at the exchange rate recorded on the claim when it was made. Which day’s Bank Negara Malaysia rate that is (today’s, or the claim’s transaction date’s) is an organisation setting; see Claiming in another currency.

Select Export CSV at any time to download exactly what’s shown as a spreadsheet, with the same grouping and filters applied.

Producing the processing report (PDF)

Use this to get a printable, shareable record of a set of claims for filing or handing to someone outside the app.

1. On the Reports page’s Summary tab, set the grouping and filters you want the report to reflect, as above.
2. Select Processing Report (PDF).
3. Enter a Report name. It’s filled in for you as “Processing Report” plus the period, if you set one; change it to something you’ll recognise later, like “October claims for audit”. The name is what you’ll see on the Exports tab and becomes the downloaded file’s name.
4. Select Generate.

What happens next: the report is put together in the background, and a note reads “Generating the processing report. Track it under the Exports tab.” You’ll get a notification in My Feed, quoting the report’s name, when it’s ready (or if it failed). Selecting it takes you to the Exports tab, where you can download it. See next.

The PDF opens with a summary page grouped exactly the way the preview was grouped: the same rows, totals, and second-level breakdown, if you set one, followed by one page per claim showing its own details, status, and line items, plus its attachments. Photos and PDF attachments are reproduced in full inside the report; anything else appears as a link instead. If you haven’t set a date range or status filter beforehand, the report defaults to this month’s Submitted and Approved claims.

You can have up to 3 reports being generated at once. Starting a fourth shows “You already have 3 exports in progress. Please wait for one to finish.” inside the name box; wait for one to finish, then select Generate again. Your name is kept, so you don’t need to retype it.

Finding your processing reports (the Exports tab)

1. Select Reports in the left-hand menu.
2. Select the Exports tab, next to Summary.

What happens next: you see the processing reports you’ve generated yourself, newest first. Other people’s reports aren’t shown here, since each one carries its own filters. Each row shows the report’s Name, its Status, the number of claims (# Claims), and when it was Generated. A report still being made shows as Queued or Generating, and the list updates by itself until it’s Ready; select Download to save it. Reports are kept for 7 days, then show as Expired and can’t be downloaded any more, so generate it again if you need a fresh copy. A Failed report shows the reason underneath it.

PDFs of reimbursement batches aren’t listed here. They have their own list on My Reimbursements, shared across your organisation. See Finding batch PDFs (the Reports tab).

This section covers the settings an administrator configures: categories, spending limits and approval routing, departments and branches, users and roles, custom fields, and organisation-wide settings.

Whether you can see any of this depends on your permissions, not on having a fixed role. The pages below live under Settings in the left-hand menu, grouped under their own headings (Organization, Claims, System), and exactly which ones you see there follows from what your role is allowed to do (see Changing what a role can do). If you can see Settings at all, at least part of this section is for you.

Setting up a new organisation from scratch? Several of the tasks below assume a toggle in Organisation settings is already switched on: category groups, branches, multi-level approval, rate tables, accounting codes. Read that task first if this is your first pass through Settings. Then come back to the rest in whatever order suits you. If you’re only here to do one everyday task, like adding a category or adjusting a limit, jump straight to it as normal.

Adding or retiring a claim category

Categories classify every claim, and a spending limit or an approval rule attaches to them. Set these up before you write rules for them.

1. Select Settings in the left-hand menu, then, under Claims, select Categories.
2. Select + New Category, type a Name (and a Code, if your organisation records accounting codes for categories, see Organisation settings) and select Create category.

What happens next: the new category appears in the list right away and is immediately available on the claim form, for auto-detection, and when writing a rule.

To retire a category you no longer want offered, select Deactivate next to it rather than deleting it. This is fully reversible with Activate, and anything already recorded against it stays unaffected either way. It simply stops appearing as an option on new claims and rules. Delete is permanent and can’t be undone. Each category on the list shows how much still depends on it, for example Used by 42 claims · 2 rules, or Not used yet. While anything still uses it, Delete is greyed out, so deactivate it instead.

Grouping categories into accounting or limit groups

If your organisation uses this: categories can be organised into groups (for example Default, Project, and Staff Benefit) so the same category can carry a different accounting code and a different spending limit under each group. This is a beta feature your organisation turns on in Organisation settings. If you don’t see a Groups tab on the Claim Categories page, your organisation isn’t using it, and every category behaves as one shared pool, as described above.

1. Select Settings in the left-hand menu, then, under Claims, select Categories, then the Groups tab.
2. Type a name into the New group name box and select Add. A new group starts empty.
3. Select Edit on the group to open its category checklist. Tick every category that belongs in this group, and optionally give each ticked category its own Code for this group specifically.
4. Save your changes.

What happens next: claimants filling in the form now see a Group field before Category (see Filling in the details), and a rule can be written for a category within one specific group rather than for the category everywhere. A category left unticked in every group, or a rule with no group chosen (All groups), still applies everywhere as a catch-all. Your organisation starts with one protected Default group, the guaranteed home for every category. It can be neither deactivated nor deleted, because every category must always have somewhere to live. A custom group, by contrast, can be deactivated at any time, and deleted only once no claim or rule still references it.

Setting a spending limit on a category

A rule ties a spending limit, and separately who approves it, to one or more categories. This section covers the limit. See Setting who approves a claim below for the approval side of the same rule.

1. Select Settings in the left-hand menu, then, under Claims, select Rules, then + New Rule. (You can also select Chat Interface to describe the rule in plain language and have it drafted for you to review on this same form instead.)
2. On the Basics tab, search and tick one or more Categories: a single rule can cover several at once. If your organisation uses category groups: choose a Group first to limit the category list to that group, or leave it as All groups for a rule that applies in every group. Set Scope to Default (all users) to apply the rule to everyone, or User-specific to write a personal rule for one named employee. Scope alone doesn’t decide which rule wins if a user ends up matching both a Default and a User-specific rule for the same category. See priority order, below, for what actually does.
3. On the Limits tab:
   • Set a Period Limit, its Currency, and a Period (Monthly or Yearly; a yearly period can also repeat Every given number of years from a fixed Anchor Year, for an allowance that doesn’t reset annually), or tick No spending limit if this rule exists only to route approvals or apply a rate, without capping the total.
   • With a period limit set, choose what happens to a claim that would take the period total over it under If the period total is exceeded: Warn and allow lets the claimant proceed past a warning, Block submission refuses it outright. A rule set to block shows a Hard tag on the Claim Rules list.
   • Tick Mileage claim type and set a Rate per km if this category is claimed by distance rather than an invoice amount. See Claiming mileage. Optionally pick a Distance table so claimants choose a start and end location and the distance fills in for them, and tick Only allow locations and distances from the table if they mustn’t type their own. See Setting up a mileage distance table below.
   • Tick Per-claim limit to additionally cap any single claim, on top of (or instead of) the period total, and choose what happens to a claim above it under If a claim exceeds this: Warn and allow lets the claimant proceed past a warning, Block submission refuses it outright. This is separate from the period limit, so you can refuse a single oversized claim while only warning about the monthly total, or the other way round. A rule with a blocking per-claim limit shows a Blocks tag beside the amount on the Claim Rules list.
   • Set a Submission window (days) to require claims in these categories to be submitted within that many days of the transaction date (leave it blank for no deadline), and choose what happens to a late one under If a claim is late: Block submission refuses it outright, Warn and allow lets the claimant proceed past a warning, and Allow, with late approval chain lets it through but sends it to a separate approval chain you set on the Approval tab (see Sending late claims to a different approver below). Under either of the last two, the claimant must give a Reason for late submission, which approvers see and which appears in the claim export. Tick Must also be submitted within the same financial year to add a second, separate deadline on top of the day count: the claim must reach you before the financial year its transaction date fell in closes. Both conditions apply, so a claim can be well inside the day count and still be refused for the year having ended. See Running yearly limits on your financial year below.
   • If your organisation has set up policy tables: choose a Rate table or Limit table to look the amount or cap up from a grid, for example by grade or country, instead of typing a fixed figure. See Setting up rate or limit tables below if you haven’t built one yet.
   • Tick Pooled limit to share one cap across an entire Branch, Department, or the whole Organisation-wide, rather than tracking each person’s spending separately. Once pooled, the choice above reads If the pooled period total is exceeded, and works the same way. It covers the period total only; the per-claim limit above has its own.
4. Select Create Rule.

Use the Test a claim panel beside the form at any point to enter a sample amount and see exactly what it would trigger under the rule as configured, before you save it. The Summary tab writes the whole rule out in words, including changes you haven’t saved yet. See Reusing a rule’s settings from its Summary below.

What happens next: claimants see their remaining allowance on the dashboard and while filling in a claim, and a warning if a claim would approach or exceed a limit. See Checking what’s left of your allowance and Submitting your claim, and what the limit warning means. A category with no active rule covering it has no submission deadline at all, just as it has no spending limit. Set one here for any category you want a deadline enforced on, and remember that two categories can carry two different deadlines (or none), depending entirely on how their rules are set up.

If the categories you chose are already covered by another active rule (including a Default rule for the same category as the User-specific one you’re writing, or the other way round), a Rule Conflict Detected dialog explains the overlap and tells you which rule would actually win before you can save. Create Anyway keeps both rules active. Which one actually applies for a given claim comes down entirely to priority order: the position of each rule on the Claim Rules list, with the one nearer the top winning, regardless of whether it’s the Default or the User-specific one. Replace instead deactivates the older one outright, as long as doing so wouldn’t strip it of every category it covers. Creating a new rule automatically places it immediately above whatever it overlaps, so it wins without you having to reorder anything by hand. But you can still drag rows up or down on the Claim Rules list at any time afterwards, and that’s exactly what makes the earlier assumption that “a personal rule always wins” unsafe: if a User-specific rule ever gets dragged below a Default one for the same category, the Default rule wins instead, silently. Check the list’s order after any manual reordering if you rely on a personal rule overriding a general one.

Reusing a rule’s settings from its Summary

Every rule form has a Summary tab beside Basics, Limits and Approval. It spells out the rule in plain words: its categories, limits, deadline, mileage settings and approval chain. It updates as you change the form, so it’s also a quick way to check a rule reads the way you meant before you save it.

To make a similar rule without starting from scratch:

1. Open the existing rule and select the Summary tab.
2. Select Open in chat. (Or select Copy and paste the text into Chat Interface on the Claim Rules page yourself.)
3. On Create Rule via Chat, edit the text to change what should differ, such as a name, an amount or a category, then select Parse Rule.
4. Check the rule form it fills in below, then select Create Rule.

What happens next: nothing is saved until you select Create Rule on that filled-in form, so the original rule is untouched. Anything the chat couldn’t match to a real category, person, department or table is left blank rather than guessed, so look over each tab before saving.

Writing a policy in plain language (Custom Rules)

Some policies don’t fit the structured rule form. “Users below 50 can claim once per year, 50 and above twice a year” isn’t an amount or a period, so there’s nowhere to type it. Custom Rules let you write that sentence as it is, and have the system flag claims that appear to break it.

Custom Rules never block a claim. They raise a warning for whoever approves it, and that person decides. This is deliberate: the check is made by reading your sentence rather than by arithmetic, so it advises a human instead of overruling one.

1. Select Settings in the left-hand menu, then, under Claims, select Rules, then the Custom Rules tab. (The Structured Rules tab beside it is the ordinary rule form covered in Setting a spending limit on a category above.)
2. Add a rule and write the policy in plain language, the way you’d explain it to a colleague.
3. Save it.

What happens next: when a claim is submitted, any Custom Rule that applies to it is checked, and the result travels with the claim. An approver sees a Custom rule flagged badge on it, with the reason, and can approve or reject as normal. They may instead see Custom rule check incomplete, which means the check couldn’t be completed rather than that anything is wrong. See When a claim is flagged by a Custom Rule.

Write one policy per rule, and be specific about who it applies to. A sentence covering three unrelated things is harder to check than three separate rules, and a vague one produces vague warnings that approvers learn to ignore. If a policy can be expressed as an amount, a period or a per-claim cap, use the structured rule form instead: those are enforced exactly, and can block.

Running yearly limits on your financial year

By default a Yearly period on a rule means the calendar year: 1 January to 31 December. If your organisation’s financial year starts in another month, you can say so once and every yearly limit follows it.

1. Select Settings in the left-hand menu, then, under System, select General.
2. In the Organisation section, set Financial Year Start Month to the month your financial year begins.
3. Select Save Settings. Before it saves, a confirmation appears showing the window you’re on now, the window you’d move to, how many rules are affected, and how many already-submitted claims would stop counting toward their limit. Read it, then confirm or cancel.

This is one setting for the whole organisation, and it applies at once. There’s no per-rule choice, because a company has one financial year: if some rules ran on the calendar year and others on the financial year, nobody could answer “how much is left this year” consistently.

What happens next: the window every yearly rule measures against moves immediately, so spend that fell before the new boundary stops counting toward the current period, and claimants’ remaining allowances change accordingly. That’s why the confirmation tells you how many claims move before you commit. Nothing already approved or paid is altered, and no claim is re-decided; only the window that future limit checks measure against is different. If you have a choice, change it at a year boundary rather than mid-year.

A claim now belongs to the financial year its transaction date falls in, not the year it was submitted. So with an April financial year, a claim dated February 2027 counts against the year that opened in April 2026.

Separately, a rule can require that a claim reach its approver before that financial year closes. See the Must also be submitted within the same financial year tickbox in Setting a spending limit on a category above. It’s an extra condition, not a replacement for the day count: a claim dated 30 March and submitted 2 April is only three days old, and is still refused, because the year it belongs to has ended.

Setting who approves a claim, including several levels

The same rule that sets a category’s spending limit also decides who reviews a claim in it. That can be anywhere from nobody at all up to three approval steps in sequence, with a larger claim needing more.

1. Open the rule (new or existing) and select the Approval tab.

2. Tick Auto-approve and set a Minimum amount and Maximum amount to skip approval entirely for claims in that range, as long as the claim doesn’t trip this same rule’s own spending-limit warning. A claim flagged for something else instead, like a possible duplicate or a category mismatch, still auto-approves if the amount qualifies. Only its own limit check can suppress this.

3. Build the Approval chain: select + Add an approval step, then tick Who approves: Reporting manager (the reporting manager set on the claimant’s own user profile: see Setting someone’s reporting manager below), Department lead (the claimant’s own department, or one you name), Department C-Suite (the one person named as that department’s C-Suite, rather than its manager: see Setting up departments and their managers below), Department Approvers (the department’s own list of approvers, rather than its manager), Branch lead (the branch’s manager) or Branch Approvers (the branch’s own list of approvers; both branch choices are only available if your organisation has enabled Branch-Level Approval, see Organisation settings), or Specific people (approvers you pick individually, shown to them as a Named Approver, with a How many must approve count if you name more than one).

   Department C-Suite exists so a senior sign-off follows the claimant automatically. A Specific people step names the same individuals for everyone, so a Sales claim and an Operations claim would go to the same person; a Department C-Suite step sends each one to its own department’s C-Suite without you writing a separate rule per department.

   Tick more than one to let any of them approve the step: for example, tick Reporting manager and Department lead so either the claimant’s reporting manager or their department lead can approve it. Everyone those choices point to forms one group, and the first approval from any of them completes the step. A step like this always needs exactly one approval, so the How many must approve count is hidden while two or more are ticked. If one of the ticked choices finds nobody for a particular claimant (say they have no reporting manager), the others still cover the step. The claim is refused at submission only if none of them finds anyone.

4. To require an extra step only once a claim passes a certain amount, select + Add amount band to add another row with its own limit (the topmost band is always left open, to cover every amount above the others), then + Add step on that band for the further level. A claim always walks its band’s steps in order, left to right. If you’ve already built this chain as an approval template, pick it from Use a template… above the chain instead of building it here. See Reusing an approval chain across rules below.

5. Select Create Rule or Update Rule.

What happens next: a submitted claim goes to whoever the first step names. See How a Claim Moves, and, if your organisation uses this, When a claim needs more than one approval, which covers what an approver sees for a quorum step or a multi-level chain. A Department lead or Branch lead step always goes to that department’s or branch’s manager alone. A Department Approvers or Branch Approvers step instead draws on that department’s or branch’s own list of approvers and minimum-approvals count, not on anything set here, and is refused at submission if that list is empty rather than falling back to the manager. See Setting up departments and their managers and Setting up branches below. A step that only names Reporting manager is refused at submission when the claimant has no reporting manager set, or theirs has been deactivated: the claimant is told to contact an administrator, and the claim stays a Draft until you set one. If you leave a category with no approval chain at all, a claim in it stays Submitted with nobody assigned to act on it, visible only to whoever can see All Claims. See Seeing every claim in the organisation.

Sending late claims to a different approver

Some organisations want a claim submitted long after the event, for example more than 90 days after its transaction date, to be signed off by someone more senior, such as the CFO. You set this on the same rule, not on a second rule: two rules covering the same category don’t split claims by age, because the higher-priority rule always wins.

1. On the rule’s Limits tab, set the Submission window (days) (for example, 90), and under If a claim is late choose Allow, with late approval chain.
2. On the Approval tab, a second section, Late claims approval chain, appears below the normal chain. Build it exactly as you build the normal one, with steps, any-of steps and amount bands, or link it to an approval template. For example, name just the CFO; or the department lead and then the CFO; or the CFO first and then the department lead.
3. Use Test a claim with Late ticked to see which steps a late claim of a given amount would go through.
4. Select Create Rule or Update Rule. The rule can’t be saved with this option chosen and the late chain empty, or with no submission window set.

What happens next: each claim follows exactly one chain, decided when it’s submitted (or resubmitted). A claim within the window follows the normal chain. A claim past it follows the late chain instead, not as well, and skips Auto-approve even if its amount is in that range. The claimant has to give a reason, and the claim’s Approval Progress is marked Late-claims approval chain. Each rule card on the Claim Rules list shows a second Late claims: line summarising this chain.

Reusing an approval chain across rules (approval templates)

If several rules should send claims through the same approval chain, build it once as an approval template and link each rule to it. Change the template later and every linked rule follows.

1. Select Settings in the left-hand menu, then, under Claims, select Approval Templates, then + New Template.
2. Enter a Name and, optionally, a Description saying when to use it.
3. Build the Approval chain exactly as you would on a rule’s Approval tab, with steps, any-of steps and amount bands (see Setting who approves a claim above).
4. Select Create template.

To link a rule to it, open the rule’s Approval tab and pick the template from Use a template… above the Approval chain. The same control sits above the Late claims approval chain, so a rule’s normal and late chains can each use a different template. Already built a chain on a rule that you’d like to reuse? Select Save as template… there instead, give it a name and select Save & link.

What happens next: a linked chain shows a Template: label with the template’s name, and is greyed out on the rule because it now comes from the template. Select Unlink to make it the rule’s own again: the chain stays exactly as it was, and you can edit it. Each rule on the Claim Rules list shows template: and the name beside its chain.

To change a template, select Edit next to it on the Approval Templates page; it opens in a pop-up. Each template lists the rules that use it. If any do, saving asks you to confirm with Save and update rules, because their chains change straight away. Claims already submitted keep the chain they were routed with. A template still linked to an active rule can’t be deleted: unlink it from those rules first.

Setting up departments and their managers

Departments (labelled Departments / Projects) group your people and decide who a claim’s first approval step goes to.

1. Select Settings in the left-hand menu, then, under Organization, select Departments / Projects, then + New Department.
2. Enter a Name and pick a Manager. Tick which Members belong to this department. Optionally pick a C-Suite: the senior person a rule can route a later approval step to, for claims from this department. It’s separate from the manager, and you only need it if one of your rules actually uses a Department C-Suite step. See Setting who approves a claim above.
3. Leave Requires manager approval ticked so claims routed here need the manager’s sign-off. Untick it so they instead skip straight to Approved (or to the branch-lead step alone, if your organisation has enabled Branch-Level Approval).
4. If your organisation has enabled Multi-Approval: tick people under Approvers and, if you tick two or more, set a Minimum approvals required. This list is used only by a rule step of the Department Approvers type, so a group of people share that step rather than the manager deciding alone. A Department lead step always means the manager, whatever is listed here.
5. Select Create.

What happens next: any claimant in this department who submits a claim routed here goes to the manager (or, for a Department Approvers step, the approver list), exactly as described in Setting who approves a claim above. If a rule routes a step to a Department C-Suite and this department hasn’t got one, the claim is refused at submission rather than quietly skipping that step, and the claimant is told to contact an administrator. The same happens if the claimant belongs to no department at all, since there’s then no C-Suite to look up. Deleting a department is refused while it has claims currently Submitted and awaiting its approval. Once none remain, deleting it unlinks it from any of its past claims and clears it as anyone’s default department, rather than deleting those claims too.

Setting up branches

If your organisation uses this: branches work much like departments, but for approval based on physical location or site rather than function, and only take part in approval routing once Enable Branch-Level Approval is turned on in Organisation settings.

1. Select Settings in the left-hand menu, then, under Organization, select Branches / Entities, then + New Branch.
2. Enter a Name, pick a Manager, and optionally a Region. Tick which Members belong to this branch. A member already assigned to a different branch is shown as such, and can only be moved across if your organisation allows branch reassignment.
3. If your organisation has enabled Multi-Approval: tick people under Approvers and, if you tick two or more, set a Minimum approvals required. As with departments, this list is used only by a rule step of the Branch Approvers type. A Branch lead step always means the manager.
4. Select Create.

What happens next: once Branch-Level Approval is enabled, a claimant with an assigned branch has their claim require that branch’s approval before their department’s, wherever a rule’s approval chain includes a Branch lead or Branch Approvers step. Claimants see a branch as Branch / Entity on their claims. See Setting who approves a claim above. Deleting a branch is refused while a claim is currently Submitted and awaiting that branch’s approval. Otherwise, its members simply lose their branch assignment.

Adding a user and giving them a role

1. Select Settings in the left-hand menu, then, under Organization, select Users, then + Add User.
2. Enter a Name and Email, and choose a Role from the dropdown. A Generated Password is filled in for you: select the copy icon to copy it, or the regenerate icon next to it for a different one. This is emailed to the new user. Leave Require password reset on next login ticked so they’re made to set their own password the first time they sign in.
3. Optionally set a Branch, a Date of Birth, and tick which Departments / Projects they belong to (with one marked as their Default Department, if they’re in more than one).
4. Select Create User.

What happens next: the new user can sign in with the emailed password (and set their own, if you left the reset requirement on). If you chose one of your organisation’s built-in roles, their menu (which pages they can open, such as My Reimbursements, All Claims, Reports, or Settings) follows immediately from that role. If you chose a custom role instead, read Changing what a role can do below before assuming what they’ll see: a new user given only a custom role starts with the same, most-restricted menu as your most basic built-in role, regardless of which permissions that custom role carries. To remove someone’s access later, select Deactivate next to them rather than Delete, unless you’re certain it should be permanent. A deactivated user simply can’t sign in any more, while everything they’ve done stays on record.

Setting someone’s reporting manager

A reporting manager is the person someone reports to directly. Setting one matters only if a rule has a Reporting manager approval step (see Setting who approves a claim above): that step goes to whoever is set here for the person claiming.

1. Select Settings in the left-hand menu, then, under Organization, select Users.
2. Select Edit next to the person.
3. Pick their Reporting manager from the list of active users, or None to clear it.
4. Select Save changes.

What happens next: the Reporting Manager column on the Users page shows the new manager. Anyone who has someone reporting to them sees My Approvals in their menu. Claims already submitted keep the approvers they were given at submission; only new claims follow the change. Each organisation keeps its own reporting line, so someone who belongs to two organisations can report to a different person in each.

Deactivating a manager doesn’t clear them from the profiles of the people who report to them. While they’re deactivated, a Reporting manager step treats those people as having no reporting manager, and reactivating the manager restores it. Their Edit form shows that manager marked (inactive), and you can still save other changes to it without picking someone new. To move those people to someone else permanently, edit each of them and pick a new manager.

Letting someone claim on another person’s behalf

Some people have their claims entered for them, for example a director whose assistant files their expenses. A claim authorisation lets one person (the Proxy) enter and submit claims that belong to another (the Principal). Each person can arrange this for themselves on the Claim for Me tab of their own profile; this page lets you see and manage every authorisation in the organisation.

1. Select Settings in the left-hand menu, then, under Claims, select Claim Authorisations.
2. Pick the Principal (claims belong to) and the Proxy (enters the claims).
3. Optionally set an End date, after which the authorisation stops working by itself. Leave it blank for one that lasts Until revoked.
4. Select Authorise.

What happens next: both people are emailed. The proxy now sees a Claiming for choice on the claim form, and a claim they enter for the principal is the principal’s own claim: it counts against the principal’s limits and goes to the principal’s approvers. The proxy can only reach the claims they entered themselves, never the principal’s other claims. The list shows each authorisation as Active, Ended (past its end date) or Revoked; use the filters above it to narrow it by status, principal or proxy. To stop one early, select Revoke next to it; both people are emailed again. For what approvers see on such a claim, see Claims entered on someone’s behalf.

What each built-in role can do

Every organisation starts with the same four built-in roles, and they keep these names: built-in roles can be viewed but not edited. Your organisation may also have custom roles of its own, so check your Roles page for the full list. The tables below describe the four built-in ones.

Two separate things decide what someone can do, and they don’t follow each other automatically: what their role has permission to do, and which pages their built-in role can open. Both tables matter, and the second one is the one people forget.

Permissions

Staff holds no permissions from this list. That is not a gap: submitting, editing and tracking your own claims needs none of them, and every role above can still do all of that.

Pages

My Approvals is not in that table because it doesn’t follow the role at all. It appears for whoever manages a department or a branch, so someone on any role may or may not see it depending on whether claims are routed to them.

Two things follow from all this, and both catch people out:

• A built-in role cannot be edited or renamed. You can look at one to see what it holds, and you can build a custom role of your own, but the four above are fixed.
• Giving someone a custom role does not give them pages. Read the next task before you rely on one.

Changing what a role can do

A custom role changes which actions a user’s clicks succeed at. It never changes which menus or pages they can open. Which pages and menu items someone can even open is a separate thing, decided solely by which one of your organisation’s built-in roles they’re set up as. The two don’t automatically follow each other, and that’s important to understand before you rely on a custom role for anything.

1. Select Settings in the left-hand menu, then, under Organization, select Roles, then + New Role.
2. Enter a Name for the role.
3. Tick each permission this role should have, grouped under Claims, Reports & Dashboard, Organisation, Settings, and Roles, for example View all claims, Process claims, Mark as reimbursed, Manage users, or Manage configuration (categories, departments, branches, and policy/rate tables). Take particular care with Manage roles: it lets whoever holds it create, edit, and delete roles, and assign any role to any user, including themselves.
4. Select Create Role.

What happens next: read this carefully before assigning a custom role. Ticking a permission here does not, by itself, add or remove any menu item or page for whoever holds this role. Whichever pages someone can open, such as My Reimbursements, All Claims, Reports, or the Settings pages this whole section lives under, are still decided entirely by which one of your organisation’s built-in roles (your basic staff role, an approver/finance role, a management role, a full administrator role) that person is assigned. Ticking View all claims and Export reports on a brand-new custom role, then assigning it to someone whose built-in role is your basic staff one, will not put All Claims or Reports in their menu. The app still won’t offer them those pages at all, even though the specific actions those two permissions unlock elsewhere already work for that person.

What a custom role reliably changes is which specific actions succeed for someone who can already open a page some other way. For instance, an administrator’s custom role stripped of Manage org settings still opens General and Currency under Settings (since that comes from being an administrator), but selecting Save Settings or Save Changes on them is refused. Used this way, meaning you assign someone the built-in role that already gets them onto the pages they need, then switch their Role to your custom one, the pages they could already reach stay reachable. Exactly which of the actions on those pages they can perform now follows your custom role’s ticked list instead of that built-in role’s own defaults. Editing an existing custom role’s permissions takes effect immediately for everyone holding it. A custom role can be deactivated at any time: anyone holding it immediately loses its permissions, and it can no longer be newly assigned. It can only be deleted once nobody is assigned it any more, so deactivate it instead if that’s not yet the case.

Asking for extra information on a claim (custom fields)

Custom fields add extra dropdowns to the claim form for record-keeping, such as an entity, a project, or a cost centre, without affecting an amount, a limit, or who approves the claim.

1. Select Settings in the left-hand menu, then, under Claims, select Custom Fields, then + New Custom Field.

2. Enter a Name: this becomes both the label claimants see and the column header in the detailed CSV export. Optionally set an Order to control where it appears among any other custom fields.

3. Fill in the Options claimants can choose from, either directly in the grid or by using Download CSV/Upload CSV to edit them as a spreadsheet.

4. Under Appears on, choose which claims show the field and whether it must be answered:

   • Every claim · optional or Every claim · required.
   • Every claim · required only for selected: shown on every claim, but required only on the claims you select.
   • Selected claims only · optional or Selected claims only · required: hidden on every other claim.

   For the last three, select the Category groups (if your organisation uses them), Categories or Departments that count as “selected”. A claim in any one of them matches.

5. Select Create field.

What happens next: the field appears on the claim form under Custom Fields on the claims it applies to, marked with an asterisk where required (see Filling in the details), and as a column in the detailed CSV export. A field hidden on a claim never stops it being submitted. If a claimant answers it and then switches to a claim it’s hidden on, their answer is dropped. The Custom Fields list tags each field Required or Conditionally required, and says which claims it’s shown on. Select Deactivate to stop offering a field on new claims while keeping every value already recorded against it (it disappears from the CSV export while inactive). Delete removes its CSV column entirely, though claims that already recorded a value for it keep showing that value on the claim itself.

Setting up rate or limit tables

If your organisation uses this: a policy table looks a value up from a grid instead of using one fixed figure, for example a different mileage rate or per-diem limit by grade or by country. Setting a spending limit on a category above lets a rule point at one of these once it exists. This task is where you build the table itself.

1. Select Settings in the left-hand menu, then, under Claims, select Policy Tables, then + New Policy Table. Enter a Name, choose its Currency, and select Create and build grid.
2. The table opens straight away. Add a Column for each thing a claim needs to specify to look up its rate or limit (for example, Grade). Each new column also needs at least one Row giving the actual figure for each value that column can take.
3. Add a Row for every combination your table needs to cover, entering the amount that applies to it.

What happens next: once a rule (see Setting a spending limit on a category above) is set to use this table instead of a fixed amount, a claimant choosing that category sees extra dropdowns matching your columns, and their claimed amount or limit comes from whichever row matches what they picked. Each table on the Policy Tables list shows how many rules use it and how many rows it has. Deactivate stops a table being offered to new rules and Delete removes it outright, but both are greyed out while any rule still uses the table: point those rules elsewhere first.

Setting up a mileage distance table

If your organisation uses this: a distance table holds the distance between pairs of places your people travel between, such as offices, clients or airports. A mileage rule linked to it lets claimants pick a start and end location and have the distance filled in, rather than typing it.

1. Open the mileage rule (see Setting a spending limit on a category above). On the Limits tab, with Mileage claim type ticked, select Create Mileage Rate Table.
2. Enter a Table name and select Create. The new table is selected as the rule’s Distance table. Save the rule.
3. Select Edit table beside Distance table (or open the table from Policy Tables, where it’s tagged Mileage distances), and add one row per route: a Start Location, an End Location and the Distance (km). Select Add after each.

What happens next: one row covers a route in both directions, so a row for A to B also covers B to A, and the table refuses a second row for the same pair. The locations claimants choose from are every place named in the rows. Unless the rule’s Only allow locations and distances from the table is ticked, claimants can still type a place that isn’t listed, or change the distance. With it ticked, a trip whose route isn’t in the table, or whose distance differs from it, can’t be submitted. A claimant can enter several trips on one mileage claim, and each one is checked. See Claiming mileage.

Setting the reimbursement report column layout

If your organisation uses this: by default, the Excel workbook Finance downloads for a reimbursement batch (see Using the Excel round trip) uses a standard, fixed set of columns. This task lets you define your own layout instead. That’s useful if your accounting system expects the columns in a particular order, or needs ones the standard layout doesn’t include.

1. Select Settings in the left-hand menu, then, under Claims, select Report Builder, then Add template.
2. Enter a Name, then build the column list: select + Add next to any field under Available fields (standard claim fields and any custom fields your organisation has defined) to add it under Columns in this template. Reorder columns with the up/down arrows, rename any column’s label by editing it directly, or remove one with ×.
3. Tick Set as default for reimbursement batch exports so this layout is the one Finance actually gets (your very first template is set as default automatically).
4. Select Save.

What happens next: every reimbursement batch Excel export uses whichever template is marked Default from then on, and Finance never chooses one themselves, unless you switch on Choose Excel template on export in Organisation settings. With that on, selecting Export Excel on a batch first asks which of your templates to use, with the default one already selected. Two columns are always added at the end of every export regardless of what you configure here, Claim Reference and Reimbursed, since the Excel round trip depends on reading them back. Until you create a template and mark one default, exports keep using a standard built-in column set. Deleting the current default template reverts to that same built-in set until you mark another template default.

Organisation settings

General and currency settings apply organisation-wide, and cover most of the optional behaviour mentioned elsewhere in this guide.

1. Select Settings in the left-hand menu, then, under System, select General. The General Settings page is split into four sections, Organisation, Claims, Approvals and Features, each under a grey heading. On a wide screen they’re also listed down the left, so you can jump straight to one. You’ll find:

   • Under Organisation:
     • Financial Year Start Month: the month your organisation’s financial year begins. Leave it as January and yearly limits run on the calendar year, which is what happens if you never touch this. Set it to, say, April and every yearly limit in the organisation then runs April to March instead. See Running yearly limits on your financial year above before you change it: it takes effect immediately, on every yearly rule at once.
     • Accounting Codes: separately switches on a Code field for Categories, Departments / Projects, Branches, and Users.
   • Under Claims:
     • Claim title format: see Building claim titles automatically below.
     • Allow Claim Retraction: lets a claimant pull a submitted claim back to Draft before it’s decided. See Tracking your claim.
     • Invoices per Combined Claim: the most receipts a claimant can merge into one claim using the combine toggle on the upload box. See Starting a claim from a receipt photo or PDF.
     • Duplicate Detection: flags a claim that matches an existing one closely enough on the signals you tick (attachment, vendor name, amount, reference number, transaction date), with its own Block submission / Warn, allow anyway choice. See Possible Duplicate Claim.
   • Under Approvals:
     • Enable Branch-Level Approval, Allow Branch Reassignment, and Enable Multi-Approval: covered in Setting up branches and Setting up departments and their managers above.
     • Require a comment when approving: see Requiring a comment when a claim is approved below.
     • Email approvers on each submission and Approval reminder digest: see Reminding approvers by email below.
   • Under Features:
     • Enable Rate Table: a separate beta page (not covered in this guide) for a simpler, named-item rate list, distinct from the policy tables covered in Setting up rate or limit tables above. Enable Category Groups turns on Category Groups above.
     • Choose Excel template on export: lets whoever exports a reimbursement batch pick which Report Builder template to use. See Setting the reimbursement report column layout above.

   Select Save Settings once you’re done. It sits under the section list (on a narrow screen, at the foot of the page) and saves every section at once. There’s no Cancel button: changes you haven’t saved simply aren’t applied.

2. Select Settings, then, under System, select Currency, to set the Default Claim Currency claimants start with on a new claim, and which currencies are in Allowed Currencies for them to choose instead. See Claiming in another currency. The same page sets which day’s exchange rate applies: see Choosing which day’s exchange rate applies below. Select Save Changes once you’re done.

What happens next: every toggle here applies the moment you save it, organisation-wide, for every claim submitted from then on. Nothing already submitted is changed retroactively. A stricter setting (for example, switching a warning to Block submission) is the difference between a claimant seeing the Review Before Submitting dialog they can proceed past, and an outright error they must resolve before they can submit at all.

Notification emails are not configurable from within the app. The wording of the emails this system sends (a new claim awaiting approval, a rejection, a reimbursement, and so on) is fixed. There’s no Settings page for it, so if your organisation needs different wording, that’s a request for whoever maintains the system for you, not something you can change here yourself. What you can choose is how approvers are emailed: see Reminding approvers by email below.

Building claim titles automatically

Left to themselves, claimants title claims however they like, which makes a long list hard to scan. You can instead give your organisation one title format that every new claim fills in.

1. Select Settings in the left-hand menu, then, under System, select General.
2. In the Claims section, type a Claim title format using any of these placeholders: {claimant}, {category}, {month} (the month the claim is filed) and {details} (a short description suggested from the uploaded receipt). Select Use example to start from {claimant} - {category} - {month} ({details}). A Preview underneath shows what a title would look like.
3. Select Save Settings.

What happens next: the claim form gains a Details box above Title, and builds each new claim’s title from the format as the claimant fills it in. The claimant can still edit the title by hand. When they upload a receipt, Details is suggested from it, and they can change it or type their own; left empty, the {details} part is left out. Titles of claims already saved are never rewritten. Leave the box blank to turn this off and let claimants type their own titles again. A placeholder the system doesn’t recognise is refused when you save, with a message listing the ones it does.

Requiring a comment when a claim is approved

A rejection always needs a reason. Switch this on if you also want approvers to say something when they approve, for example to record what they checked.

1. Select Settings in the left-hand menu, then, under System, select General.
2. In the Approvals section, switch on Require a comment when approving.
3. Select Save Settings.

What happens next: whenever someone approves a claim, including several at once or from the approval link in an email, they’re asked for a comment and can’t approve without one. The claimant sees the comment on the claim and in their approval notification. See Approving a claim.

Reminding approvers by email

By default, an approver gets an email every time a claim is submitted to them. If that’s too many emails, you can send each approver one regular summary instead, or as well.

1. Select Settings in the left-hand menu, then, under System, select General, and go to the Approvals section.
2. Switch on Approval reminder digest, then choose its Frequency (Every day, Weekdays (Mon–Fri), or Weekly, on chosen days, picking the Days), when to Send at, and your Time zone.
3. To stop the email for every single claim, switch off Email approvers on each submission.
4. Select Save Settings.

What happens next: on the schedule you chose, each approver gets one email listing every claim still awaiting their approval, with a link to each claim and to My Approvals. Approvers with nothing waiting get no email. To send it straight away, whatever the schedule, select Send now (save any schedule changes first); a message then says how many emails were sent. Switching off Email approvers on each submission stops only those emails: approvers still get the in-app notification for each claim. See Emails you get about claims waiting for you for what approvers receive.

Choosing which day’s exchange rate applies

When a claimant enters an invoice in another currency, Get BNM Rate on the claim form fetches the Bank Negara Malaysia rate. You decide which day’s rate that is.

1. Select Settings in the left-hand menu, then, under System, select Currency.
2. Under BNM Exchange Rate, choose:
   • Today’s rate: the latest rate BNM has published when the claimant fetches it.
   • Transaction date’s rate: the rate on the claim’s transaction date. Weekends and public holidays use the last business day before it, and a future date uses the latest rate.
3. Select Save Changes.

What happens next: the choice applies whenever a rate is fetched from then on; rates already on claims aren’t changed. Under Transaction date’s rate, changing the claim’s transaction date fetches the rate again. A claimant can always type a rate by hand instead. See Claiming in another currency.

One other page exists outside this Administration section that this guide doesn’t cover as a task of its own. A Management Dashboard (for whichever of your organisation’s roles includes Management or Administrator access) is a fuller version of the company-wide figures already described in What the dashboard shows. It’s a read-only report, not a setting, so it isn’t repeated here as a separate configuration task.

This section collects the messages the system actually shows when something goes wrong, what each one means, and what to do about it. It doesn’t repeat how the underlying features work. Where relevant, it links back to the section that does.

“Spending Limit Exceeded” or “Approaching Spending Limit”

What it means: the claim you’re filling in would go over, or close to, a spending limit your organisation has set for that category.

What to do: this is a warning, not a rejection. It appears in the Review Before Submitting dialog with a Proceed Anyway button, and you can still submit. See Submitting your claim, and what the limit warning means. If your organisation has set the limit to block submission, you’ll instead see an outright error that names the limit, such as “This claim of RM 600.00 exceeds the per-claim limit of RM 500.00 for Meals. It cannot be submitted.” A period or pooled limit set to block reads the same way, with its own figures. In that case there’s no Proceed Anyway, and the claim stays a Draft. You’ll need to reduce the amount, pick a different category, or ask your administrator about the limit. The same applies to claims made through WhatsApp.

“Submission Window Exceeded”

What it means: the category you claimed under only accepts claims within a certain number of days of the transaction date, and this one is older than that. This depends on what you’re claiming: another category may allow more days, fewer, or have no deadline set at all.

What to do: if that category only warns about a late claim, you’ll see it in the Review Before Submitting dialog and can still select Proceed Anyway, once you’ve filled in the Reason for late submission box (see “Please give a reason for late submission” below). See Submitting your claim, and what the limit warning means. If it’s set to block submissions outright, you’ll instead see an error like “This claim cannot be submitted — its transaction date is 12 days past the 7-day submission window.” with no way past it from the form. Ask your administrator if you believe this claim should still be accepted.

“Please give a reason for late submission”

What it means: the claim is past its category’s submission window. Your organisation still accepts it, but only with an explanation. The full message is “This claim is past the submission window. Please give a reason for late submission.”

What to do: fill in the Reason for late submission box on the form, which opens when this message appears, and submit again. The same applies when you resubmit a rejected claim that’s past the window.

“Its transaction date falls in a financial year that closed on…”

What it means: the category you claimed under requires claims to be submitted before the financial year they belong to ends, and that year has now closed. A claim belongs to the financial year its transaction date falls in, not the date you submit it.

This is a separate condition from the day count in “Submission Window Exceeded” above, and both apply. So a claim can be only a few days old and still be refused: if your organisation’s financial year ends on 31 March, a claim dated 30 March and submitted on 2 April is three days old and has missed it.

What to do: nothing on the form will get past this, because the deadline has passed rather than being close. Ask your administrator, who can tell you whether the claim can still be accepted. If you’re claiming for something near the end of your financial year, submit it before the year ends rather than in the days after.

My claim shows “Late submission” but doesn’t say how many days

What it means: the claim was late for the financial-year reason above rather than the day count, on a category that warns rather than blocks. It went through, and the note on the claim records that its financial year had already closed.

What to do: nothing. It’s a record for whoever reviews the claim, not something you need to resolve.

A required field, or the category, won’t let you submit

What it means: something the form needs is still blank. Most often this is Title, Category, or Date of Transaction (see Filling in the details), or, if your organisation uses them, a Custom Field marked with an asterisk, which names the field it wants, in quotes, for example “Project Code” is required.

What to do: if clicking Submit Claim seems to do nothing at all, check whether a collapsed section (for example Custom Fields) is hiding the field that’s still empty. The form should jump to it and highlight it automatically, but if the page doesn’t move, open each section in turn and look for a field the browser is complaining about. If Category shows “This group has no categories yet.” under the group you picked, choose a different Group, or ask your administrator to add a category to it. An error naming a category as invalid, rather than the field being empty, usually means the category was retired while you were filling in the form. Refresh the page and pick again.

“Possible Duplicate Claim”

What it means: this claim looks enough like one you’ve already submitted (matching amount, vendor, reference number, or attached file) that it’s worth a second look before you file it again by mistake.

What to do: in the Review Before Submitting dialog, check the claim it’s comparing against. If this really is a new, separate expense, select Proceed Anyway. See Submitting your claim, and what the limit warning means. If your organisation blocks duplicates outright, you’ll instead see an error like “This claim matches existing claim(s) on amount, reference number and cannot be submitted.” with no way to proceed. Check whether you (or a colleague) already filed this expense, or contact your administrator if you’re sure it’s a genuine separate claim.

A file won’t upload

Several different messages can appear here, depending on what’s wrong with the file:

• “Invalid file type. Allowed: jpg, png, webp, pdf”: the file isn’t one of the types the system currently accepts for upload. This applies to receipts and to files added under Supporting Documents alike. The upload box itself lists Excel and Word among the file types it offers to pick, but the server rejects them regardless; only JPG, PNG, and PDF files upload successfully today. If you need to attach a spreadsheet or document, save or export it as a PDF first, or check with your administrator.
• “invoice.pdf” exceeds the 10 MB limit. (with your own file’s name in place of “invoice.pdf”): the file is larger than the system allows. Compress the image or PDF, or split it, and try again.
• “No text could be extracted from this PDF. It may be a scanned document — try uploading a JPG or PNG image instead.”: this is what you’ll see if nothing at all could be read from a PDF you upload from a claim’s own Edit page. Despite the wording, a scanned PDF is normally read fine; this usually means the scan is too blurred or faint, or the receipt isn’t on the first three pages. From the + New Claim upload box, the same situation instead attaches the file quietly and marks it Extracted without filling anything in. See Starting a claim from a receipt photo or PDF. Either way, a JPG or PNG photo of the same document usually reads correctly where the PDF didn’t.
• “OCR extraction failed. Please try again.” or “Upload failed. Please try again.”: something went wrong partway through, often a temporary connection issue. Try uploading again. If it keeps failing, enter the claim’s details by hand instead and let your administrator know.

The details read from a receipt are wrong

What it means: the system read the receipt but got a field wrong, most often an amount, the tax or a date. Reading is not perfect, especially from a blurred, faint or angled photo, which is why every pre-filled field needs checking before you submit.

What to do: correct the field by hand. Selecting Extract Again on the same file gives the same result, so it won’t fix a wrong field. Uploading a clearer photo or scan of the receipt often will. If the claim combines several receipts, check each receipt’s line item: each one is read from its own file. See Starting a claim from a receipt photo or PDF.

“Your authorisation to claim for [name] has ended.”

What it means: you entered this claim for someone else, but they’ve since revoked your permission to claim for them, or the end date they set has passed. You can still open the claim, but you can’t edit, submit, retract or delete it, or change its attachments.

What to do: ask the person to authorise you again from the Claim for Me tab of their profile (see Letting someone claim for you), or ask them to finish the claim themselves. It’s already theirs and shows in their own My Claims.

“This trip has not been added yet: click Add, or clear the fields.”

What it means: your mileage claim already has at least one trip, and the mileage box still holds another trip that you haven’t added. Submitting now would lose it.

What to do: in Amount & Currency, select Add to put the trip on the claim, or clear the fields if you didn’t mean to claim it, then submit again. If you were changing a trip, you’ll see “Finish editing this trip first: click Update trip, or Cancel.” instead; do one or the other.

“BNM publishes only today’s [currency] rate, not the rate for [date]. Please enter the conversion rate manually.”

What it means: your organisation uses the exchange rate on the transaction date, but Bank Negara Malaysia doesn’t publish past rates for this currency (for example CNY), so Get BNM Rate can’t find one. The date in the message is shown year first, for example 2026-10-01.

What to do: type the Conversion Rate yourself, for example from your bank or card statement, then continue as normal.

My claim has no approver

What it means: nobody has been set up to approve claims in this category. See Submitted and Setting who approves a claim. The claim isn’t stuck or lost. It’s genuinely waiting, indefinitely, for someone who can see every claim to pick it up directly.

What to do: you can’t push it forward yourself. Ask your administrator to either configure an approval chain for that category going forward, or to have whoever can see the All Claims menu look at this specific claim. See Seeing every claim in the organisation.

“This claim needs approval from your reporting manager…”

What it means: this category’s approval rule sends the claim to your reporting manager, but you have none set, or the person set has been deactivated. If the step can also go to someone else (the message then lists them, for example “your reporting manager or your department lead”), none of them could be found for you either. Your claim hasn’t been submitted; it stays a Draft, and nothing you’ve entered is lost.

What to do: ask your administrator to set your reporting manager. See Setting someone’s reporting manager. Then submit the claim again.

“This claim needs approval from the … branch’s approvers, but none are configured”

What it means: a rule’s approval chain for this category includes a Branch Approvers step, but your branch has nobody on its approver list. Unlike a Branch lead step, this step never falls back to the branch manager, so the claim can’t be sent anywhere and stays a Draft. The same message without a branch name (“…no branch could be determined for it”) means your account has no branch set.

What to do: contact your administrator. They need to add approvers to your branch under Settings → Branches / Entities, or set a branch on your user profile. See Setting up branches. Then submit the claim again.

“… is not in the … distance table. Choose a start and end location from the list.”

What it means: this mileage category only accepts routes from your organisation’s distance table, and one of your trips uses a start or end location that isn’t in it. A similar message, “… must use the table’s distance of … km”, means the route is listed but you changed its distance.

What to do: for each trip, pick both locations from the list and keep the distance that fills in. If the route you actually drove isn’t listed, ask your administrator to add it to the table. See Setting up a mileage distance table.

“This person is already authorised”

What it means: you tried to let someone claim on another person’s behalf, but that same pair already has an authorisation that is still in force.

What to do: nothing needs adding. Find the existing one in the list, under Claim Authorisations or on your profile’s Claim for Me tab. If you want a different end date, revoke the existing one first and then authorise again.

“A comment is required to approve this claim.”

What it means: your organisation requires approvers to write a comment when approving, and the approval was sent without one. This can happen if the setting was switched on while you already had the page open.

What to do: refresh the page and select Approve again. A box will ask for your comment; enter it and select Approve.

Some claims “could not be approved” after approving several at once

What it means: you approved several claims together in My Approvals, and some of them couldn’t be approved. The message starts with how many were approved, then lists each one that failed by title with the reason, for example because someone else had already decided it, or because a comment was required. The rest were approved normally.

What to do: read the reason beside each listed claim. The claims that failed are still ticked, so you can fix the cause and select Approve selected again, or open each one and deal with it on its own. The same applies to “could not be rejected” after Reject selected. See Approving or rejecting several claims at once.

I can’t see a menu someone told me about

A few menu items only appear for certain people, even when you’re clearly involved in what they cover:

• My Approvals appears if you approve anything: you manage a department or a branch, sit in a department’s or branch’s approver group, are a department’s C-Suite, are named on a rule as a Named Approver, have someone reporting to you, or simply have a claim waiting on you right now (for example as someone’s delegate). If none of those is true yet, it doesn’t appear. See Finding claims waiting for you.
• My Reimbursements, All Claims, and Reports each depend on which built-in role you’ve been assigned, not on any custom permission list. See Changing what a role can do. Being told you now have a permission like “view all claims” doesn’t put the page in your menu by itself if your underlying role doesn’t already carry it.
• Delegations has no menu link at all, for anyone. See Handing over your approvals while you’re away. You can only reach it by typing the address, which your administrator can give you.

If you believe you should see one of these and don’t, ask your administrator to check which built-in role your account is set up as.

I’m in the wrong organisation, or keep getting signed out

• “You do not have access to this organisation” at sign-in means the address you used belongs to an organisation you’re not a member of. Use the address or link your own organisation gave you, or sign in from the general sign-in page and choose from the list instead. See Choosing an organisation, and switching organisation.
• “You are not assigned to any organisation.” on the Select Organisation screen means your account exists but isn’t a member of anything yet. Contact your administrator to be added.
• If you’re suddenly returned to the sign-in page in the middle of working, with no message explaining why, it’s usually because your access changed while you were signed in. For example, your role or department membership was updated, or your account was deactivated. Sign in again. If that doesn’t work, or you weren’t expecting the change, contact your administrator.
• If you belong to more than one organisation and something looks unfamiliar (wrong claims, wrong people, wrong categories), check which organisation you’re currently in via Switching to a different organisation before assuming something is missing.

I didn’t get an email I was expecting

• For a password reset, seeing “Check your inbox” doesn’t confirm an email was actually sent. By design, it looks the same whether or not an account exists for that address, and the link inside expires after 60 minutes. See Forgetting your password. Check your spam folder, confirm you used the email address your organisation has on file for you, and request a new link if the old one expired.
• For a claim notification (a new approval waiting, a decision on your own claim), check My Feed in the app first. See Finding your notifications, since the in-app copy always arrives even if the email doesn’t. If you’re an approver waiting on someone else, you (or the claimant) can select Send Reminder on the claim to send a fresh copy of the approval email. See Nudging an approver who hasn’t acted.
• If emails are consistently missing across the board, the most likely causes are outside your control, such as a wrong address on your account, or your organisation’s mail being filtered somewhere along the way. This is one to raise with your administrator rather than retry on your own.

Signing in fails with “Invalid email or password”

What it means: the system doesn’t distinguish between a wrong email and a wrong password, for security. The same message covers both, and also an account that has never had a password set (for example, one that only ever signs in via SSO).

What to do: double-check both fields, and try Forgetting your password if you’re unsure. If your organisation offers Sign in with Microsoft (or another provider), try that instead. See Signing in with your company account (SSO). A separate message, “Account is inactive”, means your account has been deactivated. This isn’t something a password reset fixes, so contact your administrator.

An approval link says the claim was already handled, or has expired

Opening an approval link a second time, or one for a claim someone already acted on another way, shows “This claim has already been approved.” (or whatever it now is) instead of the claim summary. A link also stops working on its own after 7 days, showing “This approval link is invalid or has expired.” Neither is an error to fix. Sign in to the app normally to check the claim’s current status instead. See Approving from an emailed link, without signing in.

“You already have 3 exports in progress. Please wait for one to finish.”

What it means: you can only have three PDF reports (processing reports or batch PDFs) being generated at once, and three of yours are still Queued or Generating.

What to do: wait for one to finish. You can watch them on the Exports tab of Reports, or the Reports tab of My Reimbursements. Then select Generate again; the name you typed is kept. See Producing the processing report (PDF).

“That template no longer exists. Pick another and export again.”

What it means: the Excel column layout you picked when exporting a reimbursement batch was deleted by someone else after the list opened. It’s been removed from the list.

What to do: pick another layout (the default is selected again for you) and select Export. See Using the Excel round trip.

A button says “Insufficient permissions”

What it means: whatever you clicked, such as approving, rejecting, deleting, or editing, isn’t something your account is allowed to do, either in general or for that specific claim (for example, trying to act on a claim that isn’t actually assigned to you).

What to do: this isn’t something you can override yourself. If you believe you should be able to do this, contact your administrator. See Changing what a role can do for why having a permission and seeing the page it applies to aren’t always the same thing.

None of this replaces your own organisation’s help. If a message here doesn’t match what you’re seeing, or the suggested fix doesn’t work, contact your administrator. They configure how your organisation’s claims, rules, and approvals actually work, and can see things about your account and your organisation’s setup that this guide can’t.