Volver a la biblioteca

Shipping document cross-check

Reconciles commercial, packing, and transport documents for one shipment and identifies discrepancies that could affect clearance, payment, or delivery. Use for export document checks, bill-of-lading review, packing-list reconciliation, and shipment release preparation.

por adlass TemplatesVersión 1Usa herramientas de adlassUniversal

Publicado 21 de ago de 2026 · Actualizado 26 de ago de 2026

Útil · 0Ver SKILL.md sin formato

Requisitos

Add the company's canonical field mapping and severity rules. Define authoritative sources for each shipment field. Set unit and currency normalization conventions. Add country or customer-specific document requirements as reference documents.

Documento de la habilidad

El SKILL.md completo que tu agente lee y sigue.

Shipping document cross-check

Purpose

Find document inconsistencies before they create customs, carrier, customer, or payment exceptions.

Scope

Commercial invoices, packing lists, bills of lading, air waybills, purchase orders, and documentary instructions. Excluded: customs classification decisions, filing, and carrier communication.

Data basis

  • Shipment documents, order or letter-of-credit terms, item master, and the company document-field mapping.
  • The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

Result

A field-level reconciliation matrix, discrepancy report, and correction instruction for each affected document.

Quality criteria

  • Core fields are compared across every document where they appear.
  • Each discrepancy names the documents, fields, values, and citation.
  • Quantity, weight, value, currency, parties, marks, and dates reconcile or are explained.
  • Severity is tied to the company rule or clearly marked as a default.
  • A clean shipment is reported explicitly rather than left blank.

Instructions

Normalize units only while retaining source values. Compare line items by a stable product or package identifier, then investigate unmatched lines. Distinguish harmless formatting differences from discrepancies that alter quantity, value, ownership, route, or payment terms. Never overwrite a source value; propose the correction and identify which document should be authoritative.

Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.

  • Add the company's canonical field mapping and severity rules.
  • Define authoritative sources for each shipment field.
  • Set unit and currency normalization conventions.
  • Add country or customer-specific document requirements as reference documents.

Habilidades relacionadas

  • 8D problem-solving report

    Builds a traceable 8D problem-solving report from a manufacturing complaint, defect record, and process evidence. Use for customer complaints, recurring production defects, containment records, corrective action reports, and structured root-cause investigations.

  • Capacity resource plan

    Converts demand forecasts, staffing calendars, work hours, absences, and throughput assumptions into a capacity plan with bottleneck dates and quantified staffing options. Use for workforce capacity planning, resource allocation, utilization review, and delivery-load analysis.

  • Construction punch list

    Converts inspection notes, photos, room data, and project requirements into a prioritized construction punch list with trade grouping and verification fields. Use for substantial completion, handover inspections, snagging, closeout walks, and defect follow-up.

  • Construction RFI draft

    Converts a construction field question or document conflict into a precise request for information with evidence, options, and schedule or cost implications. Use for RFIs, design clarifications, plan conflicts, specification gaps, and field coordination questions.