Trade Document Consistency Precheck

Problem Addressed

Trade documents often repeat the same facts across multiple files: purchase orders, pro forma invoices, commercial invoices, packing lists, and bill of lading drafts may each carry buyer/seller names, product descriptions, quantities, weights, ports, and payment terms. Manual review usually depends on scanning each document in isolation, which can miss high-risk issues such as net weight exceeding gross weight, currency mismatches, or conflicting ports. This skill gathers the same fact into one comparison checklist and classifies issues into:
- Explicit conflict: different documents provide different values
- Missing information: an expected field is absent
- Internal anomaly: the materials are logically inconsistent
- Needs human confirmation: no unique answer can be determined from the materials

How It Works

The skill does not rewrite documents directly. It normalizes and compares fields first:
1. Identify document types, including orders, pro forma invoices, commercial invoices, packing lists, and bill of lading drafts.
2. Preserve original text and create normalized fields separately; do not alter company names, addresses, product names, numbers, or ports without review.
3. Structure inputs according to references/input-schema.md; low-confidence scanned fields should be confirmed by the user first.
4. Check high-priority fields first:
- Buyer, seller, consignee, notify party, and document numbers
- Product name, specification, quantity, unit price, total amount, and currency
- Package count, packaging type, net weight, gross weight, and volume
- Port of loading, port of discharge, destination, and transport mode
- Incoterm, named place, and version
- Marks, batch, dates, and payment terms
5. For each discrepancy, explain which documents contain it, what the values are, which commercial fact should be treated as the reference, and which document should be corrected.
6. Generate a report following references/report-schema.md.

Boundaries

This skill is suitable for a pre-submission consistency check. It does not verify factual truth, infer missing values, or claim compliance with letters of credit, customs, or carrier requirements. Product descriptions may differ reasonably across documents; text differences alone are not enough to call a conflict. When semantic judgment is required, the original text and reasoning should be shown. For letter-of-credit clause review, use $precheck-letter-of-credit instead.