Multi project budgets allow a single project in Rocketlane to have more than one budget, each with its own billing method, revenue recognition method, and team. This is useful when a project contains multiple commercial components, for example implementation, support, and change orders, all under one project.
This article explains how Multi budgets work, how they affect other modules, and how to configure them.
Overview
In the default setup, each project has a single budget. With Multi budgets enabled:
A project can have multiple budgets
Each budget can have its own billing type and revenue recognition method
Each budget can have its own team members
Tasks and phases can be linked to specific budgets
Time, costs, and revenue roll up correctly per budget and per project
All budgets in a project share the same project currency.
Key Concepts
Project and Budget Relationship
A project has:
One currency
One set of overall settings
Under that project, there can be multiple budgets, for example:
Discovery
Solutioning
Implementation
Change Order 1
Each budget defines:
Billing method and revenue recognition method
Start and end dates
Budget status (proposed, active, completed, or custom)
Custom fields configured at budget level
A default budget can be defined. The default is used to prefill forms where a specific budget is not selected.
Budget Team Members
Each budget has its own list of team members:
Only budget members can:
Be allocated against that budget in Resource Management
Track time to that budget (based on settings)
Have expenses contribute cost to that budget
This prevents budget consumption by the wrong team or role.
Task and Phase Budgets
Tasks and phases can be associated with one or more budgets:
When time, allocations, or expenses are recorded against a task or phase, the linked budget determines where cost and revenue are applied.
If a task or phase has only one budget associated, that budget can be prefilled in time and expense workflows.
Budget filters in the project plan can be used to show only tasks belonging to a specific budget, which can behave similarly to a subproject view.
Permissions and RBAC
Multi budgets respect the organization’s RBAC model.
Key behaviors:
Budget membership limits who can:
Track time against that budget
Record expenses against that budget
Receive allocations from that budget
Additional permissions can control whether a team member is allowed to change the selected budget while tracking time or creating expenses.
Existing project level access rules apply alongside these budget level controls.