Handle restitution: who knows what, and where it breaks

Restitution depends on knowledge spread across people who rarely sit together. Trade compliance knows why a refund is due. Logistics knows whether the goods actually left. The broker knows what was declared. Finance knows what money arrived. Trouble starts wherever one of them assumes another has already checked.

Who holds which piece

The trade compliance team understands eligibility. They know which tariff lines qualify, which regimes allow duty to be reclaimed on re-export or rejection, and what evidence the authority will demand. They usually do not know whether the paperwork they need was ever kept.

Logistics and the warehouse hold the physical truth. They know which pallet went out on which truck and whether goods were repacked or mixed with domestic stock. That detail decides whether an export can be matched to the original import. It rarely gets written down in a form anyone outside the dock can use.

The customs broker sees the declarations. Commodity codes, declared values and the reference numbers that link one movement to another all sit in the broker's system. A broker files what it is told, and if the instruction was wrong, the declaration is wrong in a way that looks perfectly tidy.

Finance sees the cash and the ledger. A refund lands in the bank, often with a reference that means nothing to the treasury team. Someone has to decide whether it reduces cost of sales, reverses a duty expense from a prior period or belongs to a customer. Finance usually lacks the trade context to make that call alone.

Sales and contract owners know the commercial terms. If the delivery terms put duty on the buyer, or a contract promises to pass refunds through, the money may not be the company's to keep. This knowledge sits in contracts that the trade team seldom reads.

Where the gaps cause trouble

The most common failure is the claim never made. Compliance assumes logistics will flag a qualifying export. Logistics has no idea the shipment mattered. The window to claim closes quietly and nobody notices, because nothing was ever recorded as missing.

A claim made on weak proof does more harm. A refund is filed against an import that cannot be traced to the export, because stock was commingled or a lot number was lost on repacking. The refund is paid, booked and forgotten. Later an audit asks for the link, cannot find it, and the authority recovers the money with interest and sometimes a penalty. The person who filed has often moved on.

Cash without context causes a slower kind of damage. Treasury receives an unexplained credit from a customs authority and parks it in suspense. Much later someone writes it off to miscellaneous income. The margin on the original product line is now misstated, and nobody can say which shipments the refund related to.

Then there is the refund that belonged elsewhere. When contract terms entitle a customer to the reclaimed duty, keeping it creates a liability that finance cannot see. The customer may know about it before the company does.

Brokers and in-house staff also disagree about who owns the claim. Each side thinks the other is tracking deadlines. Each holds partial records, and nobody has the full chain from import entry through to cash received.

Questions to ask the people who run it

What the procedure says and what happens on the floor tend to drift apart. These questions surface the drift:

• When a shipment qualifies for a refund, how does anyone find out? Is there a flag in a system, or does it depend on someone remembering?
• Could a recent claim be walked through from the original import to the money in the bank, using only the records on file?
• What happens to goods that are repacked or split before they leave, and how is the link to the import kept?
• Who decides what to claim, and who checks that decision before it is filed?
• When a refund arrives, how does treasury learn what it is for?
• Which customers have contract terms about duty or refunds, and who would know?
• Has an authority ever asked for proof on a past claim? What was hard to produce?
• What does the broker do unprompted, and what does it wait for instruction on?
• Where is the evidence kept, and would it survive the person who keeps it leaving?

Listen for workarounds. A spreadsheet maintained by one person, a mailbox nobody else can open, a habit of claiming only the large items because the small ones feel like too much effort. Each of these is where the real process lives.

Before changing anything

Map the chain of evidence before mapping the workflow. A redesign that speeds up filing but leaves the import to export link fragile simply produces bad claims faster. Settle who owns the deadline and who owns the proof, then decide who signs off the accounting treatment, and make sure each owner can see what the others hold. Bring the contract owners in early, since their knowledge decides whether the refund is income at all.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.