Guide

Why billing revenue doesn't match the general ledger (and how to reconcile it)

The billing system and the ledger measure different things at different times. Here are the seven usual causes and a reconciliation you can repeat every month.

Eddie Ningombam Updated Nov 2026

The short answer. Billing and the general ledger rarely match because they answer different questions. Billing records what you invoiced; the ledger records revenue earned in the period, with the difference held in deferred revenue or accrued (unbilled) revenue. The gap is usually explained by recognition timing, accruals and reversals, credits, cutoff, FX, multiple entities and usage billed in arrears. Reconcile it with a deferred revenue rollforward.

Two systems, two questions

The billing system answers "what did we invoice, and what do customers owe?" The general ledger answers "what revenue did we earn this period?" Under accrual accounting those are different numbers almost every month, and that is correct. The problem is not that they differ. It is when nobody can explain the difference quickly.

This guide goes deeper on the special case in How to explain a budget vs actual variance. It describes general practice and is not accounting advice; your revenue policy and auditors decide the specifics.

Illustrative example

A customer signs a $120,000 annual contract on January 1 and is invoiced up front. In January the billing system shows $120,000. The ledger recognizes $10,000 of revenue and holds $110,000 in deferred revenue. Billing and revenue differ by $110,000, and both are right.

The seven usual causes

CauseWhat happensHow to spot it
Recognition timingInvoices are issued up front or in advance; revenue is recognized over the service periodMovement in deferred revenue explains the gap
Accruals and reversalsRevenue for work delivered but not yet invoiced is accrued, then reversed when the invoice is issuedLook for accrual entries and their reversals across two periods
Credits, refunds and write-offsAdjustments made in billing that reach the ledger later, or ledger adjustments with no billing recordCompare credit notes and write-offs in both systems for the period
CutoffInvoices dated at period end land on different sides of the close in each systemCheck invoices dated in the last and first days of the period
FXBilling in the customer's currency; ledger in the entity's functional currency at a different rateRestate billing at the ledger rate and see what remains
Multiple entitiesOne customer billed by one entity, revenue recorded in another, or intercompany entries not eliminatedReconcile entity by entity before consolidating
Usage billed in arrearsOverage or usage charges invoiced after the period in which the usage happenedMatch usage reports to the period they relate to, not the invoice date

The reconciliation: a deferred revenue rollforward

The cleanest way to tie billing to revenue is a rollforward of deferred revenue for the period:

Rollforward

Opening deferred revenue
+ Billings in the period
- Revenue recognized in the period
+/- Credits, write-offs and FX
= Closing deferred revenue

If the closing balance you calculate matches the ledger's deferred revenue balance, billing and revenue are reconciled. If not, the difference is your list of items to investigate.

Illustrative rollforward

Opening deferred revenue $1,200,000. Billings $650,000. Revenue recognized $540,000. Credits ($12,000). Calculated closing balance $1,298,000. Ledger shows $1,290,000. The $8,000 difference traces to one invoice dated on the last day of the month that billing counted in the period and the ledger posted the next day: a cutoff item.

A monthly routine

  1. Export invoices, credits and usage charges for the period from billing, and revenue, deferred revenue and accrued revenue from the ledger.
  2. Restate billing to the ledger's currency and entity structure.
  3. Run the rollforward and calculate the unexplained difference.
  4. Work the difference through the seven causes in order: cutoff first, then credits, then accruals, then the rest.
  5. Record each reconciling item with its source invoice or journal entry, so next month starts from this month's answer.

Make it repeatable

Most of the pain comes from the same mapping being worked out again each month in a spreadsheet: which billing record types become which ledger entries, for which entity, at which rate. Write that mapping down once, version it when it changes, and give it an owner. That documented mapping is part of a finance ontology, and it turns the reconciliation from one person's knowledge into a team process.

Checklist

  • Billing and ledger exports cover the same period, entities and currency
  • Deferred revenue rollforward ties to the ledger balance, or the difference is listed
  • Cutoff items around period end are identified
  • Credits, refunds and write-offs match in both systems
  • Accruals from last period have reversed
  • Usage charges are matched to the period of use
  • Every reconciling item has a source reference and an owner

Frequently asked questions

Should billing and revenue ever match?

Only in simple cases, such as monthly invoicing for the same month's service with no credits or usage. For annual or multi-period contracts they will almost always differ, and the difference should sit in deferred or accrued revenue.

Why does the CRM show a different number from both?

The CRM usually records bookings or contract value at signature, which is a third measure. Bookings, billings and revenue each answer a different question and should be reconciled in that order.

How often should billing be reconciled to the ledger?

Every month as part of the close. Waiting until quarter end turns small cutoff and credit differences into a backlog that is much harder to trace.

E
Eddie Ningombam
Founder, PhrasIQ

Building InSightOS, the decision infrastructure layer for enterprise FP&A teams. Previously in finance operations and data infrastructure. Writing about decision latency, financial reasoning, and what it takes for FP&A to own the strategy conversation.

Get new articles in your inbox
FP&A strategy, variance analysis, and decision infrastructure. No noise.
✓ You're subscribed. First issue incoming.