Cost Control
You know why the cost control grid is shorter than the budget, and how to bring an account into it.
**The cost control grid shows only the accounts the set is tracking.** It is legitimately shorter than the budget it sits on, and nothing on screen explains the gap — which is why it is worth stating plainly.
A set is a tracking layer, not a mirror. Carrying every account in a 400-line budget from day one would bury the twenty that are actually moving this month under hundreds of untouched rows.
So an account joins the set when there is something to track on it.
Side by side, the budget is longer. That is the expected state, not a sign the set is broken or that an import failed.
If a specific account is missing, the question is not *where did it go* but *is this set tracking it yet*.
Use **Add Account**, positioning the new row above or below an existing one. The account has to exist in the budget first — the dialog says so itself when there is nothing to anchor to: *No reference account is available yet. Add an account in Budgeting first.*
[Add an account to a set](/kb/article/add-an-account-to-a-set) is the way in.
An accounting import that matches a booking to a budget account brings that account into the set as part of importing. In practice this is how most sets fill up — you do not curate the list, the bookings do.
Lines the import cannot match go into an account called **Unmapped** instead, which is a real account sitting in the set until somebody moves those items out of it — see [match accounts, effects and companies](/kb/article/match-accounts-effects-and-companies).
Markdown