Use Products & Services when the revenue logic is fundamentally:
units x price
This is the right schedule for subscriptions, product volume, service hours, seats, or any other line where quantity and pricing move separately over time.
If you are modeling a fixed total-value agreement with separate billing timing, use Contracts instead.
Create a product or service
Add an item from Schedules > Products & Services; it opens in a modal on top of the schedule workspace.
Build the item in the right order
- Enter Name and Category.
- Set the Start Date and optional End Date.
- Choose the initial Revenue and COGS account allocations.
- Configure the Units Stream.
- Configure the Price Stream.
- Choose the COGS method.
- Create the item, then review its output in the schedule views.
Understand the three parts that drive the item
- Units Stream - how many units, hours, seats, or deliveries you expect
- Price Stream - what each unit is worth
- COGS - whether cost should scale as a percentage of revenue or as cost per unit
Revenue is generated from Units multiplied by Price. COGS is generated separately from the method you choose.
Method choices for Units and Price
Both Units and Price support the same modeling methods:
- Fixed - amount, repeat frequency, and in-period placement
- Growth - rate, growth period, and optional seed value
- Manual Entry - a month-by-month entry grid
- Formula - custom logic using the formula field and full builder
Use the simplest method that matches the business:
- use Fixed when the line is stable
- use Growth when the pattern is percentage-driven
- use Manual Entry when you already know the exact monthly values
- use Formula when the line should follow another modeled driver
What flows to statements
After the item is created:
- revenue posts to the configured revenue account
- COGS posts to the configured COGS account
- the schedule becomes visible in By Product & Service, By Account, and Summary
Review those views before relying on the output in the broader forecast.
Watch out for
- The initial account allocations determine where the generated values land, so they cannot be skipped.
- Leave End Date blank only when the item is intentionally open-ended.