> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jadenet.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Master data

> Maintain shared reference data safely and prevent duplicate or incorrect transaction values.

Master data supplies the selectable values used throughout JADE-ELS. Changes can affect new transactions, reports, integrations, and accounting mappings.

## Common master-data domains

| Domain         | Examples                                                                         |
| -------------- | -------------------------------------------------------------------------------- |
| Organization   | Company, office/branch, department, position, user                               |
| Parties        | Customer, vendor, carrier, agent, shipper, consignee, contacts                   |
| Locations      | Country, city, port, airport, warehouse, rack, stock location                    |
| Freight        | Service mode, shipment mode/type, package type, commodity, vessel/voyage, route  |
| Finance        | Currency, exchange rate, charge code, tax rate, payment terms, chart of accounts |
| Land/warehouse | Truck type, vehicle, driver, item, part, unit, issue type, labor, mechanic       |

## Create or change a master record

<Steps>
  <Step title="Search first">Search by code, name, tax identity, and common abbreviations to avoid duplicates.</Step>
  <Step title="Confirm ownership">Identify the business owner authorized to create or approve this type of record.</Step>
  <Step title="Use the naming standard">Enter the official code and name with consistent capitalization and abbreviations.</Step>
  <Step title="Complete required attributes">Add office scope, address, tax, currency, account mapping, status, dates, and relationships where applicable.</Step>
  <Step title="Review downstream impact">For finance and operational codes, confirm reporting and posting behavior before activation.</Step>
  <Step title="Save and test">Use a controlled transaction or list check to confirm the value appears in the expected scope.</Step>
</Steps>

## Change-control rules

* Prefer deactivation to deletion when a value has transaction history.
* Do not reuse old codes for a different meaning.
* Merge duplicates only through an approved data-correction process.
* Record effective dates for rates and time-sensitive values.
* Review high-impact mappings, including charge-to-account and tax configuration, with Finance.
* Protect personal and banking data according to policy.

<Warning>A master-data error can affect many later transactions. Correct the source master and assess already-created records; changing the master may not retroactively correct posted transactions.</Warning>