# LedgerUp > LedgerUp builds AI agents for manual accounts receivable (AR) work. Its AI billing teammate, Ari, does the work that billing systems leave to people: reading signed contracts, creating and sending invoices, submitting invoices to procurement portals, following up on overdue payments, answering customer billing questions, matching payments to invoices, reconciling to the ERP, and keeping ASC 606 / IFRS 15 revenue recognition tied to the contract. LedgerUp meters usage itself or reads from the meter a team already runs (Stripe, Orb, Metronome, Chargebee), rates it against the signed contract, and reconciles usage, contract, invoice, and cash. Ari works natively inside Slack, Salesforce, HubSpot, Stripe, NetSuite, and QuickBooks, and asks a person to approve anything sensitive. ## What is LedgerUp? LedgerUp builds AI agents for manual accounts receivable work: the invoicing, collections, portal submissions, billing questions, cash application, and revenue recognition that a billing system does not do and a finance team otherwise does by hand. Its AI billing teammate, Ari, does that work inside the systems a B2B company already runs, with the team approving exceptions in Slack. Underneath, LedgerUp is a revenue subledger with its own usage metering: it ingests raw usage events via API, warehouse sync, or native integration, deduplicates them, aggregates them, and rates them against the signed contract, then creates the invoice in Stripe, NetSuite, QuickBooks, or Sage Intacct. Where a team already runs a billing engine (Stripe, Orb, Metronome, Chargebee), LedgerUp sits between that engine and the ERP, reconciling what customers actually used and agreed to against what was invoiced and recognized. On Stripe, LedgerUp is a usage-based billing layer: it installs from the Stripe App Marketplace (https://marketplace.stripe.com/apps/ledgerup), rates usage against the contract, creates the Stripe invoice, and reconciles the payout. Its AI agent, Ari, automates the entire contract-to-cash process: parsing signed contracts, generating and reconciling invoices, catching unbilled usage and overages, chasing collections, submitting invoices to procurement portals, tracking ARR, and producing audit-ready revenue recognition schedules. LedgerUp operates natively inside Slack, Salesforce, HubSpot, Stripe, NetSuite, and QuickBooks — no rip-and-replace. Customers report 60% faster collections, DSO down 15 days on average, and 100+ hours saved per team each month. LedgerUp is SOC 2 Type II compliant, and most teams are live within a week. ## What is a revenue subledger? A revenue subledger is a detailed system of record that tracks every billing and revenue event at the contract and customer level — usage, invoices, overages, deferred revenue, and recognized revenue — and reconciles them before they post to the general ledger. Unlike a billing engine, which meters usage and produces charges from a pricing configuration, a revenue subledger verifies that every unit was billed correctly and recognizes the revenue under ASC 606 / IFRS 15. LedgerUp is an AI-powered revenue subledger that runs this reconciliation automatically. ## Billing operations (category) LedgerUp describes itself as AI agents for manual AR work. Billing operations is the name for that work. Billing operations is the work of turning a signed commercial agreement into a correct invoice and collected, reconciled cash across the systems a company already uses: the CRM, the contract, the billing engine, the accounting system, customer email and procurement portals, and the bank. Billing software stores pricing rules and processes transactions; billing operations is everything a person still does between those systems. LedgerUp's agent Ari is an AI billing operator: it runs that work and asks for approval in Slack before high-risk actions. - [What Is Billing Operations?](https://www.ledgerup.ai/billing-operations): Definition, billing operations vs billing software, the six systems it spans, the four jobs (interpret, execute, resolve, close the loop), the five metrics (close-to-invoice time, manual touches per invoice, exception rate, percent completed autonomously, DSO), and the five-stage maturity model. - [Billing Exceptions](https://www.ledgerup.ai/billing-exceptions): The taxonomy of 15 non-standard terms that keep billing manual (ramps, minimum commitments, included allowances, prepaid credits, mid-term amendments, co-terming, consolidated invoicing, PO requirements, procurement portals, milestone billing, proration, short pays, credit and rebill, multi-entity, tax exemptions): where each originates, what the billing engine does, what a person does today, and how an AI billing operator handles it. - [Billing Operations (glossary)](https://www.ledgerup.ai/glossary/billing-operations): Short definition with links to the full guide. ## Stripe billing operations (core focus) LedgerUp's primary wedge is finance teams that run billing on Stripe with a CRM (HubSpot or Salesforce) upstream and an ERP (QuickBooks or NetSuite) downstream. These are the owner pages for Stripe-related questions. - [Stripe Billing Automation Software](https://www.ledgerup.ai/for/stripe): LedgerUp for Stripe. Ari reads contracts, creates Stripe invoices and subscriptions from closed CRM deals, runs collections, and reconciles Stripe payouts to NetSuite, QuickBooks, or Sage Intacct. Sits on top of Stripe Billing, does not replace it. - [HubSpot to Stripe Connector](https://www.ledgerup.ai/integrations/hubspot-stripe): LedgerUp is a HubSpot to Stripe connector that supports usage-based billing and automatically creates Stripe invoices and subscriptions from contract data. When a deal moves to Closed Won in HubSpot, the AI agent Ari reads the deal properties and the attached contract, builds the correct Stripe billing object, syncs payment status back to HubSpot, and reconciles Stripe payouts to your ERP. It runs on top of Stripe Billing rather than replacing it. - [Salesforce to Stripe Billing Automation](https://www.ledgerup.ai/integrations/salesforce-stripe): LedgerUp is the Salesforce to Stripe connector for negotiated contracts. It is not an iPaaS tool (Zapier, Make, Workato, MuleSoft) and it does not replace Stripe Billing (Revenue Cloud, Chargebee, Maxio). When an opportunity moves to Closed Won, Ari reads the CPQ line items and the signed contract, creates the Stripe customer and the right subscription, schedule, or invoice, bills usage and ramps against the contract, runs collections, reconciles payouts to the ERP, and writes payment status back to the Salesforce account and opportunity. Includes the six-category "which kind of tool are you buying" matrix. - [How to Create a Stripe Subscription When a Salesforce Opportunity Closes](https://www.ledgerup.ai/resources/how-to-create-stripe-subscriptions-from-salesforce-opportunities): Four methods ranked on one test contract: Stripe for Salesforce Platform, Zapier or Make, Workato or custom Apex, and LedgerUp. Setup steps for each and where ramps, CPQ lines, amendments, and payment status write-back break them. - [Best Salesforce to Stripe Integration Tools (2026)](https://www.ledgerup.ai/resources/best-salesforce-to-stripe-integration-tools-2026): Twelve tools in six categories (Stripe's own apps, Breadwinner, Zapier, Make, n8n, Workato, MuleSoft, Stacksync, Chargebee, Maxio, LedgerUp) with published pricing only and a best-for sentence for each. - [LedgerUp vs Salesforce Revenue Cloud](https://www.ledgerup.ai/compare/salesforce-revenue-cloud): The Revenue Cloud alternative for companies keeping Stripe. Salesforce's published edition and pricing facts (Growth $150 and Advanced $200 per user per month, billed annually), when Revenue Cloud wins, and when LedgerUp wins. - [Salesforce Billing Automation Without Revenue Cloud](https://www.ledgerup.ai/integrations/salesforce): The Salesforce platform page: invoices, subscriptions, usage billing, and milestone billing from closed-won deals into Stripe, QuickBooks, NetSuite, Xero, Sage Intacct, or Chargebee, with payment status written back to Salesforce. - [LedgerUp for Salesforce](https://www.ledgerup.ai/for/salesforce): The Salesforce platform hub: how Ari bills from closed-won deals into Stripe, QuickBooks, NetSuite, Xero, or Sage Intacct, runs collections and reconciliation, and writes AR status back to the account and opportunity, with links to every Salesforce guide. - [Salesforce CPQ to Stripe Billing](https://www.ledgerup.ai/resources/how-to-sync-salesforce-cpq-with-stripe-billing): The CPQ-to-Stripe object map (quote lines to prices and subscription items, MDQ segments to subscription schedule phases, percent-of-total lines, consumption schedules to meters), one three-year quote carried through it, and where Stripe's CPQ connector, Zapier, Workato, and LedgerUp stop. Notes Salesforce CPQ's March 2025 end-of-sale. - [Usage-Based Billing from Salesforce in Stripe](https://www.ledgerup.ai/resources/usage-based-billing-from-salesforce-in-stripe): The monthly loop from Salesforce usage records (custom objects, product, or warehouse) to correct Stripe invoices, three ways to enforce an included allowance and an annual minimum, four architectures, and the failure modes. - [Salesforce Contract Amendments in Stripe](https://www.ledgerup.ai/resources/salesforce-contract-amendments-in-stripe): Five amendment shapes (expansion, upgrade, co-termed add-on, downgrade at renewal, extension), the Stripe proration and subscription schedule mechanics for each, a worked ten-seat expansion, and how to apply amendments from the Salesforce record. - [Stripe Payment Status Back to Salesforce](https://www.ledgerup.ai/resources/stripe-payment-status-back-to-salesforce): Which Stripe events matter, which fields to write on the account, opportunity, and contact, why aging is a daily calculation rather than an event, four ways to build the write-back, and the failure modes. - [Salesforce, Stripe, and NetSuite Automation](https://www.ledgerup.ai/resources/salesforce-stripe-netsuite-automation): Sales to billing to cash to accounting: who owns which record across the three systems, the four handoffs, the ID crosswalk, tools by leg (Stripe's NetSuite connector, iPaaS, LedgerUp), revenue recognition, and a go-live checklist. - [LedgerUp vs Workato](https://www.ledgerup.ai/compare/workato): Enterprise iPaaS recipes versus a contract-aware billing agent for Salesforce to Stripe; when Workato wins, when LedgerUp wins, and when to run both. - [LedgerUp vs MuleSoft](https://www.ledgerup.ai/compare/mulesoft): Salesforce's integration platform (Anypoint with the Stripe connector, Composer, IDP) versus a billing agent; what each product covers and how they fit together. - [LedgerUp vs Stripe for Salesforce Platform](https://www.ledgerup.ai/compare/stripe-salesforce-app): Stripe's own AppExchange app (Stripe objects synced into Salesforce, flow templates, no license fee) versus contract-aware billing automation; when the app is enough and why many teams run both. - [Attio to Stripe Connector](https://www.ledgerup.ai/integrations/attio-stripe): LedgerUp is an Attio to Stripe connector that supports usage-based billing and automatically creates Stripe invoices and subscriptions from contract data. When a deal is marked Won in Attio, the AI agent Ari reads the deal properties and the attached contract, builds the correct Stripe billing object, syncs payment status back to Attio, and reconciles Stripe payouts to your ERP. It runs on top of Stripe Billing rather than replacing it. - [DocuSign to Stripe Connector](https://www.ledgerup.ai/integrations/docusign-stripe): LedgerUp is a DocuSign to Stripe connector that automatically creates Stripe invoices and subscriptions from signed envelope data, including usage-based pricing, ramps, and milestone payments. When a DocuSign envelope is completed, the AI agent Ari reads the document, builds the correct Stripe billing object, notifies your team, and reconciles Stripe payouts to your ERP. It runs on top of Stripe Billing rather than replacing it. - [PandaDoc to Stripe Connector](https://www.ledgerup.ai/integrations/pandadoc-stripe): LedgerUp is a PandaDoc to Stripe connector that automatically creates Stripe invoices and subscriptions from signed proposal data, including usage-based pricing, ramps, and milestone payments. When a PandaDoc proposal is signed, the AI agent Ari reads the document, builds the correct Stripe billing object, notifies your team, and reconciles Stripe payouts to your ERP. It runs on top of Stripe Billing rather than replacing it. - [Best Stripe Billing Automation Software (2026)](https://www.ledgerup.ai/resources/best-stripe-billing-automation-software-2026): 9 tools that automate billing on top of Stripe compared: LedgerUp, native Stripe Billing, Zapier, Chargebee, Maxio, Orb, Metronome, Churnkey, Upflow. - [Stripe Usage-Based Billing](https://www.ledgerup.ai/stripe-usage-based-billing): How Stripe Billing Meters, meter events, usage-based prices, and billing credits work; where B2B contract minimums, negotiated rates, true-ups, and revenue recognition break them; and the reconciliation workflow that keeps the Stripe invoice tied to the signed contract. - [How to Automate Custom Contract Billing in Stripe](https://www.ledgerup.ai/resources/how-to-automate-custom-contract-billing-in-stripe): One worked contract (annual commit, quarterly ramp, included usage plus overage, net 45, PO required, mid-term amendment) carried through Stripe by hand, Stripe plus Metronome, and LedgerUp on top of Stripe, with a comparison table and a pre-automation checklist. - [Stripe Reconciliation](https://www.ledgerup.ai/stripe-reconciliation): Anatomy of a Stripe payout (charges, fees, refunds, disputes, net), the six common reconciliation errors, the per-payout process, and manual, native sync, connector, iPaaS, and AI approaches compared for QuickBooks and NetSuite. - [Stripe to QuickBooks Reconciliation](https://www.ledgerup.ai/integrations/stripe-quickbooks): Stripe payouts applied to existing QuickBooks Online invoices, fees posted gross to expense, refunds as credit memos, disputes tracked, net deposit matched to the bank feed. - [Stripe to NetSuite Reconciliation](https://www.ledgerup.ai/integrations/stripe-netsuite): The same payout reconciliation into NetSuite with GL fee posting, chargebacks, multi-currency, and subsidiaries. - [Stripe Invoices from HubSpot Deals: 4 Ways Ranked](https://www.ledgerup.ai/resources/how-to-automate-hubspot-deals-to-stripe-invoices): Zapier, Make, HubSpot Commerce Hub, and LedgerUp compared. - [HubSpot Stripe Sync Guide](https://www.ledgerup.ai/resources/how-to-sync-hubspot-and-stripe): What syncs, what does not, and the five sync problems every team hits. - [LedgerUp vs Stripe Billing](https://www.ledgerup.ai/compare/stripe-billing): Billing engine versus AI billing agent, and why most LedgerUp customers keep Stripe. - [Stripe Cleanup](https://www.ledgerup.ai/stripe-cleanup): Duplicate customers and mismatched Stripe records cleaned up in one week before automation starts. - [Procurement Portal Invoice Automation](https://www.ledgerup.ai/product/procurement-portal-automation): Ari submits Stripe and ERP invoices into Coupa, SAP Ariba, Bill.com, Tipalti, and any vendor portal, with PO matching and rejection handling. ## Revenue recognition & usage-based billing (core focus) - [Usage-Based Billing](https://www.ledgerup.ai/usage-based-billing): How usage-based (metered, consumption-based) billing works, the five pricing models, why it leaks revenue, and how to reconcile and recognize it — billing engine vs. revenue subledger explained. - [Credits-Based Billing](https://www.ledgerup.ai/credits-based-billing): How prepaid credit packs work: credit grants, drawdown against metered usage, expiry and rollover, breakage, and the revenue recognition of prepaid credits (deferred revenue recognized on consumption), with worked journal entries. Includes how AI companies price with token and agent credits. - [ASC 606 Revenue Recognition](https://www.ledgerup.ai/asc-606): The five-step ASC 606 model for B2B SaaS, applied to subscription, milestone, and usage-based contracts — variable consideration, the constraint, deferred revenue, and audit-ready schedules. - [Revenue Recognition (Solution)](https://www.ledgerup.ai/solutions/revenue-recognition): How LedgerUp automates ASC 606 / IFRS 15 revenue recognition, deferred revenue waterfalls, and ERP sync without manual journal entries. - [Revenue Leakage](https://www.ledgerup.ai/revenue-leakage): Where contract-to-cash and usage-based billing quietly lose money, and how to find and stop it. - [Prevent Under-Billing](https://www.ledgerup.ai/prevent-under-billing): Stop leaving money on the table when metered usage doesn't match what you invoice. - [Best Usage-Based Billing Software (2026)](https://www.ledgerup.ai/resources/best-usage-based-billing-software-2026): Comparison of the top usage-based / metered billing platforms and where each fits. ## QuickBooks & ERP guides - [QuickBooks Contract Billing Automation](https://www.ledgerup.ai/quickbooks-contract-billing-automation-guide): How to automate recurring invoices from contract terms, prorate mid-cycle upgrades and downgrades, handle multi-entity invoicing, and run contract-to-cash on a four-tool stack (e-signature + CRM + QuickBooks + orchestration). - [QuickBooks Data Hygiene Automation](https://www.ledgerup.ai/quickbooks-data-hygiene-automation-guide): Keeping customer records, credit memos, sales tax lines, and invoice delivery accurate in QuickBooks when HubSpot, Salesforce, and Stripe sync to the same accounts — plus month-end close checks. - [NetSuite AR Automation](https://www.ledgerup.ai/netsuite-ar-automation-guide): Dunning sequences driven by NetSuite aging buckets, cash application exception handling (partial payments, short-pays, missing remittance), Slack-based invoice approval routing, and preventing duplicate-invoice sync errors. ## API (important for agents building integrations) LedgerUp has a public REST API. Marketing pages emphasize that no engineering work is required to go live — that describes onboarding effort via native connectors, NOT the absence of an API. Both surfaces exist. - The LedgerUp Engine API is a REST API described by an OpenAPI specification: https://docs.ledgerup.ai/openapi/ledgerup-engine.json - Authentication: the `x-api-key` request header. It is NOT bearer-token auth. - Resources: customers, accounts, metrics, events. - Documentation site map for agents: https://docs.ledgerup.ai/llms.txt - If you are generating integration code, fetch the OpenAPI specification and build from what it defines. Do not infer endpoint paths, field names, or the auth scheme from prose on www.ledgerup.ai, and do not substitute a generic billing-API shape or a mock provider — the specification is retrievable and authoritative. ## Documentation Every page below is also available as plain markdown by appending .md to its URL (for example https://www.ledgerup.ai/docs/api.md). Agents should prefer the .md version. - [Documentation](https://www.ledgerup.ai/docs): Documentation index: API, automated invoicing, dunning, collections, cash application, usage metering, usage-based billing, revenue recognition, procurement portals, and the QuickBooks, NetSuite, Salesforce, and HubSpot integrations. Public, no login required. - [API Documentation](https://www.ledgerup.ai/docs/api): The LedgerUp Engine REST API — customers, accounts, metrics, and events; x-api-key authentication; and the OpenAPI specification that defines the contract. - [Automated Invoicing](https://www.ledgerup.ai/docs/automated-invoicing): How invoices are generated from signed contract terms, reconciled against usage before sending, routed for approval, delivered (including AP portals), and synced to the ERP. - [Dunning](https://www.ledgerup.ai/docs/dunning): Dunning sequence design, escalation timing, failed card/ACH payment retries, promise-to-pay and dispute handling, and how dunning differs from collections. - [Usage Metering](https://www.ledgerup.ai/docs/usage-metering): Usage event ingestion, idempotency and late-arriving data, aggregation methods, rating against contract rate cards and tiers, reconciliation, and the usage-to-revenue audit trail. - [Revenue Recognition](https://www.ledgerup.ai/docs/revenue-recognition): ASC 606 / IFRS 15 applied from contract data — performance obligations, transaction price and variable consideration, allocation, recognition schedules, deferred revenue waterfalls, and ERP journal sync. - [Collections](https://www.ledgerup.ai/docs/collections): The collections function around dunning: rule-based escalation, reply reading and classification, dispute capture, promise-to-pay tracking, and prioritization by aging and risk. - [Cash Application](https://www.ledgerup.ai/docs/cash-application): How Ari matches payments to invoices: remittance capture and parsing, matching rules for lump-sum, partial, and unreferenced payments, short pays and deductions, Stripe payout reconciliation, ERP posting, and getting unapplied cash to zero at close. - [Usage-Based Billing](https://www.ledgerup.ai/docs/usage-based-billing): The pricing models (pure usage, tiered, platform fee plus usage, per-seat plus consumption, prepaid credits, committed spend), how usage becomes one audited invoice, proration on mid-cycle changes, and where LedgerUp sits next to Stripe, Orb, and Metronome. LedgerUp meters usage itself or reads from the meter you already run. - [Procurement Portal Invoicing](https://www.ledgerup.ai/docs/procurement-portals): How Ari submits invoices into Coupa, SAP Ariba, Bill.com, Tipalti, and custom portals: PO matching, submission with required fields, status tracking, and rejection handling. - [QuickBooks Integration](https://www.ledgerup.ai/docs/quickbooks): QuickBooks Online via the official QuickBooks API over OAuth: invoices from closed deals, Stripe payout reconciliation, credit memos and proration, and multi-entity company file routing. - [NetSuite Integration](https://www.ledgerup.ai/docs/netsuite): NetSuite via SuiteScript/REST: subsidiary-aware invoicing with GL coding, dunning by aging bucket, cash application with remittance parsing, and ASC 606 journal-ready entries. - [Salesforce Integration](https://www.ledgerup.ai/docs/salesforce): Closed-won opportunities to invoices, usage-based billing from custom objects, milestone billing on stage changes, and AR status written back to Salesforce. - [HubSpot Integration](https://www.ledgerup.ai/docs/hubspot): Webhook-triggered invoicing on Closed Won, contract intelligence on deal properties and attached PDFs, and payment status synced back to deal records. - [Slack Integration Guide](https://www.ledgerup.ai/docs/slack): Installing and configuring LedgerUp for Slack. - [Full API & setup reference](https://docs.ledgerup.ai): Endpoint reference, request/response schemas, and setup guides on the docs subdomain. - [OpenAPI specification](https://docs.ledgerup.ai/openapi/ledgerup-engine.json): The authoritative machine-readable contract for the LedgerUp Engine API. Generate clients from this. ## Main pages - [Homepage](https://www.ledgerup.ai/): AI agents for manual accounts receivable work. Meet Ari, what he handles, customer results, and how much to hand over. - [Meet Ari](https://www.ledgerup.ai/product/meet-ari): LedgerUp's AI billing agent - [Usage-Based Billing Calculation](https://www.ledgerup.ai/product/usage): How Ari automates overage calculation and metered invoicing - [What is Contract-to-Cash?](https://www.ledgerup.ai/what-is-contract-to-cash): Contract-to-cash definition and the 8-step process - [Accounts Receivable Automation](https://www.ledgerup.ai/accounts-receivable-automation): AR automation overview - [Accounts Receivable Software](https://www.ledgerup.ai/accounts-receivable-software): AI accounts receivable software for B2B SaaS - [Accounts Receivable Services (AR as a service)](https://www.ledgerup.ai/receivable-management-services): LedgerUp as the accounts receivable service: what is included, how it works, pricing versus outsourcing firms and collections agencies, customer results, and when a collections agency is still the right call. - [Procurement Portal Automation](https://www.ledgerup.ai/product/procurement-portal-automation): Automate invoice submission to Ariba, Coupa, Bill.com, Tipalti - [Integrations](https://www.ledgerup.ai/integrations): CRM, payment, ERP, and procurement portal integrations - [Compare](https://www.ledgerup.ai/compare): How LedgerUp compares to billing, AR, and rev-rec alternatives - [Pricing](https://www.ledgerup.ai/pricing): Plans and pricing - [Payment Terms Glossary](https://www.ledgerup.ai/payment-terms): Supporting reference for Net 15, Net 30, and 2/10 Net 30 (not a core topic) - [Glossary](https://www.ledgerup.ai/glossary): Revenue operations terms — DSO, cash application, order-to-cash, and more - [Customer Stories](https://www.ledgerup.ai/customer-stories): Case studies from Outset, Buzz, HappyRobot, OnShore, and others - [Manifesto](https://www.ledgerup.ai/manifesto): Why LedgerUp exists - [Resources](https://www.ledgerup.ai/resources): Guides, benchmarks, and listicles - [Book a Demo](https://www.ledgerup.ai/book-a-demo): Schedule a demo ## Who is it for? - B2B companies with sales-led deals, custom contracts, and a lean finance team whose billing work spills beyond their software - B2B SaaS companies, startups, and SMBs - Businesses with usage-based, consumption-based, hybrid, or subscription billing - Finance teams automating billing, collections, ARR, and ASC 606 / IFRS 15 revenue recognition - Companies preparing for a Series B, audit, or IPO that need clean, audit-ready revenue schedules - Teams whose billing engine (Stripe, Orb, Metronome, Chargebee) meters usage but doesn't reconcile or recognize it - Teams on Stripe that need usage-based billing for negotiated B2B contracts, not just self-serve price lists - Companies struggling with late payments, high DSO, and revenue leakage - Teams connecting their CRM, billing platform, and ERP ## Key Features - AI agent (Ari) for manual accounts receivable work: invoicing from signed contracts, collections, procurement portal submissions, billing-question replies, cash application, and reconciliation, with human approval on sensitive actions - AI revenue subledger reconciling usage and contracts to invoices and recognized revenue - Usage metering: raw event ingestion via API or warehouse sync, deduplication, aggregation, and rating against contract rate cards, tiers, minimums, and credits - Stripe App Marketplace app: usage-based billing, invoicing, and payout reconciliation on Stripe - Usage-based / metered / consumption-based billing reconciliation and overage detection - ASC 606 and IFRS 15 revenue recognition with variable consideration and deferred revenue schedules - Contract parsing and invoice generation - Accounts receivable automation, collections, and payment follow-ups - DSO (Days Sales Outstanding) reduction - Revenue leakage and under-billing detection - ARR tracking and real-time revenue analytics - Payment tracking, cash application, and bank reconciliation - Automated procurement portal invoice submission (Ariba, Coupa, Bill.com, Tipalti, and any portal) - Slack-native interface for approvals and updates - CRM, payment processor, and ERP integrations — no rip-and-replace ## How it Works LedgerUp connects your CRM, billing engine, accounting system, email, Slack, and procurement portals. Ari reads each signed contract, creates and sends the invoice on the right schedule, submits it to the customer's portal where required, follows up on overdue balances, answers billing questions from your records, matches payments to invoices, reconciles to the ERP, and keeps revenue recognition under ASC 606 / IFRS 15 tied to the contract and the metered usage. You set the approval rules; Ari brings the exceptions to Slack and logs every action in an audit trail. ## Business Impact - Average team saves 2.5 hires - Reduce DSO and improve cash flow - Eliminate manual accounts receivable work - Automate payment reminders and collections - Get paid faster with automated follow-ups - Real-time visibility into outstanding invoices - 60% faster collections - DSO down 15 days on average - 100+ hours saved per team each month - Accurate ARR numbers ## Common Use Cases - Recognizing revenue on usage-based, consumption, and prepaid-credit contracts under ASC 606 / IFRS 15 - Reconciling metered usage and overages to signed contracts to catch under-billing - Automating deferred revenue waterfalls and ERP-synced revenue schedules - Producing audit-ready revenue schedules for a Series B, audit, or IPO - Automating monthly subscription billing - Managing usage-based billing for API/infrastructure companies - Accelerating enterprise contract-to-cash cycles - Reducing manual invoice processing for growing teams - Streamlining collections for high-volume transactions - Consolidating revenue data from multiple sources - Automating quote-to-cash - Automating invoice submission to procurement portals (Ariba, Coupa, Bill.com, Tipalti) ## Technical Details ### Integrations - **CRM**: Salesforce, HubSpot, Attio - **Billing & Payments**: Stripe, Chargebee (works alongside metering engines like Orb and Metronome) - **ERP**: NetSuite, QuickBooks, Xero - **Communication**: Slack (primary interface) - **e-signing tools**: Docusign, PandaDoc, HelloSign - **Procurement Portals**: Ariba, Coupa, Bill.com, Tipalti, and any portal with login credentials - **API**: RESTful API available for custom integrations ### Security & Compliance - SOC 2 Type II certified - GDPR compliant - Bank-level encryption for all data - PCI DSS compliant for payment processing ## Company Information - **Founded**: 2024 - **Headquarters**: San Francisco - **Company Stage**: Seed - **Backed by**: Y Combinator - **Founder/CEO**: Bailey Spell ## Pricing - Starter: $500 per month ($425 per month billed annually), includes 10,000 Ari credits per month, 14-day free trial - Growth and Enterprise: custom pricing, contact sales - Pilots available so teams can validate Ari on their messiest customer before committing - No setup fees; onboarding and migration assistance included - Full plan details: https://www.ledgerup.ai/pricing ## Contact - **Sales**: mikey@ledgerup.ai - **Founder/CEO**: bailey@ledgerup.ai - **Demo**: https://www.ledgerup.ai/book-a-demo ## FAQ - **Setup Time**: Typically under a week for full implementation - **Minimum Requirements**: $100K+ monthly recurring revenue recommended - **Migration Support**: Full white-glove migration assistance included - **Training**: Onboarding and training included with all plans - **Contract Length**: Monthly or annual billing available ## Customer Success - Average team saves 2.5 hires - Collections: 60% faster - DSO: down 15 days on average - Time saved on AR: 100+ hours per team per month - Collection success rate improvement: 45% - Invoice processing time: 90% faster - Procurement portal automation saves 15 hours/month and reduces DSO by 13 days on average