Skip to content

AI uses for records

Freight customs document discrepancy data as cross-document tasks

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Customs document discrepancies become cross-document reasoning tasks when each case is packaged with its full document set, the field pairs a reviewer compared, the test that decides whether a difference is a conflict, the rule or term that governs, and the correction that closed it. A model then has to find the conflict, name what governs and propose the next step, and a grader can check each part.

Document stack

Freight customs document

This page covers freight customs document discrepancy data as cross-document tasks.Illustrative

Key takeaways

  • The unit of data is the discrepancy packet, not the document: the full document set, the compared fields, the rule and the resolution.
  • Decide first whether values must be identical, must only not conflict, or must appear in a specific document; the label depends on it.
  • Record the purpose of review, because the same difference can be fine for transport and a problem for customs entry or a credit presentation.
  • Include cases where the majority of documents is wrong and cases with allowed differences, or a model learns to count votes.
  • Broker access to client files is not ownership or a license; confirm written authorization and strip party details before any packet leaves.

How do customs document discrepancies become cross-document reasoning tasks?

Treat each discrepancy as a case with a fixed document set, a named field conflict, the rule that makes the conflict matter, and the recorded resolution. The task asks a model to find the conflict across documents, say which document or rule governs, and propose the next administrative step; the grader compares that answer with what a licensed broker or documents examiner actually did and why.

Single-document extraction asks what a field says. A discrepancy task asks whether two or more fields that describe the same shipment can both be true, and if not, which one the process trusts. That is a different skill. The commercial invoice, packing list, bill of lading, importer security filing and entry summary are produced by different parties at different times, so the same carton count, origin or party name can drift between them for ordinary reasons as well as errors.

The useful unit of data is therefore not the document but the packet: every document the reviewer looked at, the pairs of fields they compared, the conflict they found, the rule they applied and the evidence that closed the case. A brokerage or forwarder already produces most of this as a by-product of its work. The specification below makes it explicit so a team can assemble packets consistently and a buyer can check them.

Which documents belong in one discrepancy case, and where does the case end?

One case is one shipment's document set examined for one purpose, from the first document received to the last correction or decision. If the same shipment is examined twice for different purposes, for example customs entry and a documentary credit presentation, those are two cases, because the rule that decides acceptability differs.

At a glance

Which documents belong in one discrepancy case, and where does the case end

Draw the boundary around the purpose, not the folder. A broker's file for an entry may hold emails, rate confirmations and arrival notices that never bear on the conflict. Including them adds noise and personal data without adding evidence. Include a document only if a reviewer compared at least one of its fields or relied on it to close the case.

The list below covers the documents most often compared in U.S. import and trade-finance work. Not every case uses all of them; record which ones were present and which were expected but missing, because a missing document is itself a common finding.

  • Commercial invoice: the seller's statement of goods, quantities, prices and parties; U.S. regulations set out what it must contain, including a detailed description, quantities and country of origin.
  • Packing list: the per-package breakdown of what was shipped; the invoice itself must also state what is in each package in adequate detail.
  • Bill of lading or air waybill: the carrier's receipt and transport contract, with its own description, marks, package count and weights.
  • Importer security filing: the advance data set for ocean cargo, including seller, buyer, manufacturer, ship-to party, country of origin and a tariff number.
  • Entry and entry summary: the filer's declaration to customs, which inherits values from the documents above and is what a later correction changes.
  • Purchase order, certificate of origin and any credit or contract terms: the buyer-side or contractual reference the shipment documents are tested against.

Which conflict test applies before anything is called a discrepancy?

Before labeling anything a discrepancy, decide which test applies: must the values be identical, or must they only not conflict? Documentary credit practice gives the clearest statement of the second test. ICC guidance on UCP 600 explains that data in a document need not be identical to data in other stipulated documents or the credit, but must not conflict with them, and that a presentation with conflicting data does not comply.

The ICC briefing illustrates this with documents that describe the same goods at different levels of detail: an invoice for a quantity of green hats, a certificate of origin for green hats and a bill of lading for hats do not conflict. A different model number does. A model that flags every wording difference as a discrepancy will be wrong in exactly the way an inexperienced examiner is wrong, so the packet must record which test the reviewer used.

Customs entry adds a second kind of requirement. Some data must be present and accurate in a specific document, whatever the others say. The invoice requirements in 19 CFR 141.86 and the entry-stage invoice rule in 19 CFR 142.6 are examples. A difference between a generic transport description and a detailed invoice description can be fine for transport and still leave the entry short of a required detail.

Which conflict test applies before anything is called a discrepancy?
Difference foundTest that usually appliesTypical labelEvidence the reviewer should cite
Same goods described more generally on the transport documentMust not conflictNot a discrepancyThe two descriptions and why one is a general form of the other
Model, part or lot number differs between invoice and packing listMust not conflictDiscrepancyBoth values, the purchase order line and the corrected document
Package count differs between packing list and bill of ladingMust not conflictDiscrepancy pending explanationCarrier receipt, tally or delivery note and the reviewer's conclusion
Country of origin differs between invoice and advance filingMust not conflict, and each filing must be accurateDiscrepancyManufacturer evidence and which filing was amended
Invoice lacks a required element present elsewhereRequired content in that documentDeficiency, not conflictThe missing element, where it was found and how it was supplied
Spelling or typing slip that leaves the meaning clearMust not conflictUsually not a discrepancyBoth strings and a note on why meaning is unchanged

Which fields does one discrepancy packet need?

The asset is a field list for one discrepancy packet. Fill one per case; keep the fields even when the answer is unknown and say so. Each field names what to capture, why a grader needs it, and how to check that the value is supported. It is written for administrative evidence only: it records what reviewers compared and decided, not the reviewer's legal judgment about penalties or liability.

Use stable identifiers for documents and fields so a grader can address them, and keep the original values next to any normalized ones. Normalized quantities, units and party names make comparison possible, but the reasoning task depends on seeing the raw form the reviewer saw.

Which fields does one discrepancy packet need?
FieldWhat to captureWhy the task needs itCheck before accepting the packet
Case boundaryShipment reference, purpose of review (entry, credit presentation, audit) and opened and closed datesFixes which rule applies and which documents belongOne purpose per packet; dates in order
Document setEach document's type, issuer role, version and date, with expected but missing documents listedLets the model reason about who said what and whenEvery compared field traces to a listed document
Compared field pairsDocument A field, document B field, raw values and normalized valuesDefines the cross-document comparison the grader scoresRaw values match the source images or files
Conflict testIdentical, must not conflict, or required contentStops wording differences being scored as errorsTest matches the review purpose
Governing rule or termRegulation section, credit clause or contract term the reviewer relied on, by citationSeparates the finding from the reason it mattersCitation resolves to the version in force on the case dates
Finding and labelDiscrepancy, deficiency, no conflict or unresolved, with the reviewer's one-line reasonThis is the target answerLabel agrees with the conflict test
Resolution evidenceCorrected or reissued document, amendment, carrier note or correction filing referenceShows how the case closed and makes the next-step answer gradableEvidence postdates the finding
ApprovalsRole of each person who decided or signed off, never their nameShows who had authority to close the caseAt least one qualified reviewer role recorded
Evidence maturityVerified by outcome, decided but unverified, or openLets buyers weight cases and exclude open onesOpen cases flagged, not mixed with closed ones
OutcomeWhat happened after resolution, such as release, accepted presentation or a later correctionConfirms the decision was right, or shows it was notOutcome date and source recorded

Which rule or term decides whether a document set was acceptable?

The answer depends on the purpose recorded in the case boundary: for customs entry it is the regulation and the filer's duty of care; for a documentary credit it is the credit terms read with UCP 600 and banking practice; for a commercial dispute it is the purchase order or contract. A packet that leaves this blank cannot be graded, because the same difference can be acceptable under one purpose and fatal under another.

For U.S. customs entries, three primary references cover most packets. The invoice content rules in 19 CFR 141.86 set what the invoice must state. 19 CFR 142.6 sets the invoice information needed at entry and allows some missing details to be supplied with the entry summary. CBP's post summary correction page describes the electronic route for correcting an accepted entry summary before liquidation, within set time limits, and warns that filers who rely on corrections excessively may be treated as failing to use reasonable care. CBP modified the PSC test by Federal Register notice in July 2026, so check that page for the current processing rules before modeling a correction route.

That last point is why resolution evidence matters. CBP's informed compliance publication on customs value notes that an importer may need to coordinate across its own departments so the value information it gives customs is complete, and that failing to do so might be treated as a lack of reasonable care. A packet that shows how a conflict was traced back to the purchase order or the warehouse count teaches the step that matters most.

For documentary credits, ICC Academy guidance on ISBP lists the usual sources of refusal: invoice errors in currency, unit price, totals or goods description, bill of lading problems such as dates, carriers and ports, and mismatches between the invoice and the transport document. It also advises reissuing a document rather than correcting it, since a correction can be treated as an alteration. Record which of these the reviewer relied on.

Worked packet: a carton count that disagrees across three documents (illustrative)

This example is illustrative and built for this article; it is not drawn from any client file. An importer's commercial invoice lists 500 cartons of one item, the packing list totals 480 cartons, and the ocean bill of lading shows 480 cartons as received by the carrier. The advance security filing and the purchase order agree with the invoice line. The broker opened the case at document receipt and closed it after the supplier's corrected invoice arrived 6 working days later.

The reasoning the task should demand has four steps: notice that two documents agree against one, identify which document is closest to the physical count, test whether a short shipment explains the gap, and choose the correction route that fits the entry's status. The packet records each step so a grader can score them separately rather than only the final answer.

Worked packet: a carton count that disagrees across three documents (illustrative)
Packet fieldIllustrative valueWhat a model must inferGrader check
Compared field pairsInvoice quantity 500 cartons; packing list 480; bill of lading 480Two documents agree against the invoiceModel names all three values and the outlier
Conflict testMust not conflictThe counts cannot all be trueModel does not treat this as a wording difference
Governing ruleInvoice quantity and per-package content requirements in 19 CFR 141.86The invoice must state accurate quantitiesCitation present and relevant
Finding and labelDiscrepancy: invoice overstates shipped quantity by 20 cartonsShort shipment is the likely causeLabel matches; cause stated as a hypothesis until confirmed
Resolution evidenceSupplier's corrected invoice for 480 cartons; broker note confirming a short shipmentThe correction must come from the issuerModel proposes obtaining a corrected document, not editing one
OutcomeEntry summary filed on the corrected quantity; case closed as verifiedCorrection route depends on whether the summary was already filedModel asks or checks filing status before naming a route

Which cases break the packet, and how should each be handled?

Every packet set needs cases in which the tempting answer is the wrong one. Without them, a model learns that the majority document always wins, which fails whenever the majority copied an earlier error.

  • The majority is wrong. If the packing list and bill of lading were both generated from the same booking that was never updated, agreement between them proves nothing. Record the provenance of each document so the task can test whether the model checks independence before counting votes.
  • The difference is allowed. A generic carrier description against a detailed invoice line, or a converted unit of measure, is not a conflict under a must-not-conflict test. Keep these as negative examples labeled no conflict, with the reviewer's reason.
  • The case is still open or contested. Exclude packets involving a penalty notice, prior disclosure, protest, investigation or a refused credit under dispute, or narrow them to the administrative facts and mark them unresolved. These depend on legal judgment the packet does not capture, and a licensed customs broker or counsel should decide whether they can be used at all.

Who may share broker and forwarder files, and what has to be removed first?

Holding the files is not the same as having the right to share them. A brokerage has access to its clients' documents to do the work; that access does not make the brokerage the owner of the commercial data, and it does not give permission to license it. Each is a separate question, along with any privacy duty attached to personal data in the files.

For U.S. customs brokers, 19 CFR 111.24 treats records about a client's business as confidential and limits disclosure to the client, the client's surety on an entry, DHS and other authorized officials, unless a subpoena, court order or the client's written authorization applies; information available from public sources is not covered. Freight forwarders and trade-finance teams have their own contractual confidentiality terms. Before any packet leaves the business, confirm in writing who may authorize the use and keep that authorization with the dataset.

Then remove what the task does not need. Party names, addresses, contact details, account and bank references, signatures and stamps can usually be replaced with stable role tokens such as seller, buyer and carrier without losing the reasoning. De-identification reduces exposure, but it does not create a right to license records that the business is not authorized to share.

Can a brokerage or forwarder license its discrepancy histories?

If your brokerage, forwarder or import operation keeps complete document sets with the corrections and decisions that closed each case, those histories are the raw material for this kind of task. The work is in assembling them into packets, confirming who may authorize their use and stripping what the task does not need.

A brokerage or forwarder that wants to license such histories can work with SourceX, which runs the rights review, contracting, preparation and delivery. Whether the business qualifies is checked first through a short questionnaire, with no files sent, and nothing is delivered until it has approved the scope and terms and signed. Location and size set the starting point: brokerages and forwarders based in the U.S., Canada or the EU need a peak workforce of at least 50 full-time employees, with contractors not counted, while those in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia can be considered when 90% or more of the records they offer are in English, as measured on the actual dataset.

Frequently asked questions

What is a customs document discrepancy?

It is a conflict between data that describe the same shipment in two or more documents, such as a quantity, origin or party that cannot be true in both. It differs from a deficiency, where a required element is missing from one document. Whether a difference counts depends on the purpose of the review and the rule that applies.

Do documents have to match word for word?

Not usually. ICC guidance on UCP 600 says data need not be identical across documents but must not conflict, so a general description on a bill of lading can stand beside a detailed invoice. Specific documents can still have their own required content, as U.S. invoice rules do for customs entry.

Which documents should a discrepancy training packet include?

Include every document a reviewer compared or relied on to close the case, typically the commercial invoice, packing list, bill of lading, advance filing, entry summary and purchase order. Leave out correspondence and attachments that did not bear on the conflict, and list documents that were expected but missing.

How is a cross-document reasoning task different from document extraction?

Extraction asks what a field says in one document. A discrepancy task asks whether fields across several documents can all be true, which document the process trusts, and what correction route fits. The grader scores the comparison, the label, the cited rule and the proposed next step.

Can a customs broker share client documents for AI training?

Only with proper authority. U.S. regulations treat broker records about client business as confidential and allow disclosure to the client and certain officials, or with the client's written authorization. Access to files is not ownership or a license, so confirm authorization in writing and have counsel review the specific facts.

Should open or penalty cases be included?

Generally no, or only in narrowed form marked unresolved. Cases involving penalties, prior disclosures, protests or disputed credit refusals depend on legal judgment the packet does not capture. A licensed customs broker or counsel should decide whether they can be used.

Sources

  • U.S. regulations require a commercial invoice to include a detailed description of the goods, quantities, country of origin and what each package contains. Source
  • The entry-stage invoice must give an adequate description and the quantities, and some missing details can be supplied when the entry summary is filed. Source
  • Customs broker records about a client's business are confidential and may be disclosed only to the client, the surety, authorized officials, under subpoena or court order, or with the client's written authorization. Source
  • A post summary correction is the electronic way to correct an accepted entry summary before liquidation, within set time limits, and excessive use may be treated as a failure of reasonable care. CBP modified the PSC test by a July 2026 Federal Register notice (91 FR 41053). Source
  • The importer security filing includes seller, buyer, manufacturer, ship-to party, country of origin, a tariff number, stuffing location and consolidator. Source
  • CBP says an importer may need to coordinate across its departments so value information is complete, and that failing to do so might be considered a lack of reasonable care. Source
  • ICC guidance on UCP 600 sub-article 14(d) says data need not be identical across documents but must not conflict, illustrated with differently worded hat descriptions that do not conflict. Source
  • ICC Academy guidance lists common invoice and bill of lading discrepancies, notes invoice and transport document mismatches are frequent, and advises reissuing rather than correcting documents. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies