Skip to content
Book a demo

Expense management · Reimbursements

From approved to paid, in one run.

Once expenses are approved, they flow into the reimbursement queue automatically. Finance processes them in batches: grouped by employee, synced to payroll or the ERP and confirmed with a single action.

Live Queued automatically One-click ERP export Full audit trail
Your booksXero · Sage · QuickBooksApprovedCodedEvidenced
Bills enter a funnel of 5 rings around the ONE RUN stamp: Read (Read, classified and extracted, however it arrived: email, upload, photo or folder.), Identify (Is this a real, verified supplier? Is it the one we think it is?), Match (Does it match the order, the delivery and the agreed price?), Check (Have we seen it before? Is the VAT rate right? Do the lines and dates add up?), Approve (Approved by the right person, under the rule on the screen.). A bill that fails is held on its ring with a named reason and one fix. Only bills that pass every ring drop into your books: approved, coded, evidenced. This page lights 05 Approve.

The reimbursement flow

Six stages. One confirmed payment.

OmniPATH takes expenses from approval to payment confirmation in a single connected flow: no spreadsheets, no manual collation and no chasing employees for bank details at month end.

1Stage 01SubmitThe employee submits an expense.
2Stage 02ApproveThe manager signs off.
3AutomaticQueueAdded to the batch queue.
4Stage 04BatchFinance selects and runs.
5Stage 05ExportSynced to the ERP or payroll.
6AutomaticConfirmPayment recorded and the employee notified.

How it works

Faster for finance. Better for employees.

Three features combine to make reimbursement the least painful part of the expense process.

01 · Batch processing

Select, batch and pay.

When an expense is approved it drops into the reimbursement queue automatically, grouped by employee. Finance opens the queue, sees every employee with approved but unpaid expenses, selects who to pay in this run and processes the batch in one action.

A batch can be the whole queue or a subset, which is useful for an interim payment to one employee. Each batch is date-stamped, totalled per employee and exported with a reference number that links back to every claim it covers.

  • One total per person per batch
  • Select all or a subset for the current run
  • ERP sync on batch completion (Xero, QuickBooks and Sage)
  • Payment confirmation recorded against each claim

Batch RB-2026-06 · processing

Illustrative
EmployeeClaimsAmount
Sarah Johnson5 claims · Visa 4821 reconciled£842.30
James Patel3 claims · personal card£316.40
Emma Carter4 claims · personal card£228.10
3 employees£1,386.80

02 · Perpetual windows

No rigid deadlines. Windows open automatically.

Most expense systems force employees to submit within a fixed window. Miss it and you wait. OmniPATH uses perpetual reimbursement windows: as soon as one batch is processed, the next window opens, so there is always an active window accepting submissions.

Finance sets the cadence (weekly, fortnightly or monthly) and OmniPATH creates, opens and closes the windows. Employees always know when the next payment run is without asking finance.

  • No manual window administration
  • Next payment date on every employee dashboard
  • Late submissions queue for the following window
  • Ad hoc runs outside the schedule when finance needs them

Reimbursement windows · weekly cadence

Illustrative
WindowOpenRunStatus
Window 2409-23 June24 JuneActive
Window 2524-30 June1 JulyUpcoming
Window 261-7 July8 JulyUpcoming
Generated automatically; three future windows always visible to employees

03 · Connected to accounting

ERP sync on every batch.

When a batch is confirmed, OmniPATH syncs the entries to your accounting system automatically. Each employee’s total posts as a creditor payment, with the batch reference and the individual claim references as line-item notes.

The GL account, cost centre and tax code carry through from the original expense coding, so there is no re-coding in the accounting system. Finance approves the batch in OmniPATH and the entries appear in the accounts within seconds.

  • GL codes and cost centres carried through
  • The batch reference links the ERP entry back to the claim list

Sync targets

Illustrative
SystemEntryStatus
XeroBill payment per employee per batchLive
QuickBooksExpense or bill payment with line itemsLive
Sage 50 and Sage 200Purchase ledger entriesLive
Microsoft Dynamics 365 Business CentralVendor payment journalOn the roadmap

Before and after

What reimbursement looks like without the chasing.

Before

Manual reimbursement

  • Finance collates claims from email, spreadsheets and printed forms
  • Bank details collected separately, and lost by the next run
  • Manual totals per employee, prone to error
  • ERP entries keyed manually from the spreadsheet
  • Employees email to ask when they will be paid
  • No audit link between the payment and the original claim

After

OmniPATH reimbursements

  • Approved expenses appear in the queue automatically
  • Bank details stored securely on the employee profile from day one
  • Totals calculated automatically per employee per batch
  • ERP entries created on batch confirmation, with no re-keying
  • Employees see the next payment date on their dashboard
  • A full audit trail: the batch reference links the payment to every claim

By the numbers

Reimbursements by the numbers.

Queued automatically

Approved expenses enter the reimbursement queue immediately, with no manual step.

Three ERP integrations

Xero, QuickBooks and Sage 50 and 200, with Business Central on the roadmap.

A window always open

Perpetual windows mean no employee misses a payment run.

One click to the ERP

Confirm the batch and entries post to the accounts within seconds.

Questions

Reimbursement batches, answered.

Can finance run an ad hoc payment for one employee outside the normal schedule?

Yes. While perpetual windows run on a set cadence, finance can trigger an ad hoc batch at any time for any subset of employees. The ad hoc batch is date-stamped and carries a distinct reference number, so it stands apart from scheduled runs in the audit trail. Ad hoc runs do not affect the schedule: the next window opens as normal.

What happens if an expense is approved after the batch has already run?

It queues for the next window automatically. The employee can see on their dashboard which claims are in the current window and which are in a future one. No manual intervention is needed, and if the amount is urgent, finance can add it to an ad hoc run.

How does the ERP sync work? Does it create one entry or one per claim?

One entry per employee per batch by default, which is how most accounting systems handle employee expense payments. The entry carries the batch total for that employee, with the individual claim amounts and references as line-item notes. That keeps the accounts tidy while preserving full traceability. If your workflow needs one entry per claim, that mode is available as an alternative export format.

Does the employee get notified when they have been paid?

Yes. When finance confirms a batch as paid, OmniPATH sends each employee in it a payment confirmation by email and in the app, showing the total paid, the claims included and the payment date. That removes the most common finance inbox query: “When will I get my money back?”

Ready when you are

From approved to paid. In one run.

Book a 30-minute demo and we'll run a reimbursement batch through to your accounting system, live.

No minimum term · UK-based support