Domain catalogue Finance

General ledger account

The chart of accounts as governed master data: one account list, its groupings, its company-code views and the mappings to every local chart.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPWorkdayHCM · financeSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN GENERAL LEDGER ACCOUNTGeneral ledger accountone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the general ledger account record comes from, how it is assembled, and who reads it. Other systems have their own page.
3 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
3
hierarchies the record sits in
catalogue
2
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today the group chart, three local charts and the consolidation tool's mapping table drift apart; the close finds a new account nobody mapped.

With Lima the GL accounts are read where they live, matched on account number within a chart and group account mapping, assembled field by field and published as one golden record per real general ledger account, with every source key underneath. Balances and journal lines per account and company code, and the mapping history behind each group account are one click away, because the transactions sit in the same bed.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Accountnumber, short and long names by language, account type, group
wins: group finance
Groupingsfinancial statement version, reporting lines, IFRS and local tags
wins: group finance
Company-code viewopen or blocked per company code, currency, tax relevance, field status
wins: local finance
Mappingslocal chart account → group account, alternative accounts
wins: crosswalk with validity
How records match

The keys, in order

account number within a chartgroup account mapping

Local accounts map to exactly one group account per version; the mapping is master data with its own history.

Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.

Where it sits

3 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Financial statementstatement → line → account, versioned
Managementreporting line for management accounts
Chartgroup chart → local charts

A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columnaccount number has the chart's length and pattern
account type is in the code list
Rowa P&L account has a cost element category or an exemption
a blocked account has no open items
Businessevery local account maps to one group account in the active version
statement lines add up: assets equal liabilities plus equity in the structure
no postings on an account created in the last 30 days with no approved request
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Journal linesSAP ACDOCA; Oracle GL balances and journals
Open itemsreceivables and payables
balance by monthpostings per accountmapping changes per closeunmapped accounts

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens balances and journal lines per account and company code, and the mapping history behind each group account.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

The chart editable by group finance through an approved request; local views editable locally; everyone else reads. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/gl-account/lookup
{
  "chart": "GROUP",
  "account": "4000100"
}
response
200 OK
{
  "golden_id": "GL-4000100",
  "name": "Revenue · products",
  "statement_line": "P&L · Revenue",
  "local_mappings": 14,
  "status": "open"
}

The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.

A group with 14 company codes on two ERPs governed one chart with 2,600 accounts and every local mapping. The consolidation mapping table was retired; the close packs read the golden statement structure directly.

illustrative scenario · General ledger account
Terms on this page

Chart of accountsThe list of accounts a company posts to, with their meaning.
Financial statement versionA hierarchy of accounts into statement lines, kept as versions.
Group accountThe account in the group chart that a local account maps to.
Golden recordThe one record for a real general ledger account, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.

How long to the first golden view?

One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Industrial manufacturing, Consumer goods, Financial services, Telecom. The industry pages show the domains each starts with.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.