Account mapping is the correspondence between each account in an entity's local chart of accounts and the group account in which it is reported. It lets entities with different charts be consolidated without reclassifying entries by hand every month.
What it includes
A table with two columns: local account (code and name in the ERP) and group account. Several local accounts can map to the same group account; a local account never maps to two. For accounts that mix natures, the mapping can be by account plus analytical dimension.
Example with numbers
The Spanish entity has account 6290001 "Software and licences" with 4,000 a month and 6290002 "Hosting" with 1,500. The Mexican entity has 5105-003 "Technology services" with 90,000 MXN. All three map to the group account "Technology". At an exchange rate of 0.05, consolidated technology: 4,000 + 1,500 + 4,500 = 10,000 EUR.
How Fibady does it
Mapping is done once per entity, between 1 and 4 hours depending on the size of the chart, with suggestions by name and code. From then on every new ERP entry lands in its group account, and new unmapped local accounts are flagged before the month is closed.