Embed accounting in your product
Start with the API or production Embedded UI, configure App Connect once, and ship ledger-backed workflows with a clear path to production.
API · UI · APP CONNECT · MCPChoose your starting point
Reference the contract, mount production components, or follow a complete implementation path.
Reference
API Reference
OpenAPI explorer, journal primitives, webhooks, OAuth, and MCP tools.
OpenAPI referenceComponents
Embedded UI
Published npm packages for accounts, journals, banking, reconciliation, and reports.
Embed accounting UIWalkthroughs
Integration guides
Working paths for journals, billing, marketplaces, expenses, and white-label setup.
Choose a guideSystem design
Architecture
Write path, tenant isolation, webhooks, and deployment models for technical review.
Review architectureFrom package to first screen
Follow one integration path, then add only the accounting surfaces your product needs.
Production packages
Operational accounting
Accounting UI
@paprel/embed-accountingProduction components and typed resources for the daily ledger workflow.
- Accounts
- Journals
- Banking
- Transactions
- Reconciliation
Financial statements
Reporting UI
@paprel/embed-reportsLedger-derived statements that stay inside your application shell.
- Trial balance
- Balance sheet
- Income statement
- Cash flow
- General ledger
Integration walkthroughs
Authenticate, post a journal, then map billing, marketplace, expense, or white-label flows onto the same ledger.
Post Your First Journal in 5 Minutes
The fastest path to value in Paprel — get sandbox keys, authenticate, post a balanced double-entry journal over REST, and read it back from the ledger.
Authentication: Client Credentials to Access Token
How Paprel API authentication works — choose App Connect or API credentials, exchange credentials for a short-lived OAuth 2.0 access token, and keep every secret off the frontend.
Build Embedded Accounting in 20 Minutes
A guided walkthrough from sandbox keys to a live P&L — extend the chart of accounts, invoice a customer, record a payment, and read the ledger entries back over the API.
SaaS Billing to Accounting: Subscriptions and Revenue
Wire a recurring subscription into real books — a recurring invoice that posts revenue, payment recording, a manual deferred-revenue schedule for annual prepay, and journals you can read back.
What stays true in every deploy
Isolation, reliable writes, and deployment models — the engineering write-ups behind the architecture map.
Tenancy, Isolation, and the Ledger Core
How Paprel is layered — company-per-tenant isolation enforced at the data layer, an append-only double-entry ledger that rejects unbalanced postings, a workflow layer that compiles documents into journals, and reports derived live from the same rows.
Webhooks, Idempotency, and Reliable Writes
How Paprel's write path stays safe under retries — idempotent writes, balanced-or-rejected validation before the ledger, signed webhook delivery, and recovery from authoritative accounting data.
Deployment Models: Brand and Hosting
How Paprel ships — two independent choices, whose brand fronts the product and where it runs — with shared hosting and Paprel-visible delivery as the defaults, and what stays identical whichever you pick.
API v1.1.0 View changelog
Evaluate in sandbox
Post a journal before you commit a design
Self-serve keys, no billing. The 5-minute guide is the shortest proof; the OpenAPI spec is the contract.