Tax codes, rates, jurisdictions and their validity as reference data shared by every system that prices, invoices or reports.
Tables are read in place through the Snowflake connector with filters and aggregates pushed down; nothing is copied out.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Tax code | CONFORMED.TAX_CODE | country · code · type · rate · valid_from · valid_to · gl_account | as fresh as the landing pipeline; live for governed tables |
| Invoice tax | CONFORMED.AR_INVOICE_TAX | invoice_id · code · base · amount | as fresh as the landing pipeline; live for governed tables |
The first object above carries the strong keys; the standardised attributes come from the same rows. A rate is a versioned value; invoices dated in the old period read the old rate from history.
Golden records and their history are written with MERGE into a governed schema, so the warehouse always carries the current keys.
| Interface | Used for | Result |
|---|---|---|
MERGE INTO GOLDEN.TAX_CODE on the golden key; history in GOLDEN.TAX_CODE_HISTORY | golden values approved for write-back: code; rate; mappings | the id or error Snowflake returns, stored beside the change |
Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.
Snowflake roles and row access policies are honoured; Lima adds its own layers on top.
Tax codes and jurisdictions on
Other domains on Snowflake
The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Snowflake.
Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.
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.
