Cost Control
You can refile cost items onto the right account, and you know what the warning about paid items means.
Bookings land on the wrong account routinely — a mis-keyed code in accounting, a mapping that was not set up yet, or an import that could not match at all and put everything in **Unmapped**.
In the Cost Items panel or, for anything spanning accounts, the [Cost Item List](/kb/article/work-with-the-cost-item-list). Several at once is fine.
**Move** in the toolbar opens **Move Cost Item**.
**Target Budget Account** — the account the items should have been on.
If any selected item is already paid you get:
*N of the selected items are already paid — moving them will change which Budget Account reports their actuals.*
This is not a refusal, and it is not really about cost control. A paid item is an **actual**: it has left the production, and downstream — cash flow, reporting, anything reading what was really spent where — attributes it to whichever account holds it.
Moving it therefore rewrites history, correctly or incorrectly:
- **Correctly**, if the item was misfiled and the actual belongs elsewhere. That is the whole point. - **Incorrectly**, if you are tidying the current picture and the item genuinely was paid against the old account.
The warning exists so you make that call deliberately rather than discovering later that a closed period moved.
An import puts every line it could not match into an account called **Unmapped**, after telling you how many and asking whether to continue. Those items are not lost — they are parked.
Clearing that account is this procedure: open the Cost Item List, filter to Unmapped, select and move each group to its real account.
Then fix the cause, or next period's import parks the same lines again — see [set up an import mapping set](/kb/article/set-up-an-import-mapping-set).
Markdown