Employee Expense Reimbursement, Now Inside Your Leave Management Tool

If your company has fewer than two hundred people, the case for a standalone expense management product is weaker than it looks. You’re paying $5–$10 per employee per month for a tool that overlaps 80% with your leave system: same employees, same approval chains, same managers, same payroll handoff at the end. The integration between the two products is the part that always breaks.

Leave Balance now handles employee expenses natively. Same login, same approver chain, same audit trail, same payroll sync — for no extra per-seat cost.

What’s in the expense module

The basics, done well:

• File an expense with category, date, amount, currency, receipt attachment, and optional project tag.
• Approval workflow that respects the same manager-and-finance chain you already configured for leave.
• Reimbursement via payroll — once approved, the amount appears on the next payslip automatically via webhook to PayrollApp (Nepal) or to your existing payroll system (UK, AU, NZ, US).
• Personal bank account selection — employees pick which of their saved accounts the reimbursement goes to.
• Audit trail — every state change is timestamped with the actor.

That’s it. We’re not trying to be Expensify. We’re trying to make sure the expenses your fifty-person team files each month don’t require a separate product, separate login, separate billing line, and separate integration to reconcile.

How it actually flows

A typical expense, end to end:

1. Employee opens Leave Balance, clicks Expenses → New.
2. Fills in the form, attaches the receipt photo from their phone.
3. Their manager sees the expense in their approvals queue (the same one that holds leave requests).
4. Manager approves; finance reviews any flagged categories.
5. On the next payroll run, the reimbursement appears as a line on the payslip and is paid into the employee’s primary bank account.

The whole loop typically completes in 24–48 hours, against 5–10 days for the average “submit-via-email-then-chase-finance” workflow we’ve seen at customers before they migrated.

Why we moved expenses into the leave app

Honest answer: customers asked, and the ownership map made sense.

The data overlap is enormous. Expenses need an employee record, a manager, an approval chain, a notification preference, a bank account, and a payroll handoff. Leave Balance already had every one of those. Adding an expense table and a reimbursement webhook was small; integrating two separate vendors to do the same thing would have been large and ongoing.

For our Nepal customers running on the PayrollApp bundle, expenses now flow into the next payroll run automatically — no second data entry, no end-of-month reconciliation. For UK/AU/NZ customers using their own payroll system, the expense module exports a CSV in the format your payroll provider expects.

What it doesn’t try to be

Some features we deliberately left out:

• Corporate cards. Use your existing card provider; we don’t compete with Pleo or Brex.
• Mileage rule engines with country-specific HMRC/ATO formulas. We capture mileage as a category; you set the rate.
• OCR receipt parsing. It’s coming, but it’s not in this release. For now, employees attach the photo and type the amount.
• Vendor payment workflows. Expenses here means employee-paid, employee-reimbursed.

That scope keeps the feature opinionated and easy to use. If you need full-spectrum spend management, keep your existing tool. If you need to stop paying per seat for two products that mostly do the same thing, we’re a better fit.

When it makes sense to switch

Run a back-of-envelope check:

• How many expense submissions per month? Under ~200 → strong fit.
• How many approvers and approval rules? Single chain or basic threshold-based → strong fit.
• Country-specific tax rules required? UK/AU/NZ/US/Nepal → covered. Niche EU rules → keep your specialist tool.
• Reimbursing via payroll already? Yes → integration is one-click.

For most SMBs in the under-200-employee range, the answer is “this is enough.” For larger or more complex finance ops, it isn’t, and we won’t pretend otherwise.

The bigger point

The “best of breed for everything” SaaS pattern made sense when integrations were rare and tools were expensive. Today most SMBs we talk to are tired of paying for ten tools that each do one thing and nine integrations that are each one update away from breaking.

Leave Balance is taking the opposite bet: the things that share employees, managers, and payroll handoffs belong in one product. Expenses is the second feature to come home (after employee payroll details). It will not be the last.