# Demurrage appeal records: system map and keys | SourceX

Canonical: https://refer.sourcex.si/guides/demurrage-invoice-appeals-records-across-systems
Last updated: 2026-11-04

Five shared identifiers stitch one demurrage dispute together: the container number, the bill of lading number, the customs entry number, the carrier's invoice number and the service contract number, with the ERP's own vendor bill and credit memo IDs tying the ledger entries to each other. Each identifier sits in some of the five places that hold the case, never in all of them. The fragile join is usually the inspection hold, recorded only in a clearance agent's message whose entry number appears nowhere in the ledger.

This map is part of the [parent guide](/guides/workflow-demurrage-invoice-appeals). The guide sets out what to inventory before a port vendor change; this page traces which identifier lives where, so a partner can tell whether a company's dispute history can be followed from first event to final credit.

## Five record holders, one shipment

- **Terminal system.** Unloading, availability and gate-out timestamps, a hold flag where the operator shows one, sometimes a last free day. Primary identifier: the container number.
- **Clearance agent.** Inspection selection, hold and lifting notices, entry records. Primary identifier: the entry number, with the container number only if the agent typed it.
- **Payables inbox.** Carrier bills as PDFs, the challenge emails and the dispute desk's answers. Primary identifier: the carrier's invoice number.
- **ERP.** Vendor bills, credit memos, payments and the job file. Primary identifiers: internal document IDs, plus whatever outside numbers staff keyed in.
- **Contract folder.** Tariffs, service contracts and amendments fixing free days and daily rates. Primary identifier: the contract or amendment number.

## Identifier map: system, record, linking key, owner

The evidence asset for this page. Each row names a record, the field that should carry a shared identifier, and who can confirm whether it does.

| System | Record | Linking key | Owner |
|---|---|---|---|
| Terminal system | Unloading, availability, gate-out timestamps | Container number | Import coordinator |
| Terminal system | Hold flag | Container number | Import coordinator |
| Clearance agent | Hold and lifting notices | Entry number plus container number | Customs compliance manager |
| Payables inbox | Carrier bill PDF | Invoice number plus container number | Logistics accountant |
| Payables inbox | Challenge email and reply | Invoice number in the subject line | Logistics accountant |
| ERP | Vendor bill | Vendor bill ID, invoice number, container in line or memo field | Payables lead |
| ERP | Credit memo | Credit memo ID referencing the vendor bill ID | Payables lead |
| ERP | Job file | Bill of lading number plus container number | Operations manager |
| Contract folder | Tariff or service contract | Contract number printed on the bill of lading or invoice | Procurement or finance director |

Federal billing rules make one join dependable: carrier and terminal bills must identify the boxes, including the bill of lading number and container number, and state free time, the dates charged and the rate. So the invoice almost always carries both keys and becomes the bridge between timestamps and ledger. The same rules let a billing party that sent the bill to the wrong party reissue it only within the 30-day window, and in 2025 the D.C. Circuit set aside the provision on who may be invoiced while leaving the rest in force, so the billed party can change from case to case. The map should record whether bills arrive at the forwarder, the importer or both. This is general information, not legal advice.

## The links that break most often

| Link | How it breaks | Question for the finance director |
|---|---|---|
| Clearance agent to everything else | Lifting notice sits in the agent's system or a personal inbox | Are the agent's hold and release messages filed with the job? |
| Terminal system to ERP | Container number typed into a memo field, or not at all | Was the container keyed on the vendor bill line? |
| Credit memo to bill | Credit netted against a later invoice instead of the original | Do credit memos reference the original vendor bill ID? |
| Contract to invoice | Free-time terms live in an amendment nobody indexed | Where are tariffs and service contract amendments filed? |
| Terminal history | Timestamps expire or end with the terminal system contract | How many years of events can still be viewed or downloaded? |

Export capability and history depth vary by terminal operator, so the company should confirm them with each provider. Where invoices were paid through a separate AP tool, the page on [Bill.com invoice history](/systems/bill-com-export-invoice-history) lists the questions for that layer.

## One case joined end to end (Illustrative)

Built for this page from the [worked exception example](/guides/demurrage-invoice-appeals-exception-examples): a fictional 340-person forwarder, one import container, a customs hold on day 3, six days billed at $175 a day. All identifiers are placeholders.

| Order | Record | System | Keys carried | Joins to |
|---|---|---|---|---|
| 1 | Free time of four days, then $175 per day | Contract folder | Service contract SC-12 | Row 5 |
| 2 | Discharge day 0, gate-out day 10 | Terminal system | Container C-1 | Rows 3 and 5 |
| 3 | Hold placed day 3, released day 8 | Clearance agent email | Entry E-55, container C-1 | Rows 2 and 6 |
| 4 | Shipment file | ERP | B/L 4410, container C-1 | Rows 2 and 7 |
| 5 | Invoice for 6 days, $1,050 | Payables inbox | Invoice INV-2207, container C-1, SC-12 | Rows 6 and 7 |
| 6 | Appeal citing hold dates | Payables inbox | INV-2207, entry E-55 | Rows 3 and 8 |
| 7 | Vendor bill | ERP | VB-883, INV-2207, container C-1 | Rows 4 and 8 |
| 8 | Credit memo for $700; $350 paid | ERP | CM-119 referencing VB-883 | Row 7 |

Row 3 is the one to watch. If the agent's email had not carried the container number, or had never been saved with the job, row 6 would cite dates nothing else in the file could confirm.

## Scoring the map with the company

Walk the linking-key table with the finance director and mark each row yes, partly or no. Add the years each system covers, roughly how many disputes a year, and whether any terminal system or clearance agent changed during the period. That is the whole partner task. [Cross-system data value](/guides/cross-system-data-value-ai) explains why joined records say more than isolated ones, and [SourceX's current data needs and value](/guides/how-to-explain-why-buyer-demand-changes-the-value-of-a-data-opportunity) explains why no partner can price the result. The [referral brief template](/resources/demurrage-invoice-appeals-referral-brief-template) turns the score into a forwardable note.

## Who confirms, who decides, what waits

The logistics accountant, AP lead and customs compliance manager can confirm which keys exist. None of them can authorize licensing; the CEO can, often with the CFO preparing the case and counsel reviewing client, carrier and broker agreements. For a forwarder, many records describe clients' shipments, so reuse limits, de-identification, SourceX's current data needs and any offer stay unknown until SourceX reviews them. Partners never take invoices, exports, broker emails or logins; the AP side of the workflow is described in [accounts payable exception handling](/data-types/accounts-payable-exception-handling-process).

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 most links on a client's map hold, especially the clearance agent and credit memo rows, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before sending the summary.

## Sources

- https://www.ecfr.gov/current/title-46/chapter-IV/subchapter-B/part-541
- https://www.fmc.gov/articles/u-s-court-of-appeals-issues-decision-in-case-on-demurrage-and-detention-billing-practices/
- https://refer.sourcex.si/terms
