Home › Guides

How to separate contract revenue, billing and the VAT tax point

Build three calendars for the same contract: when the customer is billed, when the service is delivered and when tax becomes reportable. Link them through the contract and its documents, but do not force all three to follow the invoice date.

An advance invoice can create a receivable and tax liability while most revenue remains unearned. A later cancellation can change the remaining service obligation and require a credit and refund without undoing revenue already earned.

This guide uses a deliberately simple annual service to make those relationships visible. Use the contract-event worksheet to preserve assumptions and calculate the bridge. It is a design exercise, not a claim that the transactions were executed in NetSuite.

Approve the contract analysis first

Identify the legal customer, supplier, promises, service period, price, cancellation rights and payment terms. Decide the accounting performance obligation and revenue pattern before building a schedule in the ERP.

IFRS 15 links revenue to satisfaction of performance obligations and addresses point-in-time and over-time recognition. Invoice creation or cash receipt alone does not establish that performance has occurred. IFRS Foundation, IFRS 15 overview.

The tax owner separately determines jurisdiction, tax classification, tax point and correction requirements. HMRC's VAT guide explains UK time-of-supply rules, including relevant invoice and payment events. Apply the actual supply's rules instead of deriving its VAT timing from the revenue schedule. HMRC, VAT Notice 700.

Keep those two approvals together. The contract owner confirms commercial facts, the controller approves the accounting conclusion and tax approves the tax treatment. Billing operations can then act on an explicit specification rather than choosing a tax point while entering an invoice.

Fix the example's assumptions

Assume a UK seller provides one evenly delivered service from 1 January to 31 December for GBP 12,000. The approved accounting analysis recognises GBP 1,000 revenue each month. There is no separate setup service, variable consideration, financing component or allocation between multiple obligations.

The customer is invoiced and pays on 1 January. For this synthetic example, the tax owner has determined that the full fee is taxable then at 20%. VAT is GBP 2,400 and the customer pays GBP 14,400. No cash-accounting scheme applies.

At 30 June, both parties terminate the remaining six months under the assumed contract terms. The seller issues an approved GBP 6,000 net credit plus GBP 1,200 VAT and refunds GBP 7,200. No penalty, refund for past performance or further service is involved.

Assume VAT has not yet been remitted in the isolated arithmetic. Actual filing and payment periods remain a separate operating calendar. The simple cancellation is not an accounting model for every contract modification.

Record billing and cash without accelerating revenue

At invoice, debit receivables GBP 14,400, credit a contract liability GBP 12,000 and credit output VAT GBP 2,400. The cash receipt debits bank and clears the receivable for GBP 14,400.

The customer now owes nothing, but the seller still owes the year of service. Preserve that distinction in reports: zero receivables does not mean zero performance obligation or complete revenue recognition.

Each month, debit the contract liability and credit revenue for GBP 1,000. After three months, recognised revenue is GBP 3,000 and the liability is GBP 9,000. Output VAT remains GBP 2,400 under the example's tax assumptions.

The isolated March position balances: cash GBP 14,400 equals contract liability GBP 9,000 plus VAT liability GBP 2,400 plus pretax profit contribution GBP 3,000. There are no costs or other transactions in this exercise.

Keep the invoice, receipt, revenue schedule and monthly journal references linked. A revenue report based only on invoiced sales would show GBP 12,000; the approved revenue result at March is GBP 3,000. The GBP 9,000 difference needs an explicit explanation, not a manual overwrite of the invoice register.

Reconcile the contract records in the product

NetSuite describes a revenue arrangement as a non-posting transaction recording sale information for revenue allocation and recognition. Its source links and processing are different from the posting invoice itself. Confirm the relevant Advanced Revenue Management feature, preferences and release before implementing the contract design. Oracle, Revenue Arrangement Management.

Do not treat arrangement creation as proof that a revenue journal was posted. Check the source contract, arrangement, schedule, posted journal and ledger result as separate evidence. An approved contract with a pending schedule needs a different operator action from a failed invoice transmission.

For each close, calculate opening contract liability plus new advance consideration less recognised revenue less approved refunds of unearned amounts. Reconcile the result by contract as well as in total. One over-recognised contract can offset another under-recognised contract in a control-account balance.

Process the June cancellation

By 30 June, six monthly releases have recognised GBP 6,000 revenue, leaving a GBP 6,000 contract liability. The seller has satisfied the first six months and has no further obligation after the agreed termination.

The approved credit reduces the unearned contract liability by GBP 6,000 and the VAT liability by GBP 1,200. It creates a GBP 7,200 amount repayable to the customer. The cash refund clears that amount.

Closing cash is GBP 14,400 minus GBP 7,200, or GBP 7,200. The contract liability is zero. Net output VAT is GBP 1,200 and recognised revenue remains GBP 6,000. The isolated position balances: cash GBP 7,200 equals VAT GBP 1,200 plus pretax profit contribution GBP 6,000.

The commercial bridge also agrees: net original billing of GBP 12,000 less the GBP 6,000 credit equals GBP 6,000 final consideration. Original gross cash less refund equals GBP 7,200. There is no residual revenue scheduled for July to December.

Preserve the termination agreement, credit reference, refund allocation and schedule revision. The operator should be able to explain why past revenue remains and why future revenue stops, using the same approved event.

Recover from early recognition or an orphaned credit

Suppose an invoice-posting rule immediately recognises all GBP 12,000 as revenue. At March close the result is overstated by GBP 9,000 and the contract liability understated by GBP 9,000. The cash and VAT postings may still be correct.

The controller approves a correction debiting revenue and crediting the contract liability by GBP 9,000, then checks that the corrected monthly schedule cannot recognise the same amount twice. Retain the failed rule, affected contracts and correction journals.

A separate failure occurs if billing issues the June credit but the revenue system keeps the July-to-December schedule active. Freeze further releases for the affected contract, compare the approved termination to the schedule and correct it through the supported process. Do not remove unrelated earned revenue just to clear a warning.

Where a modification changes price, scope or multiple performance obligations, return to the accounting analysis. A simple proportional credit is not automatically the right treatment. The commercial, accounting and tax decisions may require different effective dates and documents.

Hand over the operating controls

The contract owner supplies approved changes. Billing creates and corrects commercial documents. Treasury confirms collections and refunds. The controller owns recognition and contract balances, and tax owns tax-point and return treatment. Give exceptions a named case owner across those functions.

Before completion, confirm:

Performance, billing, payment and tax calendars are separately recorded.
Revenue policies are approved before schedules are generated.
Invoices, credits and arrangements link to the same contract population.
Monthly recognition and contract-liability roll-forwards reconcile.
Refunds clear customer balances and approved unearned obligations.
Cancelled services cannot keep producing revenue releases.
Tax corrections and return effects have their own review evidence.

Retain the completed worksheet and source documents with the close pack. Use currency handling for foreign-currency contracts and localization acceptance tests for the wider regression process.

Source verification date: 17 October 2026. The example assumes an approved UK VAT conclusion and a simple service pattern; it does not establish treatment for every advance, termination or subscription arrangement.

Worksheet: Revenue, billing and tax-point worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use with the revenue guide. This worksheet records decisions; it does not determine a tax point or accounting policy automatically.

Contract and tax decisions

Entity, customer, contract, framework and performance obligations:
Billing dates, delivery/service periods and recognition basis:
Tax jurisdiction, scheme, approved tax point and evidence:
Currency, credit/cancellation terms and policy owner:

Separate schedules

Record invoice net/tax/gross, cash receipts, earned revenue by period, contract-liability opening/movement/closing, and tax liability movements. Record document IDs for invoices, revenue postings, credits and refunds. Reconcile each schedule independently before connecting them.

Rehearsal: annual net 12,000 plus tax 2,400 produces cash 14,400. At March close, earned revenue 3,000 plus contract liability 9,000 plus tax 2,400 equals14,400. After six months, refund7,200 for future service leaves cash 7,200, revenue 6,000, tax 1,200 and contract liability zero.

Exceptions and approval

Invoice, recognition or tax timing mismatch and explanation:
Contract change, approved credit basis and corrected schedules:
Duplicate recognition or missing refund evidence:
Accounting owner, tax owner and controller sign-off:

Rehearse recognising12,000 in March and identify the9,000 premature amount without changing a valid tax point.

Country pages: key facts with sources
E-invoicing matrix: country × ERP support
All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: 2026-10-17 · Markdown version