Multi-Branch Workspaces
Scale across multiple Philippine corporations, RDO branch locations, and franchise outlets from a single consolidated dashboard. Guarantee strict series isolation, dedicated TINs, and partitioned API credentials with zero data leakage.
sp_live_9f82d1c0••••••••Enterprise Multi-Tenancy Architecture
Say goodbye to cross-store invoice collision. Every branch operates with its own legal identity and sequence counter while headquarters maintains executive visibility.
Collision-Free Series Numbering
Branch A (CMP-001) and Branch B (CMP-002) each start at serial #1 and advance independently. Branches will never collide, skip numbers, or cross-contaminate audit records.
Custom Legal Entities & RDOs
Different RDOs demand different TIN suffixes (e.g. 000, 001, 002) and registered business addresses. Configure distinct company headers, authorized signatories, and tax regimes per workspace.
Partitioned API Keys
Provision scoped API keys for each store location. A compromised key at an individual branch only impacts that specific store and can be revoked instantly without disrupting company headquarters.
Workspace-Scoped Webhooks
Event notifications (invoice.created, invoice.paid) only dispatch to endpoints registered for that specific branch, keeping internal ERP listeners cleanly isolated.
Role-Based Access Control
Assign branch managers to their specific location while giving company finance officers and auditors cross-workspace read access to generate consolidated group tax returns.
Independent Quota Ledgers
Monitor invoice consumption independently per store. Low-volume pilot branches remain on the Starter tier (500 docs/mo) while flagship branches utilize Growth or Scale quotas.
Consolidated Oversight with Local Autonomy
Switch between branches in one click using the built-in Workspace Switcher in your dashboard or pass the X-Workspace-Id header in API requests.
Workspace Multi-Tenancy FAQ
How multi-branch registration works under Philippine tax laws.
Can one account manage separate legal corporate entities with different 9-digit TINs?
Yes. Each workspace is a self-contained entity with its own legal corporate name, TIN, RDO jurisdiction, authorized signatory, invoice prefix, and independent 9-digit sequence counter.
How does API authentication specify the target branch?
You can authenticate with a branch-specific API key, or provide the X-Workspace-Id: CMP-002 header in your HTTP requests. The API router automatically directs invoices, series generation, and webhook broadcasts to that workspace.
Ready to Unify Your Multi-Branch Invoicing?
Set up your headquarters and branch workspaces in minutes.