Published at: 2026-10-12
Configure budget consumption rules
Let business objects use budget by rule when expenses occur.
Overview
Enterprises consume budget in multiple scenarios, such as Campaigns consuming budget and dealers consuming budget. Different business objects occupy budget in different ways.
A consumption rule specifies who consumes, when to deduct, how much to deduct, and how to find the target Budget Sheet.
This article covers only rule configuration. It does not describe how downstream business objects submit documents.
Before you start
- The Budget Management app is already enabled
- You are a CRM administrator or budget finance user
- The target budget type and expense budget sheet are ready
- You already know the consumption object, deduction method, and amount field
❗
For the same business object under the same Record Type, only one enabled consumption rule can exist.
Configuration steps
View the consumption rule list
- In the web main navigation, open Budget Management.
- Go to Budget Settings > Budget Consumption Rules.
- Review the objects and scenarios already covered by existing rules.

Create a budget consumption rule
- In the list, click New.
- In Global Settings, specify the overall rule, including the consumption object, Consumption Method, and how to find the Budget Sheet to occupy.
- In Node Settings, add the configuration required by each process node.
- Submit and save the rule.
Campaigns, dealer scenarios, and similar modules are used only as rule configuration objects. This manual does not describe operations in those modules.

Manually select a Budget Sheet
When the occupation method is to select a Budget Sheet manually on the business object:
When freezing
- Select the object used to create the budget relationship. Values come from the consumption object and its Detail Object.
- Select the field that represents the Expense Budget Sheet. The Field Type must be Lookup, and it must look up the preset Expense Budget Sheet.
- Select the field that represents the frozen amount. The Field Type must be amount.

When deducting
- Select the field that represents the deduction amount. The Field Type must be amount.

Automatically match a Budget Sheet
When the occupation method is automatic matching by mapping rules:
- In Freeze/Deduct, set:
- Trigger condition: The condition that must be met before budget is consumed
- Source field of the deduction amount: The Field Type must be amount.

- In Expense allocation, set:
- Allocation Ratio: The sum of all allocation ratios must equal 100%
- Budget Sheet mapping: Map Budget Sheet planning dimensions to consumption business fields
Mapping Field Type values must match:
- Budget Department maps to a department-type field
- Budget period maps by planning period. For example, when you plan by month, map the budget period year-month
- Budget dimensions map by planning dimensions. For example, when dealer and budget subject are selected, map fields of the matching types

View rule details
- In the list, edit and view the rule.
Enable, disable, edit, and delete
| Action | Condition |
|---|---|
| Edit | The rule is not associated with data, and the status is disabled |
| Enable | The current status is disabled |
| Disable | The current status is enabled |
| Delete | The status is disabled, and the rule is not associated with Business Data |
Verification
- Confirm that the rule is visible in the Budget Consumption Rules list.
- After you enable the rule, use one test business record to trigger freeze or deduction.
- Reconcile the occupied result on the matching Expense Budget Sheet and Income and Expense Entries.
Notes
- Deduction timing and amount source determine when and how much to deduct. Incorrect configuration causes over-deduction or missed deduction.
- Expense allocation writes one business expense into multiple budget sheets. Confirm the allocation grain and Allocation Ratio before you save.
- After a rule is enabled, applicable Business Data occupies budget. Finish and confirm the configuration while the rule is disabled.
- Do not change nodes of a rule that is already associated with data.