1 · IN
Supplier → JFS docs → IN BOE (Mirsal) → enter here
2 · OUT
JFS → Customer advice → Customer files OUT BOE
3 · CONFIRM
Match IN vs OUT BOE → confirm → give stock
4 · RECON
Auto reconciliation + Excel export
Recent IN shipments
Goods cleared into JFS from suppliers
Reconciliation snapshot
IN BOE qty/weight/value vs OUT BOE — auto match
Stock IN
Record a new Transit-IN, or open a past IN from the history below.
📋 IN History
All recorded IN shipments. 👁 Preview = JFS-generated documents (DA · Invoice · Transfer · BOE). 📎 Customer Docs = the customer's ORIGINAL files + BOE, exactly as attached (whose shipment it is).
🔍
🔍
📑 Customs Reconciliation Report
Per IN declaration (BOE) vs OUT declarations — HS code, quantity, weight and value, with free-zone balance. Filter by date range or a specific BOE. Open IN / OUT documents per row.
🔍
🔍
Deadline rules (editable)
All Dubai Customs / Mirsal 2 declaration types — set the submission window per type
Defaults reflect current Dubai Customs guidance: declaration + supporting documents within 30 days of online filing; Import for Re-Export exit within 180 days (6 months) from the declaration date. Verify against your Dubai Trade account and adjust if your bill type differs.
🛂 Acknowledgements required (Dubai Trade)
Customs mails asking the company to ACKNOWLEDGE a declaration — 30-day window from the mail date. Log in to Dubai Trade, acknowledge, then mark it done here (or wait for the customs confirmation mail — it clears automatically).
BOE submission due (IN)
Declaration + documents to be submitted to Customs
OUT BOE tracking
Transfer = 1 step (submit all). Transit Out = exit stamp → claim submit → approve / review / reject (2-month window)
BOE Passing
Documents → DT file, for any client company
🧾 Recent DT files
Every DT file created here — download again anytime
🔍
🔍
🔍
Loading…
✈ Export shipment, AWB weight & dates — SOP
Sayid, 15-Oct-2026 — applies to Stock IN, BOE Passing and the DT file
1
Always upload the AWB with the invoice + packing list. The packing-list weight can be wrong — the AWB weight is the FINAL weight. The app scales the line weights so they add up exactly to the AWB gross weight (in proportion to the printed weights, or to the pieces if none are printed) and warns when the documents differed.
2
Export shipment = consignee / destination outside the UAE (or an Export / exit declaration type). For exports, lines with the same HS code + same country of origin become ONE line automatically — e.g. Asad, Yara, Yara Candy, Fakhar → one line "PERFUME SPRAY 100ML", qty, weight and value added up. No merge question is asked.
3
Dates are DAY / MONTH / YEAR (UAE format): 12/10/2026 = 12 October 2026. An invoice date can never be in the future — if it reads that way, day and month are swapped back. Only when the document's format is truly unclear does the app ask you which date is right.
4
Check before uploading the DT file: invoice date (not in the future), total weight = AWB, total value = invoice, one line per HS + country for exports.
🧭 Declaration type, warehouse & job type — SOP
What the AI decides when you upload documents, and the masters it uses
1
Declaration type is read from the documents. Leave it blank and press Extract — the AI finds the shipper, its address / free zone, its licence and the bill type printed or ticked on the DA, then sets the type (you can still change it):
• Shipper outside the UAE (AWB from abroad, foreign address) → FZ Transit In
• Shipper in a GCC country / another emirate → FZ Transit In from GCC / other Emirates FZ
• Shipper a local mainland company (tax invoice, TRN, AED) → Export from Local to FZ
• Shipper a free-zone company in the same free zone (Internal Transfer / C-Entry / Transfer of Ownership, e.g. DAFZA → DAFZA) → Transfer within a FZ (Ownership)
• Shipper in another Dubai free zone (DAFZA ↔ JAFZA) → FZ Transit Between
• Shipper outside the UAE (AWB from abroad, foreign address) → FZ Transit In
• Shipper in a GCC country / another emirate → FZ Transit In from GCC / other Emirates FZ
• Shipper a local mainland company (tax invoice, TRN, AED) → Export from Local to FZ
• Shipper a free-zone company in the same free zone (Internal Transfer / C-Entry / Transfer of Ownership, e.g. DAFZA → DAFZA) → Transfer within a FZ (Ownership)
• Shipper in another Dubai free zone (DAFZA ↔ JAFZA) → FZ Transit Between
2
Known companies decide first. Our own companies, the party directory zone (Freezone / Mainland / Overseas) and the licence register override a guess. Keep party zones correct.
3
Warehouses have codes. JFS DAFZA DZ001 · JFS JAFZA JZ002 · SIMSAR SM0003 · STR DAFZ ST004 · STR JAFZA ST005. "+ Add new warehouse" asks for name, free zone, operator, address and contact and gives the next code automatically. Fill "Stock kept under reference of" — whose reference / account the warehouse holds the stock under.
4
Job type from the job number. Typing a job number such as AEXP C0001 sets the Type of Job to AEXP — Air Export automatically (AIMP = Air Import, SIFC = Sea Import Full Container …).
🏬 Import from Local to FZ — SOP
Buying from a LOCAL UAE company into the free zone (declaration: "Export from Local to FZ", 202-series BOE)
1
Document received = local TAX INVOICE. The local seller (e.g. a mainland / FZ LLC) issues a UAE Tax Invoice — TRN printed, amounts in AED, batch lines. HS codes are often NOT printed and weights may be missing. That is normal for this flow.
2
Stock IN — Declaration Type "Export from Local to FZ". Select it first (AI runs on Fable automatically, same as FZ Transit In). Upload the tax invoice and press Extract — the AI reads every line, suggests Dubai Trade HS codes for lines without one (verify before filing), detects the AED currency from the amount-in-words, and fills the IN.
3
BOE later (202-series). The SELLER is the declarant, so the bill prints the seller in the Importer/Exporter box and OUR company in the "EXPORTED TO" box with our AE code. Upload the BOE when it passes — the AI reads it with these rules, verifies the AE code against the registry, and completes the IN.
4
After that everything is standard. Stock, balance, OUT delivery advices and reconciliation work exactly like any other IN — the goods are now free-zone stock in the consignee's name.
🔑 Ownership SOP — Shipper / Consignee / Customer
The core rule this software and its AI follow for every transfer document
1
Two parties on every TR document. The SHIPPER is the company giving / transferring ownership of the goods. The CONSIGNEE is the company receiving ownership (the "Importer" / "release to M/S" party on the DA, the "transferred to M/S" party on the Transfer of Ownership).
2
Shipper ≠ Supplier, Consignee ≠ Customer. These two parties are not necessarily JFS's supplier or customer. The AI reads them from the documents strictly as Shipper and Consignee — it never guesses a customer.
3
Customer is manual. The actual customer is typed manually by JFS staff in the "Customer (manual)" field. It may be the consignee, or a different (3rd-party) company. It is for internal reference only.
4
Stock is always in the consignee's name. In the customs record the stock holder is the CONSIGNEE — even when the consignee keeps the stock for a 3rd-party customer. All balance stock and reconciliation in this system is consignee-wise.
5
Transfer chain. The consignee of one transfer becomes the shipper of the next. Example: AJ WORLD WIDE (shipper) → SKYRIVER (consignee) · then SKYRIVER (shipper) → ALIF TRADING FZCO (consignee) — stock now stands under ALIF TRADING FZCO.
📦 Store IN Process — Multiple HS Codes & COO
Standard Operating Procedure for inbound shipments with several HS codes and countries of origin
1
Document Identification. Gather and identify all required inbound documents: Commercial Invoice, Delivery Advice (DA), Transfer of Ownership (TOO), and the HS Code Summary.
2
Data Extraction & Cross-Verification. Run the automated (AI) extraction on the Commercial Invoice and cross-verify the extracted data against the Delivery Advice. If specific details are missing from the invoice, source them from the DA or the HS Code Summary.
3
Multi-Criteria Categorization & Description Alignment. Dual-layer sorting: first categorize line items by HS Code, then sub-categorize by Country of Origin (COO). The DA must be a consolidated, summarized version of the invoice data, and the DA description must match perfectly with both the Supplier DA and the uploaded Bill of Entry (BOE).
4
Pre-Saving Data Preview. Review and preview the complete IN data to ensure absolute accuracy before committing it to the system.
5
Document Generation. Commit and save the finalized IN record to automatically generate the system-aligned DA, Invoice and Transfer of Ownership (TOO) documents.
6
BOE Validation & Reconciliation Status. Validate the uploaded BOE against the verified IN data, then generate the verification status together with the complete data reconciliation report.
✅ Standard Process
Recommended · verify before filing
1
Order Intake
Receive transfer order details directly from the client.
Receive transfer order details directly from the client.
2
Verification
Physical + documentation check at the shipper's warehouse.
Physical + documentation check at the shipper's warehouse.
3
Customs Filing
Process BOE and collect the shipment.
Process BOE and collect the shipment.
4
System Ingestion
Execute the WMS store-in process (IN Entry here).
Execute the WMS store-in process (IN Entry here).
5
Inventory Update
Log items into the active inventory balance.
Log items into the active inventory balance.
6
Compliance
Submit final documentation to Customs.
Submit final documentation to Customs.
⚠️ Alternative Process
Audit happens after filing
1
Pre-Verification
Review and verify initial shipment documentation.
Review and verify initial shipment documentation.
2
Customs Filing
Process BOE and collect the shipment.
Process BOE and collect the shipment.
3
Cargo Audit
Physical inspection of items post-filing — mismatch risk here.
Physical inspection of items post-filing — mismatch risk here.
4
System Ingestion
Run the WMS store-in process.
Run the WMS store-in process.
5
Inventory Update
Log items into active stock records.
Log items into active stock records.
6
Compliance
Submit final BOE to Customs.
Submit final BOE to Customs.
Where this tool fits
The reconciliation guards exactly the discrepancy risk in the Alternative process
Step 3–5 (Customs Filing → System Ingestion → Inventory Update) is where this system takes over: the IN Entry records the BOE, Stock & OUT handles releases against the correct IN, and Reconciliation auto-checks qty, HS code, country of origin, weight and value — catching any gap before it reaches Customs compliance.