Multiple invoicing bills one genuine shipment two or more times. FinCEN’s advisory calls the simplest form double invoicing and groups it with over- and under-invoicing among the basic schemes.
What makes it interesting is not the mechanism, which is trivial, but where the evidence lives. Every element of the scheme is individually clean. The goods are real and can be inspected. The shipment sailed and the vessel can be tracked. Each invoice is internally consistent and each payment is properly documented. There is no anomalous transaction anywhere in the chain.
The anomaly is a relationship between two files, and relationships between files are exactly what nobody owns.
The structure that makes it work
The scheme’s essential move is separation. If both invoices are presented to the same institution, a competent operations team may well catch the duplicate on the transport document reference alone. So the presentations get split: two banks, or two branches, or a bank and an open-account settlement, or two entities in a group that keep separate books.
Each institution sees one payment against one document set for one real shipment. Each is correct in concluding that nothing is wrong with what it can see. The repetition exists only across the boundary between them, and no participant in the chain has both halves.
FinCEN’s list of indicators reaches this obliquely but usefully. The advisory flags payments made by an intermediary apparently unrelated to the buyer or seller, and payment instructions where no apparent business relationship exists between the originator and the beneficiary. Both are what the second leg of a duplicated payment tends to look like from the inside, because the parties introduced to receive it were introduced for that purpose.
Why the invoice number is the wrong key
The obvious reconciliation key is the invoice number, and it is close to useless. The seller assigns it. A party willing to bill the same goods twice will not helpfully reuse a reference, and there is no international convention that constrains the format.
The identifiers that resist manipulation are the ones assigned by parties with no stake in the payment:
- The bill of lading number, issued by the carrier or its agent. The strongest single key, and the reason a switch bill of lading is such a significant event: a second set legitimately obscures the original shipper’s identity in back-to-back trades, and it also breaks precisely this reconciliation.
- The container number, under ISO 6346, unique to the box and traceable through terminal records.
- The vessel and voyage number, together with IMO number, which fix the physical movement to a date and a hull.
- The customs declaration reference in each jurisdiction, which ties the goods to a filing made under penalty.
A reconciliation run on the transport document reference and the container number finds a duplicate that a reconciliation run on invoice numbers never will. This is a mundane point that has real consequences for system design: the field you deduplicate on determines whether the control works at all.
What visibility would actually require
There is no international registry that records which transport documents have already supported a payment, and there is no realistic prospect of one. Building it would require carriers, customs authorities and banks across every jurisdiction to share commercially sensitive transaction data on a common schema, which is a governance problem rather than a technical one.
That absence is worth stating plainly rather than treating as a gap awaiting a product. What is achievable is narrower and still valuable:
- Within an institution, deduplicate on carrier and customs references across the whole trade book, not per product line or per branch. This is the single highest-yield control available, and it is a data engineering task rather than an analytics one.
- Within a group, extend the same check across entities and across financing modes, so a documentary credit in one subsidiary and an open-account settlement in another are compared.
- Across institutions, the mechanism is the financial intelligence unit. FIUs receive suspicious activity reports from many reporting entities and can see repetition their individual filers cannot, which is a large part of why they exist and why the Egmont Group facilitates exchange between them. A report that names the bill of lading number, the container, and the vessel voyage is far more useful to that process than one that describes the pattern in prose.
FinCEN asks filers to put “TBML” in the SAR narrative and to explain why the activity is suspected. For this typology, including the transport references in the narrative is what makes the filing joinable to somebody else’s.
What it looks like on the way past
Multiple invoicing rarely travels alone. It appears with the other techniques, most often alongside price manipulation, because a party willing to bill twice has little reason to be scrupulous about the amount.
The indicators that recur, drawn from the published lists:
- payments beginning suddenly and stopping just as suddenly, consistent with a channel used and then abandoned;
- funds leaving an account in the same or nearly the same amount they arrived in;
- frequent transactions in rounded or whole-dollar amounts;
- a letter of credit amended without reasonable justification;
- an inability to produce the invoices supporting a requested transaction, which for this typology is often the most telling response of all.
That last one deserves the weight. In most trade disputes the paperwork arrives promptly, because a legitimate seller has it and wants to be paid. A request for the full set that is met with delay, partial disclosure, or a substitute document is information, and it is information obtained by asking rather than by modelling.