Section 232 Copper Smelt and Cast Reporting: A Practical ACE Filing Guide

Section 232 copper reporting now requires customs brokers to capture supply-chain data that may sit several tiers beyond the importer. For designated non-U.S.-origin copper articles, accurate ACE filing depends on identifying the primary country of smelt, the country of cast, and the correct Importer Additional Declaration before transmitting the entry summary.

Understanding the Copper Smelt and Cast Reporting Requirements

The reporting framework arises from Proclamation 10976, Adjusting Imports of Copper into the United States, issued under Section 232 of the Trade Expansion Act of 1962. Related implementation details appear in 91 FR 18201, while ACE processing uses the data structure established for copper smelt and cast country details.

ACE CERT began accepting the relevant fields on July 16, 2026, allowing software providers and filers to test their transmissions. ACE production began accepting the fields on July 30, 2026. That same date marked the start of the reporting requirement for covered non-U.S.-origin copper articles.

The enforcement posture became more consequential on September 14, 2026. From that date, the F794 error, ADDTNL DEC TYPE RQRD FOR ARTICLE, became fatal when the required Type 12 additional declaration was omitted. A covered entry summary can therefore be rejected before acceptance if the declaration is missing.

Products and Data Elements Within Scope

The requirement applies to non-U.S.-origin copper articles entered under these HTSUS provisions:

• 8544.42.10
• 8544.42.20
• 8544.42.90
• 8544.49.10

For each covered article, the filer must generally report:

• The primary country of smelt
• The country of cast
• The secondary country of smelt, when available

The secondary country of smelt remains optional. When a required smelt or cast country cannot be determined, OTH is permitted as the unknown-country value. Its availability does not eliminate the need to submit the Type 12 declaration or to populate the required fields. Brokers should treat OTH as a controlled exception rather than a default operational shortcut.

Building a Defensible Data-Collection Process

Copper smelt and cast information is not always available on a commercial invoice, packing list, or standard certificate of origin. Country of origin and country of smelt are distinct concepts, and neither should be inferred from the other. The same distinction applies to the country where a finished cable or conductor was manufactured and the country where the copper was most recently cast.

Importers should obtain the required information from manufacturers, mills, refiners, suppliers, or other parties with direct knowledge of the production chain. Brokers typically depend on importer-provided data, but they still need controls that identify incomplete, contradictory, or implausible instructions before entry summary transmission.

Recommended Broker Intake Controls

A practical intake record should capture, at minimum:

1. The HTSUS classification of the imported article.
2. The article’s country of origin.
3. The primary country of smelt.
4. The secondary country of smelt, if applicable and known.
5. The country of cast.
6. Whether OTH was supplied for an unknown required value.
7. The party that provided the smelt and cast information.
8. The supporting record or certification date.

Brokers should avoid automatically carrying smelt and cast values from one shipment to another unless the importer has confirmed that the sourcing and production chain remain unchanged. Supplier, mill, refinery, and production-location changes can make previously stored data obsolete even when the SKU, manufacturer, or country of origin appears unchanged.

A defensible workflow also distinguishes missing data from confirmed unknown data. A blank required field indicates that the filing instruction is incomplete. OTH indicates that the required declaration is being made but the actual country is unknown. That distinction matters because ACE validation treats an absent Type 12 declaration differently from a declaration containing an accepted unknown-country value.

Filing Importer Additional Declaration Type Code 12

ACE CATAIR Entry Summary Create/Update V109 uses Importer Additional Declaration Type Code 12 for Copper Smelt and Cast Country Detail. Brokers and software providers must map the importer’s instructions into the Type 12 structure associated with the covered article rather than placing the information only in free-form notes or internal reference fields.

The declaration must include the primary country of smelt and the country of cast. The secondary country of smelt may be transmitted when known but is not mandatory. If a required country is unknown, the filer may report OTH. Leaving the required element blank is not equivalent to reporting OTH and may produce an ACE validation error.

Practical Transmission Sequence

A controlled filing process generally follows these steps:

1. Confirm tariff scope. Determine whether the entry summary includes a non-U.S.-origin article classified under one of the four covered HTSUS provisions.
2. Obtain production data. Collect the primary smelt, optional secondary smelt, and cast countries from the importer’s approved instructions.
3. Validate country values. Confirm that each reported value is supported by the filing system’s accepted country-code configuration. Use OTH only when the country is genuinely unknown.
4. Create the Type 12 declaration. Associate the copper smelt and cast details with the applicable entry summary article or line structure required by the filer’s software.
5. Run pre-transmission validation. Check for a missing primary smelt country, missing cast country, invalid country values, or an omitted Type 12 declaration.
6. Review the ACE response. A rejected transmission should be corrected and retransmitted rather than bypassed through unrelated data changes.

Where an entry contains both covered and noncovered merchandise, the declaration should be applied according to the covered article data. Brokers should not assume that a declaration entered elsewhere in the summary will satisfy line- or article-level validation. Filing software should preserve the relationship between the HTSUS line, origin, and Type 12 details throughout entry creation and amendment workflows.

Resolving ACE Errors and Preventing Rejections

ACE error messages provide a starting point for diagnosis, but the broker must trace each response back to the declaration structure and importer data. Repeated manual corrections increase filing time and create a risk that unsupported values will be entered merely to obtain acceptance.

The copper reporting error dictionary includes the following messages:

• 869 COP PRIM SMELT CNTRY CD MISSING — the required primary country of smelt has not been supplied.
• 870 COP PRIM SMELT CNTRY CD UNKNOWN CNTRY — the transmitted primary smelt country value is not recognized as submitted.
• 871 COP SEC SMELT CNTRY CD UNKNOWN CNTRY — the optional secondary smelt value was supplied but is not recognized as submitted.
• 872 COP RECENT CAST CNTRY CD MISSING — the required cast-country field has not been supplied.
• 873 COP RECENT SMELT CNTRY CD UNKNOWN CNTRY — the submitted value associated with this validation is not recognized as submitted.

The separate F794 ADDTNL DEC TYPE RQRD FOR ARTICLE response indicates that the required additional declaration is absent. Since September 14, 2026, F794 is fatal for covered non-U.S.-origin copper articles when Type 12 is missing.

A Structured Error-Resolution Workflow

For F794, the filer should first confirm that the merchandise is non-U.S. origin and classified under a covered HTSUS provision. If it is, the broker should verify that Type 12 was created and correctly associated with the relevant article data.

For codes 869 or 872, the broker should check for blank required elements. If the importer has confirmed that the actual country is unknown, OTH may generally be used instead of leaving the field empty.

For codes 870, 871, or 873, the filer should inspect the transmitted country value, its formatting, and the software mapping. The underlying supplier statement may be valid while the electronic value is incorrectly configured. Firms should preserve the original importer instruction, correction history, ACE response, and final accepted transmission as part of the entry record.

Frequently Asked Questions

Which copper products require smelt and cast reporting?

The requirement applies to non-U.S.-origin copper articles classified under HTSUS 8544.42.10, 8544.42.20, 8544.42.90, and 8544.49.10. Brokers should evaluate both classification and origin because the Type 12 requirement is tied to covered articles that are not of U.S. origin.

Is the secondary country of smelt mandatory?

No. The secondary country of smelt is optional. If the importer has reliable secondary smelt information, it may be reported. The primary country of smelt and country of cast are required for covered articles.

Can a broker use OTH when the smelt or cast country is unknown?

Yes. OTH is permitted when a required smelt or cast country is unknown. It should not be confused with a blank value, and it should generally be supported by importer instructions showing that the country could not be determined.

What is the difference between the July 30 and September 14 dates?

ACE production began accepting the smelt and cast fields on July 30, 2026, when the reporting rules became effective. Beginning September 14, 2026, ACE made F794 fatal when a required Type 12 declaration was missing, causing affected entry summaries to reject.

Does the commercial country of origin satisfy the smelt-country requirement?

Not necessarily. Country of origin, country of smelt, and country of cast describe different aspects of production. Brokers should not derive smelt or cast data solely from the origin shown on the invoice or entry documents.

What records should importers and brokers retain?

Records should generally include supplier or manufacturer statements, importer filing instructions, product-level mappings, reported country values, any use of OTH, ACE response messages, and correction histories. Recordkeeping practices should align with the firm’s broader customs compliance program.

How Stable Software Can Help

Automating Copper Filing Controls

Stable Software helps customs brokers and importers turn complex trade requirements into controlled, repeatable filing workflows. Configurable validations can identify covered HTSUS lines, detect missing Type 12 declarations, verify required smelt and cast fields, and prevent incomplete data from reaching ACE.

Centralized product and supplier records also help teams preserve supporting instructions, manage OTH exceptions, and reduce repetitive data entry across shipments. By connecting classification, origin, production data, and entry-summary validation, firms can address copper reporting requirements without relying on disconnected spreadsheets or last-minute manual review. Learn more about trade compliance and customs workflow automation at Stable Software.