WorkflowCustoms Brokerage

PGA Filing

PGA filing that fans each entry line out to the agencies that want its data, fills every field from the supplier’s own documents, and breaks a branch when those documents disagree.

Follow one container’s agency data from flag to ACE ↓
Watch with transcript →
The problem

Two species on two documents, and the plate test predates the ink

One entry line can need data for several agencies: the Lacey Act declaration for wood, FDA data for anything that touches food, a children’s product certificate for a child’s plate set. Brokers key it by hand from spec sheets, harvest records and lab reports that often disagree.

ACE checks a species name against a list, not against the documents, so a wrong species that is still a valid name goes through. A certificate can be complete and rest on a test of last season’s ink. The cost is a reject and rework, a hold with terminal storage by the day, or a declaration that is accepted and simply wrong.

Built forPGA specialistsEntry writersLicensed customs brokers

The Problem Today

Agency data is keyed from supplier papers that disagree, and the system only checks that each value is on a list.

47+
partner agencies take import data through ACE published

Keyed from supplier papers

  • Spec sheets
  • Harvest log
  • Lab reports
  • Certs
  • A valid name, the wrong speciesACE accepts it; the harvest record says otherwise
  • Storage billed by the dayOne unready line can keep a container waiting

The Solution

  1. Each line fans out by agencyBranches for wood, food contact and children’s products, each field cited
  2. Fields checked across papersA disagreement breaks the branch; the agents never pick a value
  3. The importer decides its certificateThe product safety lead holds a line; a second person confirms
  4. The broker opens each branchThen transmits the lines that are ready; the held line waits in bond

Built-in controls

  • Only a licensed broker transmits agency data
  • Supplier remarks reach staff and change no field
  • The importer certifies its own products

What You Get

The broker sends agency data that matches the supplier’s own documents, and only the line in doubt waits.

  • Agents’ own errors caughtA seller named as maker corrected to the factory
  • Hold the line or the boxBoth waiting paths priced, assumptions marked
  • Rulings kept as rulesApplied once a licensed broker approves
Features

PGA filing features, from a flagged entry line to the agency’s reply

PGA specialists and licensed brokers build FDA, USDA and CPSC entry data from the supplier’s papers with them. The case shown is one container of serving boards, mugs and children’s plate sets.

demoSample entries throughout: container, importer, supplier, brokerage staff and amounts.

  1. 01Agency fan

    Each entry line fanned out to the agencies that want its data

    • Branches drawn from flags and product records. Wood, food-contact and children’s product lines each get the agency branches they need, with the tariff text the flag reader used.
    • Each field cited to its document. Spec sheet, harvest record, certificate or lab report sits beside each value, so the specialist checks the page instead of re-keying it.
    • A plain-language steer grows the plan. Asking the agents to check an earlier booking for the same ink puts one more step in the run, recorded under the specialist’s name.
  2. 02Lacey branch

    Lacey Act declaration species checked against the harvest record

    • Species compared across each document. When the spec sheet and the harvest record name different species, the branch breaks instead of one being picked.
    • Valid names that are still wrong caught. ACE accepts any listed species, so the field checker holds the declared species to the harvest record for the lot.
    • Wood quantity worked from the goods. Cubic meters come from the board size and count, so the declaration reports the wood in the shipment.
  3. 03CPSC branch

    Children’s product certificate tested against the supplier’s ink change

    • Test date set against material changes. A lab report from before a supplier’s change notice no longer tests the product in the box, and the branch says so.
    • Test, notice and production on one line. Report, change notice, production dates and the expected new test sit together for the importer to decide.
    • Certificate fields cited to their source. Certifier, rules, maker, lab and test date each point to the certificate, the lab scope or the production record.
  4. 04Agency reviewer

    Agency reviewer plays APHIS, FDA and CPSC before anything is transmitted

    • What each agency would reject or hold. Species, maker, leach tests, import alerts and certificate scope are raised before ACE or an agency sees them.
    • Agent mistakes counted too. The reviewer questions the agents’ own drafts, so a seller filed as maker is corrected to the factory before FDA reads it.
    • Points routed to whoever decides. Species goes to the PGA specialist, the certificate to the importer’s safety lead, earlier declarations to the importer and its counsel.
  5. 05Supplier answers

    Supplier answers in fixed fields, each mapped to the branch it changes

    • Fields chosen from the reviewer’s points. Each question says which branch it changes, so the supplier answers only what the filing needs.
    • Files attached to the fields. The signed harvest record, the corrected spec sheet and the lab’s acknowledgment arrive as files the specialist can open.
    • Supplier remarks shown unedited. A supplier’s reassurance changes no field; the specialist and the importer read it exactly as written.
  6. 06Correction

    Species corrected by the PGA specialist with the harvest record open

    • Correction tied to its evidence. The dialog names the documents behind the change, and the reason is in the specialist’s own words.
    • A correction proposes a standing rule. Asking the supplier whenever spec sheet and harvest record disagree becomes a proposed rule, applied only once a licensed broker approves.
    • The broker still opens the branch. The specialist signs the correction, and nothing transmits until the licensed broker has opened it.
  7. 07Certificate decision

    Importer’s certificate decision on the children’s line, held at once

    • The importer certifies, the broker files. The product safety lead decides whether to certify or hold, with the reviewer’s point and the lead’s last similar case alongside.
    • A hold acts the moment it is signed. Holding the line takes effect at once, while certifying waits for the importer’s second person, who also confirms the hold.
    • Hold the line or the whole box. The lead chooses whether the rest of the container moves in bond or everything waits.
  8. 08Hold what-if

    Hold the line or hold the box, priced in storage days and delivery dates

    • Two ways to wait, day by day. Storage, release and delivery dates under each path, with the storage rate and move cost editable, so the importer sees what waiting costs.
    • What CBP must agree to, marked assumed. The in-bond move and split carry an assumed label, so the importer weighs the saving knowing CBP may refuse it.
  9. 09Transmit

    Licensed broker opens each agency branch before transmitting

    • Each opening logged. Every branch shows when the broker opened it, and only opening them all enables the signature.
    • Only ready lines go. Lines with solid branches transmit with their Lacey and FDA data; the held line waits in the bonded warehouse.
    • The in-bond path spelled out. How the held line waits is listed step by step, with CBP free to refuse, so the broker transmits knowing the fallback.

Who builds, checks and sends the agency data on an entry

The specialist owns the fields, the broker owns the transmission, the writer keys the entry that starts it.

PGA specialists

Own agency data for dozens of entries a day and correct fields from evidence

  • Each field cited to a supplier document
  • Disagreements stopped as broken branches
  • Supplier questions sent as fields and files
Licensed customs brokers

Open every branch, transmit the ready lines and approve rules and settings

  • Five branches to open, each opening logged
  • Held lines kept out of the transmission
  • Agency replies read back and routed
Entry writers

Key entries and start the agents on new agency lines

  • Agency branches drawn from the flags
  • Status per entry: broken, waiting or ready
  • No agency field to edit by mistake

A valid species that was wrong, a test of old ink, and the seller as maker

What would have been keyed from the papers as they came on this sample container.

A species ACE would have accepted

Spec sheet rev B, written for an older item, says Acacia mangium. The harvest record for log lot PT-0417 says Acacia auriculiformis, and the supplier confirmed it.

A certificate resting on the old ink

The lab report tested ink series A. The supplier’s change notice moved production to ink series K, and this lot was made after the change.

The invoice seller named as maker

The draft named the supplier as maker of the mugs; the product record names the ceramics factory, and the document reader corrected it.

Earlier declarations from the old spec sheet

Earlier entries declared the species from rev B. They go to the importer and its counsel, with no view from the agents.

demoSample data, from the working solution.

Seven agents build the agency data, and none clears a branch or transmits

Each works from the documents it opened and stops at a named person.

Flag reader

Reads tariff flags and the client’s product records and draws a branch for each agency.

  • Drops no agency without a source saying it does not apply
Document reader

Fills each agency’s fields from the documents, citing each, and runs the steps a person adds.

  • Fills nothing from memory or a similar product
Field checker

Compares each field across every document that states it and breaks the branch on a disagreement.

  • Never picks the more likely value
Agency reviewer

Plays APHIS, FDA and CPSC and lists what each would reject or hold.

  • Clears no branch
  • Gives no view on whether a law was broken
Supplier documents

Drafts fixed-field requests to the supplier and reads replies field by field.

  • Sends no request without a person’s approval
  • Keeps supplier free text out of the fields
Hold planner

Plays forward each way to wait: storage, delivery and what CBP must agree to.

  • Chooses no path
  • Promises nothing on behalf of CBP or an agency
Agency reply reader

Reads ACE and agency messages after transmission, explains them and routes them.

  • Answers no agency
  • Never re-transmits
More screens

The entries queue, the importer’s second person, the send and the rules

From the morning’s queue to what came back from ACE.

Entries with agency data74 open entries with lines FDA, APHIS, CPSC or EPA want data for, each with its status: broken branch, waiting outside or ready for a broker.
Second person at the importerThe quality manager opens the lab report and the change notice, then confirms the hold or sends it back.
The broker’s transmitWith every branch opened, the broker writes a reason and transmits lines 001 and 002; line 003 stays in bond.
Rules learnedTwo rules wait for a licensed broker, one from this correction; three are in force and cited when used.

demoSample data, from the working solution.

Choosing a species, certifying a product and transmitting stay with people

The agents fill and challenge fields; the calls that change what goes to an agency are signed by name.

Picking between documentsWhen two documents disagree, the branch breaks and a person decides.
Certifying a children’s productThe importer’s product safety lead decides, and a second person at the importer confirms before it is filed.
Transmitting unopened branchesThe licensed broker opens each branch before the signature is enabled.
Acting on supplier remarksFree text changes no field; a person reads it and the importer sees the same words.
Judging a supplierThe agents call no supplier dishonest and offer no opinion on whether a law was broken.

Questions brokers ask about PGA filing

What is PGA filing?

PGA filing is sending partner government agency data with a customs entry: FDA data for food-contact goods, the Lacey Act declaration to USDA APHIS for wood, CPSC certificate data for children’s products. Here agents build the PGA filing from the supplier’s documents and check each field, and the licensed broker transmits after opening every branch.

What is a PGA message set?

The data elements an agency asks for with the entry, sent through ACE. Each agency has its own fields and its own rejects; here they are filled from the documents, each one cited.

Does it prepare the Lacey Act declaration?

Yes, for lines that carry wood: genus, species, country of harvest and quantity, each from the harvest record and the spec sheet. If the documents disagree on species, the branch breaks until the PGA specialist decides.

Who certifies a children’s product?

The importer. Its product safety lead decides, a second person at the importer confirms after opening the lab report and the change notice, and the broker files only what they decided.

What happens when only one line is not ready?

The importer can hold that line while the rest of the container moves in bond, if CBP approves the move and split, or hold the whole entry. The hold what-if prices both before anyone decides.

Does it answer an agency hold or reject?

No. The reply reader reads ACE and agency messages after transmission, explains them and routes them to the specialist or the broker. People answer the agency.

Bring an entry
an agency rejected.

Send one entry’s spec sheets, certificates and lab reports, and we will rebuild each agency branch field by field.