MOMIJI
Go live in ten days.
Connecteam + ADP + BambooHR + Concur, all in one.
Punches become the paycheque, with no export.
See the whole systemOne directory, one approval chain, one pay run.
An org chart, a spreadsheet, last cycle's payroll run. Upload it; Momiji reads it.
People, departments, manager chains, time off policies, laid out in minutes.
Momiji proposes; you approve.
Profiles complete, time off booking, first stubs delivered.
Every person, role, and manager chain, in one place.
Requests route to the real manager chain; approval deducts the balance.
Every stub, every period, self-served.
A ninety-day path, visible to the manager.
Photograph a receipt; extraction fills the row; a branded PDF closes the books.
Geofenced punches, Ontario wage math, straight into payroll.
Policies post to balances on their own; the ledger reads like a bank statement.
Versioned company documents, signed from a phone, sealed with a certificate.
Dry-run. Commit. Stubs delivered. Remittances reconciled.
Visible only to administrators you name.
White-glove launch, first upload to final invite wave. Not live in ten days, the setup fee comes back.
Waived for founding clients on a twelve-month commitment.
Upload what you have, review in stages, set balances, invite in waves. The five steps above are exactly what we run together, and if you are not live on day ten, the setup fee is refunded.
Every upload is read server-side by Claude, Anthropic's frontier model, against a strict schema whose standing instruction is an honest blank over a guess: it may not invent a date or an amount.
On receipts, the model returns a confidence score with every read and deterministic checks re-verify the arithmetic; a low-confidence read, or any figure that does not reconcile, is flagged for a person to confirm. Nothing is ever silently corrected.
On expenses it also learns each person's vendors over time, so a messy receipt becomes a clean, correctly categorized line on its own. It is the same pipeline our own accounting practice runs on real client books every month.
The engine implements the CRA's published T4127 formulas - CPP and CPP2, EI, federal and Ontario tax, surtax, and health premium - and is verified field-by-field against the CRA's own payroll calculator, to the penny.
Every committed run is stamped with the engine and tax-table version that produced it, and the register is immutable: corrections are reversing entries, never edits.
Checking it that way is also how we found a rounding bug in our own engine, which we fixed and then guarded. That is written up in full, along with everything else we check ourselves against.
Access rules are enforced in the database itself, not just the app: row-level security on every table, and cross-company references are impossible by schema.
Salary is revoked from the app's database role outright and released only through a call that records who read it, never the amount. SIN and banking details are never stored, and every sensitive action lands in an append-only audit log.
No. The four modules are one system, but you can start where it hurts most; the directory underneath is shared, so each module you turn on feeds the others from day one.
