PrimeForce / Plans
Scoped to your company, not picked off a shelf.
A plan sets hard limits on employees, users and branches, and decides which modules you are entitled to. Both are enforced by the software.
How plans work
Enforcement is not a billing exercise. Every request is checked against your plan before it reaches any data, and a module you are not entitled to is refused by the API — not merely hidden from the menu.
2 Password change due? middleware
3 Has permission? Module.Sub.Verb
4 Module in your plan? entitlement
5 Own record? ownership
6 Payload valid? validation
any failure → 403, logged
Scoped per company
Headcount, user seats, branches and the module set are agreed per company and written into your plan. Nothing is bundled that you will not use.
Two independent checks
Permission asks whether a user may do something. Entitlement asks whether your plan includes it at all. Both must pass — an administrator with every permission still cannot reach a module the plan does not cover.
Caps are counted, not trusted
Creating a user or an employee counts your current total against the plan limit first and refuses at the ceiling. No limit means unlimited.
Dependencies are enforced
Modules declare prerequisites — gratuity and provident fund require payroll configuration — so a plan cannot be assembled into a state that does not work.
Trials are first-class
Every company carries its own subscription status, start date, end date and trial end date. A trial is a state the software understands, not a note in a spreadsheet.
Tell us your headcount and we'll quote.
Pricing depends on headcount, which modules you need and whether you want us to migrate opening balances. One call is usually enough to scope it.