Data mappings connect your data sources to rows in your model. Most often that’s GL accounts from your accounting system, but it also covers other sources like FX rates and Google Sheets. Once mapped, the data flows in automatically every time Francis syncs.
How mappings work
Open the Mappings view to see all GL accounts from your connected accounting systems, along with accounts from any other data sources. Drag an account onto an existing row to map it. To create a new row, drag the account all the way to the row name area and release it.
You can bundle multiple accounts on a single row. This serves two purposes:
- Keeping the model clean. There are two approaches in Francis: mirror your chart of accounts 1:1, or bundle GL accounts into rows. Bundle by default. It keeps the model readable and lean. Charts of accounts are designed for accounting workflows, and that structure rarely needs to carry into the FP&A model. You can always inspect a row to see where the numbers come from.
- Matching GL accounts across entities. When you consolidate multiple entities, map equivalent GL accounts from each entity to the same row in Francis.
Rows and groups with at least one mapped account show a green connection indicator. No mapping shows gray.
Active and unused accounts
GL accounts in the Mappings view are split into two groups:
- Active: GL accounts with at least one journal entry to them. Francis notifies you to map them for completeness.
- Unused: GL accounts with no journal entries. No action required. If an entry is later booked to an unused account, it moves to the active group automatically.
The Mappings button shows a notification count for unmapped active accounts. Treat it as your to-do list.
The Mappings view also shows the last entry date for each account, which for some accounts can be far in the past. Map all active accounts to keep your historicals complete. For old or retired accounts, map them to an “Other” row to preserve historical accuracy without cluttering the model. You can also ignore an account, which clears the notification until a new entry is posted to it. Prefer mapping to an “Other” row over ignoring, since it keeps your historicals complete. Only ignore an account when you don’t want to map it and you’re sure it won’t be used again. For balance sheet accounts, which accumulate over time, only ignore ones with a zero balance.
When new GL accounts are created, or unused accounts start receiving entries, they appear in the Active section and trigger a notification. This way, your model stays complete even as your accounting system changes, since new activity always surfaces for mapping rather than slipping in unmapped.
Accounts from non-accounting data sources do not generate notifications, since they aren’t treated as a completeness checklist the way GL accounts are.
Map to top-level for breakdowns
When you break down a sheet, you map GL accounts to the template sheet at the top, and the data automatically flows to your sub-sheets based on your breakdown configuration. You cannot map to sub-sheets directly.
See in action
See mappings in practice in the Consolidation masterclass. 
