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 ERP, confirmed with a single action.
Six stages. One confirmed payment.
OmniPATH takes expenses from approval through to payment confirmation in a single connected flow - no spreadsheets, no manual collation, no chasing employees for bank details at month end.
Faster for finance. Better for employees.
Three features combine to make reimbursement the least painful part of the expense process.
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 - useful when you want to run an interim payment for one employee without waiting for everyone else to finish submitting. The batch is date-stamped, employee-totalled and exported with a reference number that links back to every individual claim it covers.
- Group by employee - one total per person per batch
- Select all or a subset for the current run
- Batch reference links back to every claim included
- ERP sync on batch completion (Xero, QuickBooks, Sage, Dynamics)
- Payment confirmation recorded against each claim
- Full audit trail from approval to payment confirmation
No rigid deadlines. Windows auto-open.
Most expense systems force employees to submit within a fixed window - end of month, end of quarter. Miss it and you wait. OmniPATH uses perpetual reimbursement windows: as soon as one batch is processed, the next window opens automatically. There is always an active window accepting submissions.
Finance sets how often they want to run reimbursements - weekly, fortnightly or monthly. OmniPATH creates the windows, opens them and closes them automatically. Employees always know when the next payment run is without asking finance.
- Windows open automatically on a configured cadence
- No manual window creation or administration
- Employees see the next payment run date on their dashboard
- Late submissions queue for the following window automatically
- Ad hoc runs can be triggered outside the schedule by finance
ERP sync on every batch.
When a reimbursement batch is confirmed, OmniPATH syncs the entries to your accounting system automatically. Each employee's total posts as a creditor payment in Xero, QuickBooks, Sage or Dynamics - with the batch reference and the individual claim references as line-item notes.
The GL account, cost centre and tax code are carried through from the original expense coding - no re-coding in the accounting system. Finance approves the batch in OmniPATH and the entries appear in the accounts within seconds.
- Xero - Bill payment per employee per batch
- QuickBooks - Expense or bill payment with line items
- Sage 50 and Sage 200 - Purchase ledger entries
- Microsoft Dynamics 365 Business Central - vendor payment journal
- GL codes and cost centres carried through from expense coding
- Batch reference links ERP entry back to OmniPATH claim list
What reimbursement looks like without the chasing.
Reimbursements by the numbers.
Reimbursement batches - answered.
Can finance run an ad hoc payment for one employee outside the normal schedule?
What happens if an expense is approved after the batch has already been run?
How does the ERP sync work - does it create one entry or one per claim?
Does the employee get notified when they have been paid?
Process your first reimbursement batch today.
Connect your ERP, import your approved expenses and run your first reimbursement batch - all in the same session. Book a demo to see the full flow live.