Cost Control
You can bring a budget account into the set, and you know why the dialog sometimes has nothing to offer.
Most accounts arrive on their own, brought in by an accounting import that matched a booking to them. **Add Account** is for the ones that do not — an account you want to forecast against before anything has been booked to it.
From the toolbar.
**Reference account** is the account the new row will sit next to, and you say whether it goes **Above** or **Below**.
This is positional only. It creates no relationship between the two accounts and no rollup — it is how the set knows where to put the row.
**Account No** and **New Account Name**.
Use the number the budget uses. Account numbers are how an accounting import finds its target, so a set whose numbers match the budget's — and the accounting system's — imports cleanly and one that invents its own does not — see [set up an import mapping set](/kb/article/set-up-an-import-mapping-set).
The dialog says so: *No reference account is available yet. Add an account in Budgeting first.*
It means the set has nothing to position against — the budget itself has no accounts to anchor to. The fix is in **Budgeting**, not here: add the account to the budget, then come back.
This is the module being consistent about where things are authored. Cost control tracks accounts; it does not invent the budget structure.
**Remember the budget is locked.** If adding that account to the budget is refused, it is because this set locked it. [How a cost control set relates to a budget](/kb/article/how-a-cost-control-set-relates-to-a-budget) covers the way round it.
Markdown