Duty Accrual Reconciliation: Closing the Gap Between Accrued and Filed Duty
Chen Cui Co-Founder of GingerControl What changed: A retired service name (financial-visibility work) is replaced by the PO reconciliation service.
Duty accrual reconciliation is the month-end control that compares the duty you accrued, the duty your entries actually filed at, and the duty your brokers billed, and under stacked, fast-moving tariffs a flat annual accrual rate misstates margin within a quarter, so the rate must be derived from the live tariff stack of what you actually import.
What is duty accrual reconciliation?
Duty accrual reconciliation is the month-end control that compares three numbers that should agree and almost never do: the duty finance accrued, the duty your entries actually filed at, and the duty your brokers billed. We call this the Accrual Triangle. When its sides diverge and nobody signs off on the spread, margin is misstated, inventory is valued wrong, and classification errors age quietly past their recovery windows.
Use AI in import financial oversight to distinguish entry and invoice reconciliation from a tool that only reads the general ledger.
Duty accrual reconciliation compares accrued, filed, and billed duty per entity, per month. The filed number is the truth; the other two drift from it. Under current volatility, 72 percent of trade professionals call U.S. tariffs their top risk per Thomson Reuters' 2026 Global Trade Report (November 2025), a duty accrual set annually is not an estimate, it is a guess that compounds monthly on every imported unit.
Why does accrued duty never match filed duty?
Each side of the Accrual Triangle is built by different people from different data at different times:
| Side | Built by | From | Drift source |
|---|---|---|---|
| Accrued | Finance, at close | Last year's blended rate | Tariff actions, sourcing shifts, mix changes |
| Filed | Brokers, at entry | The live tariff stack per line | Misclassification, missed preferences |
| Billed | Broker invoicing, weeks later | Duty plus fees plus brokerage, bundled | Billing errors, timing, bundling |
The structural problem is that finance usually reconciles accrued to billed, the two soft numbers, because the filed truth sits in broker ABI files and ACE where finance never looks. That is the Five-System Split doing its damage at close: the one number grounded in law is the one missing from the working papers. Billed-side drift is its own audit.
How do you build an accrual rate that tracks reality?
Derive it, do not inherit it. The rate should come from the live tariff stack of what you actually import, weighted by value: per product and origin, base duty plus Section 232, Section 301 (the forced-labor Section 301 included) and other Chapter 99 layers in force on the entry date, as covered in how tariff stacking works. Then refresh it on Rate-Refresh Triggers rather than a calendar:
Check the Chapter 99 tariff layers after the primary product code, since the base rate is only part of the calculation.
- A tariff action touching any heading you import
- A sourcing-country shift on a top-20 product
- A product-mix change moving more than a few points of import value
- A preference program qualification or expiry
- Minimum quarterly, even if nothing above fired
GingerControl's Tariff Calculator covers the full U.S. tariff stack across 200+ countries, which is exactly the per-product rate truth a derived accrual model needs, and the same stack math your entries should be filing at, so accrual versus filed variance becomes a real signal instead of noise.
What should the close-week routine actually look like?
Quotable insight: The duty accrual is the only material cost estimate most multinationals never reconcile to its legal source document. Finance reconciles accrued to billed, two soft numbers, while the filed rate, the one grounded in the tariff schedule, never enters the working papers. In a regime where the top-risk item moves by proclamation, the Accrual Triangle's third side is not optional, it is the control.
The Close-Week Five, one entity at a time, biggest duty payer first:
- Pull the month's entries and compute the blended filed rate per entity
- Compare to the accrual rate; document the spread and who approved it
- Sample the largest-spread lines against the modeled stack, persistent excess points to recoverable errors
- Reconcile billed invoices to filed duty, fees separated from duty
- Log triggers fired this month and whether the rate refreshes next close
Teams at Level 0 or 1 of the Four Levels of Import Financial Control should start with step 1 alone, it is the analyst-week that prices everything else.
Where this fits your close calendar
GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes, and the accrual use case is what its PO reconciliation service, quoted for its scope, works on: matching entries line by line and keeping a record of every variance until it closes. Calculate your current stack or, for the standing control, book a call.
References
- Thomson Reuters Institute, 2026 Global Trade Report
Data cited: 72 percent name U.S. tariff volatility top risk; 225 senior trade professionals surveyed
Source: 2026 Global Trade Report
Published: November 2025 - 19 U.S.C. 1484, Entry of merchandise
Data cited: importer of record's reasonable care obligation
Source: 19 U.S.C. 1484
Questions people ask
What is duty accrual reconciliation in import finance?
It is the month-end comparison of three numbers that should agree and rarely do: the duty finance accrued, the duty actually declared on that month's entries, and the duty brokers invoiced. Persistent spread between them means margin is misstated and errors are aging past recovery windows. GingerControl's platform derives the filed number per entity from entry-level data, which turns the reconciliation from a broker data request into a lookup.
Why does our accrued duty never match what we actually paid?
Because the accrual rate was set annually while the filed rate moves with every tariff action, and because broker invoices bundle duty with fees and arrive weeks after entries file. A controller accruing a flat 5 percent while stacked Section 301 and 232 layers push filings to 12 percent is understating cost of goods every month. GingerControl's Tariff Calculator prices the current full stack per product and origin, which is the number an accrual model should track.
How often should we refresh our duty accrual rate?
On triggers, not on a calendar: any new tariff action touching your headings, any sourcing-country shift, any material product-mix change, and at minimum quarterly. In Thomson Reuters' 2026 Global Trade Report, 72 percent of trade professionals named U.S. tariff volatility their top risk, an annual rate-set is not a control in that regime. GingerControl's Compliance Radar catches the tariff-action triggers: it checks new U.S. trade notices against your HTS codes and lists what to redo by the effective date.
What journal entry problem does duty accrual drift cause?
Accrued duty lands in cost of goods or inventory at the accrual rate; the true liability follows filings. Drift between them means inventory is valued wrong, margins by product are wrong, and the catch-up entry at true-up distorts whichever month absorbs it. For a three-entity group importing $8M a month, a 3-point rate drift is $240,000 of monthly misstatement. GingerControl gives finance the filed-rate truth per entity so the accrual and the true-up both come from evidence.
Who should run the duty accrual reconciliation, finance or the trade compliance team?
Finance owns the control, compliance supplies the filed truth. The failure mode is each assuming the other watches the spread. The practical split: compliance certifies entry-level accuracy, finance reconciles totals to GL and invoices monthly, and both see the same variance report. GingerControl's audit tooling produces that shared view, entry-grounded numbers with reasoning finance can hand to auditors.
Can duty accrual reconciliation find recoverable money?
Yes, it is usually where leakage first becomes visible: a filed rate persistently above the modeled stack points to misclassification or missed preferences, both recoverable while their windows are open. Reconciliation finds the signal; the recovery lanes, Post-Summary Correction, protest, or refund claims, return the money. GingerControl pairs the reconciliation layer with recovery execution, starting with the compliance audit, a paid 30-minute review.
Rebuilding the same evidence for every audit?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS
