Every business that gets paid more than once has the same problem.
Occurly is the system that solves it.
11
Modules on one data model
Subscriptions through revenue analytics, one customer record.
3days
To close the month
Down from nine, on consolidated multi-entity revenue.
38%
Failed payments recovered
Smart retries and automated dunning, first 30 days.
1sprint
To ship billing
REST API, idempotency keys, webhooks and a full sandbox.
Outcome figures are reported by Occurly customers on their own billing volumes.
Results depend on pricing model, payment mix and the state of the data at migration.
Grow the revenue you already have.
Eleven modules on one data model, so nothing here needs reconciling against
anything else here.
Renews on the anniversary. Proration on any mid-cycle change.
Invoice preview
Draft · USD
Description
Qty
Unit price
Service period
Amount
Business planSubscription, monthly in advance
1
$1,800.00
1 Jun to 30 Jun
$1,800.00
Subtotal
$1,800.00
Tax, 20%
$360.00
Total due
$2,160.00
Plan
Scale, 62 seats, monthly
Lines
2 on this invoice
Seats added on day 15 are billed for the 16 days they existed, not the month. The period column is where that becomes checkable.
Invoice preview
Draft · USD
Description
Qty
Unit price
Service period
Amount
Scale planSeats at start of cycle
48
$89.00
1 Jun to 30 Jun
$4,272.00
Scale plan, added seatsProrated, 16 of 30 days
14
$89.00
15 Jun to 30 Jun
$664.53
Subtotal
$4,936.53
Tax, 20%
$987.31
Total due
$5,923.84
Plan
Volume tiers, 42,000 units
Lines
3 on this invoice
Graduated, not volume: each tier is charged at its own rate, not at the last rate reached. Three lines, because three rates applied.
Invoice preview
Draft · USD
Description
Qty
Unit price
Service period
Amount
API calls, tier 1First 10,000
10,000
$0.0400
1 Jun to 30 Jun
$400.00
API calls, tier 210,001 to 25,000
15,000
$0.0280
1 Jun to 30 Jun
$420.00
API calls, tier 325,001 and above
17,000
$0.0190
1 Jun to 30 Jun
$323.00
Subtotal
$1,143.00
Tax, 20%
$228.60
Total due
$1,371.60
Plan
Committed spend, 12 month term
Lines
3 on this invoice
Credits are consumed before cash, so the invoice only charges what the commitment did not cover.
Invoice preview
Draft · USD
Description
Qty
Unit price
Service period
Amount
api.tokensMetered, billed in arrears
3,120,000
$0.0009
1 Jun to 30 Jun
$2,808.00
storage.gbMetered, peak in period
820
$0.4500
1 Jun to 30 Jun
$369.00
Prepaid credit appliedDrawn from commitment balance
1
$2,500.00
Term to date
-$2,500.00
Subtotal
$677.00
Tax, 20%
$135.40
Total due
$812.40
Plan
Scale + metered, monthly
Lines
3 on this invoice
One invoice, one payment, one revenue record. The customer never sees the seam between the seat line and the meter.
Invoice preview
Draft · USD
Description
Qty
Unit price
Service period
Amount
Scale planPer seat, monthly in advance
62
$89.00
1 Jun to 30 Jun
$5,518.00
api.tokens over allowanceMetered, billed in arrears
1,120,000
$0.0009
1 Jun to 30 Jun
$1,008.00
Annual commitment discount12% on the subscription line
1
$662.16
1 Jun to 30 Jun
-$662.16
Subtotal
$5,863.84
Tax, 20%
$1,172.77
Total due
$7,036.61
135+
Currencies billed and settled
Any
Entity count, consolidated
1
Platform, no country edition
One platform, wherever your customers are.
Bill in the customer's currency, route the payment on a local rail, apply the
right tax and consolidate all of it into one statement. There is no country
edition to buy and nothing to reconcile between regions.
Four entities, four currencies, one closed month.
Entities, currencies and tax rules are configuration, not a second instance to
reconcile.
Bill each customer in their currency and tax rules
Rates are the period-close rates on the entity's own books. Nothing is restated
after the close.
Who Occurly is for
Recurring revenue is not one industry.
Seat-based SaaS, metered AI, consumer subscriptions at volume, platform billing
and multi-entity enterprise groups are the same operational problem wearing
different clothes. One catalog, one ledger, one close.
Each segment above links to how Occurly is configured for it. The companies to
the right are real customers.
The stack
One platform, wired to everything else you run.
Occurly owns the subscription, the invoice and the money. Your gateway, your
ledger, your CRM and your warehouse keep doing their own jobs, and none of them
has to be told twice.
Payment rails, ledgers, CRMs, tax engines and the warehouse.
How it goes
Moving your billing, step by step.
A typical mid-market migration. Complex catalogs and heavily customised legacy
systems take longer, and we scope that before you sign rather than after.
Plans, prices, add-ons, coupons and price-book versions go in first, per currency and per entity. Anything your current system cannot express is where the conversation starts, because that is usually the reason you are moving.
02
Import the base
Week 1 to 2
Customers, subscriptions, payment methods and historical invoices arrive with their terms, their anniversaries and their grandfathered prices intact. Tokenized payment methods transfer without asking a single customer to re-enter a card.
03
Connect the stack
Week 2
Gateways, the accounting ledger, the CRM, the tax engine and the warehouse. Occurly is the system of record, so these are outbound syncs rather than a second source of truth to reconcile against.
04
Run the cycle in parallel
Week 3
A shadow billing run produces the same period on both systems and the two invoice sets are compared line by line. Nothing is sent to a customer. This is the step that makes the cutover boring, and it is not optional.
05
Cut over
Week 4
Billing moves on a date you choose, mid-cycle if the calendar requires it. Proration is computed from the imported terms, so no cycle is skipped, doubled or re-dated.
06
Close the first month
Month 1
MRR, retention, cohorts and the consolidated statement are computed from live billing data rather than exported and rebuilt. The close is the test, and the first one is run alongside your team.
Subscription Management$4,820 MRR
Catalog & Pricing$89.00 / seat
Quote-to-Cash$2,140,880
Usage Billing$0.0009 / call
Collections$412,880 open
Payments$24,180 captured
Dunning$182K recovered
Customer Lifecycle52 records
Entitlements$5,863.84
Revenue Analytics$4.28M ARR
Integrations38 connected
Consolidated ledger$4,040,658
One platform
Everything that touches revenue, on one system.
Eleven modules and one ledger. Nothing here syncs to anything else here, because
there is no "else" for it to sync to.
Usage-based pricing used to mean a spreadsheet and a prayer. Now meters, credits and invoices just line up, every cycle.
Diego MartinsHead of RevOps
Meridian Media
Dunning recovered revenue we were quietly losing every month. The retries and reminders paid for the platform on their own.
Sara OkonkwoDirector of Billing
Forge Labs
The API is clean, webhooks are reliable, and the sandbox let us build with confidence. We shipped billing in a sprint.
Tom BeckerStaff Engineer
What buyers ask before the demo.
What is Occurly?
Occurly is a recurring revenue platform. It runs subscriptions, usage-based billing, invoicing, payments, dunning, entitlements and revenue analytics, and it replaces the patchwork of billing scripts, spreadsheets and point tools that revenue teams stitch together as they grow.
Does Occurly support usage-based and hybrid pricing?
Yes. Ingest usage events at scale and bill on tiered, volume, stairstep or per-unit pricing, including prepaid credits and commitments. You can combine recurring subscriptions and usage on the same plan, so seat-based and consumption pricing live on one invoice.
Is Occurly built for global businesses?
Occurly is multi-currency and multi-entity from day one. Bill customers in their currency, route payments across gateways by region, and consolidate revenue across entities. There is no per-country edition to choose, the same platform runs everywhere your customers are.
Can we migrate from our current billing tool?
Yes. Onboarding includes data import for plans, customers, subscriptions and historical invoices, with a guided cutover so billing never skips a cycle. Teams switching from Chargebee, Recurly, Stripe Billing, Zuora or Maxio follow a documented migration path.
How long does a migration take?
A typical mid-market migration runs about four weeks: catalog modelling, data import, connecting the stack, a parallel billing run and then cutover on a date you choose. Complex catalogs and heavily customised legacy systems take longer, and that is scoped before you sign rather than after.
How do engineers integrate Occurly?
Through a clean REST API, reliable webhooks, idempotency keys, SDKs and a full sandbox. Entitlement checks, the customer portal and checkout are drop-in, so teams ship billing in a sprint instead of building plumbing.
Is my billing data secure?
Occurly encrypts data in transit and at rest, isolates tenants, and logs every access for audit. Payment details are tokenized and vaulted with PCI-compliant processors. Security and compliance posture is documented on the Trust page.
Quote-to-cash CPQ, quotes, orders, invoices and credit notes on one record, so what you quoted is what you billed. 
Payments Route across gateways by region, store methods once, and reconcile every capture back to its invoice. 
Collections Receivables ageing, retry schedules and dunning sequences that close out the balance without a chase. 
Developer API REST, signed webhooks, idempotency keys and a sandbox with clocks you can advance. 
