Skip to content
Invarent
PortalStart building

One accounting backend from first journal to year-end.

Invarent combines the accounting system, control layer, developer platform, and customer delivery surfaces required to make accounting a durable part of your product.

Explore the API Create a workspace
  1. Source eventinvoice.approvedStable identity and exact amount
  2. Accounting policyRevenue rule appliedPeriod, chart, dimensions, authority
  3. Balanced effectJournal posted atomicallyDebit equals credit · history retained
  4. Your productVerified state returnedBalances, reports, audit, webhook

Illustrative flow · not customer data

The source-derived production contract exposes 292 operations across 192 paths. The feature map below describes implemented API and platform surfaces; it does not imply independent certification or a customer outcome that has not been verified.

Complete embedded accounting feature map

Ledger and accounting foundation

The invariant core every other accounting workflow depends on.

  • Tenants, legal entities, books, currencies, charts, dimensions, and fiscal periods
  • Balanced journals, submission, separate approval, atomic posting, reversal, and additive correction
  • General-ledger detail, trial balance, P&L, balance sheet, and report snapshots
  • Exact decimals, stable external identity, request hashes, and atomic idempotency

Accounts receivable

Customer balances and cash application on the same ledger chain.

  • Customers, invoices, receipts, payments, cash applications, and AR aging
  • Source-linked lifecycle state and accounting effects
  • Revenue schedules, deferrals, recognition state, and exception handling
  • Customer-facing balance and statement data for embedded experiences

Accounts payable and spend

Payables, approvals, disbursement state, and expense evidence.

  • Vendors, bills, purchase orders, payment runs, payments, and AP aging
  • Content-bound approvals and actor-separation controls
  • Documents, receipts, exception queues, and source evidence
  • Accruals, prepaid schedules, fixed assets, and depreciation state

Cash, banking, and reconciliation

Independent proof that source activity, subledgers, books, and cash agree.

  • Bank accounts, imported bank transactions, connection state, and sync workflows
  • Source-to-subledger, subledger-to-ledger, and ledger-to-external reconciliation
  • Matching state, exceptions, evidence, and durable retry behavior
  • Cash receipts, applications, and reportable cash position

Close, reporting, tax, and year-end

Operate the accounting calendar instead of exporting disconnected reports.

  • Soft close, hard close, reopen controls, close cycles, and accountable tasks
  • Financial statements, report runs, immutable snapshots, and certification records
  • Tax packages, tax returns, filing gates, access evidence, and year-end workflows
  • Multi-entity, multi-book, multi-currency, and consolidation-oriented records

Job cost and government contracting

Extend the accounting system into demanding operating models without forking it.

  • Jobs, projects, contracts, CLINs, WBS nodes, timesheets, and job-cost summaries
  • Cost pools, allocation bases, indirect rates, funding, billing, and evidence
  • Location, technician, department, service-line, and custom dimensions
  • Industry policy records on the same immutable ledger foundation

Controls, audit, and bounded automation

Automation can move quickly without silently acquiring accounting authority.

  • Accounting policies, control definitions, approval grants, scopes, and materiality
  • Append-only audit events with actor, source, content, request, and session context
  • AI suggestions that require explicit approve or reject actions
  • Tenant isolation, runtime roles, RLS, negative-access tests, and recovery evidence

Developer and delivery platform

Everything required to make the accounting backend usable by a product team.

  • Self-serve provisioning, resettable sandboxes, and API-key lifecycle
  • OAuth 2.0 client credentials, TypeScript and Python SDKs, OpenAPI, and typed errors
  • Ed25519-signed webhooks, DNS revalidation, retry, dead letter, and replay
  • Usage metering, account management, billing surfaces, portals, support, and administration

The public contract is the detailed feature inventory.

Hosted documentation

Read authentication, quickstart, coverage, SDK, and lifecycle guidance.

Open the docs →

OpenAPI 3.1 contract

Inspect the exact production paths, methods, schemas, and error families.

Download OpenAPI →

Trust boundary

Review tested technical controls and the conclusions Invarent does not claim.

Read trust evidence →
See how the developer platform fits together

Start with one controlled accounting loop.

Start with the sandbox

Create a sandbox, submit a source-linked financial event, and verify its policy, approval, posting, report, audit, and webhook records before expanding the integration.

Create a workspace Explore the API