> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Changing the group chart from a month

> Move local accounts and dimension items to new group accounts and items from a chosen month while earlier months keep reporting as they were reported.

When you restructure the group chart of accounts, for example at the start of a fiscal year, you can move local
accounts to new group accounts from a chosen month. Months before it keep reporting under the group accounts they were
reported under, so closed and distributed reports don't change. Local dimension items move to new group dimension
items the same way.

## Availability

| Attribute | Value |
| - | - |
| Roles | Members with edit access can draft, save and revert changes. A change that restates months closed in Control needs an organization Owner or Admin. Viewers can see the history. |
| Availability | Every workspace. If the **Timeline** column is hidden, select **Show timeline** above the grid. |
| Scope | Profit and loss (P\&L) and balance sheet accounts. Dimension items, for P\&L postings: balance sheet postings always use the item they map to today. See [Balance sheet accounts](#balance-sheet-accounts) and [Dimension items](#dimension-items). |

## What "as reported" means

Control remembers which group account each local account mapped to in each month. A statement shows every month on the
group account the local account was mapped to at the time: **as reported**.

Example (illustrative values): local account 3000 maps to group account 4000 until December 2026 and to 4100 from
January 2027. A 2026 P\&L still shows 3000's postings on 4000; from January 2027 they appear on 4100.

To compare periods in one structure, choose **Display → Account mapping → Current structure** on any statement,
balance sheets included. Every month then reports on today's group accounts. **Restate prior year to current
structure** restates only the year-over-year comparison. Budget pages always use the current structure. The basis is
part of the statement's link and its saved views, so a link opens in the basis it was copied in.

> [!NOTE]
>
> A change in the middle of a year splits year-to-date and full-year figures between the old and the new group account.
> That is what as reported means. Use the current structure when you need comparable figures.

## Change a mapping

Open [**Group accounts**](https://app.control.dev/consolidation/entities/chart-of-accounts) (Configuration → Entities → Local → Group accounts) and select an account's cell in the **Group account** column.
In the dialog, choose the new group account, or create one with the **+** next to the list, and when it applies:

| Applies to | What it changes | Use it to |
| - | - | - |
| **From a month** | That month and every later one, once you save. Earlier months keep reporting as they were reported. | Restructure the group chart. |
| **Whole history** | Every month, including the account's mapping history, once you save. | Correct a mapping that was wrong from the start. |

The dialog starts on **From a month**, at the first open month or after the account's last change, when the account's
entity has months closed in Control or the account has earlier mappings. Otherwise it starts on **Whole history**. A change that restates months closed in
Control follows the [closed-month rules](#months-closed-in-control); Save asks for the reason.

An account that is unmapped now has no dialog: choose its group account in the cell. Mapping it maps every month, so
there is nothing to change from a month. **Remove mapping** in the dialog unmaps an account.

## Change mappings from a month

1. Select the account's cell in the **Group account** column and choose the new group account.
2. Keep **From a month** and pick the first month of the new structure. Control suggests the first open month, the next
   quarter starts, next January and the month the current mapping started, and marks months closed in Control. A month
   at or before an earlier change replaces that change, and the dialog says so; picking the month the mapping started
   fixes a wrong remap.
3. Read the checks in the dialog. It checks the change as you choose, and **Apply** stays off while a blocker stands, for
   example a move out of the cash accounts of a cash flow layout. Fix that first, or choose another group account. If a
   draft is already open for the month, the dialog says so and your change joins it, because a draft saves as a whole.
   Select **Keep this change in a separate draft** to save it on its own; this is on by default when that draft has a
   blocker.
4. Select **Apply**. The cell reads, for example, "4100 - Sales was 4000 · from Jan 2027": "was" is the group account the
   account mapped to in the month before. An account that was never mapped reads "was unmapped · every month". Use the
   row's undo button to take a change back.
5. Change more accounts the same way. All pending changes start in the same month, so the next dialogs stay on that
   month until you save or discard them.
6. Review the bar under the grid, for example **3 pending changes · From Jan 2027**. Your changes are kept in a draft, so
   they survive a reload and colleagues see the same draft. After a reload, the notice above the grid has **Open draft**.
7. Select **Show checks** to see what still refers to the old group accounts: elimination rules, rate exceptions,
   budgets, statement layouts, cash flow rows, group settings, dashboards and group postings. You must resolve
   blockers. Some findings offer a fix, such as copying an elimination rule or a rate exception to the new account.
8. Select **Save**. A change for a month that has started is published at once. A change for a later month is scheduled.

An account can have any number of periods. Add them one change at a time, oldest first, saving each before the next: a
month at or before an earlier change replaces it. The dialog starts after the account's last change, so adding a period
is the default. An account is in only one open draft or scheduled change at a time, so at most one future period waits at
a time, and a change that is still in a draft has to be saved or removed first. **Remove from draft** in the dialog takes
the account out; **Unschedule** on Mapping changes turns a scheduled change back into a draft.

To change many accounts at once, paste a column of group accounts into the **Group account** column: go to the first
cell with the arrow keys, or select it and close the dialog with Esc, then paste. To paste one group account into several
cells, select them by dragging, then paste. A paste restates the whole history, with no question: the changes wait under
the **Whole history** bar until you select **Save**. While a draft is open it stays as it is, so save or discard the draft
first. To change an account from a month, select its cell, or ask Control chat. A pasted legacy group
account is taken only with **Show legacy** on, and an archived one never, as in the pickers. Unmapped accounts in a paste
map at once, as in their cells. A blank cell in a paste leaves the account's mapping as it is.

To remove a mapping, select the cell, or several in the column, and press Delete or Backspace, or select **Remove mapping**
in the dialog. This applies at once and removes the mapping in every month, earlier mappings included, so there is nothing to revert: map the
account again to undo it. If months are closed in Control, you give a reason first. On a cell with a pending change,
Delete takes that change back instead; press it again to remove the mapping.

To verify, find the account under **Show → All accounts**: it reads "Jan 2027 – ∞ In effect since Jan 2027 (was 4000)".
While a draft or a scheduled change moves the account, the cell also has a dashed chip such as "4100 · Jan 2027",
whose tooltip names the change. In a narrow column the cell keeps "was 4000" and the tooltip has the full text. Every
change is listed on [**Mapping changes**](https://app.control.dev/consolidation/entities/mapping-changes) (Configuration → Entities → Mapping changes).

**Whole history** changes also stay pending under a bar with **Discard**, **Show checks** and **Save**, and Save applies
them as one correction. Leaving the page with pending changes asks first, since nothing is saved until you select Save.

The **Mapping history** column lists an account's earlier mappings. It's hidden by default, like **Active period**: turn
either on from any column header's **⋮ → Choose Columns**. To change an earlier mapping, use **From a month** from that
month, or revert the change that made it on Mapping changes.

## Balance sheet accounts

A balance sheet account changes from a month the same way. Its balance moves with it:

* **Mapping transfer.** At the change month Control moves the account's balance from the old group account to the new
  one with a non-cash transfer on a hidden system account per entity, at the same counterparty and dimension detail as
  the balance. From that month the old group account holds nothing for the account and the new one holds the whole
  balance; earlier month-ends don't change. The drilldown shows the transfer as a **Mapping transfer** line per entity.
* **Cash flow.** The transfer isn't a cash movement: the cash flow statement leaves it out of operating, investing and
  financing activity and out of the currency effect.
* **Current structure.** In the current structure the transfers aren't shown: every month reports on today's account.
* **Postings to the old group account.** Group-level postings made directly to the old account, such as manual
  journals and eliminations, are part of its balance, also when they name an entity. When nothing maps to the old
  account from the change month, Show checks shows its group-level balance at the end of the month before the change
  and offers **Move group-level balance to *new account* from *month***; when its accounts move to several new
  accounts, you pick one. While another local account still maps to the old account from that month, the balance
  stays on it and nothing is offered: the balance belongs to no account. With the move, the change moves the old
  account's whole group-level balance at the change month, so the old account is 0 from then, except for group-level
  postings dated from the change month, which stay on it (Show checks lists them). **Keep it on *old account*** takes
  the choice back.
* **Layouts.** A balance sheet layout must still place a legacy account with history: months before the change report
  balances on it. The layout editor lists the legacy balance sheet accounts the layout misses.

Rules that keep the figures consistent, checked when you save:

* An account stays on its side of the statements: a P\&L account maps to P\&L group accounts, a balance sheet account to
  balance sheet group accounts.
* Every month of an account's history translates at the same consolidation rate type, rate exceptions included. In an
  entity whose currency differs from the group currency, a change can't move a historical-rate account or move an
  account between liabilities and equity. A rate exception change, or a change of a default rate type, that would break
  this for a published change is refused and names the accounts.
* If the old group account is a cash account in the cash flow settings, the new one must be too.

## Dimension items

Open [**Group dimensions**](https://app.control.dev/consolidation/entities/dimensions) (Configuration → Entities → Local → Group dimensions). The tab has the same dialog, save bar,
**Show** filter and timeline as the accounts tab.

* **P\&L postings only.** A change from a month applies to P\&L postings: they report under the group item in effect in
  their month. Balance sheet postings use the group item the local item maps to today, in every month.
* **One group dimension.** Every month of a local item's history maps into the same group dimension. To move an item to
  another group dimension, change its **Whole history**.
* **Checks.** Show checks lists layout rows filtered on the old item, allocation keys, budgets and dashboards. Dimension
  checks are warnings; they don't offer fixes.
* [**Group dimensions**](https://app.control.dev/consolidation/group/dimensions) (Configuration → Group → Group dimensions)

  shows each group item's status, as the group chart does for accounts.

## Scheduled changes

A scheduled change publishes on its own shortly after midnight UTC on the first day of its month, if its checks still
give the same result. Balances read from the books, such as the balance a balance sheet account moves, are taken
again when it publishes. If something else changed in the meantime, such as a new elimination rule on the old account,
a newly closed month, or a group-level balance that appeared on an old balance sheet account with no choice to move or
keep it, it stays unpublished. A group-level balance that was there when you scheduled the change and is 0 by then
doesn't hold it: there is nothing left to move. Mapping changes and the mapping grid show the reason a change stays
unpublished. Select **Unschedule** to turn the change back into a draft, review the checks and save it again. You also
unschedule a change to edit it.

A draft that you leave unsaved never publishes on its own. The grid lists it above the rows with **Open draft**, as
**Ready to publish** once its month starts.

## Months closed in Control

A month counts as closed when a manual close in Control covers it; see
[Track closed accounting periods](https://control-dev.mintlify.site/product-docs/integrations/closed-periods.md). A lock in the accounting system alone
doesn't count.

Any change to an existing mapping of an account or a dimension item in a month closed in Control restates that month,
whether or not it has postings there. It needs an organization Owner or Admin, a confirmation and a reason, whoever or
whatever makes it:

* a change from a closed month, a **Whole history** change or a revert;
* a change through the API or a bulk update, removing a mapping, or accepting an AI mapping suggestion;
* moving a group-level balance in a published change's follow-ups from a closed month;
* deleting a group account or group item that accounts or items map to in those months.

Without them, Control refuses the change and suggests changing it from the first open month instead. Deleting such a group account on **Group chart of accounts**, or a group item or a whole
group dimension on **Group dimensions**, asks in the same prompt. A delete has no first-open-month option: to keep the
closed months as they are, remap what maps to it from that month first. Members who aren't an Owner or Admin see who
can make the change instead of the prompt. The reason is kept with the change; for a cleared mapping, which has no
change to keep, it is kept in the audit log. Mapping an account or item that is unmapped now needs none of this, also
when an earlier change cleared its mapping. Control chat, AI tools and automations never restate closed months; see
[Changes by AI assistants](#changes-by-ai-assistants).

**Undoing an AI auto-mapping.** When the AI mapped an account or item after the month was closed in Control and nothing
has changed its mapping since, the closed months were reported without that mapping. Undoing it or rejecting it then
needs none of the above. Otherwise rejecting it needs them, and the undo from Control chat or a system action leaves the
mapping as it is and says so.

> [!NOTE]
>
> One thing in closed months still changes without any of this: balance sheet splits by dimension. Balance sheet
> postings use the group item a local item maps to today, so remapping a dimension item, even from the first open month,
> changes how closed months split by dimension on the balance sheet. Their totals don't change.

## After you save

* **Statements** in Control show the new mapping at once. Automatic eliminations, the Google Sheets and Excel
  connectors and Parquet exports follow after the next consolidation run. Until it finishes, the grid and Mapping
  changes show **Consolidation running** (for at most 30 minutes).
* **Follow-ups.** On Mapping changes, a published change has **Follow-ups**: what still points at the old accounts, with
  fixes to move a budget's plan values to the new account from the change month, to point dashboard widgets at the
  new account, and to copy an elimination rule or a rate exception to the new account when that wasn't done before
  saving. A fix is offered only when the new account is unambiguous. A group-level balance left on an old balance
  sheet account is listed too, with **Move group-level balance**. The move applies from the change month at once; when
  that month is closed in Control for an entity whose accounts the change moved, it asks for a reason and needs an
  Owner or Admin.
* **Variance Analysis** warns when a budget has plan values on a group account that nothing maps to in those months.
  Members who can edit can move the values once the change is published; the warning links to Mapping changes.

## Group account statuses

On [**Group chart of accounts**](https://app.control.dev/consolidation/group/chart-of-accounts) (Configuration → Group → Group chart of accounts),
each account has a status and the columns **Mapped now** (local accounts mapped to it now), **Mapped earlier** (local
accounts mapped to it in earlier months) and **Mapped through** (the last month anything maps to it):

| Status | Meaning |
| - | - |
| **Active** | A local account maps to it now, a draft or scheduled change maps to it, or group settings use it. |
| **Legacy since *month*** | Only months before that month report under it. |
| **Active until *month*** | Still in use through that month. Scheduled changes move every account away from it after that. |
| **Unused** | No local account maps to it, now or in earlier months. |
| **Archived** | Nothing new can map to it. Earlier months that mapped to it still report under it. |

If a scheduled change is still unpublished once its month starts (see [Scheduled changes](#scheduled-changes)), the
account reads **Active** until the change publishes.

* **Filter.** **In use** (the default), **Legacy**, **Unused** or **All**. While no account is in use, the page opens
  on **All**. An account that turns legacy in a later month stays under In use until that month; archived accounts are
  listed under Legacy. The footer says how many accounts the filter hides.
* **Details.** The details button opens a panel with the account's mapping range, the accounts that replaced it, the
  local accounts that map to it now or earlier, and what still points at it. Delete stays disabled while that check
  runs, when it fails, and while mapping history or a pending change uses the account; archive the account instead.
* **Pickers.** Legacy accounts are hidden from mapping, rule and rate exception pickers unless you turn on **Show
  legacy**, except in eliminations dated in months the account was still mapped. Archived accounts are never offered.
  Pasting into the mapping grid follows the same rule. Transaction and dashboard account pickers, and the account list
  of the layout editor for Functional P\&L and custom reports, list legacy and archived accounts last, under **Legacy**,
  since earlier months still report under them.
* **Mapping grid.** An account mapped to a legacy or archived group account shows the status next to it. A banner says
  how many accounts still map to a legacy or archived account with no change moving them; scheduling the move clears
  it.
* **Statements.** **Display → Hide legacy accounts with no value in range** is on by default.

## Review the history

* The **Timeline** column shows each account's mappings by month (**Hide timeline** turns it off). Earlier mappings are grey,
  the current one is green (amber when its group account is legacy) and drafts and scheduled changes are dashed blue.
  Months closed in Control are shaded and months before an entity's first posting are hatched. The header counts the
  mapping changes in each month.
* **Show → Scheduled changes** lists accounts with a pending change from a month; **Changed before** lists accounts
  with earlier mappings. The filter appears once there are any.
* Check **Include all periods** in the grid's **⋯** menu before **Export CSV** to get a row per mapping period, with
  **Mapping From** and **Mapping Through**.
* In the statement layout editor, **Mappings: As reported / Current** shows which local accounts sit under each group
  account. **Has transactions** counts postings in every month an account mapped to the group account.

## Revert a change

On Mapping changes, select **Revert** on a published change and give a reason. Its accounts go back to the mappings
they had before, and a group-level balance the change moved stays on the old account again. An account changed again
since then blocks the revert, and the dialog lists it.

A revert doesn't undo the fixes: moved plan values and re-pointed dashboard widgets stay on the new account, and the
reverted change lists them. Rules copied to the new account also stay. Elimination rules that the change ended are
restored, unless they were edited since or another rule on the old account now covers those months.

## Changes by AI assistants

* **Control chat** proposes mapping changes of accounts and dimension items, to the current mapping, from a month or
  for the whole history, and shows what would change; nothing is saved until you confirm. When a balance sheet change leaves a group-level balance on an old
  account, the confirmation asks whether to move it. A change that restates months closed in Control can't be
  confirmed in chat. An Owner or Admin saves it from the mapping grid.
* **AI tools connected to Control and automations.** When one changes the current mapping of an account or a dimension
  item mapped in months closed in Control, Control applies the change from the first open month instead. It
  appears on Mapping changes as "Agent remap from *month*" and can be reverted. For a balance sheet account, the old
  group account's group-level balance moves too, but only when every local account that mapped to the old account
  moved to the same new account, in this change or an earlier one. Otherwise, for example when another account moved
  from it to a different account earlier, the change's follow-ups list it for a person to decide. If Control refuses
  the remap, the mapping stays as it was and the tool gets an error. An AI tool can't clear such a mapping.
* **Copying local dimensions to the group.** The automatic copy of local dimension items to group dimension items
  changes an item mapped in closed months from the first open month too. The change appears on Mapping changes as
  "Automatic copy of local dimensions from *month*", with the person who ran the copy when a person did. It leaves an
  item on its mapping when the change would move it out of the group dimension its history is in.

## Limitations

* Dimension items change from a month for P\&L postings only. Balance sheet postings use today's group item in every
  month.
* The Google Sheets and Excel connectors and Parquet exports always use the as-reported mapping.
* Budgets keep today's structure. Plan values on a group account don't move by themselves; use the follow-up.
* Postings made directly to the old group account, such as manual journals and manual eliminations, stay on it in
  their month; Show checks lists the ones dated from the change month. Only on a balance sheet account can the change
  move its group-level balance (see [Balance sheet accounts](#balance-sheet-accounts)).
* A moved group-level balance doesn't show in drilldowns and transaction lists filtered by a dimension, or in the
  consolidation run's dimension breakdowns: there it stays on the old account.
* A posting reversed after the change month lands on the old account and its reversal on the new one. Late postings
  into months before the change land on the old account.
* An account or item can be in only one open draft or scheduled change at a time.
* History belongs to the local account. If the accounting system renumbers an account, the new account starts without
  history.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.