Audience: Finance/Ops, Admins, Developers, Compliance
Outcomes: Clean invoicing; immutable numbering; compliant data handling
Invoicing & documents of record
# Download invoice PDF curl -s $API_BASE/api/invoices/ord_123.pdf -b cookies.txt --output invoice-ord123.pdf
Branding: upload org logo/details under Admin → Settings → Branding; appears on invoices & quotes.
Numbers & references: schemes are configurable; immutable after issuance.
Identifiers & numbering
Resource prefixes:
ct_
,ord_
,inv_
,dsp_
.Default contract numbers:
NXT-<timestamp>-<random>
(overrideable).Always attach your own reference (e.g., PO number) for reconciliation.
Anti-patterns
Reusing the same external reference across different orders.
Mutable contract numbers (breaks audit continuity).
Using emails as IDs; storing PII in free-text.
Data retention & privacy
Operational records (contracts, orders, invoices) retained per legal/tax obligations.
Personal data can be deleted/anonymized on request; business records remain.
Export tools produce evidence bundles for audits on demand.
Time zones & effective dates
Store all timestamps in UTC; display in user’s timezone.
Contracts accept effective_at and expires_at (UTC).
Reminder emails show absolute dates (e.g., “16 Aug 2025 17:00 UTC+3”).
QA checklist
Invoice number remains immutable after edits/refunds.
Deletion request anonymizes PII but preserves tax records.
UI shows dates in local timezone; API returns UTC.