Company
Recurring revenue is one thing, happening over and over.
Most companies run it as four. A billing tool, a payments stack, a collections process and a spreadsheet that reconciles them. Occurly exists because that split is the complexity, not the scale.
Why we started
The bill is the last thing to get built.
Every company that sells on a subscription starts the same way. Billing is a cron job and a card charge, and it works. Then pricing changes. Then usage arrives. Then a second currency, a second entity, a tax rule, a customer who wants one consolidated invoice instead of nine.
By the time anyone calls it a system, it is a billing script, a payments dashboard, a dunning inbox, a collections spreadsheet and a revenue model that disagrees with all four. Nobody chose that architecture. It accumulated. And the cost of it is not the software, it is the ten days a month finance spends proving the numbers.
We built Occurly to put the whole lifecycle on one platform: 11 modules that are peers, not a core product with add-ons. Subscriptions and usage rate onto the same invoice. Payments, collections and dunning act on that invoice. Analytics read the same data rather than a nightly copy of it.
What we hold to
Four decisions, made once.
- One platform, not four systems.
- A subscription, its usage, its invoice and its revenue number are the same fact seen from different desks. When they live in different systems, reconciliation becomes a job. Occurly keeps them on one platform so it stays a report.
- Global is the default, not an edition.
- Multi-entity, multi-currency and multi-country are not an upgrade path. A business that opens a second entity should not be migrating, and no country is treated as the normal case the others deviate from.
- Finance and engineering read the same page.
- The objects a controller closes the month on are the objects a service writes to. There is no second model kept in sync by hand, which is where most billing incidents actually start.
- Correct beats clever, every cycle.
- Billing is the one system a company cannot be relaxed about. Proration to the second, idempotent writes, replayable webhooks and an audit trail on everything, because a wrong invoice costs more than a slow feature.
Global by default
No country is the normal case.
A business with entities in four countries is not an enterprise edge case, it is what growth looks like. Occurly bills in the customer's currency, invoices in the local format, collects on regional rails, and rolls the whole thing up to one reporting currency for finance.
- Platform, whatever the geography
- 1
- Entities, consolidated
- Many
- Currency, at the customer's end
- Any
Plainly
What Occurly is not.
- Not a payment gateway. Occurly routes to the processors you already use.
- Not a spreadsheet with an API. Revenue analytics are computed from live billing data.
- Not a single-feature tool. The modules are peers, and they ship together.
Occurly helps businesses build, operate and scale recurring revenue.
Questions before you book? Talk to us.