What is Metering?
What is Metering?
Metering is the process of tracking and recording how much of a product or service a customer uses. In software, it means capturing usage events (API calls, tokens processed, storage consumed, transactions completed, agent actions performed) and aggregating them into numbers that can be billed against.
It's worth mentioning that metering is not billing. Billing takes the metered data and turns it into an invoice. Metering is the step before: the measurement system that answers "how much did this customer use?" before the billing system answers "how much do they owe?".
This distinction matters because metering is where most usage-based pricing breaks down. Not in the invoice generation, not in payment collection, but in the accurate, real-time capture of what actually happened inside the product.
How metering works
A metering system has four jobs: capture events, aggregate them, apply rules, and make the data available.
Stage | What happens | Example |
|---|---|---|
1. Event capture | Product emits usage events every time a billable action occurs | Customer makes an API call → event logged with customer ID, timestamp, action type, metadata |
2. Aggregation | Raw events are grouped by customer, metric, and billing period | 147,382 API calls by Customer X in March, broken down by endpoint |
3. Rating | Pricing rules are applied: tiers, volume discounts, included allowances, credit deductions | First 10K calls included in plan. Next 100K at $0.01. Remaining 37,382 at $0.008 |
4. Delivery | Metered and rated data is passed to the billing system for invoicing, and surfaced to customers for visibility | Billing system generates invoice. Customer dashboard shows real-time usage |
In a simple subscription business, metering barely exists. You count seats. In a usage-based or hybrid business, metering is critical infrastructure that processes millions of events per day and feeds every downstream system: billing, revenue recognition, customer dashboards, cost analysis, and entitlement enforcement.
What typically gets metered
The usage metric you meter determines what you can charge for. Choosing the wrong metric, or metering it poorly, creates problems that cascade through pricing, billing, and customer trust.
Metric type | What's measured | Common in | Example |
|---|---|---|---|
API calls | Number of requests to an API endpoint | Developer tools, infrastructure, integrations | Twilio: per SMS sent. Stripe: per API call |
Tokens | Input and output tokens processed by an AI model | AI products, LLM-based tools | OpenAI: per million tokens. Anthropic: per million tokens |
Compute time | CPU/GPU seconds or minutes consumed | Cloud infrastructure, ML training, rendering | AWS: per EC2 instance-hour. Replicate: per second of GPU time |
Data volume | Gigabytes stored, transferred, or processed | Storage, analytics, data platforms | Snowflake: per TB scanned. S3: per GB stored |
Transactions | Completed business events (payments, orders, invoices) | Payments, e-commerce, billing platforms | Stripe: per successful transaction. Adyen: per transaction |
Active users | Distinct users who performed a qualifying action in a period | PLG products, collaboration tools | Slack: per active user. Segment: per tracked user |
Agent actions | Tasks performed by AI agents | AI agent platforms, automation tools | Intercom Fin: per resolved ticket. Salesforce Agentforce: per conversation |
Credits consumed | Proprietary units drawn from a balance | Multi-feature AI products | Clay: per enrichment credit. ElevenLabs: per audio generation credit |
The best usage metric has three properties: it correlates with customer value (usage goes up when the customer gets more value), it's measurable without ambiguity (both sides agree on the count), and it scales with the vendor's cost to serve (more usage = more infrastructure cost).
Real-time vs. batch metering
How frequently you process usage events determines what you can do with the data.
Real-time metering | Batch metering | |
|---|---|---|
Processing | Events processed as they arrive (sub-second to seconds) | Events collected and processed at intervals (hourly, daily, end of billing period) |
Customer visibility | Customers see current usage in real time | Customers see usage after the batch runs |
Entitlement enforcement | Can block or throttle usage when limits are reached | Limits enforced retroactively or at next batch cycle |
Invoice accuracy | Charges reflect actual usage up to the moment | Charges may lag behind actual consumption |
Infrastructure cost | Higher (streaming architecture, always-on processing) | Lower (scheduled jobs, simpler infrastructure) |
Best for | Products with hard usage limits, credit drawdown, real-time dashboards, or where over-consumption is costly | Products where end-of-period billing is acceptable and usage doesn't need real-time gating |
Most billing systems that "support metering" do batch processing: you send usage records at the end of the period, and the billing system calculates charges. That works for simple usage-based pricing. It breaks when customers need real-time visibility, when you need to enforce limits mid-cycle, or when credit balances need to draw down as events occur.
AI products in particular need real-time metering. Token consumption is spiky and variable. A customer burning through a credit balance needs to see it happening, not find out after the invoice arrives.
Metering vs. billing vs. rating
These three terms are often used interchangeably. They're different stages of the same pipeline.
Metering | Rating | Billing | |
|---|---|---|---|
What it does | Captures and counts usage events | Applies pricing rules to metered data | Generates invoices and collects payment |
Input | Product events (API calls, tokens, actions) | Aggregated usage data from metering | Rated charges from the rating engine |
Output | "Customer X used 147K API calls this month" | "That costs $1,221.06 based on their rate card" | "Invoice #4721 for $1,221.06, due March 31" |
Who owns it | Engineering / Infrastructure | Product / Finance (pricing rules) | Finance / Revenue Operations |
What breaks when it fails | Everything downstream. Wrong usage data = wrong invoices = wrong revenue = lost trust | Pricing changes require engineering. Finance can't iterate | Late invoices, failed payments, revenue recognition errors |
Metering is the foundation. If your usage counts are wrong, your pricing, invoicing, and revenue recognition are all wrong. Companies that under-bill due to metering errors lose 4-7% of revenue according to m3ter's research. Companies that over-bill lose customer trust, which is harder to quantify but often more expensive.
What makes metering hard
Metering looks simple on paper (count events, add them up). In practice, several challenges make it one of the hardest infrastructure problems in billing.
Challenge | Why it's hard | What goes wrong |
|---|---|---|
Scale | AI products can generate millions of usage events per day per customer | Batch processing can't keep up. Events get dropped or delayed |
Idempotency | The same event can be sent multiple times (retries, network issues) | Double-counting inflates usage and breaks trust |
Multi-metric | Products often bill on multiple dimensions simultaneously (tokens + storage + seats) | Each metric needs its own metering pipeline, aggregation logic, and rate card |
Attribution | Some events are hard to assign to a single customer or action | Shared resources, multi-tenant systems, and agent-to-agent interactions create ambiguity |
Retroactive corrections | Customers dispute usage. Events arrive late. Pricing changes need to apply retroactively | The metering system needs to support amendments without corrupting historical data |
Consistency | The number the customer sees in their dashboard must match the number on the invoice | Two different systems calculating usage independently will eventually disagree |
Metering and hybrid pricing
In a pure subscription business, you don't need metering. In a pure usage-based business, metering is everything. Most companies in 2026 run hybrid pricing (base subscription + usage components), which means metering coexists with subscription logic.
Pricing component | Metering requirement |
|---|---|
Base subscription | None. Fixed fee, no usage tracking needed |
Included usage allowance | Metering tracks consumption against the included amount. No charge until exceeded |
Overage charges | Metering counts usage above the allowance. Rating engine applies overage rates |
Credit drawdown | Metering events decrement credit balance in real time |
Committed spend | Metering tracks consumption against the annual commitment. Usage rated at contracted rates |
Tiered pricing | Metering aggregates total usage. Rating engine applies correct tier at each threshold |
This hybrid reality is why metering can't live in isolation. It needs to know about the customer's plan, their contract terms, their credit balance, and their included allowances. A metering system that just counts events without context produces numbers that still need manual processing before they become an invoice.
The companies that get this right build metering into their billing infrastructure from the start, so usage data flows directly into rating, invoicing, and revenue recognition without spreadsheet intermediaries.
Learn more about how hybrid pricing models work in our post on hybrid pricing, and how credits add another layer of metering complexity in our deep dive on credit architecture.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
Advance Billing
AI Agent Pricing
AI Token Pricing
AI-Led Growth
AISP
ASC 606
Billing Cycle
Billing Engine
Consolidated Billing
Contribution Margin-Based Pricing
Cost Plus Pricing
CPQ
Credit-based pricing
Customer Profitability
Decoy Pricing
Deferrred Revenue
Discount Management
Dual Pricing
Dunning
Dynamic Pricing
Dynamic Pricing Optimization
E-invoicing
Embedded Finance
Enterprise Resource Planning (ERP)
Entitlements
Feature-Based Pricing
Flat Rate Pricing
Freemium Model
Grandfathering
Guided Sales
High-Low Pricing
Hybrid Pricing Models
IFRS 15
Intelligent Pricing
Lifecycle Pricing
Loss Leader Pricing
Margin Leakage
Margin Management
Margin Pricing
Marginal Cost Pricing
Market Based Pricing
Metering
Minimum Commit
Minimum Invoice
Multi-currency Billing
Multi-entity Billing
Odd-Even Pricing
Omnichannel Pricing
Outcome Based Pricing
Overage Charges
Pay What You Want Pricing
Payment Gateway
Payment Processing
Penetration Pricing
PISP
Predictive Pricing
Price Benchmarking
Price Configuration
Price Elasticity
Price Estimation
Pricing Analytics
Pricing Bundles
Pricing Engine
Proration
PSP
Quote-to-Cash
Quoting
Ramp Up Periods
Recurring Payments
Region Based Pricing
Revenue Analytics
Revenue Backlog
Revenue Forecasting
Revenue Leakage
Revenue Optimization
SaaS Billing
Sales Enablement
Sales Optimization
Sales Prediction Analysis
Seat-based Pricing
Self Billing
Smart Metering
Stairstep Pricing
Sticky Stairstep Pricing
Subscription Management
Tiered Pricing
Tiered Usage-based Pricing
Time Based Pricing
Top Tiered Pricing
Total Contract Value
Transaction Monitoring
Usage Metering
Usage-based Pricing
Value Based Pricing
Volume Commitments
Volume Discounts
Yield Optimization
Why Solvimon
Helping businesses reach the next level
The Solvimon platform is extremely flexible allowing us to bill the most tailored enterprise deals automatically.
Ciaran O'Kane
Head of Finance
Solvimon is not only building the most flexible billing platform in the space but also a truly global platform.
Juan Pablo Ortega
CEO
I was skeptical if there was any solution out there that could relieve the team from an eternity of manual billing. Solvimon impressed me with their flexibility and user-friendliness.
János Mátyásfalvi
CFO
Working with Solvimon is a different experience than working with other vendors. Not only because of the product they offer, but also because of their very senior team that knows what they are talking about.
Steven Burgemeister
Product Lead, Billing