You paid the supplier in euros at 1.09 and declared the value at the same figure, and the entry was fine, until an audit pointed out that the conversion rate for customs is set by the date of exportation and taken from the prescribed source. Your bank's rate was not the legal one, and the difference was not rounding.
Customs valuation in dollars uses the rate of exchange prescribed by the Secretary of the Treasury, as published by the Federal Reserve Bank of New York, for the date of exportation. CBP guidance on currency conversion states the rule plainly: the conversion is tied to the date of export, not the payment date, not the entry date, and not the date the invoice was issued. Where no Federal Reserve rate exists for a currency or date, CBP certifies a rate instead.
The practical consequence is a spreadsheet column your team may not have. For each entry, the rate in force on the export date, applied to the transaction value in the foreign currency, is the dollar value. Your bank's applied rate is a cash reality that belongs in your finance records. It is not the customs value, and filing one where the other belongs creates a valuation difference on every affected entry.
Volatile currencies make the gap visible: a two percent move between the export date and the payment date is a two percent valuation difference, and across hundreds of entries it compounds into a real number. Long production lead times make it worse, because the export date can be weeks after the order date, and the rate the buyer mentally locked at order is history by then.
A second, quieter gap sits in invoices that mix currencies: goods priced in one currency, freight in another, insurance in a third. Each component converts at its own applicable rate and date logic, and a model that converts the invoice total at one rate will be wrong on the components even when the total looks close.
Record the rate source, the rate itself, and the export date it applies to, on the entry file, for every foreign currency entry. The Federal Reserve's daily rates are public, and CBP's own conversion tools exist, so there is no data access excuse. The failure mode is not access. It is that nobody owns the column.
Brokers often do this conversion as part of filing, which is fine, provided someone in your organisation can check it. Ask for the rate applied on a sample of entries each month and verify it against the published rate for the export dates. A broker error in the rate column repeats on every entry until someone samples it, and the correction cost grows with the delay.
Beyond the filing, the rate rule changes how to think about pricing. A supplier quote in euros is a price in a moving currency, and the duty you pay is a percentage of a dollar value set by a rate you do not choose. Contracts that quote in dollars push the risk to the supplier. Contracts that pay in a volatile currency should carry a margin allowance for the movement between quote and export date.
The habit to build is boring and valuable: every foreign currency purchase order carries the export date rate column, checked at entry, filed with the entry. Valuation disputes are slow and expensive. A rate column that is right costs a minute per entry. A rate column that is wrong costs the same minute, plus interest, spread across every entry since the error began.
Keep reading: A worked landed cost with a stacked duty: one container, every line shown, MPF and HMF: the two small fees that quietly wreck cost models.
The rate prescribed by the Treasury, published by the Federal Reserve Bank of New York, for the date of exportation. Where no Federal Reserve rate exists for a currency or date, CBP certifies one. The bank rate applied to the payment and the rate on the invoice date are not the customs conversion rate.
The export date. A payment made weeks before or after export can use a materially different rate, and the customs value must be converted on the export date rate. Long lead times make this gap larger, which is why the export date, not the order or payment date, is the one to record.
Each component converts at its applicable rate and date logic. Converting the invoice total at a single rate can be close on the total and wrong on the components. The entry file should show the rate per component with its source, so an auditor can follow each conversion.
The importer of record remains responsible for the accuracy of the entry, including the conversion, even when a broker performs it. Sampling the applied rates against the published Federal Reserve rates for export dates each month is the check that catches a repeated error before it compounds across entries.