.png)
Most demos of metered billing solutions go the same way. The vendor starts with a single product event, walks it all the way to a revenue report, and shows their platform handling every step in between.
If you're sitting through those demos, you probably landed here for one of three reasons.
Sound familiar? Wherever you're starting from, the answer begins in the same place. A metered billing solution turns product usage into invoices at the prices in each customer's contract, and some solutions also recognize the revenue from that usage. Before comparing vendors, decide which of those jobs your own team should run.
Andrew Bihl, CTO at Numeric, recommends that usage-priced companies keep metering with their engineers and run invoicing and revenue recognition in one system on the same contract, so engineering keeps control of the usage and pricing customers see, and finance gets invoices and revenue that match because they come from the same terms.
This guide compares the five main types of metered billing solutions and how to decide which parts of billing your team should own. It also covers what to look for in a demo, the questions to ask every vendor, and how Numeric's Billing & Revenue works with the metering your engineers already run.
A metered billing solution charges customers for what they use. It takes usage, such as API calls or tokens, applies the prices in each customer's contract, and turns the result into invoices.
In his post on why AI companies should own their metering, Andrew Bihl breaks billing into four jobs that sit behind every metered billing setup.
Metered billing solutions differ in which of these jobs they cover, and that difference is the clearest way to compare them.
Each type of solution is built around a different job. For a finance team, the useful question is which jobs a solution leaves for them to handle in another system each month.
Usage billing platforms, subscription billing platforms, paired billing and revenue tools, and ERP billing modules all keep metering in a vendor's platform. Back-office billing and revenue systems like Numeric's Billing & Revenue work with the metering a company's engineers already run, so the first decision is which parts of billing to keep in-house.
Andrew's rule for usage-priced companies is to build in-house where billing shapes the product and the customer experience, and to buy the work customers never see. Metering is usually part of the product. Customers see their usage and their remaining balance in the product, so decisions about pricing changes and usage limits are product decisions.
His post offers four questions to help a team decide.
A yes to these questions points toward keeping metering with engineering. Andrew describes how the work then splits between the two teams.
"Billing engineers own the metering side, and both teams work from the same agreement model as pricing and contracts change."
Andrew Bihl, CTO at Numeric
When one platform owns everything from metering to invoicing, growing companies often end up building around it. Engineering teams collect and aggregate events themselves before sending them to the vendor, to bring the event volume down. Enterprise agreements that the platform's contract model wasn't built for move into a second system. Revenue recognition shifts into spreadsheets or another tool.
Each of these workarounds makes the platform harder to move off later, because pricing, usage data, and invoicing all depend on it.
A usage billing platform can be a good fit for an early-stage company with simple pricing and modest event volume that wants its engineers focused on the core product. The platform handles metering and invoicing from the start, and the company can revisit the setup as pricing and volume grow, using the questions in Numeric's guide to switching to a usage-based pricing model.
The back office works best as one system. Everything needed to invoice a customer is part of what revenue recognition needs, and revenue accounting also needs the full contract terms and the state of billing. The difference between what has been billed and what has been earned becomes deferred revenue or unbilled receivables, so the two can only be calculated with both in view.
When invoicing and revenue recognition run on one contract, billings and revenue come from the same terms, and finance has one set of numbers to check. For the revenue accountant, a contract change is entered once. When a customer upgrades or cancels, the invoice and the revenue schedule both update from that contract.
Once a team knows it will keep metering in-house, the evaluation centers on the back office. These are the capabilities worth checking in every demo.
Numeric's billing and revenue management guide goes deeper on ASC 606 requirements, including contract changes and how a bundled price is split across a deal. For feature and pricing detail on individual vendors, see Numeric's roundup of usage-based billing software.
Take these questions into each demo. A good answer is specific and shows the workflow in the product.
Engineering keeps metering, along with the usage, live pricing, and balances customers see in the product. Numeric's Billing & Revenue takes usage from the company's own systems, such as Snowflake or Databricks, as individual records or already aggregated.
Deal terms come in from Salesforce or HubSpot. AI reads the signed contract and checks it against the deal booked in the CRM, so errors are caught before the first invoice goes out. Numeric's team sets up these connections with each customer.
Once usage arrives, Billing and Revenue Recognition both work from the customer's contract.
Every revenue number traces back to the contract and the usage behind it, which makes audit requests and customer invoice questions faster to answer.
Built, the AI-powered real estate finance platform connecting lenders, owners, developers, and contractors, needed a system that could handle usage-based billing. Running billing and revenue on Numeric freed up 2 FTEs worth of bandwidth from billing and revenue work, and Built now delivers invoices to customers 4 business days earlier.
"We're almost operating in a different century, it feels like, from a data perspective."
Asia McKnight, Controller at Built
Billing & Revenue runs alongside NetSuite, with invoices and revenue entries exported to NetSuite. Teams ready to move their full accounting can run it on Numeric's ERP replacement, the Financial Data Platform.
Billing & Revenue is built for complex SaaS, fintech, and usage-based revenue businesses in need of a unified data platform, especially companies whose engineers already run their own metering. If you're interested in switching, you can start your journey here.
Bill and recognize revenue for every contract change without updating two systems.
Once a team knows which parts of billing its engineers will keep, it can judge every vendor by how well it runs invoicing and revenue recognition on the same contract. The questions above give finance a way to test that in a single demo.
If your engineers own metering and your finance team needs billing and revenue on one contract, see how Numeric's Billing & Revenue works.
A metered billing solution is software that charges customers for what they use by turning measured usage into billable amounts and invoices. Some solutions also recognize the revenue from that usage.
Metered billing measures usage and prices it. Usage-based billing is the full process of charging for consumption, which also includes invoicing and revenue recognition.
Companies with fast-changing pricing, real-time customer balances, or very high event volume usually keep metering in-house and buy a system for invoicing and revenue recognition. Early-stage teams with simple pricing and modest volume can start with a usage billing platform.
It depends on the type of solution. Some recognize revenue in the same system, some pass usage to a separate revenue tool, and some offer revenue reporting, so ask each vendor where revenue recognition runs and what finance reconciles each month.
Revenue follows the contract's performance obligations, and invoicing sets billing timing. Usage has to be tied to the right contract and obligation, and the difference between what was billed and what was earned becomes deferred revenue or unbilled receivables.
For AI companies that keep metering in-house, Numeric's Billing & Revenue runs invoicing and revenue recognition on the same contract. It takes usage from the company's own systems and produces the invoices, revenue schedule, and accounting entries from one contract.