Tax codes, rates, jurisdictions and their validity as reference data shared by every system that prices, invoices or reports.
Today a rate change is keyed into each ERP and the web shop separately; one of them keeps the old rate for a week and the invoices are wrong.
With Lima the tax codes are read where they live, matched on country + code and jurisdiction code, assembled field by field and published as one golden record per real tax codes, with every source key underneath. The invoices posted with a code and the rate history behind them 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.
A rate is a versioned value; invoices dated in the old period read the old rate from 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 |
|---|---|
| Jurisdiction | country → state → county → city |
| Type | VAT, sales tax, withholding, excise |
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 | rate is between 0 and 100 valid-to is after valid-from country is in the ISO list |
| Row | a code with a rate has a GL account mapping a reduced rate names its legal basis |
| Business | one active rate per code per date every taxable product class has a determination for every active jurisdiction it sells into |
| Transactions in the bed | Read from |
|---|---|
| Invoices | billing documents |
| Tax returns | tax engine |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the invoices posted with a code and the rate history behind them.
Tax edits rates through an approved request; pricing and finance read; everyone else sees the code and rate. The twelve layers apply on every door; see security.
POST /api/v1/golden/tax/resolve
{
"country": "DE",
"product_class": "standard",
"customer_class": "business",
"date": "2026-10-01"
}200 OK
{
"code": "A1",
"rate": 19.0,
"gl_account": "GL-1750000",
"valid_from": "2007-01-01"
}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.
Tax codes read from T007A · T007S.
Open the SAP S/4HANA page →Tax rates and codes read from ZX_RATES_B · ZX_TAXES_B (REST: taxRates).
Open the Oracle Fusion Cloud page →Tax rates (Revenue Cloud / CPQ) read from TaxRate · TaxTreatment.
Open the Salesforce page →Tax code read from CONFORMED.TAX_CODE. 2 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A retailer selling in 11 countries keeps tax rates once and publishes them to two ERPs and the web shop. A rate change in one country reached all three the same morning.
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; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Consumer goods, High-tech and semiconductor, Financial services. 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.