Contract-driven billing explained: from quote to invoice

Many organisations bill from memory. Someone knows that a customer pays monthly, that one site has a discount and that a price rise was agreed last spring. The invoice is assembled from that knowledge, a spreadsheet and the previous invoice.

That works until the person is on leave, the customer queries a charge or an auditor asks why two similar customers are paying different amounts.

Contract-driven billing takes a different approach. Every invoice is generated from a contract record, and every contract is built from a governed catalogue and price list. This article walks through how that works, from quote to invoice.

The product catalogue and price lists

Everything starts with the catalogue: a single list of the products and services you sell, each with a code, description, unit of measure and accounting treatment.

Prices sit in price lists rather than on the products themselves. That separation matters. It lets you run different prices for different customer groups, schedule a price change from a future date and keep a record of what the price was at any point in time.

Good catalogue design is mostly about restraint. Fewer, well-defined items are easier to price, report on and audit than hundreds of near-duplicates.

Quotes with approvals

A quote is built from the catalogue and the relevant price list. Where a quote departs from standard pricing, such as a discount, a non-standard term or a bespoke item, it routes for approval according to rules you set.

Approval rules typically look at the size of the discount, the overall value or the type of change. The point is not to slow sales down. It is to make sure that non-standard commitments are seen by someone with the authority to make them, and that the decision is recorded.

Contracts as the source of truth

When a quote is accepted, it becomes a contract. From that moment, the contract is the source of truth for what the customer has agreed to buy, at what price, for how long and on what billing terms.

A well-structured contract record holds:

• The customer and billing account
• Start date, end date and renewal terms
• Charge lines, each linked to a catalogue item and price
• Billing method and frequency for each line
• Any agreed discounts, caps or minimums

Changes to the contract, such as adding a service, changing a quantity or extending the term, are made as amendments with effective dates. The system can then calculate exactly what should be billed for any period, including part periods either side of a change.

Billing methods

Different charge lines need different billing methods. A contract-driven system supports several, often on the same contract.

Recurring

A fixed charge billed on a regular cycle: monthly, quarterly or annually. Proration rules handle contracts that start or end part way through a period.

Milestone

A charge triggered when an agreed deliverable is reached and confirmed. Common for projects and implementation work. The milestone needs a clear owner who confirms completion, so invoices are not raised early or forgotten.

Usage

A charge based on measured consumption: units delivered, hours worked, collections made. Usage data usually arrives from an operational system, so the integration and the rules for late or corrected data are as important as the pricing.

Advance

Billing ahead of the service period, with revenue recognised as the service is delivered. Finance teams need the system to keep billing and recognition clearly separated.

Consolidated invoicing

Customers with several contracts or sites often want a single invoice. Consolidation rules decide which charges are grouped together, how they are presented and which billing account receives the invoice.

Consolidation should be a presentation choice, not a data choice. Each line on a consolidated invoice still traces back to its own contract and charge line.

Validation rules and exception queues

Before invoices are released, they pass through validation rules. Typical checks include:

• A charge line with no price or a zero price
• An invoice that differs sharply from the customer's previous one
• Usage that is missing or outside expected ranges
• A billing account with incomplete address or tax details

Invoices that fail go to an exception queue rather than to the customer. A named person reviews each exception, fixes the cause and releases or holds the invoice. Over time, the pattern of exceptions shows where upstream processes or data need improving.

Credit notes, reversals and rebilling

Mistakes and disputes happen, so the correction process deserves as much design as the billing process.

In a contract-driven model, invoices are never edited after issue. Instead, corrections are made through credit notes, full reversals or a reversal followed by a rebill. Each correction links back to the original invoice and records who made it, when and why.

That audit trail answers the questions that matter in a dispute or an audit: what was billed, what was changed, who authorised it and what the customer now owes.

Keep payments separate

Billing creates the debt. Payments settle it. These are different processes, often owned by different teams and frequently handled in a different system such as the finance or income management platform.

Keeping them separate, with a clean integration between them, avoids a common problem where billing staff adjust invoices to make them match what was paid. If a customer short-pays, that is a matter for credit control, not a reason to change the invoice.

Where this fits

Contract-driven billing is as much an operating model as a piece of software. It relies on clear ownership of the catalogue, disciplined contract changes and a team that works the exception queue. Our business systems work covers the configuration and integration side, and our public sector page explains how we work with councils and other public bodies.

Talk to us

If you want to move from spreadsheet billing to a contract-driven model, see our contract management, billing and invoicing solution or contact us to talk it through.