The entity register
One entity and one cost center per employee per period. A transfer is an end date in one and a start date in the other.
Every legal entity in your group, in one payroll register
Muntin is a register, not a payroll engine. €1,290 a month, flat, with every entity, user and endpoint inside it. One legal entity? Close this page.
No card. The rate is on this page.
A fine-tuned classifier proposes each column mapping and an embedding model proposes identity matches across entities. An operator confirms each one, and a period cannot lock with a row unresolved.
Scope
We do not run payroll.
Four things Muntin refuses, then the four it holds.
What's in scope
- 01The entity register. One row per legal entity: number, incorporation date, pay calendar, currency, cost center tree.
- 02Ingestion every period, from every entity, onto one fixed row contract, with the source file kept as it arrived.
- 03The check list and its queue: a person in two entities, a person in none, a leaver still on a register.
- 04The way out: a journal per entity, the headcount webhook, the immutable period record, the API and the sandbox.
What we don't do
- 01We do not run payroll. No PF, ESI or gratuity, no US tax filing. Keka's US pricing page lists payroll inside its plans; we do not.
- 02We are not an HR suite. No hiring, reviews, learning or helpdesk. Your employees never log in.
- 03We are not on the money path. No payment file, no bank connection, no payslip. Four digits of an account, as a matching key, is all we see.
- 04We are not an audit and not advice. The check list is fixed and finite; clearing it is not an opinion about a payroll's lawfulness.
Who it fits
Four reasons to stop reading. Three to keep going.
The refusals come first: they disqualify more readers than they keep.
This is for you if
- ✓Two or more registered entities on different systems, one still closing on a spreadsheet.
- ✓A monthly close where one person reconciles two payroll truths by hand.
- ✓An ERP that wants the journal and the headcount, and a controller who countersigns it.
This is not for you if
- ✕One registered entity, one pay calendar, one chart of accounts. Every cross-entity check is a check against itself.
- ✕Under roughly 150 employees. The flat rate costs more than the spreadsheet it replaces.
- ✕Shopping to replace an HRMS or a payroll provider. We sit above both and need one working.
- ✕Entities that each keep their own chart of accounts. Nothing to reconcile to.
Compare
Keka carries the payroll engine. Muntin carries the entities.
Everything here about Keka is read off its own pricing pages in a browser.
CriterionMuntinKeka
Where a second entity sitsA row in the register on day oneMultiple Legal Entities is listed under Add Ons, not inside a plan
Cost centers and headcount into the ERPA journal per entity and a webhook, base priceAPI & Webhooks is under Add Ons
Statutory payroll and filingNone of it, anywhereUS payroll features are listed inside the plans
Hiring, performance and learningNot built, not plannedIn the product line, sold separately
Setup
Week one is dull and it is the whole job.
Four steps. Nobody enjoys the third.
- 01State the registerSomebody writes down every entity the group actually has. It comes back with one more row than finance expected.
- 02Drop three closed periodsHR exports, bureau CSVs, and the second entity's spreadsheet. Muntin's classifier proposes a column mapping; an operator confirms it.
- 03Clear what the first run findsCross-entity matching surfaces the people counted twice. That backlog is the week of real work.
- 04Issue one ERP service userScoped to posting journals and reading the chart of accounts. It is IT's task, and it arrives last.
What you get
Three screens and one API.
One fixed row contract
entity_id, period_id, employee_id, cost_center, gross, employer_cost, net, currency, pay_date. Whatever the file looked like, it lands here.
Mapping that survives a template change
A header dictionary first, then a fine-tuned classifier reading the header and the values. An operator confirms once per file shape.
Cross-entity identity
Two entities share no payroll ID, so an embedding model proposes candidates from name, date of birth and the last four of the account. Below the threshold the row stays unresolved and the close waits.
The lock
A period does not close while one queue row is unresolved. A correction afterward is a new version, never an edit.
The journal and the endpoints
On lock a journal per entity posts to NetSuite, Sage Intacct, Xero or QuickBooks Online, and the webhook fires.
what you get
The exceptions queue, two days before a close
What the checks found across every entity at once, and what the lock is waiting on.
period 2026-08 · 3 entities · not locked
| exception | entity | owner | state |
|---|---|---|---|
| same person on two registers | operating co, subsidiary | payroll ops | ✓merged, one lineage id |
| cost center not in the chart | subsidiary | finance | ✓added to the chart |
| employer cost outside band | operating co | payroll ops | ✓confirmed, bonus month |
| leaver still on register | subsidiary | HR ops | ✓removed |
| identity match under threshold, 0.71 | subsidiary, bureau file | payroll ops | ✕unresolved, lock held |
A drawn queue, not a customer period. The last row is a proposal nobody confirmed, so nothing is guessed and the close waits.
What we chose
No override. Not for you, not for us.
A period stays open while one exception is unresolved. No button skips it.
An override gets used at six on close day, by whoever is under the most pressure. Two quarters later the reconciliation is optional in practice.
So there is no button. The lock is what makes the period record worth countersigning.
It costs us: one duplicate found late can hold a journal past the deadline, so we staff support for that hour.
Pricing
€1,290a month. The whole group.
Flat per company group, up to 2,500 employees. Entities, users and endpoints are not metered.
- Every registered legal entity, in any number
- Operator and read-only users of every kind, including your auditor
- The REST API, the webhooks and the sandbox
- Onboarding: the register build, the column mapping, the three-period backfill
- The published check list, across every entity, every period
- The journal posting per entity and the headcount webhooks
- The immutable period record, exportable as CSV and JSON on demand
- Up to 2,500 employees on the register
Pin it up
- Thirty days on your own last three closed periods, no card and no call
- Month to month after three months, 30 days' notice, no minimum term
- The price is held for 24 months from signature
Ask for the exclusion list.
Your name and a work email. No call is booked off this form.
We'll come back within one business day with a straight yes or no.