Skip to main content

​
Audit Trail + Compliance

Better Data stores loop transition history as first-class operational data. Compliance export is generated from the same transition records used to run the system.

​
How The Audit Trail Works

Every transition stores:
  • Actor identity (actorId)
  • Transition timestamp (occurredAt, UTC)
  • Triggering event name (triggeredBy)
  • Correlation trace (correlationId)
  • Causation trace (eventId and event chain context)

​
Exporting The Audit Trail

GET /api/organizations/{orgId}/audit-trail
​
loopId
string
Optional loop filter such as scm.procurement or dcm.returns.
​
aggregateId
string
Optional aggregate filter (PO, order, RMA, shipment, lot).
​
from
string
Optional ISO-8601 lower bound for transition timestamps.
​
to
string
Optional ISO-8601 upper bound for transition timestamps.
​
format
string
json (default) or csv.
curl -H "x-api-key: <your-key>" \
  "https://api.betterdata.co/api/organizations/org_lumebonde_demo/audit-trail?loopId=scm.procurement&format=csv"

​
Regulatory Alignment

DSCSA

Transition-linked chain-of-custody signals support transaction traceability expectations.

FSMA

Goods receipt and movement transitions support CTE/KDE style trace evidence.

FDA 21 CFR Part 11

Actor-attributed transitions provide auditable electronic action history.

EU CSRD / Due Diligence

Correlated actor and event chains provide defensible supply chain evidence.
Regulatory references are informational and do not replace legal/compliance review for your jurisdiction and use case.

​
Signal Tags

Signal Tags add product-level provenance semantics that complement loop-level audit records. See Signal Tags documentation.