01
99.9%
Uptime target — measured on newledger.io
Embedded accounting API
The accounting API platforms build on Paprel.
A programmable double-entry ledger, signed webhooks, and an MCP surface for AI agents — wired into your product in days. The same primitives that run newledger.io today.
- Ship in days, not months
- Skip the ledger rebuild
- Focus engineers on product, not plumbing
paprel ▸ accounting · stack
live- 01Product events and API orchestration
- 02Double-entry ledger and sub-ledgers
- 03Native accounting workflows
- 04Reporting, permissions, and audit controls
Spec sheet
What you wire up in the first two weeks.
Four primitives every integration hits in its first sandbox. Each maps to a real endpoint, a signed event, and a row in the audit log.
POST /journals · idempotent
Post balanced double-entry journals over REST or SDK. Idempotency keys deduplicate retries within a 30-day window; replays return the original 201.
Webhooks v1 · signed + replayable
Every state change emits a signed webhook with a content hash. Replay any event from the last 30 days through the dashboard or API.
OAuth 2.0 / 2.1 · scoped tokens
Standard OAuth 2.0 and 2.1 authorization flows with PKCE. Tenant-scoped tokens with per-route grants — same model powers RBAC, MCP, and machine-to-machine clients.
Sandbox tenant · 30-day window
Real OpenAPI client, real signed events, isolated data. Promote to production by swapping a token — same wire format, same primitives.
embedded.relatedPath.eyebrow
embedded.relatedPath.title
embedded.relatedPath.description
02
US · EU · APAC
3 regions, tenant-pinned data residency
03
30-day
Idempotency + signed webhook replay window
04
7 years
Signed audit retention, CSV/JSON exportable
Category Definition
Defining embedded accounting
Embedded accounting is not just invoicing inside an app. It is a system of record built into a software product, where ledger logic, workflows, reporting, permissions, and audit history operate as native platform capabilities.
Best fit for
SaaS platforms turning workflow products into financial systems of record
Fintech products extending from money movement into accounting operations
Marketplaces and vertical software products with structured financial activity
Accounting-led platforms that need APIs, controls, and shared client workspaces
Not the primary fit
Freelancers looking for a lightweight standalone bookkeeping app
SMBs shopping for a generic accounting UI without platform requirements
Teams that only need invoicing or expense capture without a ledger-backed model
Products that do not need accounting controls, reporting integrity, or API extensibility
Build the ledger, or build the product.
A production-grade double-entry core takes a senior team 8–18 months and never ships finished. Below is what you delegate the moment you adopt Paprel.
Building it yourself vs. shipping on Paprel primitives
| Architectural Capability | Build In-House (8-18 Months) | Paprel Infrastructure (2-4 Weeks) |
|---|---|---|
| Core Accounting Ledger | Complex debit/credit logic, edge case handling, and ledger integrity | Production-ready double-entry foundations |
| Regulatory Workflows | Custom engineering for journals, adjustments, and audit controls | Prebuilt workflows designed for compliance |
| Financial Integrity | Manual effort to reconcile product activity with financial records | Programmatic synchronization with a shared source of truth |
| System Longevity | Technical debt accrual and continuous maintenance overhead | Scalable architecture that evolves with the industry |
| Engineering Cost | Diverts resources from your core product value | Ship accounting features faster with zero infrastructure drag |
Ledger plumbing is a solved problem. Spend your engineers on the surfaces, workflows, and data products only you can build.
The primitives, by name.
Double-entry engine
POST a journal with balanced debits and credits. The engine rejects unbalanced postings, deduplicates by idempotency key, and writes to an append-only ledger. Multi-entity and multi-currency are built in, not modules.
- Append-only ledger
- Multi-entity, multi-currency
- Idempotent POST
- FX revaluation
Workflow primitives
Invoicing, expense, and reconciliation flows wired to the ledger. Drafts, approvals, and posting are first-class API states — not UI conventions.
- Drafts → approved → posted
- Reviewer + approver roles
- Programmatic reconciliation
- Sub-ledger reads
API + webhooks + MCP
One OpenAPI spec generates clients in any language. OAuth 2.0 / 2.1 with PKCE for auth. Signed webhooks replay for 30 days. MCP surface lets AI agents post journals and read balances with scoped tokens.
- OpenAPI 3.1 spec
- OAuth 2.0 / 2.1 · PKCE
- Signed webhooks · replayable
- MCP tool surface
Tenant-pinned regions
Tenant data lives in one of US, EU, or APAC — no cross-region replication. Switch on a per-tenant basis at provisioning time.
- US · EU · APAC
- Per-tenant residency
- Managed cloud today
- Private VPC on roadmap
Signed audit log
Every mutation produces a content-hashed envelope: actor, action, before/after, signature. Queryable by entity, by actor, by time window. Seven-year retention, exportable.
- Content-hashed envelopes
- RBAC scoped tokens
- 7-year retention
- CSV / JSON export
Chart of accounts
Multi-entity COA with parent-child accounts, custom dimensions, and per-tenant overrides. Map your application's event types to ledger accounts once, post journals against them forever.
- Parent · child · dimension
- Per-tenant overrides
- Event-to-account mapping
- Trial-balance ready
AP/AR + accounting close
Receivables and payables as first-class ledger objects. Aging reports, application of receipts and payments, accruals, reversals, period locking, and close checklists — all queryable through the same API.
- AR · AP · aging buckets
- Receipt + payment application
- Period lock + reopen
- Close checklist via API
Live reports
P&L, balance sheet, and trial balance read from the same primitives — no separate analytics DB to keep in sync. Stream to the API, embed in your UI, or export as CSV/JSON.
- P&L · balance sheet · trial balance
- Same source as the ledger
- GET endpoints, cached
- CSV / JSON export
Where Embedded Accounting Fits Best
The same primitives — programmable ledger, signed events, MCP surface — adapt to the shape of your business. A few of the patterns we see most.
Sector Profile
Fintech Platforms
Move beyond money movement and give business customers accounting tools that reflect what happens in their accounts and products.
Common use cases
Business transaction ledgering
In-app reporting and statements
Cash movement tied to accounting entries
Operational finance visibility
Why it matters
What ships
The product changes teams in this segment make once the accounting layer is wired in.
Outcomes
Deeper product utility
Stronger retention
Better financial visibility
New revenue opportunities
Design partner program
Build with us, while we build the standard.
Paprel is still in design-partner mode. We're working hand-in-hand with a small group of fintechs, vertical SaaS, and AI-native platforms shaping the primitives. Architecture sessions, direct line to the founders, pricing that reflects the partnership.
- Direct line to the engineers building the ledger
- Architecture review tailored to your platform
- Early access to MCP tooling and white-label primitives
- Pricing that reflects the partnership, not the list
What partners get
- 48h
- Architecture review turnaround
- 1:1
- Direct founder channel
- MCP
- Early-access AI tool surface
- White-label
- Co-design of partner-facing UI
Three layers. One source of truth.
Your application emits events. Paprel turns them into signed, validated, double-entry journals. Your read surfaces — reports, exports, audit trails — pull from the same ledger.
Product Surface
your trust zoneYour application experience
serviceOrders
serviceWallets
serviceBilling
producerCustom events
paprel ▸ core
signed · isolated tenant serviceEvent ingestREST · SDK · MCP
serviceSchema validatorJSON-schema · COA mapping
engineDouble-entry postingmulti-entity · multi-currency · FX
cacheIdempotencyreplay-safe · 30-day window
storeAudit logsigned · 7yr retention
storeImmutable ledgerappend-only · double-entry
Platform Outputs
live · signedWhat ships on top
reportP&L
reportBalance sheet
reportTrial balance
exportGL export
streamAudit trail
Same primitives running in production on newledger.io today.
SOC 2Type II roadmap
ISO 27001Targeted roadmap
AuthOAuth 2.0 / 2.1
Uptime99.9% on newledger.io
RegionsUS · EU · APAC
Audit7yr · CSV/JSON
Five lines to ship
Embed accounting with one API call.
Type-safe SDKs, language-native clients, and an MCP tool for AI agents. Same journal API across every surface.
curl https://api.paprel.com/api/v1/accounting/journals \
-H "authorization: Bearer $PAPREL_KEY" \
-H "x-data-signature: $(paprel-sign $PAPREL_SIGNING_KEY)" \
-H "content-type: application/json" \
-d '{
"currency": "USD",
"date": "2026-05-16",
"description": "Stripe payout · acct_1Q3aBcd",
"reference": "po_1Q3aBcd",
"lines": [
{ "account_code": "1010", "account_name": "Cash · Operating", "debit": "1240.00" },
{ "account_code": "5300", "account_name": "Payment Processing Fees", "debit": "35.50" },
{ "account_code": "4000", "account_name": "Revenue", "credit": "1275.50" }
],
"meta_data": {
"root_entity_type": "stripe_payout",
"root_entity_id": "po_1Q3aBcd"
},
"posted": true
}'MCP-Native · Live today
The first accounting API that AI agents can call safely.
Paprel ships an MCP tool surface so AI agents can post journals, query balances, and propose corrections — through the same signed, audited, double-entry primitives your engineers use. No spreadsheet exports, no jailbroken admin seats.
- Scoped tools — agents only see what their role can touch.
- Draft actions — every agent edit lands as a pending journal, never auto-posted.
- Full audit trail — who, what, when, signed.
Already shipping. These aren't mockups — the same MCP surface is live in production on newledger.io, our reference accounting platform built on Paprel primitives. What you see below is real.
No vendor lock-in — by design.
Switching costs are an architectural choice. Paprel was built to be exportable, replayable, and inspectable end-to-end. Here's how that holds in practice.
01
Standard GL export
Full general ledger exportable as standard CSV / JSON / OFX — at any time, for any period, no engineering review. Goes anywhere accounting goes.
02
Replayable webhook stream
Every journal posted emits a signed webhook event. Replay the full history into your own warehouse or a successor system — bit-for-bit.
03
Immutable audit log
Every action — human or agent — captured with a content hash and a cryptographic signature. Inspectable forever. Yours, not ours.
Implementation Path
How Platforms Roll Out Embedded Accounting
Most teams do not start with a full accounting suite. They map product events, validate the ledger model in sandbox, and expand from the first production workflow.
1
1-2 days
Map Product to Accounting
Define how platform activity, customer workflows, and financial events should map into the accounting model.
2
2-3 days
Choose Integration Model
Use embedded UI for speed, go headless for maximum control, or combine both where it makes sense.
3
3-5 days
Validate In Sandbox
Test workflows, ledger behavior, reporting outputs, and operational edge cases before rollout.
4
1 day
Launch And Expand
Ship the first embedded accounting experience, then extend into deeper workflows and more customer segments over time.
Roadmap
Where the platform is heading.
Honest about what's live, what's coming, and what's planned. Design partners get to shape what's in the Next column.
Now
- Programmable ledger + journal API
- Multi-entity, multi-currency
- Signed webhooks + replay
- OpenAPI spec — generate SDKs in any language
- MCP tool surface for AI agents
- Hosted reports — P&L, balance sheet, trial balance
- US · EU · APAC regions
Next
- SOC 2 Type II certification
- ISO 27001 certification
- First-party reconciliation engine
Later
- Embedded white-label UI kit
- Expanded regional tax + filing packs
Where This Goes Next
Embedded accounting, AI agents, and MCP
Once the accounting layer is in place, teams can extend it into governed workflows, AI-agent interactions, and MCP-driven accounting operations.
Foundation
AI-Ready Embedded Accounting
Start with the infrastructure view: what makes embedded accounting ready for AI agents, governed workflows, and future MCP-style interactions.
Read article
Trust Layer
Why AI Agents Need Accounting Infrastructure
See why permissions, accounting structure, and reviewable workflows matter before teams let AI agents operate inside finance processes.
Read article
Interface Layer
MCP for Embedded Accounting Infrastructure
Understand how MCP can expose accounting tools, context, and draft actions through a governed interface instead of scattered automation.
Read article
Launch Story
Paprel MCP for AI Agents and Accounting Workflows
Explore the release story, including scoped access, draft invoice and expense actions, journal visibility, and reviewable agent activity.
Read article
Skip the ledger. Build the product.
Talk to the engineers building Paprel. Architecture review in 48 hours, sandbox token same week. The same primitives running newledger.io today.
For CTOs, CPOs, and platform engineers evaluating embedded accounting.