Import and Export Documentation Software for Nepal

Shipments are rarely held because something was packed wrong. They are held because a name on one document does not match the name on another, a value is inconsistent, a piece count is off by one, or a required document was never raised.

Almost all of those are data entry problems dressed up as compliance problems. A landlocked country routing most of its trade through third-country ports and airports has more document handovers than most, and every handover is another chance for a transcription error.

One record, many documents

The principle is simple and almost nobody implements it: the consignor name, consignee name, address, description of goods, piece count, weight and value should be entered once, on the shipment, and every document should be generated from that record.

In practice most cargo offices do the opposite. The shipment details live in a spreadsheet, and then someone opens a Word template for the commercial invoice, a different template for the packing list, a carrier’s portal for the airway bill, and a customs form, and types the same details into each. Four opportunities to introduce a discrepancy, and no way to tell afterwards which one is authoritative.

When documents are generated:

• A correction to the consignee address propagates to every unissued document automatically
• Piece counts and weights cannot disagree between the packing list and the airway bill, because they come from the same field
• Declared value appears identically on the invoice and the customs declaration
• Anything missing is missing loudly, before dispatch, not at a border

What a Nepali export shipment typically needs

Exact requirements vary by destination, commodity and mode, and this is not a substitute for your customs broker’s advice — but a document set for an export from Nepal commonly involves:

• Commercial invoice — parties, goods description, HS code, unit and total value, currency, incoterm
• Packing list — pieces, marks and numbers, dimensions, gross and net weight per piece
• Certificate of origin — issued by the relevant chamber or authority
• Airway bill or bill of lading — house and, where consolidated, master
• Customs declaration — with the reference retained against the shipment
• Product-specific certificates — phytosanitary, quality or permit documents depending on the commodity

The system’s job is not to know every rule. It is to hold a checklist per shipment type and destination, mark what has been produced, and refuse to let a shipment be marked ready when something on the list is missing.

HS codes belong in the product record

HS classification is one of the highest-risk fields, because getting it wrong changes duty and can turn a routine clearance into an inspection.

The fix is boring: HS codes should live on the customer’s product records, not be typed per shipment. A customer who exports the same handicraft category every month should be selecting from their own catalogue, where the code was set once and reviewed by someone who knows. Typing an eight-digit number per shipment guarantees an eventual typo.

The same applies to consignee records. A repeat consignee should be selected, not retyped, and their address should be the one that cleared last time.

Amendments need a history

Documents get amended. A value changes, a piece is removed, a consignee corrects their address after the invoice went out.

What causes trouble is not the amendment — it is nobody being able to say afterwards which version the carrier and the broker each received. A cargo system should version documents, timestamp each issue, and record who it went to. When a broker says the invoice they hold shows a different value, the answer should be a lookup rather than an argument.

Currency and value

International cargo is commonly quoted and invoiced in foreign currency while the operator’s own books are in NPR. The declared value on customs documentation, the commercial invoice value, the insured value and the amount you actually bill your customer are four different numbers that people routinely conflate.

The system should store the invoice currency and amount as entered, the exchange rate used and its date, and the NPR equivalent — separately, not as one converted number. Once a conversion is baked in without the rate being recorded, reconciling against a bank statement months later becomes guesswork.

The checklist that prevents most holds

Before a shipment is released for dispatch, a system can mechanically verify:

• Consignor and consignee names match across every generated document
• Piece count on the packing list equals the piece count on the airway bill or bill of lading
• Gross weight is consistent across documents
• Declared value on the invoice matches the customs declaration
• Every document on the checklist for this destination and commodity exists
• HS code is present on every line item
• Incoterm is set

None of those checks require judgment. All of them catch the errors that actually cause holds.

Import is the mirror image

On the import side the same discipline applies in reverse: the arrival notice, the delivery order, the customs entry and the final invoice to the consignee should all draw on one shipment record. Storage and demurrage charges accrue against that same record from arrival, so the charge presented to the consignee is derived rather than reconstructed.

Import shipments in Nepal also spend real time at the border and in transit through a third country. That dwell time should be visible as its own state with an age, not folded into a generic “in transit”, because it is the number a consignee will ask about.

We build cargo and logistics software for import, export and courier operators in Nepal, including document generation, HS code catalogues and per-destination checklists. If your documentation is a folder of Word templates, talk to us.