Preview as:
CS and Sales have no Customs module (PRD §3.3/§3.2 scope lists).

Customs

Customs jobs per PRD §3.4 scope: every record links to a Job Order, carries its declaration, tax components and document set. Tax components here are read/write for Customs; revenue stays out of this module.

Import tax calculator

Customs status

Customs jobs

§27.E1 · TASK-037 · click a row to show its status
Customs #Job orderCustomerImport typeDeclarationTax basePPNPPHBMStatus

Customs documents

§27.E2 · TASK-038 · stored in the Document module (EPIC 06) with customs scope
DocumentTypeCustoms jobVersionStatus
Status vocabulary (TASK-040). PRD defines the customs record but not its status machine; this prototype uses Documents → Declaration submitted → Processing → Released → Closed as a labeled assumption for the backend rule. Scope: Customs role sees tax components and edits customs fields (§3.4); Finance sees the same numbers for costing; CS sees customs state only inside the Job Order detail; Sales never sees this module. Revenue and invoice references are not part of Customs API responses.

New customs job

TASK-037 · linked to a Job Order

Record starts in Documents. Declaration number is filled after PEB/PIB submission. All changes audit-logged (PRD §15).