Standard or Enterprise, based on where you are today.
cifraHQ Standard is the P4 Books successor for SMB: self-serve, efficient, covers 90% of Panama cases. cifraHQ Enterprise adds multi-entity, advanced commissions, dual audit trail, SOC 2, and a complete OpenAPI. Same brand DNA, two different contracts.
The end-to-end matrix
Standard and Enterprise share the accounting, inventory, purchasing, and sales core. The matrix below summarizes where Enterprise adds capability and controls. If you operate a single Panama entity with no commissions team, Standard is almost certainly enough; if you run a multi-country group, structured commissions, or require SOC 2 evidence, Enterprise is the right ground.
| Standard | Enterprise | |
|---|---|---|
| Multi-entity | Single entity per subscription Multiple entities require separate subscriptions with no consolidation between them. | Party hierarchy, intercompany mirror postings (v1), consolidation elimination (v1.5) |
| Commissions | Not included — external or manual calculation | Rule engine with preview mode, multi-tier quotas with accelerators, automatic clawback |
| Landed cost | Manual cost adjustment per receipt | 5 allocation methods (value, weight, volume, quantity, custom), multi-receipt |
| Audit trail | Application events in the audit table Enough for operational traceability. | Dual audit: application events + SQL-level database log With app_rw principal denied UPDATE/DELETE on AuditEvents. |
| SOC 2 | Not applicable to this edition | SOC 2 Type I in progress with independent auditor Quarterly report with CC6.1, CC7.2, CC8.1, A1.2, P1/P3 control excerpts. |
| API | REST scoped to Standard modules, no public webhooks | Full OpenAPI 3.0, HMAC-signed webhooks, auto-save with RowVersion |
| Support SLA | Best-effort, email support during business hours | 99.9% monthly availability with tiered credits, quarterly report See /en/security/sla for credit table. |
Concrete signals that you crossed the line
The decision is rarely "Standard no longer fits" on the day you sign. The signal usually shows up months earlier, typically in one of these moments. If you recognize two or more, it is worth at least a conversation with sales to map the upgrade against your calendar.
- When you cross three countries. The first foreign entity is manageable on Standard. The third or fourth, each with its own tax stack and its own close, demands real consolidation and party hierarchy.
- When the CFO asks for a guaranteed 3-day close. Manual close on top of application events is auditable but not deterministic. A formal state machine with
HardCloseenforced in the database is what turns "we hope to close on time" into an internal SLA. - When sales pushes for tiered commissions. A commissions spreadsheet grows until someone breaks it. If the sales leadership is asking for multi-tier quotas with accelerators, territory splits, or automatic clawback, the rule engine with preview mode pays back more than its incremental cost on the first cycle.
- When procurement demands SOC 2 evidence. A large enterprise customer asks for the SOC 2 report or pen test summary. Standard does not produce that evidence; Enterprise does — and the quarterly report is designed exactly for that conversation.
- When your internal integrator needs a public API. If you are already writing automations against the ERP, or if a partner portal or field system must integrate, the full
/swaggerwith signed webhooks saves weeks over a fragile scrape or a nightly export.
From Standard to Enterprise, one way
The Standard-to-Enterprise migration is deliberate, documented, and one-directional. Standard remains a live product for SMB; Enterprise is not "Standard with more features turned on" — it is a different schema with physical isolation, party hierarchy, and additional modules. The migration bridge respects that difference.
- Canonical export from Standard. A structured export of the Standard tenant: chart of accounts, opening balances, customer and supplier masters, valued inventory, document history within the open period. Documented format, runnable from the admin console.
- Assisted import into Enterprise. The import runs against a freshly provisioned Enterprise database — never on top of an existing Enterprise — with referential-integrity validation and total reconciliation. Opening balances land as an identified journal, not as an anonymous bulk post.
- Open history, not closed. Closed periods in Standard stay in Standard as a reference archive. Enterprise starts from a clean cut-over, with the current period open and the historical record accessible for reports if needed, without mixing the two source-of-truth systems.
- One direction only. There is no Enterprise → Standard bridge. Once the group operates with party hierarchy, dual audit trail, and intercompany, there is no non-destructive way to collapse it back to the Standard schema. The decision is made with that clarity up front.
- Coexistence window. During cut-over we agree on a controlled window in which Standard goes read-only while Enterprise takes live operation. Sales and Customer Success work the calendar with your close team.
Map your case to the right edition.
A 45-minute session with sales. We walk through your operation, your multi-entity roadmap, and the real signal that would trigger the upgrade. No pressure.