Skip to main content

Revenue overview

A summary of Planhat revenue features - whether you're new to Planhat or want to learn about changes introduced in early 2026

Written by Carly Hammond
Updated over 2 weeks ago

Summary

  • Revenue data is structured in Planhat in 3 main data models:

    • Deals

      • E.g. "Renewal Deal for Apple"

      • Can move along a pipeline

    • Line Items

      • E.g. "Advanced Data Subscription on Renewal Deal for Apple"

      • Belong to a Deal

    • Products

      • E.g. "Advanced Data Subscription"

      • Templates for Line Items; housed in the Product Catalog

  • We have a library of pre-built - yet customizable - System Reports for revenue, where you can filter on these revenue data models, and choose how you would like to forecast (e.g. based on "Open" or "Closed Won" Deals)

  • Our CRM integrations can be used to sync revenue data to/from Planhat

  • You can configure revenue settings within the "Settings" Global Tool

Who is this article for?

  • All Planhat Users, whether you are new to Planhat or have been using Planhat for some time and would like to learn about changes introduced in early 2026

  • Anyone else who would like to learn more about Planhat's revenue offering

This article refers to new revenue features in Planhat, launching in early 2026, so you may not have access to them yet. Please speak with your Planhat CSM if you would like to discuss the rollout.

Introduction

Revenue is at the heart of all businesses. Planhat is a customer platform optimized for both pre-sales (CRM) and post-sales (CSP) activities, and that includes revenue. It's been designed for recurring revenue (subscriptions/licenses) - unlike some other tools that were built for simple one-off sales - although Planhat is fully compatible with non-recurring revenue (fees) too. Planhat is great for managing your new-business sales and also your renewals (and upgrades etc.).

πŸ“Œ Summary of key revenue features

  • Specialist data models for revenue

    • Deal - associated with a Company; used both before a sale (opportunity) and after a sale; can progress along stages in pipelines; generally have one or multiple Line Items linked to them

    • Line Item - associated with a Deal; either a Subscription (recurring revenue) or Fee (non-recurring revenue)

    • Product - located in the Product Catalog in the "Settings" Global Tool, these act as templates for Line Items; can be organized in Packages

  • Revenue reporting

    • Library of pre-built (yet configurable) System Reports

    • You can filter on Deals, Line Items and Products

    • You can choose whether to forecast based on "Open" and/or "Closed Won" Deals, and even select which model and field to use

  • Integrations

  • Settings

    • Customize how revenue data behaves in Planhat via a series of settings

    • For example, choose whether you work in MRR or ARR, and whether MRR/ARR or Total Value should take precedence

If you've been using Planhat for some time, note that in early 2026, we're releasing a series of changes to Planhat's revenue features, particularly regarding the data models ("object" equivalents).

πŸ“Œ Summary of revenue changes released early 2026

  • Introduction of the granular "line item" concept, so deals can have multiple separate line items, each associated with a different product

  • Changes in data models

    • Opportunity replaced with Deal

    • License replaced with Line Item, Product Type: Subscription

    • Sale replaced with Line Item, Product Type: Fee

    • Recurring and Non-Recurring Products (within Settings) replaced with new Product model, housed in an enhanced Product Catalog

    • Invoice model "soft deprecated" - not part of new data model structure (i.e. no in-built connections to Deal, Line Item or Product). It will still be available for some customers as required

  • Integrations (for Salesforce and HubSpot) updated to be fully compatible with new data models

  • Enhanced revenue reporting

    • Can filter on Deal, Line Item and Product, and combine multiple filters

    • Can choose whether to forecast based on "Open" and/or "Closed Won" Deals, and also which model/field to forecast on

πŸ“Œ Important to note

This update is being rolled out in stages, so at time of writing, you may have these features available in your Planhat tenant, or they may become available to you in future. Please speak with your Planhat CSM if you have any questions.

Let's take a look at some of these topics in further detail. We'll still be fairly brief in this article, but we'll link to additional documentation if you would like to learn more.


Data models

Overall structure

Data model

Description

Example

Company

Customer or prospect organization; top of hierarchy

Zoom

Deal

Sales opportunity or confirmed/lost revenue; can have Line Items

Renewal Deal for Zoom

Line Item

Subscription or Fee on a Deal

Subscription for Advanced Data on Renewal Deal for Zoom

Product

Template for a Line Item

Subscription for Advanced Data

πŸŽ₯ Quick video overview

You can watch a video about these revenue data models here.

Deal

Deal is the "parent" revenue data model; it typically has one or more Line Items (Subscriptions/Fees) associated with it (as "children"). Each Deal belongs to a specific Company (either a prospect or customer organization).

Deals are used for both potential revenue ("Open" Deals - sales opportunities) and also when revenue is confirmed as either won ("Closed Won" Deals) or lost ("Closed Lost" Deals). Deals can be new-business sales or renewals.

You can display Deals in Board Pages and "drag and drop" them between process stages in a pipeline.

Click the image to view it enlarged

πŸ“š Further reading

To learn more about the Deal data model, check out our separate article here.

To read about creating Deals and pipelines, see here.

Line Item

Within the overall Deal, you usually have one or more Line Items. Each Line Item represents a specific "item" or "unit of revenue": either recurring revenue (a license - "Subscription" in Line Items terms) or non-recurring revenue (a one-off sale - "Fee" in Line Item terms).

Although you can configure a Line Item from scratch for a Deal, you typically use a Product as a template. A key difference between the two is that a Product does not correspond to a Deal (e.g. "Enterprise Deployment"), whereas a Line Item belongs to a specific Deal (e.g. "Enterprise Deployment on Deal with Dell").

You can also add Line Items to a Deal in bulk, e.g. by adding a "Package" (which is a group of Products).

πŸ“š Further reading

To learn more about the Line Item data model, check out our separate article here.

Product

Products act as templates for Line Items. They are a way to improve efficiency and consistency, as you don't need to configure Line Items from scratch for each Deal.

Like Line Items, each Product is either a Subscription (recurring revenue) or a Fee (non-recurring revenue).

Unlike other data models, Products can be found in the Product Catalog, a specific part of the "Settings" Global Tool.

Click the image to view it enlarged

Products can be categorized using the "Packages" and "Color" fields (both shown in the screenshot above).

πŸ“š Further reading

To learn more about the Product data model, check out our separate article here.


Revenue reporting

System Reports: Pages for revenue

Planhat includes a library of pre-built (yet customizable) specialist reports, tailored for specific use cases, covering a whole range of different revenue reporting needs - these are the "System Report" Pages in upgraded Planhat (ws.planhat.com).

The available reports (Page types) are: Revenue Base, Renewal Rate, Bookings, Renewals and Invoices.

Having these reports as Page types means you can add multiples of the same report to the same View/Section, filtered for different team members, to quickly and easily compare revenue data of different portfolios.

πŸ“š Further reading

  • You can read an overview of each of the System Reports on revenue - what they are and why they are useful - in our separate article here

  • For further technical details, you can refer to another article here

Filtering on different models in System Reports

In early 2026, we are introducing multi-level filtering in System Reports. You can create Company filters, Deal filters, and Line Item filters - and they can be combined.

In the next screenshot you can see filters for different revenue models stacked together (plus a date range filter). As you can see, we show different icons for different filter types, to help you identify them at a glance.

Click the image to view it enlarged

πŸ“š Further reading

For more details on this multi-level revenue filtering, see here.

Forecasting settings within System Reports

There are also now (as of early 2026) enhanced configuration options for forecasting within the System Reports for revenue.

You choose:

  • "Forecast method" - do you want to forecast based on "Open" Deals, "Closed Won" Deals, or both?

  • If you select "Open Deals", you then choose whether you want to look at the Deal model or the Line Item model. Typically, when forecasting based on Open Deals, you'll most commonly select the Deal model

    • You then select (using the dropdown menus) which fields on that model (e.g. Deal) you would like to use for the forecasting

  • Alternatively, if you select "Closed Won Deal", you will find that this is specifically for the Line Item model (rather than the Deal model)

    • As with Open Deals though, you can select your choice of field to base the forecasting on, from the dropdown menu

πŸ“š Further reading

These different forecasting methods relate to different renewal pathways/processes. For more information on this, see here and here.


Settings

As well as the configuration panel for System Reports as we showed/discussed above, there are also various revenue settings within the "Settings" Global Tool for admins - including some new settings specific for Line Items etc.

Click the image to view it enlarged

One of the new parts of the revenue settings is the "Product Catalog" where Products are located, as we discussed earlier.

Did this answer your question?