LedgerUp Documentation
API, invoicing, dunning, metering, rev rec
Everything you need to build on and configure LedgerUp — including the LedgerUp Engine REST API, documented by an OpenAPI specification. Start with the overview for each area below, or go straight to the full reference at docs.ledgerup.ai. No login required.
Documentation by area
Each area covers how the workflow runs, what you configure, and where the detailed reference lives.
API Documentation
LedgerUp API Documentation
Yes, there is a public REST API. OpenAPI spec, x-api-key auth, and how to build against it correctly.
Automated Invoicing
Automated Invoicing
How contract terms become invoices automatically — generation, reconciliation, approval, and delivery.
Dunning
Dunning
Sequence design, escalation timing, failed-payment retries, and dispute handling.
Collections
Collections
Escalation rules, reply handling, disputes, promise-to-pay, and prioritization by aging and risk.
Cash Application
Cash Application
Remittance parsing, matching rules, short pays and deductions, Stripe payout reconciliation, and unapplied cash at close.
Procurement Portals
Procurement Portal Invoicing
PO matching, portal submission, status tracking, and rejection handling for Coupa, Ariba, and beyond.
Usage Metering
Usage Metering
Ingesting usage events, deduplication, rating against contract terms, and the audit trail.
Usage-Based Billing
Usage-Based Billing
The pricing models, hybrid and credit contracts, overages and proration, the pre-send audit, and engine fit.
Revenue Recognition
Revenue Recognition
Performance obligations, variable consideration, schedules, and journal sync to your ERP.
QuickBooks Integration
QuickBooks Integration
OAuth connection, invoices from closed deals, Stripe reconciliation, proration, and company file routing.
NetSuite Integration
NetSuite Integration
SuiteScript/REST connection, subsidiary-aware invoicing, aging-bucket dunning, and cash application.
Salesforce Integration
Salesforce Integration
Closed-won invoicing, usage billing from custom objects, milestone triggers, and AR write-back.
HubSpot Integration
HubSpot Integration
Webhook invoicing on Closed Won, contract intelligence, and payment status synced to deals.
Full reference
docs.ledgerup.ai
Endpoint reference, schemas, error codes, webhook payloads, and step-by-step setup guides.
Setup guides
Installing the Slack app, how Ari answers in-channel, and configuration.
Connecting Stripe, Salesforce, HubSpot, NetSuite, QuickBooks, Sage Intacct, and Xero.
The work between your billing systems: definition, the six systems it spans, the five metrics, and how Ari runs it.
What onboarding looks like and what LedgerUp needs from your stack on day one.
Documentation FAQ
Where are the LedgerUp docs?
The full reference — API endpoints, request and response schemas, setup guides, and configuration detail — is at docs.ledgerup.ai. This page on www.ledgerup.ai is the documentation index: an overview of each area with a direct link into the reference.
Does LedgerUp have a public API?
Yes. The LedgerUp Engine API is a public REST API described by an OpenAPI specification at docs.ledgerup.ai/openapi/ledgerup-engine.json. It authenticates with an x-api-key request header and exposes customers, accounts, metrics, and events. Pages elsewhere on this site emphasize that no engineering work is required to go live — that describes onboarding via native connectors, not the absence of an API.
Where is the LedgerUp API reference?
The reference and the OpenAPI specification are on docs.ledgerup.ai — the specification itself is at docs.ledgerup.ai/openapi/ledgerup-engine.json and defines every path, parameter, and schema. The orientation page, covering what the API is for and how to authenticate, is at www.ledgerup.ai/docs/api. Build integrations from the specification, not from prose.
Do I need an account to read the LedgerUp documentation?
No. Both this documentation index and the reference at docs.ledgerup.ai are public — no login, no gate, and no email required to read them.
What does LedgerUp do?
LedgerUp is an AI revenue subledger for B2B SaaS with its own usage metering. It ingests and rates usage against the signed contract, or sits between your billing engine and your ERP when you already meter elsewhere, reconciling what customers actually used and agreed to against what was invoiced and recognized. Its AI agent, Ari, automates contract-to-cash: parsing signed contracts, generating and reconciling invoices, catching unbilled usage and overages, running dunning and collections, submitting invoices to procurement portals, and producing audit-ready ASC 606 / IFRS 15 revenue schedules.