Bea reviews every expense, so you review what's left.
The whole company submits by chat — no app, no login. Your finance lead gets a tool that surfaces only what's notable, each flag with a reason. One click to a proof pack your accountant trusts.
Request early accessBea matches the tool to the role. The 95% of your company who touch expenses lightly submit and approve in chat. The one person who owns the consequence — your finance lead — gets a power tool that does the looking for them and hands the accountant clean proof.
- Most of the company installs nothing and logs in nowhere. Submission and approval happen in chat.
- Finance reviews only the expenses that need a second look — not everything — each one explained.
- One click produces an accountant-ready proof pack, with receipts kept attached to their bookings.
- Bea is not a card, not a spend suite, not enterprise software. It sits in front of the systems you already run.
Expense work is lopsided. Bea matches the tool to the role.
Most people touch expenses a few times a month. One person owns all the judgment and the consequence. Every other tool gives them the same app, the same login, the same dashboard — so the burden spreads evenly and badly.
No software to learn
Submitters and approvers — over 95% of the company — work entirely in chat. Telegram or WhatsApp.
Nothing to install. No account to create. No training. They send a receipt, answer one question if needed, and they're done.
A tool that does the looking
The finance lead gets the power tool — not another dashboard to read, but a queue of only what's notable.
Bea does the reviewing. Finance makes the decisions. One click turns the month into proof the accountant trusts.
Everyone else sells you a place to do the work. Bea removes the work.
Card-first platforms, legacy enterprise suites, receipt-scanner apps — they all assume the hard part is capture.
Capture is a commodity now. It isn't the expensive part.
The expensive parts are:
- Friction for the person who submits a few expenses a month
- The finance lead reading everything to catch the few things that matter
Bea attacks both.
It doesn't give you a better place to do the work.
It does the work you were doing by hand.
Correct before it reaches a human.
The reviewing starts before submission. In chat, before anything moves, Bea makes sure:
- Required fields are complete
- Receipts are attached when required
- Amounts and currencies are explicit
- Approval limits are respected
- The submitter confirms the data
No silent assumptions.
No hidden edits.
No floating numbers.
Incomplete claims never reach the approver. Or finance.
For the many: send a receipt. You're done.
No app, no login. A submitter sends a photo in chat. Bea reads it, asks only what's missing, and confirms. That's the whole experience for almost everyone in the company.
EXPENSE SUMMARY
Capture
Upload a receipt in chat. Bea extracts structured data.
Validate
Bea checks completeness and policy boundaries. If something is missing, it asks immediately.
Confirm
The expense is summarized clearly. Nothing moves forward without explicit confirmation.
Submit
Only confirmed, validated expenses reach your backend. Finance receives structured input.
For the few: a queue, not a dashboard.
Bea reviews everything and stays silent on the routine. When something is notable, it says so — and tells you why. Silence means routine. Words mean check closely. You decide; Bea never approves on its own.
Proof your accountant trusts. In one click.
At month-end, the work is already done. One click turns the month into a complete, audited proof pack — the kind an external accountant can book straight from.
- Receipts stay attached to their bookings. No re-linking by hand, no media breaks.
- Replacement receipts (Eigenbeleg) handled when the original is gone.
- Cover sheet, line items, and approval log in one document.
- DATEV-style structured export your Steuerberater can import directly.
Built to survive a year-end audit — not a demo.
Built for audit, not demos.
The GoBD liability sits with you, not your accountant. Bea is designed for that from day one.
- Explicit audit trail and deterministic workflow states
- Receipts kept attached to their bookings
- Minimal data retention
- Multi-tenant separation
- Explainable flags — no silent automation, no LLM authority over financial truth
And a privacy boundary by design: Bea flags expenses, not people. Behavioral context stays on the finance surface only and always describes the expense — never the person's habits.
Correctness over speed.
Not a card. Not a suite. Not another app to roll out.
Bea is not:
- A corporate card or banking switch
- A spend-management suite or dashboard
- Enterprise software with a per-seat login for everyone
- A replacement for your ERP, bookkeeping, or payroll
Bea sits in front of the systems you already run.
It does the reviewing, then hands over clean proof.
Built for the finance lead.
Bea is bought and used by one person: the finance lead — full-time or fractional — at a 10–200 person company that reimburses expenses monthly and works with an external accountant.
It fits best when:
- Most employees submit expenses only now and then
- Incomplete claims keep coming back for the same fixes
- Month-end means reading everything to find the few that matter
- Your Steuerberater works in DATEV
Your colleagues barely touch software. You get your time back.
Why expense submission correctness mattersPacks, not seats.
You don't pay for the many who barely use it. You pay for correct, finished expenses — in packs of processed expenses, not per login. Bea is free during early access while we get this right with our first teams.
- Chat submission and approval — no app, no login
- Exception queue with explained flags
- Accountant-ready proof packs, DATEV-style export
- Direct onboarding support
Currently in controlled rollout.
We're onboarding selected finance leads who'd rather review what's notable than read everything. If that's you, get in touch.
Request early accessFrequently Asked Questions
Bea splits expense work by role. The whole company submits and approves by chat — no app, no login. The finance lead gets a web tool that surfaces only the expenses that need a second look, each with a reason, and produces an accountant-ready proof pack in one click.
Bea reviews every expense, so finance reviews what's left.
No. Most of the company submits and approves in chat — Telegram or WhatsApp.
Nothing to install, no account to create, no training. Only the finance lead uses the web tool.
Bea reviews every expense and stays silent on the routine. When something is notable — over policy, missing a receipt, unusual for that submitter — it says so and explains why.
Silence means routine. Words mean check closely. The human always decides.
No. Bea flags expenses, not people.
Objective flags like a missing receipt or over-policy spend are visible to approvers. Behavioral context stays on the finance surface only and always describes the expense — never the person.
No. Bea sits in front of your existing systems.
It hands finance and the external accountant an audit-ready proof pack — cover sheet, line items, receipts kept attached to their bookings, approval log, and a DATEV-style structured export.
No. Bea surfaces what needs attention and explains why. People decide.
Validation and workflow logic are deterministic — correctness is enforced, not guessed — and Bea never claims authority over the final decision.
Learn more about expense submission correctness
Guides, definitions, and comparisons for finance teams who care about clean, audit-ready submissions.
Expense Submission Correctness
The pillar guide: why workflows break at submission and how to fix it.
Replacement Receipts (Eigenbeleg)
How to create a compliant replacement receipt when the original is missing.
Audit-Ready Expense Reports
What makes an expense report hold up under audit — a practical checklist.
Expense Compliance Glossary
Clear definitions of the terms finance teams and auditors use.
Best Expense Submission Tools
How Bea compares to Circula, Expensify, Pleo and other options.
Bea vs Circula
Review-reduction layer vs full spend-management suite.