外贸单证一致性检查

概述

Export Document Checker

Find actionable document discrepancies while preserving each source value, its location, and the limits of the available evidence.

Workflow

1. Inventory every supplied document by type, filename, issue date, revision, draft or final status, and readable scope. Mark superseded copies and uncertain OCR or extraction instead of treating all text as equally reliable.
2. Establish the review basis. Record any user-designated source of truth and applicable purchase order, contract, letter of credit, shipping instruction, or approved amendment. If authorities conflict or are unclear, report the conflict; do not choose a winner silently.
3. Read [references/document-field-matrix.md](references/document-field-matrix.md) and select only checks relevant to the supplied document set.
4. Extract comparison values with document name, page or section, raw value, normalized value, and confidence. Normalize only for comparison; never overwrite the source wording.
5. Compare identities, references, goods, quantities, units, commercial values, packaging, weights, marks, route data, dates, Incoterms, and documentary instructions.
6. Recalculate line extensions, totals, carton or package rollups, and weight relationships when inputs are readable. Apply an explicit tolerance and separate rounding from substantive differences.
7. Classify each finding by impact, evidence confidence, and resolution state. Name the exact documents and values, likely consequence, proposed correction, and party that should confirm it.
8. If the task includes letter-of-credit, transport-draft, single-document, or revision-control concerns, use [references/review-profiles.md](references/review-profiles.md).
9. When fields are available as normalized JSON, run scripts/document_preflight.py using [references/normalized-input-schema.md](references/normalized-input-schema.md), then reconcile its deterministic findings with the source documents.
10. For item-level matching, specify document IDs, equal shipment scope, composite keys and whether split rows are approved. Never use row order or fuzzy SKU matches as proof of identity. Check mixed cartons and fees only after confirming their units and amount basis.
11. Use –out NEW_DIRECTORY to export review.xlsx, review-summary.md, review.json and review-state.json. For a correction recheck use –previous prior/review-state.json. Read [revision workflow](references/recheck-workflow.md) before closing old issues.

Runtime: Python 3.10+; JSON review uses the standard library. Excel export requires scripts/requirements.txt. The host extracts source documents; the script is not an OCR, PDF or spreadsheet ingestion engine. Run the fictional examples/review.json for a deliberately inconsistent practice set.

Deliverable

Return:

• review basis, document inventory, versions, and scope limitations;
• a numbered high, medium, and low severity findings table;
• a cross-document comparison showing exact source values and locations;
• arithmetic, packing, weight, and total reconciliations with tolerances;
• missing, not applicable, illegible, and unresolved fields kept as distinct states;
• proposed correction owner or confirmation party for each open issue; and
• a pre-submission checklist with open blockers clearly identified.

The workbook contains scope/coverage, field comparison, line comparison, calculations, a correction register and a pre-submission checklist. States are passed, failed, unable and not_applicable. A zero finding count is not a pass if checks could not run. Coverage refers only to configured deterministic checks, not all possible trade requirements. Review the workbook for readability before sharing; the JSON retains the full evidence if a cell is too long.

If only one document is supplied, perform completeness and internal-consistency checks and state that cross-document validation was not possible. If the user requests a direct pass or fail answer, lead with the recommendation but retain the evidence and unresolved limitations that support it.

Boundaries

Do not invent unreadable values, infer that a blank field means not applicable, or silently use a pro forma invoice or older revision as the current authority. Do not assert that goods will clear customs, a bank will accept documents, or a carrier requirement is satisfied. Requirements vary by destination, product, payment method, contract, letter of credit, and carrier; distinguish common checks from verified shipment-specific requirements. Do not edit source documents unless the user asks.

Use [references/test-cases.md](references/test-cases.md) when evaluating future changes.