Allocations are the financial labels clients use to track spend internally. They help answer key questions like: Who owns this cost? What type of cost is it? Which project does it belong to?
Conditional Logic for Allocations allows you to automatically control which allocation options appear based on predefined rules. This reduces errors, improves accuracy, and saves time when coding matters and invoices.
Why Use Conditional Logic? 🎯
Conditional Logic helps you:
✅ Reduce risk of incorrect coding
⏱️ Save time by introducing default options
By filtering allocation options based on matter attributes (e.g., department, entity, country), users only see valid combinations.
Who Can Use This Feature?
| Role | Access |
|---|---|
| Admins | Configure rule sets and logic in Admin Settings |
| Legal Ops / Attorneys / Matter Participants | Select allocations on matters (filtered by admin rules) |
Enabling Conditional Logic
Conditional Logic must be enabled for your instance.
📩 To enable this feature, contact your Customer Success Manager.
How to Set Up Conditional Logic
⚠️ We recommend starting with a few small examples before rolling out broadly.
Step 1: Access Allocation Rules
Navigate to:
Menu → Admin Settings → Allocations → Allocation Rules (Conditional Logic)
Step 2: Create a Rule Set
Click Add Rule Set and complete:
Name
Priority
Click Add Rule to define logic
Step 3: Define Rule Conditions
Rule Types Available:
Matter Category
Department
Country
Entity
Select a rule type and choose one or multiple condition values.
Example:
Department = Brand Protection
Country = United States
This rule will apply to all US matters within Brand Protection.
Step 4: Build Allocation Logic
After defining conditions, you configure what allocation options should appear.
Allocation fields appear in hierarchical order, based on your instance setup.
For example:
Cost Center
Entity Code
Brand
How it works:
Select the allowed Cost Center
Then select valid Entity Codes
Then select valid Brand options
Only the ticked combinations will appear to users.
If you do not tick any values at a level, then all options for that segment will appear.
Example: Hierarchical Filtering
| Allocation 1 | Allocation 2 | Allocation 3 |
|---|---|---|
| Stationery | Pen | Ballpoint |
| Stationery | Paper | Recycled |
If Allocation 1 = Stationery, Allocation 2 will only show Pen and Paper.
This prevents invalid accounting combinations.
Managing Rule Sets
From the Rules List, you can:
✅ Enable / Disable
✏️ Edit Name, Priority, or Logic
🗑️ Delete (with confirmation)
Important Notes ⚠️
Disabling an Allocation Segment
If you disable a segment used in logic, it breaks the configuration from that segment onward.
Example:
Current order:
A → B → C → D → E → F → G
If you disable Segment E:
Segments F and G break
Segments A–D remain intact
⚠️ All custom configuration from the disabled segment downward is lost.
Adding a New Segment
New segments are added to the bottom of the list to protect existing logic.
Example:
Current order:
A → B → C → D
You create Segment E →
A → B → C → D → E
If you move Segment E between B and C:
Segments C and D break
Segments A and B remain unaffected
⚠️ Changing segment order can damage existing configurations.
Need Help?
If you’d like assistance reviewing your allocation hierarchy or designing rule priorities:
📩 Contact your Customer Success Manager.