Accounting › Revenue Recognition
Revenue Runs
Step 5, per period. A contract whose allocation is stale is reported as an exception rather than recognised on the old price.
Where to find it
- Module: Accounting
- Group: Recognition
- Section: Revenue Recognition
- Screen: Revenue Runs
Address in the console: /accounting/rev-runs
Read-only list · 9 columns · 1 action
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Run | Code | run_no |
| Period | Code | period_code |
| Ledger | Code | ledger_code |
| Contracts | Number | contract_count |
| Obligations | Number | obligation_count |
| Revenue | Amount | total_revenue |
| Exceptions | Number | exception_count |
| Journal | Code | journal_no |
| Status | Status | status |
What you can do here
Recognise revenue primary
Asks for: Period (YYYY-MM)* Test run — calculate and post nothing
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.