MomijiExpenses
Receipt to reimbursement, no data entry.
Snap the receipt, confirm what Momiji read. In most suites this module is Concur; here it is the same system that pays the reimbursement.
Six steps, receipt to report.
Snap it anywhere
One action: add a receipt. A phone opens the camera; a desk takes a photo or a PDF. The paper goes in the bin.
Confirm, don't type
Extraction prefills vendor, date, tax, and total; you glance and confirm. Unread fields stay honestly blank, never guessed.
HST, checked every line
Subtotal is total less tip, divided by 1.13; tips are never taxed. Lines that miss that math are flagged for review.
One report per client
Separate drafts file side by side, one per client each month; overhead lands on a protected corporate report.
Approvals with a trail
Reports route to the real manager, with an admin fallback. Every decision is audited.
The PDF closes the books
Totals, line items, one embedded receipt per expense, your logo and colours. Hand it to the accountant or attach it to the invoice.
Not a bolt-on.
The broad suites bolt expenses onto a time clock; it shows.
| The broad suites | Momiji |
|---|---|
| Hours-only job tracking | Billing-native, line by line |
| Compliance tuned for the US | Canadian by construction |
| Track, then export to a payroll vendor | Momiji runs the payroll |
| Always-on location tracking | Location read only at the punch |
Proof
Every dollar traced.
Receipts retained, privately
Kept on file in access-controlled storage, never deleted after reading.
Confidential by design
A confidential employee's expenses stay invisible to managers and non-owner admins.
Every decision recorded
Submit, approve, request changes, reopen: an immutable audit line for each.
Walled off per company
Cross-tenant access is impossible by construction, not by a checkbox.
The things people ask first.
How good is the receipt reading, really?
The receipt is read server-side by Claude, Anthropic's frontier vision model, against a strict schema: vendor, date, subtotal, HST, tip, total, and a suggested category. The prompt's standing instructions forbid guessing, it may not invent a date or an amount, and it copies what is printed rather than computing figures, so a hard read stays honestly blank with the receipt attached.
Every read returns a confidence score from 0 to 1, and deterministic checks then re-verify the arithmetic line by line. A low-confidence read, or any figure that does not reconcile, is flagged for a person to confirm before it enters the report.
It also learns. Every receipt you confirm or correct teaches Momiji that merchant's proper name and the category you file it under, remembered per person in Momiji's own database. The next time a messy "STORE #1234" appears, it arrives as a clean, correctly categorized line, and your corrections never leak into anyone else's data.
It is the same extraction pipeline our own accounting practice runs on real client expense reports every month.
Does it get better the more we use it?
Yes, for each person individually. Every time you confirm or correct a receipt, Momiji remembers that merchant's proper name and the category you filed it under, keyed to you.
The next time the same vendor appears, even printed as a messy "STORE #1234", it proposes your clean name and the right category automatically, at high confidence. Your corrections are private to you and never leak into anyone else's data; an organization can also keep a shared merchant list so a new hire benefits from the company's common vendors on day one.
Does it handle HST correctly?
Yes, including the part most tools miss: tips are not taxable, so the reconciliation rule is subtotal equals total minus tip, divided by 1.13, checked to the cent with a two-cent rounding tolerance.
When the printed figures do not reconcile to that rule, Momiji flags the line and shows you the expected values; it never silently corrects a receipt.
Can one person file expenses to several clients in the same month?
Yes. Admins add clients inline, and each client gets its own draft for the month, so two clients in the same period never mix.
Who can see and approve expenses?
The employee, their manager chain, and admins, always subject to the confidential carve-out; the chain is walked on the server, so the app cannot be talked into showing more.
Approving is final; requesting changes requires a written note and reopens the report, with a question thread on the report itself. Receipts live in a private bucket and are served through signed links that expire in sixty seconds.
Approved reimbursements ride the next pay run.
Paid as a non-taxable line; nothing re-keyed.