A separate regulation controls administration. 19 C.F.R. 159.42 says that duties under Section 338 shall be imposed only pursuant to specific instructions from the Commissioner of Customs. The official CBP CSMS sources reviewed through 3.47 p.m. Eastern Time on August 14 did not yield a Section 338-specific instruction naming the five headings or their treatment in ACE. The August 14 consolidated HTS release also contains none of them.
That result is narrower than a finding that no instruction exists. Section 159.42 does not prescribe a public format. A nonpublic instruction from the Commissioner could satisfy the regulation. Other CBP direction may evidence implementation, but it should not be treated as satisfying Section 159.42 unless the record connects it to Commissioner authority. The HTS omission likewise does not show that ACE will reject a heading.
Importers still need to reserve for the scheduled exposure. As a recommended internal control, filing sign-off should separate administrative support from technical deployment. The administration file should identify the specific Commissioner instruction, or written CBP direction that connects the treatment to Commissioner authority. The technical file should identify the ACE environment, ABI message set, installed software release, test transaction, and response.
The proclamation and filing instruction do different work
Section 338(d) and Proclamation 11046, Proclamation 11047, and Proclamation 11048 establish the duty, scope, and scheduled entry trigger. Their Annex II amendments to the HTS state the governing exceptions. Those records support classification work, provisional exposure accrual, contract review, and inventory decisions.
Section 159.42 adds a distinct administrative condition. Its wording requires specific Commissioner instructions when the duties are imposed. A public CSMS message is one possible way for CBP to convey operating treatment, but the regulation does not require that channel or public notice by a particular date.
An HTS publication or ACE deployment, standing alone, establishes only the published or deployed treatment. It does not reveal the provenance or content of the Commissioner instruction unless another record makes that connection. A vendor release note is narrower still. It can show that a code table was installed, not that the reporting treatment rests on the required official instruction.
The earlier Traverse analysis Canada Section 338 Tariffs Put HTS Scope Ahead of USMCA identified the legal heading for a listed product and left implementation as a later handoff. A USMCA Win for Canada Would Not Refund Section 338 Duties treated the Commissioner's instruction as one record that could affect importer rights. A third article examined the separate 19 U.S.C. 1338 comment-participation record. The remaining operating question is narrower. Which record supports a named broker template for a named entry profile?
The filing test begins after the scope map
The proclamations settle the scheduled legal map. Proclamation 11046 inserted U.S. Note 51 and headings 9903.03.12, 9903.03.15, and 9903.03.16. Proclamation 11047 added 9903.03.13, and Proclamation 11048 added 9903.03.14. Traverse's Policy Signal for Proclamation 11046 links the originating record into the continuing policy timeline.
Carry the full 10-digit classification, Canadian-origin analysis, controlling proclamation, U.S. Note 51 coordination route, Chapter 98 treatment, and foreign-trade-zone status into each filing profile. Shipment from Canada does not establish origin. Scope turns on U.S. Note 51(b)(1), (2), or (3), as inserted and amended by Annex II. Annex I descriptions are informational and do not delimit scope.
The duty file should include every independently applicable additional duty, antidumping or countervailing duty cash deposit, tax, fee, exaction, and charge. U.S. Note 51 preserves those amounts. Do not add the Section 338 charge when 9903.03.15 or 9903.03.16 applies, and use the Chapter 98 value rules exactly as the note directs.
USMCA treatment does not remove Section 338 by itself. A separately satisfied U.S. Note 51(c) or (d) coordination category can do so. The note also disapplies the additional duty for a proper Chapter 98 claim when CBP agrees that the provision is appropriate, except for in-scope subchapter XXIII goods and the specified 9802 provisions. A product subject to the Section 338 duty and admitted to an FTZ on or after the effective moment must be admitted in privileged foreign status under 19 C.F.R. 146.41 unless it is eligible for admission in domestic status under 19 C.F.R. 146.43.
What the August 14 search found
The search covered named official surfaces and exact terms through 3.47 p.m. Eastern Time on August 14. It covered the CSMS homepage and archive page, the August 13 archive PDF through July 31, indexed GovDelivery messages, and CBP site-search results. Queries included Section 338, U.S. Note 51, all five headings, the proclamation numbers, and the Federal Register citations.
The archive's first listed entry is message 69403181 dated July 31. Exact-string inspection found no Section 338 message and no occurrence of 9903.03.12 through 9903.03.16. Searches of indexed August messages produced no dedicated filing instruction in the reviewed results.
Revision 16 was released on August 14. Its 12,631,914-byte JSON file contains zero exact matches for each of the five headings. This establishes an omission in that dated consolidated file. The Federal Register annexes remain the controlling public source for the new headings. The result says nothing about a later or separate USITC record, and no ACE transmission was made for this analysis.
CSMS 18-000657 supplies the general order for reporting multiple HTS numbers. It places Chapter 98 first, Chapter 99 additional-duty provisions next, specified trade remedies after them, replacement-duty and quota provisions later, and the Chapter 1 through 97 classification last. It also addresses general value and duty placement.
That 2018 message predates these Section 338 headings and does not expressly assign all five within every possible stack. CBP's 2025 Canada message named the relevant headings, reporting order, value placement, contacts, and error route. Its January 2026 semiconductor message provided action-specific entry, stacking, and FTZ treatment. Those messages do not supply the Canada Section 338 instruction. They illustrate the details that one can settle.
Match each control to its supporting record
This filing-readiness map is current through the August 14 freeze. Each row supports a separate control. A later record changes only the field within its scope.
| Record | Status in the reviewed record | Decision supported | Limit of the record |
|---|
| Section 338(d), Proclamation 11046, Proclamation 11047, and Proclamation 11048 | Issued, with duty treatment scheduled for August 19 | Provisional exposure accrual, product mapping, rate, exceptions, and entry trigger | Whether the instruction contemplated by 19 C.F.R. 159.42 has been issued or how the treatment is deployed in ACE |
| Requirement for a specific Commissioner instruction, or implementing CBP direction shown to have been issued pursuant to that instruction | No Section 338-specific public instruction located in the enumerated sources | Only the administration points identified in the record, including reporting order, value placement, coordination treatment, contacts, or error route |
Under this recommended control, the administration field is ready only when the file contains a specific Commissioner instruction, or written CBP direction that identifies its Commissioner-authority basis, and states the reporting treatment and scope for the named entry profile. If the direction does not connect itself to the instruction required by Section 159.42, keep the field open unless counsel makes and documents an express legal determination that the record is sufficient. An unidentified internal instruction is not a filer placeholder.
Technical deployment is ready only when a named environment and installed software release return the expected result for the intended profile without an unresolved response. "Broker ready" is not evidence. "ACE tested" lacks the environment, timestamp, transmitted values and headings, returned messages, and tester. A plain .12 result does not establish the treatment of .15, Chapter 98, or .16.
Build the legal profile before testing ACE
Begin with the classification and origin records carried from the scope map. Each test card should name the proclamation and action heading, entry type, ACE message set, controlling entry or warehouse-withdrawal event, entered value, quantity and unit, every Chapter 98 and Chapter 99 provision, expected heading set, duty base and amount, expected response, environment, software version, and pass-or-fail owner. The card should not prescribe reporting order, value placement, or omission of a heading unless authoritative CBP direction supports that treatment.
When an antidumping or countervailing duty order may apply, identify the order and case number, scope basis, exporter and producer combination, cash-deposit rate and source date, and applicable entry type. An AD/CVD cash deposit is not another Chapter 99 provision.
Test one legally distinct profile at a time. The baseline is an ordinary HTS line plus its applicable .12, .13, or .14 heading, without another additional-duty Chapter 99 program. Add a second Chapter 99 provision only when the legal file shows that it can independently apply to the same Canadian-origin line. Identify its authority, origin predicate, and expected interaction before constructing the combination.
For a U.S. Note 51(c) coordination profile, identify the otherwise applicable .12, .13, or .14 heading, the basis for .15, and every independently applicable Section 232 provision. The article is legally provided for in .15 rather than subject to the additional duty under .12, .13, or .14. The filing order and value treatment stay open until supported by the applicable direction. Use the same discipline for a qualifying .16 civil-aircraft profile.
Chapter 98 treatment under U.S. Note 51 needs separate cards when material. A non-excepted provision requires a proper claim and a record of how CBP agreement will be established. Test an in-scope entry under subchapter XXIII separately. For 9802.00.40, .50, .60, and .80, use the provision-specific Section 338 value basis. Do not infer whether an exempt profile omits the Section 338 heading, reports it without duty, or uses another treatment until an instruction answers that point.
For a consumption entry, determine the time of entry under 19 C.F.R. 141.68 for the procedure used. Preserve an estimated entry date separately until the time of entry is established. Record arrival, the submitted cargo-release path, any SE transmission, any AE transmission, cargo-release disposition, estimated-duty payment, and liquidation in separate fields. Mark a transaction that does not apply to the selected path as not applicable, not missing. For warehouse merchandise, retain the warehouse entry and withdrawal for consumption separately. An FTZ profile should also keep admission timing, zone status, and the later consumption entry in different fields.
A profile remains open without a named legal treatment, ACE environment and message set, expected result, observed result, and decision owner. Code recognition by itself is not a pass.
Record ACE results with transaction precision
CBP describes Certification and Production as separate ACE environments. Certification is used to test capabilities before live trade filing. Production processes live submissions. A clean Certification response establishes only that the tested stack was accepted in that environment at that time. Availability of a future-effective code in Certification must be verified, not assumed.
Use "Certification environment" only for CERT testing and "certify for ACE Cargo Release" only for the AE Cargo Release Certification Request Indicator. Record whether Production used separate SE Cargo Release and AE Entry Summary transactions or an AE Entry Summary certified for ACE Cargo Release. Validate the fields and responses for the selected message-set path. Use an AE Entry Summary certified for ACE Cargo Release only when the Entry Summary CATAIR permits that request for the entry type. The certification request is not permitted for a 3x warehouse withdrawal or entry type 51.
Do not record a result merely as "ACE accepted." Name the environment, ABI message set, entry type, transaction or control number, software and version, timestamp, response code, warnings, and disposition. For a separate SE filing, retain the SX acceptance or rejection response and SO Cargo Release status output separately. For an AE Entry Summary certified for ACE Cargo Release, retain the AX Entry Summary response and SO Cargo Release status output separately. Treat only the release disposition in the SO output as cargo-release evidence. No acceptance or release event establishes that the legal reporting treatment was correct.
If Certification does not recognize a legally supported profile, keep technical deployment in not-ready status. A broker deployment plan or vendor release record remains pending evidence. If CBP supplies a different authorized treatment, update the legal template, install or configure the treatment, and test the applicable message set in a named environment before changing the technical status.
The first live filing is a controlled observation, not a test transaction. Transmit only a legally supported entry. Preassign rejection and escalation owners, retain every ABI response, and compare each returned result with the approved template for that message set.
Maintain separate evidence for transaction acceptance, cargo-release disposition, Entry Summary status, estimated-duty deposit amount and date, payment method or statement identifier, and liquidation date and assessed rate. No earlier event closes a later field.
The contingency file should name affected entries, the stop or hold point, the CBP or client-representative contact, any expressly authorized alternative reporting treatment, a response deadline, the correction route, and the decision owner. It cannot omit a supported duty heading, substitute an unrelated heading, alter origin or value, or shift the controlling event merely to obtain acceptance. Use only a treatment supported by the legal file or written CBP direction, and record who authorized it.
Which field a later record can change
| New record | Field it can change | Field it cannot change by itself |
|---|
| Presidential suspension, revocation, supplement, or amendment | Legal scope, rate, timing, or the affected proclamation | Filer deployment unless the change is implemented there |
| Specific Commissioner instruction or implementing CBP direction | Administration and entry reporting identified in the record | The underlying tariff unless the controlling legal instrument changes it |
| USITC release after Revision 16 | Consolidated HTS text and reference data | ACE response or the broker's installed software release |
| ACE or vendor deployment evidence | Technical readiness for a named environment, version, message set, and profile | Legal correctness or negotiated relief |
A political agreement does not supply an entry instruction. The President can change the proclamations under Section 338(c). Any instrument should identify the affected action, headings, scope, and effective entry event. A conforming HTS or CBP update could then make the revised treatment usable without becoming an extra legal condition unless the controlling instrument says so.
CBP could close the public filing gap through a message while every 50 percent duty remains scheduled. For one importer's decision, a written nonpublic CBP communication may be relevant if it identifies the sender, authority, date, exact transaction, environment, and scope. Broker or vendor readiness evidence alone does not establish the Commissioner instruction or close the public-record gap.
Caveats
This analysis freezes the reviewed public record at 3.47 p.m. Eastern Time on August 14, 2026. A new presidential action, Commissioner instruction, CBP cargo message, USITC release after Revision 16, or ACE deployment can overtake it.
The absence finding covers the enumerated official sources and exact terms. It does not prove that no internal Commissioner instruction, nonpublic client-representative message, broker notice, or vendor deployment exists. Section 159.42's public format and timing remain unspecified.
Revision 16 is one dated consolidated file. The three Federal Register records are the controlling public sources used here. No live or Certification entry was transmitted for this article, so it makes no claim that ACE accepts or rejects the headings.
The duties remain scheduled for August 19 on the reviewed record. Keep the exposure file intact, identify the administrative authority for the reporting treatment, and test the actual entry profile in a named environment.