FFA

Epic Goal¶

To design and implement a complete Air Clearing Module within MFreight that enables users to:

• Create, manage, and process Air Clearing Files
• Handle both Import and Export shipments
• Maintain full operational traceability through Activity Logs

The module must support creation from:

• Existing HAWB (House Air Waybill)
• Existing MAWB (Master Air Waybill)
• Existing Quotation
• Or manual creation (from scratch)

Business Context¶

In air freight:

• MAWB (Master Air Waybill) = Airline shipment (master level)
• HAWB (House Air Waybill) = Shipment per customer (house level)
• A single MAWB can contain multiple HAWBs
• Clearing is the process of:
  • Declaring goods to customs
  • Paying duties/taxes
  • Getting cargo released

A Clearing File is used internally by freight forwarders to:

• Track customs processing
• Manage charges (cost & sales)
• Store shipment & party information
• Record BOE (Bill of Entry)
• Maintain audit trail of all actions (Activity Log)

Scope of the Epic¶

1. Clearing File Creation¶

System must allow creation of a clearing file using:

• Existing HAWB
• Existing MAWB
• Existing Quotation
• Manual entry

2. Shipment Types¶

• Air Import
• Air Export

3. Core Functional Areas¶

A. Retrieve / Search Clearing Files¶

• Search by:
  • HAWB No.
  • MAWB No.
  • Clearing Reference
  • Airline
  • Flight No.
  • BOE Reference
  • Status
  • Date Range

B. Clearing File Management¶

• Create
• View
• Update
• Save
• Status tracking

C. Shipment Information¶

Capture and manage:

• MAWB / HAWB details
• Airports (Origin / Destination / Transit)
• Flight details
• Shipment type (Import / Export)

D. Party Information¶

• Shipper
• Consignee
• Notify Party
• Delivery Agent

E. BOE Management¶

• One Clearing File can have multiple BOEs
• BOE details must be captured and allow update

F. Cost & Sales Management¶

• Record operational costs
• Record customer billing (sales)
• Support multiple charges

G. Document Management¶

• Upload
• View

H. Workflow & Status Management¶

Statuses include:

Draft → Confirmed → Closed

Confirmed → Draft

Cancel → Cancelled

I. Activity Log¶

A section/screen showing system-generated logs.

Columns:

• Activity Date & Time
• Activity By (User)
• Activity Description

Key Functional Rules¶

1. Creation Logic¶

• From HAWB → auto-populate data
• From MAWB → allow future expansion
• From Quotation → fetch commercial data
• From scratch → manual entry

2. BOE Logic¶

• Multiple BOEs per clearing file
• Each BOE independent

3. Data Integrity¶

• Clearing Reference must be unique
• Required fields enforced
• AWB format validation

4. Terminology Replacement¶

Ocean	Air
Vessel	Airline
Voyage	Flight
Port	Airport
BL	AWB
HBL	HAWB
MBL	MAWB

User Roles¶

• Allow permissions to view only, operations level, supervisor level for approval.

Epic-Level Acceptance Criteria¶

• User can create clearing file using all 4 methods
• Supports Air Import & Export
• Multiple BOEs supported
• Costs & Sales can be captured
• Documents can be uploaded
• Status workflow works correctly
• Activity Log captures all system & manual actions
• Activity Log is present and updated everytime

Dependencies¶

• Air Shipment Module (HAWB / MAWB)
• Quotation Module
• Customer & Supplier Master—Shipper, consignee, notify, agent
• Charges Module
• Flight Scedule Module

Technical Considerations¶

• Reuse Ocean Clearing architecture
• Create separate Activity Log table for Air