Built for the parts
other expense tools skip.
Most expense tools handle the easy stuff — scanning receipts, basic approvals, syncing to QuickBooks. Eloope handles the rest. Hotel bills that should be five expenses. Foreign currency that actually reconverts. Duplicate receipts caught before they're paid. Nineteen specific things your finance team usually does by hand.
Every expense tool gets the basics right. Scan a receipt. Send it for approval. Push it to QuickBooks. The hard parts come later — the hotel bill that's really five expenses, the report that needs to reconvert when your base currency changes, the duplicate receipt that has to be caught before reimbursement. That's where most tools stop. We started there.
A hotel bill is really five expenses in one: the room, dinner at the bar, parking, pay-per-view, the minibar. Your expense tool just sees one charge.
Eloope reads the folio and splits it into the right categories automatically.
Eloope reads each line of the folio, sorts it into the right category, and checks it against your policy and the booked rate as it goes. The minibar gets flagged as personal so no one accidentally writes it off. Parking goes to transport, dinner goes to meals. Your category totals match what was actually spent, and nobody has to re-type the bill.
Marriott Berlin · Folio #28471
Submitted by S. Müller · uploaded 1 PDF
Room — 3 nights × $480
Restaurant — bar & breakfast
Valet parking — 3 nights
Pay-per-view (×2)
Minibar
Every line, its own category
Each line on the folio gets its own category, GL code, and policy check.
Catches rate mismatches
Flags it when the nightly rate doesn't match what was booked, or when there's a charge you didn't expect.
Personal charges flagged
Minibar and other personal items get marked separately so they don't get reimbursed.
Receipt stays linked
The original folio PDF stays attached to every line in case anyone needs to look it up.
Submit in any currency, report in one — most tools promise it. What you usually get is missing conversions, blank fields on cash advances, and reports that go stale the moment you change your reporting currency.
Submit in any currency. Report in one. Switch reporting currencies and everything updates — including the report total.
Every expense converts to your base currency the moment it's submitted, using that day's rate. Change the base currency later and every open report updates — line items and totals both. Your CFO can read everything in USD while the team in Berlin reads it in EUR, both views off the same numbers. And every expense always has a converted amount, so reports never have blank cells.
Open report · 4 currencies
Org default · USD · FX as of submission
Hotel — Berlin
S. Müller · €620.00
Dinner — Tokyo
K. Tanaka · ¥18,400
Taxis — London
S. Smith · £74.50
Coworking — Lagos
I. Okafor · ₦92,000
Report total
$947.71
Converts at submission
Each expense uses the rate on the day it was submitted, so there's no drift later.
Switch base, everything updates
Change your reporting currency and every open report recalculates — line items and totals.
Read in any currency
Toggle the dashboard between currencies without changing the underlying data.
No blank conversions
Every expense and advance always carries a converted amount.
Most “AI” in expense tools is just receipt scanning with a fancy label. It can't tell you what engineering spent in Tokyo last quarter, or approve the three reports finance already vetted. A real AI should actually be able to do the work.
Luna is a chat assistant that can actually use the app — file expenses, run reports, route approvals, find duplicates.
Luna isn't a chatbot bolted onto receipt scanning. Ask her to file an expense, pull a spending breakdown, find duplicates, or unstick an approval — she does it. Every action runs as you, so it shows up in the audit log under your name, the same as if you'd clicked through the dashboard yourself.
What did engineering spend in Tokyo last quarter?
Engineering · Tokyo · Q1 2026
Real actions, not just answers
Luna can create expenses, approve reports, query analytics, set policies, and more.
Acts as you
Every action runs with your permissions and shows up under your name in the audit log.
Plain-English questions
Ask in plain English and get totals, charts, and breakdowns back.
Multi-step requests
One conversation can file, route, escalate, and notify — without you opening a single menu.
Some expense tools require you to use their corporate card to get auto-reconciliation. Switching banks just to run expenses isn't a trade most teams want to make.
Connect any US bank or card through Plaid. Keep the banking relationships you already have.
Connect any US bank or card supported by Plaid and Eloope imports transactions automatically. No required card program, no minimum spend, no need to move off whatever you're already using. Transactions match themselves to receipts, sort into the right categories, and go straight into the approval flow. Pleo, Brex, Ramp, Mercury, your regular business credit card — they all just work.
Connected via Plaid
Auto-imported transactions · matched to receipts
Chase Business
···· 4521
182 txns · 30d
Capital One Spark
···· 8810
94 txns · 30d
Mercury
···· 0042
67 txns · 30d
Amex Business
···· 1004
248 txns · 30d
All Plaid-supported US banks & card programs are eligible
Connect anotherWorks with any US bank
Every US bank and major card provider Plaid supports.
Matches receipts automatically
Imported transactions find their receipt by amount, date, and merchant.
Works with the card you have
Pleo, Brex, Ramp, Mercury, or a regular business credit card — Eloope reconciles on top.
No new card required
Keep your bank. Keep your spend program. Eloope just reads from it.
Duplicate receipts. Round-number amounts. Weekend dinners filed as client meetings. By the time finance catches them at close, the money's already been reimbursed.
Five checks that catch the most common problems — at submission, not at close.
Every submission runs through five checks: duplicate receipts (even ones that have been re-scanned or re-cropped), round-number amounts, weekend dates, odd-hour timestamps, and the same merchant appearing too often. The checks run before the report ever reaches an approver — so if something's off, you ask the submitter while the receipt's still on their phone, not the auditor three months later.
Dinner — Le Coucou
$214.80 · client meeting · M. Chen → Apr 21
5-rule scan
Duplicate receipt
Similar receipt submitted Apr 18 by M. Chen
Round number
Weekend date
Odd-hour timestamp
Repeat-merchant velocity
Catches re-scanned duplicates
Even when a duplicate receipt has been re-cropped or re-rotated, the check still catches it.
Five checks on every submission
Duplicate, round number, weekend, odd-hour, and repeat-merchant frequency.
Caught before approval
Flags surface before the report enters anyone's approval queue.
Routes to a reviewer
Flagged items go to finance or audit for a quick decision.
SOC 2 access reviews usually mean a quarterly consultant bill and a spreadsheet — or they're behind an enterprise paywall your team can't justify yet.
Access reviews built in — mapped to SOC 2 CC6.1–6.6, with snapshots, auto-apply, and an auditor view.
Each control under SOC 2 CC6.1 through CC6.6 has its own review cycle. When a cycle runs, Eloope captures a snapshot of who has access to what, sends it to the right reviewer, and either applies the decision automatically or escalates it if it goes past due. When the audit comes, your auditor gets a read-only view of every cycle and snapshot — no exporting screenshots into a binder.
Access review · Q2 2026
Snapshot · 2026-05-01 09:00 UTC
Logical access · prod database
Reviewer · P. Costa
New-hire provisioning
Reviewer · R. Park
Role changes · finance team
Reviewer · P. Costa
Off-boarding · 90-day check
Reviewer · —
Mapped to SOC 2 controls
Each control gets its own review cycle, with its own cadence.
Snapshots on every cycle
Each cycle captures the exact access state at that moment, for the audit later.
Auto-applies or escalates
Decisions apply automatically. Overdue cycles escalate up the chain.
Read-only auditor view
Auditors see the review history without touching production data.
Your tool calls it a “trip,” but it's really just a tag on each expense. There's no trip-level policy, no shared cost-center allocation, no trip object your CFO can actually read.
A trip in Eloope is a real record — one object that holds every expense, with its own policy, total, and cost centre.
A trip groups every expense, advance, and mileage entry. It carries its own per-diem cap, allowed categories, and daily limits. It allocates to a single cost centre. And it adds up to one total your CFO can actually read. TripIt is supported too — itinerary, dates, and destinations import on their own, so the trip exists before the first receipt does.
Berlin Q2 Roadshow 🇩🇪
Apr 14 → Apr 17LH 401 · SFO → BER
Imported from TripIt
Marriott Berlin · 3 nights
Folio · 5 line items
Client dinner · Lutter & Wegner
Within per-diem cap
Taxis · BER airport ↔ hotel
Mileage · 38 km total
Trip total · base currency
$4,034.10
One trip, all the spend
Every expense, advance, and mileage entry belongs to the same trip record.
Trip-specific policy
Set per-diem caps, allowed categories, and daily limits just for this trip.
Allocate the whole trip
Send the entire trip to one cost centre, not each line.
TripIt itinerary import
Pulls itinerary, dates, and destinations in automatically.
Your tool gives you routing rules too simple to model your org, or a workflow builder too complex for anyone to maintain. Most finance teams need both.
Two layers: simple routing rules for the common cases, and a visual workflow builder for everything else.
The routing layer covers the everyday cases. Set thresholds by amount, department, category, or cost centre in a few minutes — no logic to write. When routing isn't enough, switch to the visual workflow builder: branch, run paths in parallel, call an external API, drop in a human-review step. Dry-run mode lets you replay last quarter's expenses through a new workflow before flipping it on. Most teams use both.
Approval workflow · Travel > $1K
Routing rule + visual builder · dry-run available
Expense submitted
Trigger · category = Travel
Amount > $1,000 AND role ≠ Director
Conditional · two branches
Finance review
Human node · 1 reviewer
Auto-approve
No human required
POST to QuickBooks · sync as bill
External action · response logged
Plain routing rules
Set rules by amount, department, category, or cost centre without writing any logic.
Visual workflow builder
Branch, run in parallel, call an external API, add a human-review step.
Dry-run before going live
Replay past expenses through a workflow before turning it on.
Every run is logged
Every workflow run records its inputs, decisions, and external responses.
Plus the small things that break expense work every day.
None of these are flashy. They're the kind of details a finance team only notices when they're missing — and then notices every day.
Problems are usually caught at close — when fixing them is expensive.
Policy, fraud, and folio checks all run before the submit button.
Three checks run while the submitter is still in the form. Catch it now, fix it now — not three months later at close.
Splitting a $200 dinner between two people is not the same as breaking a hotel bill into five charges. Most tools treat them as the same thing.
Splits and line items are different things in Eloope.
Splits decide who owes what. Itemizations break a single charge into its real categories. Policy, reporting, and the audit log treat them differently — because they are.
Editing a submitted expense usually means rewriting the audit trail.
A proper amendments flow that keeps the original.
Once an expense is submitted, you amend it through a dedicated flow. Every change saves the original, the new version, who asked for the change, who approved it, and when.
Cash advances usually end up in a side spreadsheet nobody trusts.
Cash advances handled in the system, end to end — in any currency.
Request, approve, settle, and reconcile advances inside Eloope. Currency conversions carry through to settlement. Expenses filed against an advance reconcile against it automatically.
Most expense tools sync to QuickBooks. Anything else is a paid upgrade.
QuickBooks, Xero, Sage, and FreshBooks — all native, all included.
Four native accounting syncs, no upcharge. Plus Google Drive, OneDrive, Slack, Microsoft Teams, Zapier, and webhooks. Connect whichever your team already uses.
In most tools, “cost centre” is just a text field — a tag pretending to be something more.
Cost centres are real objects, with real hierarchy.
Cost centres have parent-child structure, roll up cleanly in reporting, and allocate properly across expenses, trips, and advances. Everything that moves money knows what cost centre it belongs to.
The approver is out, and the whole queue sits.
Approvers can delegate or hand off — without breaking the audit log.
Approvers can name a delegate, escalate by amount or category, or pass an item to a peer. Delegation has a start and end date, and the original approver still shows in the record.
Most tools categorize by matching merchant names. New vendor, manual sorting.
Smart categorization that learns from your team.
Eloope looks at what the submitter usually picks for this merchant, then what your org usually picks, then a keyword model. When someone corrects a category, the model learns from it.
Most workflows can branch on what was submitted — never on who submitted it.
Workflows can branch on who submitted the expense, not just what was submitted.
Job title, department, and role are built-in filters in routing rules and the workflow builder. “If the amount is over $1K and the submitter isn't a director, notify finance” is one rule — not a custom integration.
Most SMB finance tools have no way to restrict access by IP.
Org-level IP allowlist and blocklist.
Set allowed and blocked IP ranges for your whole org. Requests from outside the allowlist are blocked before they reach the app.
“Reminders” in most tools means one notification.
Real recurring reminders — across email, in-app, and Slack.
Reminders run on a schedule, with a start date and an end date. They deliver through email, in-app, and Slack. Each user picks which channels they want, per reminder.