Skip to main content

Map ERP data

Every CFO row must trace back to a stable ERP document or line without putting PII or secrets in its identity.

CFO fieldMapping rule
external_refStable document/line business identity; unchanged on retry
external_batch_idSubmission batch identity saved before the network call
Idempotency-KeyTransport identity for one canonical request
document_dateYYYY-MM-DD inside the selected reporting period
activity_codeValue returned by capability discovery
catalog_item_codeItem paired with that discovered activity
quantityPositive ERP amount that does not round to zero
unitExact accepted unit from discovery

Some Scope 3 transport items accept direct tkm; others may support weight_kg with distance_km. Follow the discovered contract. Do not calculate or hard-code emission factors in the ERP—CFO resolves the factor and returns the calculation version.

Canonicalize and hash the payload before sending so a restart can prove that the exact request was retried.