The chart of accounts as governed master data: one account list, its groupings, its company-code views and the mappings to every local chart.
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.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
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.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Financial statement | statement → line → account, versioned |
| Management | reporting line for management accounts |
| Chart | group 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.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | account number has the chart's length and pattern account type is in the code list |
| Row | a P&L account has a cost element category or an exemption a blocked account has no open items |
| Business | every 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 |
| Transactions in the bed | Read from |
|---|---|
| Journal lines | SAP ACDOCA; Oracle GL balances and journals |
| Open items | receivables and payables |
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.
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.
POST /api/v1/golden/gl-account/lookup
{
"chart": "GROUP",
"account": "4000100"
}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.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Chart of accounts read from SKA1 · SKAT.
Open the SAP S/4HANA page →Chart of accounts values read from GL_CODE_COMBINATIONS · FND_FLEX_VALUES (REST: chartOfAccountsValues).
Open the Oracle Fusion Cloud page →Ledger accounts read from Get_Ledger_Accounts · Get_Account_Sets.
Open the Workday page →GL account read from CONFORMED.GL_ACCOUNT.
Open the Snowflake page →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.
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.
One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Industrial manufacturing, Consumer goods, Financial services, Telecom. The industry pages show the domains each starts with.
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.