🏛️

PGA Identification, Data, and Release Workflow

Identify the regulating agency from product facts, use its own supplemental guide, and distinguish ACE messages from agency admissibility and release.

19 CFR Part 12ACE PGA Message SetAgency Supplemental Guides

Structured from CBP-designated exam references; confirm the editions approved for your exam sitting.

The textbook layer behind Study Map

From learning route to full explanation

This guide identifies the regulating agency and program from complete product facts, intended use, HTS flags, and agency law before building a commodity-specific data set. It distinguishes supported disclaimers, ACE technical messages, agency document requests, holds, admissibility decisions, and release.

Study Map tells you what to learn and in what order; this page explains the rules, decision method, and boundaries. Reading completion is not proof of mastery.

1. Identify the regulating agency before filing PGA data2. Use agency-specific data and resolve status messages

Textbook chapter 1

Identify the regulating agency before filing PGA data

Back to Study Map task →

Answer first

Use product facts, intended use, HTS flags, and agency sources to identify the correct PGA and program before transmitting data. Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient.

Rule breakdown

Controlling rule for Identify the regulating agency before filing PGA data

19 CFR Part 12 ↗

The result must be derived from the cited legal elements rather than from a label, commercial expectation, or memorized shortcut. Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Apply every stated condition to the documented facts and stop if an essential condition cannot be proved.

Evidence route for Identify the regulating agency before filing PGA data

19 CFR Part 12; CBP, How to Use the Automated Commercial Environment; FDA, Harmonized Tariff Schedule and FD Flags; CBP October 28, 2026 CBLE Reference Materials Notice ↗

Use the official source in the order required by the issue and record both the rule and the fact that satisfies it. The assigned lookup is: For one flagged HTS line, document the product identity and intended use, identify the possible agency, and find the exact agency supplemental guide before deciding to file or disclaim. Follow this source route: Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law.. A technically accepted filing or a completed reading is not itself proof that the legal outcome is correct.

Decision path

  1. 1

    Set the gate for Identify the regulating agency before filing PGA data

    Use product facts, intended use, HTS flags, and agency sources to identify the correct PGA and program before transmitting data. Identify the legally significant party, merchandise, event, date, value, status, and document before selecting a rule or performing a calculation.

  2. 2

    Verify 19 CFR Part 12

    Open 19 CFR Part 12, complete the chapter lookup task, and preserve the exact subsection, table, form, or agency guide used. Follow Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law. rather than jumping directly to a remembered result.

  3. 3

    Test the boundary of Identify the regulating agency before filing PGA data

    Apply each controlling element to the documented facts, calculate only after eligibility is established, and compare the result with the worked example conclusion: No. Verify jurisdiction from the actual intended use and use a supported disclaimer if appropriate; never fabricate agency data from the flag alone. Record any unresolved fact instead of converting uncertainty into a pass or mastery claim.

Worked example

Scenario: An FD1-flagged shipment contains safety goggles documented and sold solely for industrial grinding, with no medical claims or medical intended use. Should the filer invent FDA product data merely because of the flag?

  1. 1.Treat FD1 as a may-or-may-not-be-regulated signal rather than conclusive FDA jurisdiction.
  2. 2.Verify the industrial intended use and product facts against FDA's flag guidance.
  3. 3.If the documented facts support non-FDA use, use the supported FDA disclaimer route rather than fabricated PGA data.
  4. 4.Still check whether a different agency or non-PGA rule applies to the same goods.
  5. 5.Boundary check: change one decisive fact identified by “For one flagged HTS line, document the product identity and intended use, identify the possible agency, and find the exact agency supplemental guide before deciding to file or disclaim.” and explain whether the result changes under 19 CFR Part 12; CBP, How to Use the Automated Commercial Environment; FDA, Harmonized Tariff Schedule and FD Flags; CBP October 28, 2026 CBLE Reference Materials Notice.

Conclusion: No. Verify jurisdiction from the actual intended use and use a supported disclaimer if appropriate; never fabricate agency data from the flag alone.

Common traps and corrections

× Treating every HTS agency flag as a conclusive jurisdiction decision.

✓ The shortcut “Treating every HTS agency flag as a conclusive jurisdiction decision.” skips a controlling distinction in Identify the regulating agency before filing PGA data. Return to 19 CFR Part 12, follow Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law., and test the decisive fact against this boundary: Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Copying fields or codes from one PGA's guide into another PGA filing.

✓ The shortcut “Copying fields or codes from one PGA's guide into another PGA filing.” skips a controlling distinction in Identify the regulating agency before filing PGA data. Return to 19 CFR Part 12, follow Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law., and test the decisive fact against this boundary: Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Equating an ACE technical acceptance with final agency admissibility.

✓ The shortcut “Equating an ACE technical acceptance with final agency admissibility.” skips a controlling distinction in Identify the regulating agency before filing PGA data. Return to 19 CFR Part 12, follow Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law., and test the decisive fact against this boundary: Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Marking the topic verified despite the absence of a dedicated supported question pool.

✓ The shortcut “Marking the topic verified despite the absence of a dedicated supported question pool.” skips a controlling distinction in Identify the regulating agency before filing PGA data. Return to 19 CFR Part 12, follow Start with the HTS flag, verify jurisdiction from agency guidance, then follow only that agency's PGA implementation guide and governing law., and test the decisive fact against this boundary: Answer first: ACE is the electronic Single Window, not a universal PGA rulebook. An HTS flag is a routing signal, not always a final jurisdiction decision; the commodity's identity and intended use can determine whether agency data are required or a supported disclaimer is appropriate. After identifying the agency and program, use that agency's own supplemental guide and underlying law—never copy another agency's fields. Technical ACE acceptance does not by itself establish admissibility. For the October 2026 CBLE, use the designated 2025 Annual CFR and listed CBP references; current agency guides are a separate live-operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

Frequently asked questions

Which fact controls first for Identify the regulating agency before filing PGA data?

Begin with the chapter objective and the legally controlling facts, not with the desired commercial result. Use product facts, intended use, HTS flags, and agency sources to identify the correct PGA and program before transmitting data. Then use 19 CFR Part 12 and the remaining cited sources to test every required element before calculating or filing.

Where should I verify Identify the regulating agency before filing PGA data for the exam and live work?

For the October 28, 2026 CBLE, use the designated exam source card and pinpoint 19 CFR Part 12. For live work, separately verify the dated current source cards for this chapter as of the transaction date; a current statute, eCFR, HTSUS, recordation, or agency guide does not silently amend the exam edition.

Official sources and editions

Textbook chapter 2

Use agency-specific data and resolve status messages

Back to Study Map task →

Answer first

Build a commodity-specific PGA data set, distinguish technical rejects from agency review, and resolve holds or requests through the correct channel. Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient.

Rule breakdown

Controlling rule for Use agency-specific data and resolve status messages

CBP ACE Cargo Release Business Rules for Trade, Version 4.0 ↗

The result must be derived from the cited legal elements rather than from a label, commercial expectation, or memorized shortcut. Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Apply every stated condition to the documented facts and stop if an essential condition cannot be proved.

Evidence route for Use agency-specific data and resolve status messages

CBP ACE Cargo Release Business Rules for Trade, Version 4.0; FDA, Transmitting Required Information; FDA ACE/ITDS; CBP October 28, 2026 CBLE Reference Materials Notice ↗

Use the official source in the order required by the issue and record both the rule and the fact that satisfies it. The assigned lookup is: Choose one regulated commodity and list the correct agency guide, exact commercial description, product and intended-use codes, required entities, mandatory affirmations, document channel, and status owner. Follow this source route: Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow.. A technically accepted filing or a completed reading is not itself proof that the legal outcome is correct.

Decision path

  1. 1

    Set the gate for Use agency-specific data and resolve status messages

    Build a commodity-specific PGA data set, distinguish technical rejects from agency review, and resolve holds or requests through the correct channel. Identify the legally significant party, merchandise, event, date, value, status, and document before selecting a rule or performing a calculation.

  2. 2

    Verify CBP ACE Cargo Release Business Rules for Trade, Version 4.0

    Open CBP ACE Cargo Release Business Rules for Trade, Version 4.0, complete the chapter lookup task, and preserve the exact subsection, table, form, or agency guide used. Follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow. rather than jumping directly to a remembered result.

  3. 3

    Test the boundary of Use agency-specific data and resolve status messages

    Apply each controlling element to the documented facts, calculate only after eligibility is established, and compare the result with the worked example conclusion: Rebuild the line from the FDA-specific guide and resolve the actual message owner; neither copied APHIS data nor ACE retransmission acceptance establishes FDA admissibility. Record any unresolved fact instead of converting uncertainty into a pass or mastery claim.

Worked example

Scenario: A filer enters an FDA-regulated human drug as 'pharmaceutical product' and copies APHIS PGA codes. ACE returns a technical or agency error before FDA admissibility is complete.

  1. 1.Replace the broad description with complete commercial terminology supported by the invoice and product facts.
  2. 2.Use the FDA—not APHIS—supplemental guide to determine product code, intended use, entities, and mandatory affirmations.
  3. 3.Identify whether the response is a CBP transmission reject or an FDA status or document request.
  4. 4.Correct through the matching channel and wait for the responsible agency's disposition rather than treating retransmission acceptance as release.
  5. 5.Boundary check: change one decisive fact identified by “Choose one regulated commodity and list the correct agency guide, exact commercial description, product and intended-use codes, required entities, mandatory affirmations, document channel, and status owner.” and explain whether the result changes under CBP ACE Cargo Release Business Rules for Trade, Version 4.0; FDA, Transmitting Required Information; FDA ACE/ITDS; CBP October 28, 2026 CBLE Reference Materials Notice.

Conclusion: Rebuild the line from the FDA-specific guide and resolve the actual message owner; neither copied APHIS data nor ACE retransmission acceptance establishes FDA admissibility.

Common traps and corrections

× Using a tariff description or vague product family instead of complete commercial terminology.

✓ The shortcut “Using a tariff description or vague product family instead of complete commercial terminology.” skips a controlling distinction in Use agency-specific data and resolve status messages. Return to CBP ACE Cargo Release Business Rules for Trade, Version 4.0, follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow., and test the decisive fact against this boundary: Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Treating one agency's codes, affirmations, or status meanings as universal PGA fields.

✓ The shortcut “Treating one agency's codes, affirmations, or status meanings as universal PGA fields.” skips a controlling distinction in Use agency-specific data and resolve status messages. Return to CBP ACE Cargo Release Business Rules for Trade, Version 4.0, follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow., and test the decisive fact against this boundary: Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Equating successful ACE transmission with the responsible agency's release decision.

✓ The shortcut “Equating successful ACE transmission with the responsible agency's release decision.” skips a controlling distinction in Use agency-specific data and resolve status messages. Return to CBP ACE Cargo Release Business Rules for Trade, Version 4.0, follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow., and test the decisive fact against this boundary: Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Assuming every PGA blocks release at the same processing point.

✓ The shortcut “Assuming every PGA blocks release at the same processing point.” skips a controlling distinction in Use agency-specific data and resolve status messages. Return to CBP ACE Cargo Release Business Rules for Trade, Version 4.0, follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow., and test the decisive fact against this boundary: Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

× Creating verified progress from an unsupported general-practice visit.

✓ The shortcut “Creating verified progress from an unsupported general-practice visit.” skips a controlling distinction in Use agency-specific data and resolve status messages. Return to CBP ACE Cargo Release Business Rules for Trade, Version 4.0, follow Start at the CBP PGA implementation-guide index, open the agency's own guide, then use the agency's status or document system rather than another PGA's workflow., and test the decisive fact against this boundary: Answer first: PGA data are agency- and commodity-specific. Use the applicable supplemental guide to determine commercial description, product code, intended use, entities, licenses or affirmations, and supporting documents; broad tariff descriptions and fields copied from another agency are not substitutes. Distinguish an ACE transmission acceptance or reject from the PGA's admissibility review, hold, document request, or refusal. A refusal by the responsible PGA prevents entry into U.S. commerce, but timing and release dependencies vary by agency and must not be generalized. October 2026 exam answers remain tied to designated references; current CBP/FDA data guides are a separately versioned operations layer. CBLE Ace currently has no dedicated verified PGA question pool for this topic; route practice to the general practice page and keep verification status pool-insufficient. Do not infer eligibility, release, or mastery from the shortcut.

Frequently asked questions

Which fact controls first for Use agency-specific data and resolve status messages?

Begin with the chapter objective and the legally controlling facts, not with the desired commercial result. Build a commodity-specific PGA data set, distinguish technical rejects from agency review, and resolve holds or requests through the correct channel. Then use CBP ACE Cargo Release Business Rules for Trade, Version 4.0 and the remaining cited sources to test every required element before calculating or filing.

Where should I verify Use agency-specific data and resolve status messages for the exam and live work?

For the October 28, 2026 CBLE, use the designated exam source card and pinpoint CBP ACE Cargo Release Business Rules for Trade, Version 4.0. For live work, separately verify the dated current source cards for this chapter as of the transaction date; a current statute, eCFR, HTSUS, recordation, or agency guide does not silently amend the exam edition.

Official sources and editions

Key Terms

Partner Government Agency|合作政府机构
HTS Flag|HTS 标记
Supplemental Guide|补充指南
Supported Disclaimer|有依据的免责声明
Admissibility|准入

Related Articles

🛡️

Restricted Merchandise and IPR Border Enforcement

Distinguish prohibitions from conditional restrictions and route counterfeit, gray-market, and piratical-copy facts to the correct border rule.

🛡️

Importer Security Filing (ISF / 10+2)

ISF requirements, filing timelines, data elements, and penalties for non-compliance.

📋

Types of Customs Entry

Overview of formal, informal, and special entry types used in U.S. imports under 19 CFR Part 141-143.

Back to Knowledge BaseUpdated 2026-08-19