Mapping is the step that connects your General Ledger Accounts (GLAs) to the classes in your reporting structure. This article covers how to map for the Profit & Loss (P&L) and Balance Sheet (BS), how the Cash Flow Statement (CFS) mapping works via references, and how to verify a complete mapping.

For configuring the reporting structure itself (adding, removing, or repositioning classes), see Structure.

Each GLA (also referred to as *grootboekrekening* / GBR) needs to be assigned to a class in your reporting structure. Mapping rules:

By default, the left table is filtered to show only unmapped GLAs. To see all GLAs (or those mapped to a specific class), open the Filter (top right) and change the Mapping dropdown to All or a specific class.

To remove a mapping, click the × button on the mapping pill next to the GLA.

Once you've mapped, click Refresh at the top right of the right-hand table to update the numbers in the Management report preview. This lets you verify the report reflects the mapping as you expected.

GLAs mapped to the credit side of the Balance Sheet (Liabilities and Equity) are automatically inverted on display — negative ledger values are shown as positive. This way, the credit side of the Balance Sheet always shows positive figures, matching standard financial-statement presentation.

You don't need to flip signs manually; Finstack handles this based on which side of the structure the class lives in.

For the CFS, you don't map individual GLAs. Instead, the CFS is built from references to the P&L and the Balance Sheet:

Open Setup → Mapping and select the Cash Flow tab. On the left, you see the BS and P&L structures with checkboxes. On the right, the CFS structure shows the references you've assigned (e.g., EBITDA references Services, Subscriptions, COGS, Support, Personnel, etc.; Δ Debtors references Debtors from Current Assets).

To map: select one or more items on the left (BS or P&L class), then click the CFS line on the right to assign the reference.

To get Cash Flow from investments separately from Cash flow from operations, the following GLAs must be separated in your balance sheet structure using separate classes:

If investments and depreciation aren't separated in the structure, the CFS cannot distinguish them. To split them, adjust your balance sheet structure in Setup → Structure first.

Cash GLAs references the Cash class on the Balance Sheet. This makes the CFS reconcile back to the Balance Sheet — the calculated cash movement should equal the actual change in your Cash position.

The Difference line in the CFS should sum to 0 once everything is mapped correctly. A non-zero Difference points to incomplete mapping in either the BS or P&L.

For P&L and BS mapping, look for:

For Cash flow statement mapping:

Click the download icon at the top right of the Mapping page to export your current mapping configuration.

For every GLA, the values for the current and previous month are shown. Click either cell to drill down to the underlying entries:

Yes. The filter (top right) is set to Unmapped by default. Open the Filter, change the Mapping dropdown to All or to a specific mapped class, and apply.

No, Finstack doesn't support importing a mapping file. If you already have a mapping documented in Excel or another tool, the most efficient way is to open that file alongside Finstack on your screen — you can then compare line by line and reproduce the same mapping in Finstack quickly.

By default, the Mapping filter excludes empty ledgers (GLAs with no transactions). Use the toggle in the Filter panel to include empty or newly created GLAs.

Hover the icon to the left of the structure in Setup → Mapping to see which statement has an incomplete mapping. Then switch to that statement's tab and use the Unmapped filter to find and map the remaining GLAs. Unmapped accounts typically cause the Balance Sheet not to balance.

Most ERPs don't notify Finstack when account numbers change or accounts move between statements. To pick up these changes, request a full import via the chat interface within Finstack.

When a GLA gets a new number or moves from P&L to BS (or vice versa), it appears in Finstack as a new GLA — the old number may still be visible but without transactions. You need to map the new one, and check that any Intercompany eliminations that referenced the old GLA are updated to the new one as well.

The GLA may not have had recent activity. Drill down on the GLA's value and adjust the calendar to look further back. If the GLA is no longer in active use, map it to a generic line in your statement so it doesn't sit unmapped.

This usually means the GLA was moved between statements in your ERP (e.g., from P&L to BS), but Finstack still holds the old assignment because most ERPs don't notify Finstack when such changes happen.

When a GLA moves between statements — or gets a new account number — Finstack treats it as a new GLA. The old GLA may still appear in Mapping, just without transactions. To fix the position:

Most ERPs do not indicate when such changes have happened. Request a full import via the chat interface within Finstack to load the latest configuration.

When a GLA has a new number (account_id) or it has moved from P&L to BS or vice versa, it will be reflected as a new GLA — and the 'old' number may still appear, but without transactions. The new GLA needs to be mapped again.

Be aware that all changes also have to be manually corrected in the configuration of Intercompany eliminations.