All modulesSHEET 05 / 09 · CLAIMS

Claims that paythemselves out.

Snap a receipt in any currency. It converts to your office's base currency, routes to the approvers your rules choose, and settles straight through payroll — no spreadsheet in the middle, no chasing anyone for a signature.

Any currency in, SGD out Rule-matched approvers Settles via payroll
app.leadmighty.com/claims
My claims grouped by submission batch, each line showing type, amount, date and approval status.
SHEET
05 / 09
MODULE
CLAIMS
PARTS
4 / 5
STATUS
LIVE

A closer look

Claims in 5 parts.

Straight from the running product — what an administrator sets up, and what everyone else does with it.

Every claim in the organisation, by batch

Stepped by month and filtered by department, team or country. Each batch carries its pending count and its total, so the queue can be worked from the top rather than opened one claim at a time.

/hr-lounge/claims

app.leadmighty.com/hr-lounge/claims
Expense claims across the organisation, grouped by submission batch with pending counts and totals.

Limits enforced at the door

Medical, travel, meals, mileage, training, entertainment and any custom type you add. Each carries a per-transaction cap, a per-period cap, and whether a receipt is required — enforced on submission, not discovered at audit.

/hr-lounge/claims

app.leadmighty.com/hr-lounge/claims
Claim types with categories, per-transaction and per-period limits, and receipt requirements.

Approval flows that match the claim

Different flows for different roles or named people, plus a default catch-all. Submission caps per period, and a rule set that decides a claim's path the moment it's raised.

/hr-lounge/claims

app.leadmighty.com/hr-lounge/claims
Claim settings: general rules, submission caps and approval configuration.

The approver's queue

Claims waiting on this person, grouped by batch — a trip's expenses advance together as one unit rather than trickling through one line at a time.

/team/claim-approvals · CAPTURE PENDING

app.leadmighty.com/team/claim-approvals
PLATE PENDING

A manager's claim approvals queue with claims awaiting a decision.

drop the capture at public/shots/claims-approval.png

Payment requests, same rails

Spend that isn't a reimbursement — a supplier invoice, a deposit — routes through the same approvals and lands with the same finance stage.

/hr-lounge/payment-requests

app.leadmighty.com/hr-lounge/payment-requests
Payment requests — the non-reimbursement side of spend, routed through the same approvals.

What's inside

Everything the claims module does for you.

Snap and submit

Photograph the receipt, pick a category, done. The receipt stays attached and viewable in the browser.

Multi-currency native

Spend in yen, bill in dollars — every claim converts to the office's base currency at submission.

Approval flows that match

Different flows for different roles or people, with a default catch-all — the claim finds its own path.

Thresholds and caps

Per-claim limits and per-period submission caps are enforced at the door, not discovered at audit.

Batches move as one

Submit a trip's expenses together and the batch advances through approvers as a single unit.

Paid with payroll

Approved claims land in the month's payroll run — one payment, one payslip line, no second transfer.

How it runs

Three steps, start to finish.

01

Snap the receipt

From a phone, in any currency, seconds after the meal ends.

02

It routes itself

Your rules pick the approvers; each one clears it in a tap, in order.

03

It pays out with payroll

The approved amount joins the next run and appears on the payslip.

Claims is one of nine modules — already working together.

One login, one record of truth, no re-keying between systems. Try the whole suite with your team.