These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Revenue Recognition
- Features
- Revenue schedules
Revenue schedules
Track recognition methods and deferred balances by customer and product.
OverviewMy Revenue Schedules×
Revenue Recognition · Revenue schedules
New
My Revenue Schedules
Revenue schedules
| Schedule number | Contract reference | Customer | Start date | End date | Recognized to date | |
|---|---|---|---|---|---|---|
| RS-93537 | CR-310 | CUS-182 | 27 Oct | 31 Oct | 650 | |
| RS-40435 | CR-540 | CUS-021 | 06 Oct | 10 Oct | 640 | |
| RS-59938 | CR-871 | CUS-076 | 17 Oct | 19 Oct | 120 | |
| RS-97334 | CR-511 | CUS-140 | 26 Oct | 04 Nov | 920 | |
| RS-20936 | CR-695 | CUS-155 | 11 Oct | 20 Oct | 30 |
6 of 6 records
CR-310Revenue schedules · RS-93537
PendingCustomerCUS-182
Start date27 Oct
End date31 Oct
Recognized to date650
Deferred balanceDB-228
What you can do
Revenue schedules in practice
A customer signs a service contract with a dated term. Revenue Accountant creates the schedule against the customer, product and organization, chooses the recognition method and enters the total amount. The contract reference gives the team a stable way to find the commercial agreement. Start and end dates define the schedule window; recognized to date and deferred balance show the accounting position currently recorded.
How the work is organized
- Set up. Revenue Accountant links the customer, product and organization to the schedule.
- Measure. Dates, method, total, recognized amount and deferred balance frame the period review.
- Resolve. A held schedule carries a reason and owner for the next investigation.
For a subscription spanning two reporting periods, inspect the active schedule before the second period review. Compare the contract reference and period dates with the supporting contract document, then compare recognized to date with total and deferred balance. A held schedule needs a reason that the reviewer can investigate before relying on its balance. Keep the schedule owner visible so a question about method or timing has a named recipient.
What to agree during setup
Agree who may change a method, how a milestone or usage amount is supported, and which evidence belongs with the schedule. Decide how changes to a contract are reflected in the schedule record and who reviews the revised amount. The customer owns its revenue policy. Treat the schedule status as the team’s work state and the recorded amounts as values to reconcile to the accounting system.
For the pilot, use a contract whose term crosses a reporting boundary. Compare its supporting document with the schedule dates and method, then inspect recognized to date and deferred balance. Decide who corrects a schedule if the contract amount changes after an invoice line has linked to it.
Check the handoff on an actual case
The Revenue Accountant brings a real contract reference, customer and product to the review. The Finance Approver asks whether the dates and method match the agreement, and whether the recognized amount leaves the expected deferred balance. Follow the linked invoice line to check its service period. Record a review decision when a documented human judgment is needed, with the relevant evidence document alongside the schedule.
Ask Billing Operations Manager to find the linked invoice line and compare its service period with the schedule dates. If the periods differ, Revenue Accountant should investigate the contract reference and explain the difference before the billing review proceeds.
What your team sees
- Active Revenue Schedules — Review current methods, amounts and deferred balances.
- Schedules On Hold — Find each held schedule with its owner and hold reason.
- Fully Recognized Schedules — Check completed schedules before closing the period review.
Follow the work through
Use schedule and billing review to trace this module through the period. Review the data model when mapping source identifiers and roles when assigning the people who may act.
What it keeps track of
Data model- Revenue schedules
- Revenue recognition schedules with method, recognized to date and deferred balance.
- Customers
- Customer master with numbers, payment terms and billing status.
- Products
- Billable products and services with unit, list price and revenue type.
- Organizations
- Business units and legal entities that own plans, revenue and billing activity.
Who uses it
Permissions- Revenue Accountant
- Owns schedule dates, methods and balance review.
- Finance Approver
- Examines a documented decision on a schedule.
- Admin
- Maintains customer, product and organization reference records.
Set up Revenue Recognition your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.