Ledger Account Map
For a parallel ledger that posts automatically: the account its copy of a posting uses instead of the leading account. A ledger set adjustment-only (and every delta ledger) takes only journals that touch a mapped account.
Where to find it
- Module: Accounting
- Group: Close & Controls
- Section: Finance Configuration
- Screen: Ledger Account Map
Address in the console: /accounting/ledger-account-map
List · 5 columns · 4 fields on its form · 3 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Ledger | Code | ledger_code |
| Leading account | Code | from_account_no |
| Name | Text | from_account_name |
| Posts to | Code | to_account_no |
| Name | Text | to_account_name |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Parallel ledger required | Choice | Looked up from existing records | |
| Leading-ledger account required | Choice | Looked up from existing records | |
| Posts to required | Choice | Looked up from existing records | |
| Notes | Long text |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.