What is ERP? Enterprise resource planning and where billing fits around it

Enterprise resource planning (ERP) is the system of record for a company's core business operations. General ledger, accounts payable and receivable, procurement, inventory, and often HR and manufacturing, all running on one shared data model.

For a software company the relevant question is not what ERP does but where its boundary sits. ERP is the authoritative record of financial truth. It is not where usage gets metered or where consumption charges get calculated, and trying to make it do that is a well-documented way to spend two years on an implementation.

What ERP is genuinely good at

• A single financial truth. One ledger that everything reconciles to, which is the whole reason the category exists.

• Statutory compliance. Local GAAP, tax filing, audit trails, and multi-entity consolidation across jurisdictions.

• The close. Structured period-end processes with controls, approvals and reconciliation.

• Procurement and payables. Purchase orders, three-way matching, vendor management.

• Consolidation. Rolling up subsidiaries in multiple currencies into group reporting.

Where ERP struggles with modern software billing

The mismatch is architectural rather than a matter of configuration.

Event volume. An ERP is designed around transactions measured in thousands per period. A consumption product generates millions or billions of usage events. Loading raw events into a general ledger system is not a scale problem you configure your way out of.

Rating complexity. Tiered rates, credit wallets, commitment drawdown, ramps and hybrid structures require a rating engine. ERP billing modules were built for invoicing known quantities of known items.

Timing. Entitlement decisions and spend alerts need to happen in seconds. ERP operates on a period cadence, and correctly so.

Change frequency. Pricing on an AI product changes often. ERP is deliberately hard to change, because it is the system auditors rely on. Those two properties are in direct conflict, which is why pricing changes end up implemented in spreadsheets alongside it.

The working division of labour

The integration between them should be a summarised journal, not a firehose. Billing computes the charges and posts periodic summary entries to the ledger, with the detail remaining queryable in the billing system where the events live.

The common failure pattern

A company outgrows spreadsheet billing, decides billing is a finance problem, and implements the ERP billing module. It works while pricing is simple. Then a usage meter is introduced, and the workaround begins.

Usage gets aggregated monthly in a data warehouse, exported to a spreadsheet, adjusted by hand for the accounts with non-standard terms, and imported as invoice lines. The audit trail from a customer's invoice back to the events behind it runs through a file on someone's laptop.

This is the split-stack problem, and it is where revenue leakage becomes structural rather than occasional. The way out is not a better spreadsheet. It is putting rating and metering in a system built for them and letting ERP be the ledger.

Where Solvimon fits

Solvimon handles metering, rating, invoicing, collection and revenue recognition schedules, then posts summarised journal entries into the ERP. The general ledger stays the financial system of record and does not have to carry event-level detail it was never designed to hold.

Every invoice line remains traceable back to the underlying usage events inside Solvimon, so the audit path exists without pushing raw usage into the ledger.

Frequently Asked Questions

What does ERP stand for?

Enterprise resource planning. It refers to software that runs core business operations, including the general ledger, payables, receivables, procurement and often inventory and HR, on one shared data model.

Can ERP handle usage-based billing?

Poorly, at scale. ERP billing modules are built to invoice known quantities of known items. Consumption billing requires high-volume event ingestion and a rating engine handling tiers, commitments and wallets, which is a different class of system.

Do I need both an ERP and a billing platform?

Most software companies past early stage do. The billing platform meters and rates usage and produces invoices. The ERP holds the general ledger, the close and statutory reporting. They connect through summarised journal entries.

What is the difference between ERP and a billing system?

The billing system calculates what customers owe, based on contracts and usage. The ERP records the financial consequences in the ledger and supports the close, consolidation and statutory reporting.

Should usage data go into the ERP?

Not at event level. Post summarised journal entries and keep the event detail queryable in the billing system. Loading raw usage events into a general ledger creates a scale problem and no analytical benefit.

Why do ERP billing implementations struggle with AI pricing?

AI pricing changes frequently, and ERP is deliberately hard to change because auditors depend on its stability. Those requirements conflict, so pricing changes end up implemented in spreadsheets beside the ERP instead.

Related

• Billing engine. The system that rates usage and produces charges.

• Revenue recognition. Where billing output meets accounting standards.

• Quote to cash. The end-to-end process ERP sits at the end of.

• Usage metering. The workload ERP is not designed to carry.

• Invoice. The document produced upstream of the ledger.