# Customs hold demurrage appeal, worked example | SourceX

Canonical: https://refer.sourcex.si/guides/demurrage-invoice-appeals-exception-examples
Last updated: 2026-11-04

Six records explain this kind of exception: the arrival and gate-out events, the free-time clause, the inspection hold and its lifting, the bill, the written challenge and the credit that settled it. Read in date order, they show when the goods could legally leave, when charges started, which days the importer contested and what the shipping line conceded. The Illustrative case below follows one box whose free days ran out while inspectors held it.

This worked case belongs to the [parent guide](/guides/workflow-demurrage-invoice-appeals), which covers what to inventory before a port vendor change. Here the job is narrower: one hard dispute, told day by day, with the person who made each call and the document that proves it.

## Setting: four free days and an inspection

A fictional 340-person freight forwarder clears an inbound 40-foot box for a furniture client. The shipping line allows four free days after unloading, then charges a flat $175 per day. On day 3, the shipment is selected for an intensive inspection. Selected shipments generally go to a privately operated Centralized Examination Station, and the importer pays for the inspection. The hold lasts five days, and the free days run out while nobody is allowed to collect the goods. This shipment, line and settlement are invented for this page.

## Timeline of the dispute

| Day | Event | Evidence and where it sits | Charge consequence |
|---|---|---|---|
| 0 | Unloaded from the vessel | Discharge event, terminal website | Free days begin |
| 3 | Inspection hold placed | Hold flag online; clearance agent's notice with entry number | Goods frozen |
| 4 | First chargeable day | Free-time clause, service contract | Daily charges start |
| 8 | Hold lifted | Release notice from the clearance agent, by email | Goods collectable |
| 10 | Truck collects the box | Gate-out event, terminal website | Clock stops: 6 days billed |
| 24 | Bill arrives: 6 days, $1,050 | PDF in the payables inbox; vendor bill in the ERP | Inside the 30-day billing limit |
| 31 | Challenge sent, citing hold dates | Email to the line's dispute desk, release notice attached | Inside the request window |
| 52 | 4 days credited, $700; $350 paid | Credit memo in the ERP, tied to the vendor bill | Settled |

Days 24 and 31 both sit inside federal limits: the line must bill within 30 calendar days of the last charge, and the billed party has at least 30 calendar days to ask for a refund or waiver. Each date is documented. This is general information, not legal advice.

## Five calls, five owners

The file is only as good as the trace each decision left.

1. **Inspection officer: hold the shipment.** Traced in the online hold flag and the clearance agent's notice. The forwarder does not own that notice; the agent does until a copy is saved to the job.
2. **Line billing team: charge six days.** Traced on the bill, which states the daily rate and the free days allowed.
3. **Forwarder's logistics accountant: contest four of the six days.** The judgment call. Days 4 to 7 fell inside the hold; days 8 and 9 came after release, when the goods could have left. Challenging only the frozen days is what makes the request credible. Traced in the challenge email.
4. **Line dispute desk: concede four days.** Traced in its reply and in the credit memo.
5. **Finance director: approve paying the remaining $350.** Traced as the payment and the memo's reference to the original bill.

The reasoning in step 3 is simple: the charge exists to get boxes collected, and for days 4 to 7 nobody was allowed to collect this one. The challenge says exactly that, with the agent's dates attached. The line also has a duty here: under the federal billing rules it must try to resolve a timely request within 30 calendar days of receiving it, and the day 52 credit falls inside that window.

## What a weaker file would lose

Take away one record at a time and see what the case becomes.

| Missing record | What the file can no longer show |
|---|---|
| Agent's release notice | When the hold ended; the four credited days look arbitrary |
| Online hold flag | That a hold existed at all, unless the agent's notice survives |
| Free-time terms | Why charges began on day 4 rather than another day |
| Challenge email | Which days were contested, and why only four |
| Credit memo link to the bill | Whether the $700 settled this invoice or was netted elsewhere |

The full set is what turns an invoice into a decision record: the problem (charges while cargo was held), the action (a challenge limited to the frozen days, backed by dated evidence) and the checked result (a credit matched to the bill). The same problem-action-result shape appears across [logistics exceptions and their documented resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) and in [accounts payable exception handling](/data-types/accounts-payable-exception-handling-process).

## Signs a client has files like this

Listen for these in conversation with a finance director or logistics accountant at a forwarder, NVOCC, importer or [freight audit and payment company](/industries/freight-audit-and-payment-company):

- Charge disputes are a routine task with a named owner, not an occasional email.
- Broker hold and release messages are filed with the job, not left in personal inboxes.
- Credit memos reference the original vendor bill number.
- Denied requests are kept alongside successful ones.
- Several years of history exist, and someone can say roughly how many disputes a year.

Three or four of these is enough to raise the topic. The [records across systems map](/guides/demurrage-invoice-appeals-records-across-systems) shows which keys join the portal, broker and ERP records, and the [who-can-license tree](/questions/who-can-license-demurrage-invoice-appeals-records) identifies the executive to introduce. Partners record answers only: no invoices, exports, broker emails or logins.

## Qualification and the open points

SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. For a forwarder, many records concern clients' shipments, and client agreements may limit reuse. That, along with de-identification, SourceX's current data needs and any offer, stays unknown until SourceX reviews it. [How AI labs buy data](/questions/how-do-ai-labs-buy-data) gives the buyer side in general terms.

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client keeps hold evidence with its disputes and links each credit to its bill, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before raising it with the finance director.

## Sources

- https://www.cbp.gov/trade/basic-import-export/importer-exporter-tips
- https://www.ecfr.gov/current/title-46/chapter-IV/subchapter-B/part-541/subpart-A
- https://refer.sourcex.si/terms
