From receipt to reimbursement to the ledger
Receipt capture, per-diem and mileage automation, policy checks, and batch reimbursement — every reimbursement posting to the GL.
Everything Expenses & Travel handles
Expense claims that post to the GL
Multi-line reports with category, merchant, project, and tax; on reimbursement a balanced journal posts — expense debits to the mapped accounts, credit to your configured cash or clearing account.
Receipt OCR with a Sebee fallback
Uploaded receipts are validated, re-encoded, and read by OCR; on low confidence Sebee’s vision model extracts merchant, date, amount, tax, and currency and drafts the line.
Per-diem and mileage automation
Per-diem rate masters by country and region and mileage masters by vehicle auto-generate expense lines for a date range or trip distance.
A real policy engine
Per-category limits with block, warn, or require-approval at submit time, plus duplicate-receipt detection by merchant, amount, and date across reports.
Multi-level approval with segregation of duties
Amount-tier thresholds route through supervisor, department head, and CFO; an approver can’t be the submitter or beneficiary, and a reimburser can’t pay themselves.
Batch reimbursement runs
Select approved reports by cutoff or employee and process them as one journal that flips every report to reimbursed — with a payroll CSV export and double-payment guards.
From action to ledger, in four steps
- 1Capture
Create a report and add lines — typed, per-diem or mileage generated, or extracted from a receipt.
- 2Submit
The policy engine runs on submit — blocking, forcing approval, or warning on duplicates — and foreign lines snapshot their FX.
- 3Approve
The report advances through amount-tier levels with segregation-of-duties guards.
- 4Reimburse
A single report or a batch run posts a balanced journal — expense debits, cash credit — under a row lock with idempotency guards.
Real screens, real data
Honest onboarding, not a hidden failure
Reimbursement posting needs a few account-assignment keys mapped — the reimbursement cash account, category expense accounts, and the employee-advance receivable. Until they’re set, the resolver fails closed with a clear message rather than misposting.
What you get
- Expenses reach the GL automatically, coded to the right accounts and cost centers.
- Policy limits and duplicate detection are enforced by the system at submit time.
- Foreign-currency lines translate to functional currency, with FX gain or loss journaled.
- Segregation of duties and double-payment guards on every money-moving step.
- Sebee reads a receipt and drafts the line so people key less and claim faster.
Frequently asked questions
Do reimbursements post to the GL?
Yes. On reimbursement a balanced journal posts — expense debits to the mapped accounts, credit to your configured cash or clearing account. A single report or a batch run posts under a row lock with idempotency guards.
How does receipt capture work?
Uploaded receipts are validated, re-encoded, and read by OCR; on low confidence Sebee’s vision model extracts merchant, date, amount, tax, and currency and drafts the line.
How are expense policies enforced?
A real policy engine runs at submit time — per-category limits that block, warn, or require approval, plus duplicate-receipt detection by merchant, amount, and date across reports.
Can someone approve or pay their own expense?
No. Amount-tier thresholds route through supervisor, department head, and CFO; an approver can’t be the submitter or beneficiary, a reimburser can’t pay themselves, and batch runs carry double-payment guards.
Are per-diem and mileage automated?
Yes. Per-diem rate masters by country and region and mileage masters by vehicle auto-generate expense lines for a date range or trip distance.