ACE Copper Reporting Requirements: Prevent Fatal F794 Entry Rejections

ACE copper reporting requirements have moved from an implementation concern to an immediate entry-processing risk. As of September 14, 2026, missing smelt and cast country data for covered copper articles causes a fatal ACE rejection, making accurate upstream data and automated filing controls essential.

How Fatal F794 Rejections Affect Copper Entries

ACE now fatally rejects covered entry summaries when the required copper declaration is missing. The system returns error code F794, ADDTNL DEC TYPE RQRD FOR ARTICLE, when a qualifying line does not include the applicable 54-record Type 12 declaration.

This represents a significant operational change for customs brokers and importers. ACE began accepting the additional copper declaration on July 30, 2026, creating an implementation period during which filers could update software, templates, and internal procedures. Since September 14, however, the declaration has been enforced through a fatal validation. Affected entry summaries cannot proceed successfully until the missing data is supplied and the filing is retransmitted.

Covered HTSUS Classifications and Required Data

The requirement applies to non-U.S.-origin merchandise entered under the following HTSUS classifications:

• 8544.42.10
• 8544.42.20
• 8544.42.90
• 8544.49.10

For covered lines, the filer must report the primary country of smelt and the country of cast. A secondary country of smelt may also be transmitted, but that element is optional. If the required country is unknown, OTH may be reported rather than an unsupported country code.

The smelt and cast declarations are additional data elements, not replacements for ordinary country-of-origin reporting. The commercial origin, primary country of smelt, and country of cast can reflect different stages of the supply chain. Entry writers therefore should not assume that the invoice origin or export country provides the correct answer for all three fields.

Because the error is fatal, correction after transmission can delay entry summary acceptance, increase exception handling, and consume broker and importer resources. High-volume filers face greater exposure when the same incomplete template or product master is used across multiple entries.

Building a Reliable Smelt and Cast Data Workflow

The most difficult aspect of copper reporting is often not ABI transmission. It is obtaining reliable manufacturing data before the entry is prepared. Smelt and cast information may sit several tiers upstream with a mill, foundry, component producer, or other supplier that has no direct relationship with the U.S. importer.

Importers should identify products classified under the four covered HTSUS provisions and map the parties that can provide the required information. Purchase orders, supplier onboarding forms, commercial invoice instructions, and product qualification procedures can then be updated to request the primary country of smelt and country of cast in a structured format.

Using OTH Without Creating Unsupported Data

When the country is genuinely unknown, the entry may generally report OTH. This option is operationally important because it allows the filer to transmit the required Type 12 declaration without inventing a country code or making an unsupported inference.

Entry writers should be trained to distinguish among three situations:

• A verified country has been supplied and can be reported.
• The country is unknown, making OTH the appropriate value.
• Documentation is incomplete or contradictory and requires escalation before filing.

OTH should not become a default value used merely because supplier outreach has not occurred. Compliance teams will generally want a documented process showing how smelt and cast information is requested, validated, stored, and refreshed. That process can help the importer demonstrate reasonable care and improve data quality over time.

Supplier communications should also define the terminology clearly. A supplier may confuse the place where wire was insulated, cable was assembled, or goods were exported with the country where the copper was smelted or cast. Standardized questionnaires and data definitions reduce that risk. Where multiple manufacturing sources exist for the same SKU, the importer may need shipment-specific information rather than one static product-level value.

Brokers should agree with importer clients on who owns data collection and how unresolved cases will be handled. Without that allocation of responsibility, the filing desk often becomes the final point of discovery for missing information.

Updating ABI Templates and Entry Controls

A compliant supplier process must be matched by accurate ABI configuration. Brokers and self-filing importers should confirm that their customs filing platform can generate the required 54-record with Importer’s Additional Declaration Type Code 12 for every covered non-U.S.-origin line.

Static templates deserve particular scrutiny. A template created before copper reporting took effect may still classify the product correctly while omitting the additional declaration. Copying a prior entry can produce the same problem. Because ACE evaluates the transmitted line data, information stored in an email, document image, or broker note does not satisfy the requirement unless it is mapped into the appropriate electronic record.

Pre-Transmission Validation and Exception Management

Effective controls should identify a covered HTSUS line before the entry reaches ACE. A rules-based validation can check whether the merchandise is non-U.S. origin, determine whether one of the four classifications is present, and verify that Type 12 contains both required country fields.

A mature workflow typically includes:

• HTS-driven prompts for primary smelt and cast countries.
• Controlled country-code values, including OTH when the data is unknown.
• A clear distinction between required and optional declaration fields.
• Blocking rules that prevent transmission when required data is blank.
• Audit logs showing the source and timing of data changes.
• Exception queues for conflicting or incomplete supplier information.

These controls should operate at the line level. One entry may contain both covered and noncovered classifications, and different lines may involve different smelt or cast countries. Applying a single header-level answer across the entry can create inaccurate declarations.

Brokerage managers should also monitor F794 activity after implementation. Rejection reporting can reveal recurring problems by client, supplier, HTSUS classification, branch, or entry writer. Root-cause analysis should separate missing master data from mapping failures, user errors, and incomplete supplier documents.

When a technical transmission problem persists, the filer’s assigned Client Representative is generally the appropriate technical contact. Operational or entry-summary questions may be directed to ESAR at esar@cbp.dhs.gov, while trade remedy questions can be sent to traderemedy@cbp.dhs.gov. Internal escalation procedures should identify who is authorized to contact each resource.

Frequently Asked Questions

When Did the Copper Declaration Become a Fatal ACE Requirement?

ACE began accepting the Type 12 copper declaration on July 30, 2026. Beginning September 14, 2026, covered entry summaries missing the required declaration became subject to fatal rejection. Filers should therefore treat the requirement as an active pre-transmission validation, not a future implementation task.

What Does F794 Mean?

F794 means ADDTNL DEC TYPE RQRD FOR ARTICLE. For the covered copper classifications, it generally indicates that the entry line requires an additional Type 12 declaration and the necessary 54-record was not transmitted. The filer must add or correct the declaration and retransmit the rejected entry summary.

Which Copper Country Details Are Mandatory?

The primary country of smelt and the country of cast are mandatory for covered non-U.S.-origin lines. The secondary country of smelt is optional. These data elements should be reported separately from the product’s ordinary country of origin because the relevant manufacturing stages may occur in different countries.

Can a Filer Use OTH When the Country Is Unknown?

Yes. OTH may be reported when the primary country of smelt or country of cast is unknown. Entry writers should use OTH rather than guessing or selecting a country based only on invoice origin, shipment origin, or final assembly location. Internal records should generally document that the information was unavailable.

Does the Requirement Apply to Every Copper Product?

No. The fatal validation addressed here applies to non-U.S.-origin articles entered under HTSUS 8544.42.10, 8544.42.20, 8544.42.90, and 8544.49.10. Classification should still be determined from the product’s characteristics and applicable tariff rules rather than selected solely to trigger or avoid the declaration.

How Can Brokers Reduce Repeat F794 Rejections?

Brokers can combine HTS-based automation, mandatory data prompts, controlled country-code fields, and pre-transmission blocking rules. They should also analyze rejection trends and work with importers to correct supplier data at its source. Fixing a single rejected entry without updating the underlying template or product record often allows the problem to recur.

How Stable Software Can Help

Turn Copper Reporting Into a Controlled Digital Workflow

Manual reminders are rarely sufficient for a fatal ACE requirement. Stable Software helps importers and customs brokers structure trade data, automate entry workflows, and create validations that identify missing information before transmission.

Rules can flag covered HTSUS lines, require Type 12 copper data, distinguish mandatory fields from the optional secondary smelt country, and route unresolved records for review. Centralized data and audit trails also make it easier to address recurring supplier or template issues across a high-volume operation.

Explore how Stable Software can support scalable customs entry automation and stronger trade compliance controls.