Appearance
Revenue contract
FinanceRevenue recognitionRevenue contractPermission:
finance.revrec.viewAlso known as
- new revenue contract
- performance obligation
- standalone selling price
- SSP
- transaction price allocation
- ratable
- point in time
- milestone
- usage-based
- bill contract
This screen sets up a revenue contract with its performance obligations, activates it to generate the recognition schedule, records fulfilment, milestones and usage, and bills it. It serves New revenue contract (/app/finance/revrec/contracts/new) and every existing contract.
Set up and activate a contract
- Go to FinanceRevenue recognition and select New revenue contract.
- In Contract, fill in the fields (table below).
- On Performance obligations, select Add obligation for each distinct promise (a licence, onboarding, support, training) and fill in its fields. Milestone obligations need at least one milestone (Add milestone).
- Select Save contract. The Allocated price of each obligation is the transaction price split in proportion to the standalone selling prices ("The transaction price is allocated in proportion to the standalone selling prices.").
- Select Activate and confirm: "The schedule is generated from the obligations and the obligations can no longer change." The Recognition schedule tab fills in.
| Field | Required | What to enter |
|---|---|---|
| Customer | Yes | A customer of the entity. |
| Name | Yes | For example ERP implementation project. |
| Start, End | Yes | The contract term; end on or after start. |
| Transaction price | Yes | The total consideration, in the contract currency (default the customer's). |
| Deferred revenue account | No | A liability account. "Empty uses the deferred revenue mapping." |
| Description | No |
| Obligation field | What to enter |
|---|---|
| Name | For example Implementation. |
| Pattern | Ratable (straight-line) over its dates, Point in time when fulfilled, Milestones, or Usage-based. |
| Standalone selling price | The price you would charge for it alone (SSP). |
| Start, End | For ratable obligations (default the contract term). |
| Recognition date | For point-in-time obligations, once known. |
| Estimated quantity | Usage-based: total expected units (above zero). |
| Revenue account | A revenue account; empty = the revenue mapping. |
| Milestones | Name, % of price or Amount, Planned date; percentages total 100 at most. |
Record delivery
- Mark fulfilled on a point-in-time obligation: its revenue is scheduled in the fulfilment month ("Fulfilled on …").
- Mark achieved on a milestone: its share is confirmed in the month achieved.
- Record usage on a usage obligation: enter the date and Quantity; revenue = quantity × allocated price ÷ estimated quantity.
The schedule shows each month's line as Recognised, Due (ready for the next run) or Planned.
Bill the contract
- Select Bill contract (needs Permission:
finance.invoice.manageandPermission:finance.revrec.manage). - Enter the Amount to bill ("empty bills the unbilled price") and confirm. "Draft invoice INV-… created"; it appears on the Invoices tab. Post it like any invoice.
Posts when the contract invoice is posted
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable, party = customer | ✓ | |
Deferred revenue (contract account, else the deferred_revenue mapping) | ✓ | |
| Output tax | ✓ |
When revenue was recognised before billing, the invoice first clears unbilled receivables (a true-up entry Dr deferred revenue / Cr unbilled receivables).
Complete or cancel
- Complete once every schedule line is recognised (an active contract also completes automatically after the last run).
- Cancel contract: "Unrecognised revenue of RRC-… is removed from the schedule; recognised revenue stays."
The totals panel shows Transaction price, Billed, Recognised and Deferred (negative = recognised ahead of billing).
