Allocation Runs
A residue above the threshold means the iteration gave up before converging, and the cost left over is stranded on the sender — so the run says so rather than letting it disappear.
Where to find it
- Module: Accounting
- Group: Close & Compliance
- Section: Settlement & Allocation
- Screen: Allocation Runs
Address in the console: /accounting/allocation-runs
Read-only list · 10 columns · 1 action
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
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 |
|---|---|---|
| Run | Code | run_no |
| Cycle | Code | cycle_code |
| Period | Code | period_code |
| Iterations | Number | iterations |
| Senders | Number | distinct_senders |
| Receivers | Number | distinct_receivers |
| Allocated | Amount | allocated_amount |
| Residue | Amount | residual_amount |
| Did not converge | Yes or no | did_not_converge |
| Status | Status | status |
What you can do here
Run cycles primary
Asks for: Period (YYYY-MM)* Cycle (blank = every active cycle, in order) Test run — calculate and post nothing
* required
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.