Customer Module
<aside>
The Revenue Event calculates your income by combining customer or sales counts from upstream with pricing information. It can reference either a Pricing Event for fixed product prices or an Average Order Value Event for more flexible, spend-based modeling.
</aside>
This event takes care of applying prices to the number of purchases or users and pushes the resulting revenue into your selected income ledger — giving you accurate, time-based revenue projections for each product, service, or customer cohort.
Let’s say you’re modeling revenue for an EV charging company. You’ve already set up a Customer Event to track how many units are sold each month, and a Pricing Event that defines the sale price of each charging station.
The Revenue Event brings these together — multiplying the number of sales by the unit price to calculate total revenue over time. If you were using an Average Order Value instead (like in an online store with varying cart sizes), the Revenue Event would use that input instead of fixed pricing to generate your income stream.
In this mode, you select a specific customer cohort to pull in sales or user data from, and pair it with a Pricing Event to calculate revenue.
By default, the Revenue Event will inherit the start and end dates from the selected customer cohort, but you can override these if you need revenue to begin or end on a different schedule.
The resulting revenue is pushed into your chosen Income ledger or subledger, giving you full control over how revenue is categorized and tracked in your financial model.
This functionality is not live yet.