FFA

MAWB (FWB)

Create MAWB header (FWB core)

• A freight forwarder should be able to create a MAWB with all mandatory FWB fields
• So that to transmit an error-free (X)FWB to the carrier
  Details: AWB No. (3-digit prefix + 8-digit serial), Issue Date/Time, Airport of Departure/Destination, Carrier code, Flight routing (multi-leg), Pieces/Weight/Volume (gross/chargeable), Commodity item, Nature of Goods, Incoterms, Currency, WT/VAL/Other charge codes (PPD/COLL), Other Charges Due Carrier/Agent, Handling Information (SSR/OSI), SHC codes, Accounting information, Optional references.

Acceptance Criteria

• Mandatory fields enforced per IATA FWB v16+; character set/length checks; auto UPPERCASE where required.
• Multi-leg routing captured with sequence, flight no., dates.
• Validation prevents save/transmit until “Ready” (see Pre-transmission validation & quality meter).

Parties & addresses

• The Freight forwarder should be able to capture Shipper/Consignee/Agent with IATA-conform lines
• So that transmitted FWB is accepted by carriers

Acceptance Criteria

• Address book lookup + auto-fill; enforce Cargo-IMP character set (subset of ASCII; no underscores, etc.); auto line-breaks 35 chars.
• IATA Agent code (CASS/IATA) optional per airline rule.

Rates & charges panel

• Rate lines (rate class, chargeable weight, rate/amount, totals)
• So that MAWB totals and PP/CC split compute correctly

Acceptance

• Auto compute: freight total, other charges due Carrier/Agent, grand totals PP/CC; audit trail on overrides.
• Currency chooser with stored FX (if needed) + rounding per airline rules.

Special Handling & DG flags

• System should have the SHC (e.g., PER, EAP), OSI/SSR, DG indicator
• So that carriers/handlers know how to process the cargo

Acceptance

• Pick-list of SHC with multi-select; free-text OSI/SSR with length limits; DG flag triggers required notations (no full DGD here, just references).

Security (e-CSD) / OCI

• System needs to capture security status in OCI
• So that e-CSD information travels via (X)FWB or FSU as per IATA
• Acceptance
• OCI lines for security status, method, date/time, RA/RC details; toggle to send in FWB or defer to FSU (per airline/country).

Customs/regulatory annotations

• Optional HS code, ECCN, AES/ACAS flags and references
• So that shipments needing advance screening (e.g., ACAS to US) are covered

Acceptance

• Capture ACAS-related data points (where available) to avoid later re-keying; warnings if missing for US exports.

Import workflows (MAWB received)

Import: Consume airline FWB

• System should be able to upload/receive airline-sent FWB/XFWB
• So that a MAWB record pre-populates for clearance & breakdown

Acceptance

• Parse inbound FWB/XFWB; map to fields; show differences if a record exists; keep raw EDI/XML for audit.

Import: link HAWBs (FHL)

• System should be able to link received FHLs to MAWB
• So that total pieces/weight reconcile vs. master

Acceptance

Auto-reconcile totals; discrepancy banner; drilldown to house list.