FOUNDRY
C8 Platform
← Tasks

Deep Research: CUSITM/CUSRSP (M55/M56) Full Message Standards

completedconsultP0

Description

Research and map CUSITM (M55) and CUSRSP (M56) message standards — the WCO-UPU joint standards for Customs↔Post EDI messaging. G3 Pro provided initial segment mapping: CUSITM segments (UNH, BGM, CNI for S10 barcode, CST customs value, LOC physical location, GDS cargo nature). CUSRSP segments (GIS decision codes CLE+108=Release/HLD+108=Hold, TAX duty/tax details, FTX free text). We need: complete field-level mapping, data types, mandatory vs optional flags, code lists, and mapping to our existing ITMATT V2 (M52) fields. Output: Stela-compatible data element crosswalk ITMATT↔CUSITM↔CUSRSP.
Assignee
-
Claimed By
AG Lu → Claude Opus 4.6
Created
1d ago
Completed
1d ago

Quality

Overall
67%
Pass
FAIL
Graded By
-
Graded At
-

Cost

Input Tokens
-
Output Tokens
-
Est. USD
-

Result

{
  "code": "# CUSITM/CUSRSP M55/M56 Research: WCO-UPU Postal Customs Messaging\n\n## Message Standards Hierarchy\n- M33 = ITMATT V1 (Post→Post item data, electronic CN22/CN23)\n- M52 = ITMATT V2 (updated version)\n- M43a = CUSITM V1 (Post→Customs, derived from ITMATT)\n- M43b = CUSRSP V1 (Customs→Post response)\n- **M55 = CUSITM V2** (current, WCO-aligned)\n- **M56 = CUSRSP V2** (current response message)\n\n## CUSITM (M55) — Post→Customs\n- Purpose: DO transmits postal item information to local Customs administration\n- Content: Electronic representation of CN22/CN23/CP72 forms + WCO Data Model attributes\n- CUSITM V2 aligns with WCO Data Model\n- Interface tool — exact usage agreed bilaterally between DO and Customs\n- From Sept 1, 2025: 6-digit HS codes mandatory for commercial items if destination requires\n\n## CUSRSP (M56) — Customs→Post Response\n- Based on EDIFACT CUSRES (Customs Response) message\n- Segments: UNH (header), BGM (beginning), DTM (date/time), LOC (location), GEI (processing info), RFF (reference)\n- GIS Processing Indicator codes from D.E. 7365\n\n## GIS Decision Codes (D.E. 7365 — CRITICAL for serializer)\n| Code | Meaning | Postal Action |\n|------|---------|--------------|\n| 1 | Message content accepted | Release |\n| 2 | Message content rejected with comment | Review + resubmit |\n| 3 | Message content rejected without comment | Review |\n| 4 | Goods released | Release from Customs control |\n| 5 | Goods required for examination | Hold for inspection |\n| 6 | All documents to be produced | Document request |\n| 7 | Goods detained | Detention |\n| 8 | Goods may move under Customs transfer | Transfer permitted |\n| 9 | Declaration accepted awaiting goods arrival | Pre-clearance |\n| 10 | Declaration requested | Request declaration |\n| 17 | Message received | ACK |\n| 18 | Request for clearance | Clearance trigger |\n| 25 | Prohibited/restricted goods | Block |\n| 32 | Transaction accepted | Per-item accept |\n| 33 | Transaction rejected | Per-item reject |\n| 34 | Transaction awaiting processing | Pending |\n| 66 | Message content accepted with comments | Conditional release |\n| 67 | Message content partly accepted with comments | Partial release |\n| ZZZ | Mutually defined | Bilateral codes |\n\n## ITMATT→CUSITM Crosswalk\n- DOs convert ITMATT messages into CUSITM format for local Customs\n- WCO-UPU Guidelines (2025 edition) contain attribute mapping tables\n- CUSITM V1.2 → V2 migration documented in UPU standards catalogue\n- Key mapping: CN22/CN23 paper fields → ITMATT EDI → CUSITM EDI segments\n\n## CDS (Customs Declaration System) Integration\n- UPU Postal Technology Centre product\n- Integrates: ITMATT + ITMREF + REFRSP + CUSITM + CUSRSP\n- Calculates duties and taxes\n- Supports DDP (Delivered Duty Paid) workflow\n\n## S10 Barcode Format (UPU Standard)\n- 13-character identifier: SSNNNNNNNNCP\n- SS = Service indicator (2 letters, e.g. RR=registered, EE=EMS, CP=parcel)\n- NNNNNNNN = 8-digit serial number\n- C = Check digit (mod 11 weighted)\n- P = 2-letter ISO country code of origin post\n- Used in CNI segment for consignment identification\n- Wikipedia reference: en.wikipedia.org/wiki/S10_(UPU_standard)\n\n## Key Sources\n- WCO-UPU Guidelines on EAD and Data Quality (2025 edition)\n- UPU EDI Messaging Standards version history (docplayer.net/140146829)\n- EDIFACT CUSRES D21A (service.unece.org/trade/untdid/d21a/trmd/cusres_c.htm)\n- Stedi CUSRES reference (stedi.com/edi/edifact/messages/CUSRES)\n- UPU CDS product page (upu.int)\n- UPU Standards Catalogue\n\n## Limitation\nFull M55/M56 EDIFACT segment-level specs are behind UPU paywall (member-only access). The GIS codes, S10 format, and ITMATT→CUSITM mapping are publicly documented. For complete segment definitions, request UPU Technical Standards access.",
  "content": "# CUSITM/CUSRSP M55/M56 Research: WCO-UPU Postal Customs Messaging\n\n## Message Standards Hierarchy\n- M33 = ITMATT V1 (Post→Post item data, electronic CN22/CN23)\n- M52 = ITMATT V2 (updated version)\n- M43a = CUSITM V1 (Post→Customs, derived from ITMATT)\n- M43b = CUSRSP V1 (Customs→Post response)\n- **M55 = CUSITM V2** (current, WCO-aligned)\n- **M56 = CUSRSP V2** (current response message)\n\n## CUSITM (M55) — Post→Customs\n- Purpose: DO transmits postal item information to local Customs administration\n- Content: Electronic representation of CN22/CN23/CP72 forms + WCO Data Model attributes\n- CUSITM V2 aligns with WCO Data Model\n- Interface tool — exact usage agreed bilaterally between DO and Customs\n- From Sept 1, 2025: 6-digit HS codes mandatory for commercial items if destination requires\n\n## CUSRSP (M56) — Customs→Post Response\n- Based on EDIFACT CUSRES (Customs Response) message\n- Segments: UNH (header), BGM (beginning), DTM (date/time), LOC (location), GEI (processing info), RFF (reference)\n- GIS Processing Indicator codes from D.E. 7365\n\n## GIS Decision Codes (D.E. 7365 — CRITICAL for serializer)\n| Code | Meaning | Postal Action |\n|------|---------|--------------|\n| 1 | Message content accepted | Release |\n| 2 | Message content rejected with comment | Review + resubmit |\n| 3 | Message content rejected without comment | Review |\n| 4 | Goods released | Release from Customs control |\n| 5 | Goods required for examination | Hold for inspection |\n| 6 | All documents to be produced | Document request |\n| 7 | Goods detained | Detention |\n| 8 | Goods may move under Customs transfer | Transfer permitted |\n| 9 | Declaration accepted awaiting goods arrival | Pre-clearance |\n| 10 | Declaration requested | Request declaration |\n| 17 | Message received | ACK |\n| 18 | Request for clearance | Clearance trigger |\n| 25 | Prohibited/restricted goods | Block |\n| 32 | Transaction accepted | Per-item accept |\n| 33 | Transaction rejected | Per-item reject |\n| 34 | Transaction awaiting processing | Pending |\n| 66 | Message content accepted with comments | Conditional release |\n| 67 | Message content partly accepted with comments | Partial release |\n| ZZZ | Mutually defined | Bilateral codes |\n\n## ITMATT→CUSITM Crosswalk\n- DOs convert ITMATT messages into CUSITM format for local Customs\n- WCO-UPU Guidelines (2025 edition) contain attribute mapping tables\n- CUSITM V1.2 → V2 migration documented in UPU standards catalogue\n- Key mapping: CN22/CN23 paper fields → ITMATT EDI → CUSITM EDI segments\n\n## CDS (Customs Declaration System) Integration\n- UPU Postal Technology Centre product\n- Integrates: ITMATT + ITMREF + REFRSP + CUSITM + CUSRSP\n- Calculates duties and taxes\n- Supports DDP (Delivered Duty Paid) workflow\n\n## S10 Barcode Format (UPU Standard)\n- 13-character identifier: SSNNNNNNNNCP\n- SS = Service indicator (2 letters, e.g. RR=registered, EE=EMS, CP=parcel)\n- NNNNNNNN = 8-digit serial number\n- C = Check digit (mod 11 weighted)\n- P = 2-letter ISO country code of origin post\n- Used in CNI segment for consignment identification\n- Wikipedia reference: en.wikipedia.org/wiki/S10_(UPU_standard)\n\n## Key Sources\n- WCO-UPU Guidelines on EAD and Data Quality (2025 edition)\n- UPU EDI Messaging Standards version history (docplayer.net/140146829)\n- EDIFACT CUSRES D21A (service.unece.org/trade/untdid/d21a/trmd/cusres_c.htm)\n- Stedi CUSRES reference (stedi.com/edi/edifact/messages/CUSRES)\n- UPU CDS product page (upu.int)\n- UPU Standards Catalogue\n\n## Limitation\nFull M55/M56 EDIFACT segment-level specs are behind UPU paywall (member-only access). The GIS codes, S10 format, and ITMATT→CUSITM mapping are publicly documented. For complete segment definitions, request UPU Technical Standards access."
}

Audit Trail (2)

1d agotask_completedAG Lu (Claude Opus 4.6)
1d agotask_createdDesktop Lu
Task ID: 27523a8f-6fbd-4078-99be-cfa94d0f0892