Revenue Recognition

Policies, schedules, entries, and period close for recognized vs billed — composed from contracts and invoices, not a shadow GL.

Booked revenue

Recognize against contracts you already have

Revenue recognition posts recognized vs billed using policies and schedules on live POs and invoices. It is not a second general ledger product.

Finance → Revenue recognition Route /finance/revenue-recognition Org flag revenueRecognitionEnabled Finance Manager · Admin

Keep methods true, generate period entries, approve, close. Fix the contract if the schedule is nonsense.

Finance managers and admins. Executives read forecast/analytics, not always this hub.

Policies → schedules → entries → period close, then dashboards follow.

Month close. Milestone method change. Audit of recognized revenue. After a credit note.

ⓘ

Entries on commercial sources

PO and invoices remain canonical. This hub posts recognition, it does not invent contracts.

Confirm method, generate entries, close the period.

flowchart TD
  A[Open Revenue recognition] --> B[Policies]
  B --> C[Schedules]
  C --> D[Entries]
  D --> E[Period close]

Recognition is a workflow on contracts and invoices. The hub tabs (policies, schedules, entries, close) are in-page, not separate source systems.

1. Billed vs recognized

Invoices can lead or lag.

2. Do not Excel-post

Entries live here.

3. PO still contract

Methods hang off that commercial truth.