{
  "id": 20686985,
  "title": "Day 26: Numeric Semantics, Multiple Currencies and Units of Measure",
  "url": "https://urgent.news/2026/11/19/day-26-numeric-semantics-multiple-currencies-and-units-of-measure",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-19T01:48:10.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jeff377/day-26-numeric-semantics-multiple-currencies-and-units-of-measure-2n2p"
  },
  "original_language": "en",
  "account": "This is the 26th day of the story, focusing on numeric semantics, multiple currencies, and units of measure. The story seeks to understand what the values in a document truly represent, despite how they appear in the TableSchema definition.\n\nNumerical fields are marked with a decimal place limit, but the actual number of decimal places shown, whether rounding is needed, and who controls the decimal places are not explicitly defined. The framework assigns a NumberKind to each field, determining how many decimal places to keep and whether to round. Quantity, amount, and percentage fields are rounded, while unit price, cost, and exchange rate fields are preserved.\n\nThe decimal places for amounts, quantities, and weights depend on the currency or the unit of measure. Currency decimal places are determined by the currency itself, not company policy. ISO 4217 sets the decimal places for each currency, which remain constant across companies. The base currency is chosen by the company, and exchange rates are fixed at five decimal places.\n\nWhen a document has multiple currencies or units, the total can only be calculated when all values are in a single currency or unit. The column header shows the total when all values are in the same currency, and the column footer shows the total when all values are in the base currency.",
  "summary": "The chapters so far asked whether a value gets in, whether it gets across, and whether it gets recorded. This post asks a different question: what the value that got in actually stands for. The quantity, unit price, amount, discount rate and exchange rate on a document look almost identical in the TableSchema definition, each one a decimal number with a precision. The real difference lies in…",
  "key_points": [
    "Numerical fields have decimal place limits not explicitly defined",
    "Quantity, amount, and percentage fields are rounded",
    "Exchange rates fixed at five decimal places"
  ],
  "editors_take": "Standardizing decimal precision through ISO 4217 and specific NumberKinds shifts control from individual company policy to global technical frameworks to ensure consistent calculation across diverse currencies and units.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}