Accounting › Settlement & Allocation
Fixed Allocation Split
Where a driver is not appropriate: 40% to production, 35% to sales, 25% to admin, because that is what the board agreed.
Where to find it
- Module: Accounting
- Group: Close & Compliance
- Section: Settlement & Allocation
- Screen: Fixed Allocation Split
Address in the console: /accounting/allocation-receivers
List · 6 columns · 7 fields on its form · 1 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Segment | Text | segment_name |
| Line | Number | line_no |
| Type | Status | receiver_type |
| Receiver | Code | cost_center_code |
| % | Number | percentage |
| Portion | Number | portion |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Segment required | Choice | Looked up from existing records | |
| Line | Number | ||
| Receiver type | Choice | cost_center, profit_center, order, project | |
| Receiver | Choice | Looked up from existing records | |
| Or receiver code | Text | ||
| Percentage | Number | ||
| Portion | Number |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.