Table of Contents
Trade compliance recordkeeping knowledge is the ability to say, for any given shipment, which documents must exist, who is legally obliged to hold them, how long each retention clock runs, in what form the records may be stored, and how fast the file can be produced when an authority asks. It is procedural knowledge. That makes it one of the easiest compliance areas to assess fairly, and one of the most commonly fumbled in real work.
Almost everyone in trade touches the records. Far fewer can explain the rule behind the record, or say which party carries the obligation when a broker, a forwarder and a buyer all hold copies of the same document.
Below: what the knowledge consists of, how assessments test it, and where contract terms sit inside the file.
What recordkeeping knowledge covers, precisely
Break it into five questions. Any competent assessment of this area, and any competent internal audit, works through the same five.
- Which records does this transaction have to generate?
- Who is the legal recordkeeper for each of them?
- What event starts the retention clock, and how long does it run?
- What form may the record be held in, and what has to be reproducible from it?
- How quickly can the file be retrieved, and can you prove the process is consistent?
Most published guides answer only the first question, then stop. The list is the shallow part. Ownership, the clock and the retrieval test are where audits are lost.
The document set, by side of the transaction
Import records
The entry package sits at the centre. That means the entry summary and everything that supports the declared values and the declared classification. Commercial invoice, packing list, transport document, any preference claim and the evidence behind it, any permit or agency filing, and the payment records that show what was actually paid for the goods.
A preference claim pulls a second document set in behind it. If a good entered at a preferential rate, the supporting origin evidence becomes part of the retained file, and a certificate of origin and the data behind it has to survive as long as the entry does. Auditors ask for the evidence, not the certificate alone.
Export records
The export side is broader than people expect, because the obligation attaches to the transaction rather than to a single filing. Licences and licence exception records. Electronic filing confirmations. Classification determinations and the reasoning that produced them. Screening results. Correspondence that discusses end use, end user or destination. Contracts, bids and quotations. Boycott request records where the rules require them.
Note the pattern. Emails and internal notes are records. A written classification rationale sitting in someone’s inbox is part of the file, and a question that tests whether you know that is testing something real.
The contract layer nobody lists
Here is the gap in almost every published guide. The sale contract and the documents that vary it belong in the compliance file too, and they often decide the answer to a compliance question.
The delivery term chosen in the contract determines who clears the goods and therefore who files, and filing is what creates the retention duty. The payment mechanism determines which bank documents exist. A price adjustment agreed by email after shipment changes the value that should have been declared. Where the contract names an importer of record, it has effectively named the party carrying the import recordkeeping obligation. Auditors read the contract. Compliance teams frequently do not keep it.
Retention clocks, and why the start date is the hard part
Retention periods vary by authority, by programme and by record type. The period itself is something you look up. The knowledge being tested is usually what starts the clock, because that is what people get wrong.
Retention is generally event triggered, not creation triggered. A record is not kept for a set period from the day it was written. It is kept for a set period from a defined event: the date of entry, the date of export, the date the transaction ended, the date a claim was paid, or the date a licence expired. A file created early in a long contract can therefore have a clock that has not even started.
Three practical rules follow, and they are worth memorising.
- One transaction can carry several clocks at once, because several agencies have an interest in it. Customs, export control, financial sanctions and tax authorities each set their own.
- When clocks overlap, the longest one governs the file in practice. Splitting a file so that half is destroyed early creates an unexplainable gap.
- A request, a summons or an open enquiry suspends destruction. Once an authority has asked, the retention schedule stops being the controlling document.
A fourth rule applies to anyone working across borders. Retention obligations follow the jurisdiction of the filing, not the location of the head office. A regional team that keeps one global schedule and applies it everywhere will be wrong somewhere.
Form, storage and the reproduction test
Electronic storage is widely permitted, and that permission comes with conditions. The usual conditions are that the stored image is complete and legible, that it can be reproduced on demand in a readable form, that the storage system is documented in writing, and that the business periodically tests its own system and keeps the test result.
That last condition is the one teams skip. A written procedure with no evidence that anyone has tested it is a weak defence. Regimes that allow alternative storage also tend to require a backup copy held separately, and some require advance notice to the authority before the business switches methods.
Scanning also destroys things quietly. A screenshot of a screening result may not carry the date and time of the check, the list versions used, or the reviewer’s name. If the reproduced record cannot answer the question the original could, the storage method has failed even though every file opens.
What gets tested, and where it lives in the job
Assessment questions in this area tend to be scenario shaped rather than definitional. The table below maps the knowledge areas to the form the question usually takes and to the daily task behind it.
| Knowledge area | How an assessment asks it | The job task behind it |
|---|---|---|
| Who is the recordkeeper | A scenario with a broker, a forwarder and a buyer, asking which party carries the duty | Deciding what your own file must contain versus what an agent holds for you |
| Retention trigger | A date sequence, asking when the clock starts | Setting destruction dates in the document system |
| Scope of a record | A list of items including emails and notes, asking which are records | Capturing correspondence that varies price, term or end use |
| Storage conditions | A described electronic system, asking what is missing | Writing and testing the storage procedure |
| Retrieval under request | A demand letter scenario, asking what you do first | Running the response process without touching the underlying data |
| Contract terms in the file | A term of sale plus a later email, asking what the declared value should reflect | Reconciling the contract against the declaration |
Retrieval is the part that fails
Most businesses have the records. What they lack is the ability to assemble a named file quickly, completely and without altering it. When a request arrives, the clock is short and the scope is specific.
Run a drill. Pick a shipment from a previous year at random, name it to the team, and ask for the full file. Time it. Then check what came back against the five questions above.
- Did the pack include the correspondence, or only the formal documents?
- Was the classification or valuation reasoning retrievable, or only the result?
- Did anyone have to ask a forwarder or broker for a copy, and how long did that take?
- Did the retrieved copies show dates, versions and reviewer names?
- Did anyone edit, re-save or re-export a file in the process?
That drill tells you more than any policy review. It is also close to what happens in a real examination, so it is worth knowing how a customs audit actually unfolds before one lands. Keep the drill result. A dated internal test is itself a useful record, and it is the kind of evidence an audit trail is supposed to produce.
Screening records deserve their own treatment
Sanctions and denied party screening produces a record every time it runs, including when it returns nothing. A clean screen is evidence. Losing it is the same as never having screened.
The retained screening record should show who was screened, exactly as the name was entered, when the check ran, which lists were covered, what the system returned, who reviewed any possible match, and what they decided. Teams that keep only the final decision cannot later show the reasoning. Good practice on record keeping for denied party screening is a distinct discipline from entry recordkeeping, and assessments treat it separately.
How different credential categories treat this topic
Credentials in this field fall into rough categories, and they handle recordkeeping very differently.
- Government issued licences. These test statutory recordkeeping in depth, because the licence holder is personally accountable. They are jurisdiction specific, slow to obtain and usually restricted by nationality or residency.
- Association certificates. Broad coverage across many compliance topics, often assessed by coursework plus an exam, with continuing education attached. Recordkeeping normally appears as one module among many.
- Employer internal programmes. Closest to the actual job, because they test your own systems and your own document control. They carry no weight outside the employer.
- University short courses. Strong on principles, generally light on procedural mechanics like retention triggers.
- Independent online assessments. These test knowledge only, with no training bundled in. They prove you know the material, not that you have applied it.
None of these substitutes for a working document control system. A credential signals that you understand the rules. Your file cabinet, physical or electronic, is what an auditor will actually examine.
Where the contract side sits, and how it is assessed
If the gap you are closing is the contract layer, that is a distinct body of knowledge. Delivery terms, payment terms, title and documents, governing law, and how each decides which party files and therefore keeps the file.
The Global Trade Contracts Specialist certification is built around exactly that material. It assesses eight domains, including delivery terms and risk transfer, title, documents and carriage, payment and credit risk, and customs, classification and origin. It is a contracts assessment. It is not a customs broker licence, not a government qualification and not a general export compliance credential, and it should not be described as one.
The exam runs to 60 questions in 60 minutes, multiple choice and true or false, drawn at random from a larger bank. The pass mark is 85%. One retake is included, so two attempts in total. Delivery and marking are handled by ClassMarker, an independent online assessment service. You get a score and a topic level breakdown immediately, and the certificate downloads on the spot. There are no prerequisites, though the questions assume you have seen a few contracts. The Incoterms® rules are published by the International Chamber of Commerce, and it should be stated plainly that this is an independent Globalior assessment, not affiliated with, endorsed by or accredited by the International Chamber of Commerce. Details of what the GTCS exam covers are set out on the introduction page.
Key takeaways
- Recordkeeping knowledge means knowing which records exist, who owns the obligation, what starts each clock, what form is permitted, and how retrieval works.
- Retention is usually triggered by an event such as entry, export or the end of a transaction, not by the date the document was created.
- One transaction can carry several retention clocks from different authorities, and an open enquiry suspends destruction entirely.
- Emails, notes, classification reasoning and contract documents are records, even though most published document lists omit them.
- Electronic storage is normally allowed on condition that the system is documented, tested and able to reproduce a legible copy on demand.
- A clean screening result is a record, and it should capture the name screened, the date, the lists covered, the reviewer and the decision.
- A credential can show you know the rules; only a tested retrieval process shows the records are actually there.
Frequently asked questions
Does using a customs broker transfer the recordkeeping obligation?
No. Appointing an agent does not move the legal duty away from the party responsible for the declaration. The broker keeps its own records and may hold copies of yours, but an authority will come to the responsible party for the file. Agree in writing what the agent keeps, for how long, and how fast it returns copies on request.
Are emails really part of a compliance record?
Frequently, yes. Correspondence that discusses price, end use, end user, destination or a variation to the contract can be a record in its own right, because it evidences the facts behind a declaration. The practical problem is capture. Messages living in individual mailboxes are not a controlled file, and they leave when the employee does.
Can I destroy the paper once a document is scanned?
Usually only if the electronic system meets the conditions the relevant authority sets. Those conditions typically cover legibility, completeness, documented procedures, periodic testing and the ability to produce a readable copy on request. Some regimes also expect a separate backup, and some expect notice before you switch storage methods. Check the rule for each authority involved.
What happens if a record is missing during an audit?
The examination widens. A missing document tends to convert a narrow review into a sampling exercise across more entries, and it weakens any argument that the business exercised reasonable care. Penalty exposure generally scales with whether the failure looks careless or deliberate. Documented procedures and a history of internal testing help considerably at that point.
Do exporters have recordkeeping duties, or only importers?
Both. Export rules impose their own retention duties covering licences, filings, classification decisions, screening results, correspondence, contracts and quotations. The trigger dates differ from the import side, and so does the list of records. Treating export records as an afterthought to the entry file is a common and avoidable weakness.
Is a certification needed to work in trade recordkeeping?
No. Nothing requires a credential to maintain trade records, and experienced people do the work without one. A certification is useful when you want an external check on your understanding, or a defined body of knowledge to study against. It does not replace access to the current regulations.
How does recordkeeping connect to contract terms?
The contract decides who clears the goods, who files, who pays which charges and what the price actually is. Those decisions create the filings, and the filings create the retention duties. Reading a term of sale correctly is therefore part of getting the file right, which is why the GTCS certification introduction treats delivery terms and documents as assessed domains.
If you want to talk through which part of the file your team is weakest on, get in touch with Globalior. A short conversation usually identifies the gap faster than a policy rewrite.