What it does
You record the movement once, with the account from the main book. When someone queries the secondary book, Fail Fast shows the target account instead, with its own code and its own name. The movement does not change. How it reads in that book does. A mapping changes the account, not its name. If you also want it shown under a different name, configure that in account names by book: the homologated name takes priority over the target account’s name.Create a mapping
1
Open the screen
Go to Account Book Mapping in the accounting configuration and click New.
2
Pick the source account
Under Source account, find the account from the main book you want to translate.
3
Pick the target book
Under Target book, choose the secondary book where the account should read differently. You cannot pick the main book: a mapping always describes a secondary book.
4
Pick the target account
Under Target account, find the account that book should show. It has to be an account of your company and different from the source account.
5
Leave it active and save
Is active stays at Yes. Save.
Rules you will run into
- The target book is never the main book. A mapping describes how a secondary book reads the main one, not the other way round.
- Source and target account must be different. Mapping an account to itself does nothing and the app rejects it.
- One mapping per source account and target book. An account cannot have two targets in the same book.
- The target account cannot be deactivated while an active mapping uses it. If you try from the account form, the app stops you. Deactivate the mapping first.

