Northshore Retail
example subsidiary
- Own ledger & chart of accounts
- Isolated at the data layer
- Own audit history
Multi-entity accounting
Multi-Entity Accounting Embedded In Your Product
Paprel's multi-entity accounting API gives each subsidiary, location, seller, or fund its own ledger, chart of accounts, and reporting — provisioned by API, isolated at the data layer, and accessible from the same workspace.
- Isolated ledger and chart of accounts per company
- Journals looked up by your product IDs
- Workspace switch without leaving the product
- Role-aware access across entities
Each company keeps its own ledger, chart of accounts, and document numbering.
Add A Company Without Ad Hoc Setup
Bring a new legal entity or operating unit into the workspace with structure that reporting and permissions can use from day one — not a spreadsheet of company codes.
Keep Multiple Entities In One Finance Workspace
Teams access each company's books from one product while keeping the underlying ledgers separate. Parallel finance operations no longer require separate accounting-system logins.
Switch Entities Without Losing Context
Move between companies, books, and workflows in the same environment. The team stays oriented while each set of books remains separate.
Report Within Each Company's Books
Hosted P&L, balance-sheet, and operational views stay tied to the same ledger each company writes to. Consolidated statements are outside the current public API contract.
Entity Layer
Isolated Ledgers Your Platform Can Provision
Multi-entity is not another company record in a settings screen. It is isolated books, source-entity journals, and controlled collaboration — the same primitives Paprel uses for every tenant.
Isolated Company Books
Every company gets its own ledger, chart of accounts, and audit history. Isolation is scoped at the data layer, not left to application filters.
API-Provisioned Entities
Create a company with POST /v1/company and the books come with it — ready for journals, documents, and reporting without a separate finance stack.
Workspace Switching
Operators move between entities inside the same product. Finance teams stay oriented without opening a second accounting system.
Company-Scoped Reporting
Keep each company's financial reports tied to the isolated ledger and chart of accounts that produced them.
Journals By Your IDs
Look up the ledger impact of an order, payout, or invoice with GET /v1/accounting/journals/for-entity using the IDs your product already owns.
Role-Aware Collaboration
Give operators access to the books they run and keep finance leaders visible across the structure — without sharing credentials across entities.
Tenancy model
A Company Is The Boundary
Provision connected companies with their own books. Configure tenant permissions and validate access boundaries for your deployment.
Isolation is documented in how a company is the boundary. Source-entity lookup uses the Journal API. For destination-app limits, see the QuickBooks API alternative and the marketplace accounting guide.
Your platform
one tenant per customer · OAuth-scoped tokens
Harbor Franchise Co
example operating unit
- Own document numbering
- Separate reporting books
- Scoped staff access
Atlas Seller Books
example marketplace seller
- Journals tied to your IDs
- Settlement-ready history
- Accessible in one workspace
Illustrative operating units — not customer case studies.
Isolation sits below application code. Every journal, invoice, and report is company-scoped at the data layer.
How it ships
From Provisioning To Company Review
Platforms do not need a second accounting product for the second entity. Provision the company, post against your own IDs, and keep review inside the product.
01
Provision The Company
Create the entity with POST /v1/company. Paprel stands up the ledger, a default chart of accounts, and document numbering in the same call.
02
Keep The Books Isolated
Each company is a hard boundary. Journals, invoices, expenses, and reports stay inside that company's books.
03
Post Against Your IDs
Tie journals to the order, payout, property, or loan ID your product already stores. Retrieve the accounting trail later without a mapping spreadsheet.
04
Switch And Review Each Company
Operators switch between company workspaces for day-to-day work while each ledger and its reports remain separate.
Where it lands
The Same Entity Model Across Platform Types
Whether you serve operators, sellers, property managers, or funds, the pattern is the same: one company boundary, isolated books, journals keyed to your records.
Vertical SaaS
Franchises, locations, and client entities with isolated books inside the industry workflow.
Vertical SaaS accounting
Marketplaces
Seller books, settlement journals, and payout trails keyed to your order and merchant IDs.
Marketplace seller books
Property Management
Owners, LLCs, and portfolios as separate books that managers access from one workspace.
Property management books
Lending & Funds
Funds, SPVs, and lending entities as isolated ledgers with audit-ready history.
Lending and fund ledgers
Common Multi-Entity Questions
What is multi-entity accounting in an embedded product?
Multi-entity accounting keeps a separate set of books for each legal entity or operating unit — own ledger, chart of accounts, and reporting — while customers still work inside one product. Paprel exposes that as an API: provision a company, isolate reads and writes at the data layer, and look up journals by the IDs your product already stores.
Can my platform offer multi-entity books to customers with several legal entities or operating units?
Yes. Each company is provisioned with its own ledger, chart of accounts, and document numbering. Your product can create those companies over the API and keep day-to-day work inside the same embedded accounting layer.
How is isolation enforced between entities?
Company-scoped access separates accounting entities. Confirm the enforcement design and privileged access paths for your deployment.
Can I look up journals using IDs from my own product?
Yes. GET /v1/accounting/journals/for-entity takes the entity_type and entity_id your product already stores — an order, payout, invoice, or loan — and returns the balanced journal behind it.
How do permissions work across companies?
Access is role-aware and company-scoped. Operators can work inside the entities they run, while finance leaders keep visibility across the structure without sharing a single set of credentials.
Does reporting still hold up as the structure grows?
Reports stay on the same ledger each company writes to and are reviewed within that company's books. Formal consolidation, intercompany eliminations, and consolidated financial statements are not part of the current public API contract.
Adjacent modules
What Teams Wire Next
Chart Of Accounts
Each company starts with its own account structure and can extend it as the books grow.
Financial Reports
P&L, balance sheet, and trial balance from the same ledger each entity posts to.
Team Permissions
Scoped roles so operators see their books and finance still reviews across entities.
Embed this capability
Everything on this page is an API call away
These workflows ship inside your product through the same endpoints, signed webhooks, and MCP tools proven in production today. Sandbox keys are self-serve — post a journal before you talk to anyone.
POST /v1/company OpenAPI 3.1
{
"company_name": "Northshore Retail Ltd",
"company_signature": "…",
"company_type": "…",
"currency_id": "…",
"contact_email": "finance@northshore.example"
}- POST
/v1/company - GET
/v1/company/list - GET
/v1/accounting/journals/for-entity
Live paths from the OpenAPI spec — same wire format in sandbox and production.
Evaluate Paprel
Ready To Embed Multi-Entity Books?
Talk to Paprel about company provisioning, isolated ledgers, and journals keyed to the records your platform already owns.
API-First Delivery
Audit-Ready Controls
Sandbox And Guided Rollout