Export Documentation from Pakistan: PSW, Customs, Invoices, Packing Lists and Certificates

Export documents are one data set. The contract defines the sale; the commercial invoice records it; the packing list accounts for packages; the customs declaration reports the shipment; and the transport document records carriage. Certificates and bank documents add required evidence. Names, quantities, values, dates, ports, and references should remain consistent throughout.

Open a control sheet when accepting the order. Record one internal reference, legal parties, Incoterm and named place, currency, payment method, proposed HS code, product description, destination, transport, and certificates. Assign each document an owner and deadline.

Pakistan Single Window (PSW) provides the electronic Single Declaration for export clearance and routes data to Customs and participating agencies. Access depends on current subscription, customs, and banking-profile requirements. PSW says a trader or customs agent can create the declaration and associate a financial instrument for specified payment modes. Use the current manual because portal fields can change.

1. Confirm active PSW and Customs access, authorized users, business profile, and bank association before dispatch.
2. Verify payment mode and the relevant instrument with the authorized dealer bank.
3. Have the customs agent review classification, regulatory measures, ports, procedure, and expected evidence before packing.
4. Finalize invoice and packing-list data from actual production, then issue controlled copies.
5. Compare the draft declaration with source documents before submission and retain its reference and approvals.
6. Coordinate cargo arrival, possible examination, carrier cut-offs, loading, and final documents on one timeline.

Portal acceptance does not prove the facts are correct. Review classification, value, origin, restrictions, and contract terms. Also check current practice before following old Form-E advice: PSW describes electronic bank-profile and financial-instrument exchange replacing the earlier EIF/EFE step for covered flows.

The export Goods Declaration should reflect the actual consignment. Typical data covers parties, goods description and HS classification, quantity and unit, value and currency, origin and destination, transport, ports, packages, and payment. Exact fields vary. Give the agent specifications, composition, intended use, and catalog material where useful; a product nickname is rarely enough.

Assign who will answer Customs or agency queries and coordinate an examination. Corrections after filing may require a formal process and miss carrier cut-offs, so compare the draft with the invoice and packing list first. Never split, undervalue, or redescribe goods to avoid a control; escalate uncertainty.

• Use specific descriptions that a reviewer can connect to the invoice, packing list, and product.
• Reconcile invoice quantity and value to declaration line items, including units of measure and any permitted adjustments.
• Reconcile package count, marks, net weight, and gross weight to the final packing record and carrier booking.
• Verify whether a licence, permit, certificate, or other approval must be linked or uploaded before clearance.

A proforma invoice is a pre-sale offer or confirmation of specifications, price, delivery, validity, payment, and shipping assumptions. Label and reference it clearly. It may support buyer approvals, but should not become the final record when quantities, dates, freight, or values change.

The commercial invoice reflects the sale and actual shipment. Common fields include number and date; required parties; order or LC reference; goods description; HS code where requested; quantity, unit, unit price, totals, currency, discounts or charges; Incoterm and named place; origin; known transport details; payment terms; and required signature or certification.

Keep the product description identifiable and compatible across documents. Check arithmetic, currency, decimals, units, and legal names. An Incoterm such as FOB or CIF needs a named port or place and agreed edition. It allocates specified costs and risks, not title, payment timing, or every customs responsibility.

The packing list explains the physical shipment and normally omits prices. Show parties, invoice and order references, date, package type and count, marks, contents by package, quantities, net and gross weights, and relevant dimensions or volume. Number cartons, pallets, crates, or bundles consistently.

Finalize it after packing, not from an estimate. Reconcile quantity to the invoice and packages and weight to warehouse and booking records. Explain valid differences, such as pallets included only in gross weight. Avoid duplicate carton numbers or marks conflicting with carrier instructions.

For sea freight, the carrier or agent issues a bill of lading (B/L) after receiving or loading cargo. An air waybill (AWB) records air carriage but is generally non-negotiable. Neither should be described simply as proof of ownership; its effect depends on the document, contract, mode, and rules.

Send instructions early and check the carrier draft: parties, route, marks, packages, description, gross weight, freight notation, relevant on-board date, and originals. Match LC requirements. Agree whether originals, a sea waybill, surrender or telex release, or an electronic document is acceptable. Never request false dates or descriptions.

A certificate of origin (COO) identifies origin for customs or commercial purposes; it does not mean every input came from Pakistan. Preferential treatment requires meeting the agreement's specific rule, such as tariff shift, value content, or production. Non-preferential origin serves another purpose.

TDAP says preferential certificates may be issued through TDAP or self-certified under the arrangement, while chambers issue non-preferential certificates. Covered TDAP applications use PSW. Confirm the agreement, route, origin criterion, evidence, and buyer requirement. Retain bills of materials, supplier declarations, production records, and calculations supporting the claim.

There is no universal certificate pack. Plants may require phytosanitary controls; food or animal products may need health documents; chemicals can need safety data or permissions; and medical devices, pharmaceuticals, textiles, wood packaging, or industrial goods may face conformity, testing, registration, labeling, fumigation, inspection, or traceability rules. Authorities vary by product and destination.

• Ask the buyer for the rule and issuing authority, not a certificate name copied from another supplier.
• Check PSW and Pakistani and destination authorities for current measures tied to the likely HS code.
• Confirm whether testing covers the exact batch, site, season, or shipment and when inspection occurs.
• Validate issuer accreditation, format, language, validity, presentation form, and legalization.
• Allow time for sampling, laboratory work, inspection, and amendments; certificates may not be retrospective.

Under a letter of credit, banks examine documents against the credit and applicable practice, not the goods. If it incorporates ICC UCP 600, review it and all amendments with your bank. Check expiry, presentation place and period, shipment date, amount and tolerance, partial shipment or transshipment terms, required issuers and copies, insurance, and conditions lacking documentary evidence.

Map each LC condition to a document and owner. Compare drafts before shipment; amend impossible clauses before cargo moves. Consistency matters, but "character-for-character" is not a universal rule: UCP and banking practice govern examination, while the credit may require particular wording. Ask the bank about ambiguous clauses.

In a documentary collection, banks transmit documents, commonly against payment (D/P) or acceptance (D/A), but generally give no LC-style payment undertaking. ICC URC 522 applies when incorporated. Match the collection order, draft, invoice, transport records, certificates, amount, currency, and release instruction. Assess risk carefully where release is against acceptance.

Store a read-only final pack under the order and declaration reference: contract, invoices, packing list, declaration and amendments, approvals, certificates, test reports, transport and insurance documents, bank presentation, carrier correspondence, delivery evidence, and payment reconciliation. Retain origin, classification, production, and supplier evidence too.

Use clear DRAFT, APPROVED, and ISSUED versions; restrict editing; record approval; and back up securely. Set retention periods with qualified advisers because legal and contractual periods differ. Records support audits, origin checks, eligible claims, and buyer questions, but cannot cure an inaccurate filing.

Create an index page for every shipment file. Record the document name, issuer, issue date, version, original or copy status, recipient, dispatch method, and responsible employee. The index gives management a fast completeness check and helps a bank, buyer, customs agent, or auditor locate the controlling record without opening dozens of similarly named attachments. Protect personal and banking data with role-based access, and send sensitive files through an agreed secure channel rather than informal messaging groups. When a document is corrected, preserve the superseded copy with a clear reason instead of silently overwriting it; the audit trail should explain what changed, who approved it, and which external parties received the replacement.

• Party names or addresses differ across the order, invoice, LC, declaration, certificate, and transport instructions.
• A vague invoice trade name conflicts with the declaration's technical description or HS code.
• Quantities, units, packages, net or gross weights, and carrier data do not reconcile.
• A preferential form is used without meeting its rule, or the COO has wrong shipment data.
• A product certificate is missing, expired, for another batch, or obtained at the wrong stage.
• The B/L or AWB has incorrect parties, route, freight status, marks, dates, originals, or LC wording.
• LC documents are late, incorrectly signed, inconsistent, or cannot evidence a credit condition.
• Cargo arrives before approvals or misses carrier cut-offs, causing storage, rollover, or rebooking.

Stop circulating superseded versions. Record the issue, documents, owner, deadline, and correction. Ask each agent, carrier, issuer, or bank how its record must be amended; changing only your PDF can leave official data inconsistent.

1. Confirm the contract, buyer instructions, payment, Incoterm and named place, shipment window, and document responsibilities.
2. Confirm active PSW, Customs, and bank profiles and authorize only appropriate users.
3. Validate description and proposed HS code; check export controls and destination measures.
4. List each approval, COO, product certificate, inspection, test, and insurance record with issuer, validity, and lead time.
5. Finalize packing; reconcile invoice, packing list, labels, marks, weights, quantities, and packages.
6. Compare the draft Single Declaration with controlled documents, payment data, and approvals.
7. Check the B/L or AWB draft for parties, route, dates, cargo, freight terms, and originals.
8. For an LC or collection, check every instruction, signature, original, and presentation deadline.
9. Confirm handover, carrier cut-offs, examination coordination, certificate status, and query contacts.
10. Assemble and send the final pack securely, reconcile payment, and retain the record.

In an RFQ response, state the Incoterm and named place, likely port, lead time, payment assumptions, and available certificates. Separate standard documents from buyer-specific testing or legalization affecting price or schedule. Verify the exact product, market, standard, and evidence before claiming compliance.