Understand how drivers in Jirav impact different Versions and Plans
Jirav constructs the financial model, reflecting your company's COA and historical data once you have connected and synced your actuals from your financial system.
Sales actuals for reporting and forecasting are imported into the system. The import populates the database and becomes a reference point for drivers.
The company's workforce is imported into the system to generate an additional reference point for drivers as well as workforce reporting.
Custom Lines give you the ability to calculate values using drivers that would not ordinarily be in your financial systems, things such as website visitors or average expense per headcount.
The image below shows the flow of how the global drivers and plan drivers impact the Jirav model.
Note that in the image above that each "Model" box has a different name, each name is either a Version or a Plan within Jirav.
Versions are Actuals and Goals. The Actuals are populated with your historical financial information through the Actual imports of Financial information, Workforce, and Sales. Goals are high level targets that you input manually into Jirav.
Plans are a Pro account feature and represent scenarios for your business as well as budgets that have been approved. Refer to our Plan Management article for further information.
The Custom Lines will reflect the same value or calculation from the Global Driver across all Plans and Versions. For example, a Global Driver that calculates average expense per headcount would calculate the historical value in the Actuals Version and also perform the same calculation within each of the Plans.
This gives you the ability to see how one Plan compares to another Plan and how the two Plans compare against your Actuals to determine if the expenses are aggressive, conservative, or within expectation based on historical performance.