Conservative invoice analysis

Understanding EDI 810 Invoice Analytics

Read source-reported and safely calculated measures without turning either into an unsupported reconciliation claim.

Published and reviewed August 30, 2026

The 810 summary exposes two deliberately separate measures: Source-reported TDS01 Invoice Amount and Eligible Calculated Product Line Value. They answer different questions. The product does not compare them as “expected versus actual,” calculate a variance, or claim that they reconcile.

Source-reported TDS01 Invoice Amount

This measure comes from the invoice's TDS01 source element under the mapper's documented scale rule. It reports what the sender placed in that element; it is not independently recomputed, verified, or certified by the product. Multiple transactions are grouped conservatively so unlike or unresolved currencies are not silently combined.

The label intentionally includes “Source-reported” and “TDS01.” It identifies source lineage and avoids implying that any available amount is a universally verified invoice total. When TDS01 is absent or unusable, analytics should show that absence rather than invent a value from unrelated AMT, SAC, TXI, FOB, or ISS content.

Eligible Calculated Product Line Value

This measure is based on eligible product-line quantity and price semantics. It uses exact decimal calculation when a row's quantity, unit of measure, unit price, price basis, currency, and ownership context are safe under the implemented rules. It excludes SLN, SUMMARY, ambiguous, incomplete, and otherwise ineligible rows according to the approved contract.

Present this measure only under the label Eligible Calculated Product Line Value. It does not add tax, freight, allowances, charges, terms discounts, summary adjustments, or source-reported TDS01. It is not a receivable, payable, balance due, settlement amount, or substitute for partner invoice logic.

Read the value with eligibility and reason fields

The canonical fields CalculatedLineValue, CalculatedLineValueEligible, and CalculatedLineValueReason belong together. A blank value can be an intentional conservative result rather than a parsing failure. Reasons distinguish conditions such as missing or invalid quantity, missing unit, missing or unsafe price, unsupported price basis, row-level tax context, unresolved currency, or ownership that is not a physical IT1 product line.

Do not coerce ineligible blank values to zero: zero is a real numeric value and would change the meaning of a report. Retain the reason when exporting, filtering, or presenting calculated metrics downstream.

Currency and unit-of-measure boundaries

Reported monetary facts and calculated line values are grouped by resolved currency where the contract permits. Unresolved or conflicting currency context is not guessed. Values from different currencies are never presented as one combined amount without a user-supplied conversion model outside this product.

Unit-of-measure differences matter to calculation eligibility and interpretation. The summary does not create cross-unit-of-measure totals or imply that quantities such as cases, eaches, pounds, and hours are interchangeable. A unit description is presentation context, not a conversion factor.

Use other conservative metrics as context

The invoice summary can count records, IT1 lines, SLN children, SUMMARY-only transactions, source qualifiers, parties, notes, taxes, allowances or charges, carrier details, and validation outcomes where the approved metric registry permits. Counts describe the mapped corpus; they do not establish economic correctness.

Source-reported quantities, monetary occurrences, terms, tax, freight, and shipment facts remain distinct dimensions. The summary does not synthesize an invoice total from them, perform 810-to-850 matching, calculate payment due, or judge a partner tolerance.

A safe workflow for EDI 810 analysis

  1. Convert the source with Smart Mapping and retain provenance and eligibility columns.
  2. Review validation findings in the EDI Validator.
  3. Group source-reported TDS01 values only by their resolved currency bucket.
  4. Filter calculated values to rows where CalculatedLineValueEligible is true and retain CalculatedLineValueReason for excluded rows.
  5. Present the two approved measures separately, with their exact labels and limitations.

Use the 195-field reference for field-level semantics and the EDI 850 overview for the conceptual purchase-order relationship. Partner workflows vary, and this is conservative file analysis rather than invoice reconciliation or accounting advice.