Based on the verbatim source provided, here are the data elements of eBond Record Identifier 10 (Output) that appear in the source. Note that the source excerpt does not include all elements (it begins with "Bond Activity Code" at position 5-7, so elements at positions 1-4 are not shown in the excerpt provided): From [S5] ACE ABI CATAIR Customs eBond Status Notification BS V01.16 June 2024 DRAFT — Record Identifier 10 (Output) pp.28-29: 1. Bond Activity Code - Length/Class: 3AN - Position: 5-7 - Desig.: C 2. Bond Amount - Length/Class: 10(S)N - Position: 8-17 - Desig.: C 3. Execution Date - Length/Class: 6D - Position: 18-23 - Desig.: C 4. Surety Reference Number - Length/Class: 9X - Position: 24-32 - Desig.: O 5. Effective Date - Length/Class: 6D - Position: 33-38 - Desig.: C Caveat: The verbatim source excerpt provided begins with "Bond Activity Code" at position 5-7. Data elements occupying positions 1-4 (and any elements beyond position 38) are not found in the sources provided.

Per [S1] ACE ABI CATAIR Customs eBond Create-Update CB-CX V1.9, Record Identifier 10 (Input/Output), pp.23-25, the valid Bond Designation Type Codes are quoted verbatim below: - B = Add a new basic bond. - A = An additional bond; the bond that secures an AD/CVD, PGA or any other aspect not covered by the basic bond requirement. Applies to a Single Transaction Bond only. - V = Void the Single Transaction Bond on file. - C = Adjust the bond amount of the Single Transaction Bond on file. - U = Substitute for the bond presented at time of entry. Applies to a Single Transaction Bond only. - E = Supersede the bond presented at time of entry. Applies to a Single Transaction Bond only. - T = Terminate the Continuous Bond on file. - R = Bond Rider to take the following actions: - Add Reconciliation Flag - Remove Reconciliation Flag - US Virgin Islands - Add a Bond User - Delete a Bond User. Source: [S1] ACE ABI CATAIR Customs eBond Create-Update CB-CX V1.9 04102020, Record Identifier 10 (Input/Output), pp.23-25.

Not found in sources. The verbatim sources provided include ISF error codes ranging from 105 through 211 (in [S4] ACE CATAIR Appendix S ISF Error Codes - October 2012), but error code 901 is not present in the excerpts available to me. To get an accurate definition and recommended filer response for error code 901, please consult the complete Appendix S: Importer Security Filing Error Codes document directly.

Batch vs. Block in ABI Batch and Block Control

Based on the verbatim sources available, here is what can be determined:

Structural Relationship

Per [S3, p.9-11]: "Submit all ABI transactions and queries 'wrapped' in a block control envelope." Further, "In an ACE batch, the Application Identifier code must be specified at BOTH the A-Record level and the B-Record level. The Application Identifier Code in each block enclosed in the batch must be the same and must match the A-Record code." This indicates that a Batch is the outer envelope which contains one or more Blocks (inner envelopes), and each Block contains the actual ABI transactions or queries.

Control Identifiers

From [S2, p.8-13], which references the Batch and Block Control chapter: > "See the *ABI Batch & Block Control* chapter of the ACE CATAIR for a complete description of the Block Control envelope (B-, Y-Records and Batch Control envelope A-, Z-Records)." Therefore:

Envelope	Start Record	End Record
Batch Control	A-Record	Z-Record
Block Control	B-Record	Y-Record

Additional Detail on Usage

Per [S1, p.1-9], the Table of Contents references: - "Batch Control Header (input B-Record)" — wait, correction: [S1] lists "Block Control Header (input B-Record) + Notes; Block Control Trailer (input Y-Record)" and references the "Batch Control Header (Output A-Record)." Per [S3, p.9-11], regarding batch contents: "Only a single type of ABI transaction or query data can be included in a batch."

Note on Limitations

The verbatim sources provided do not include a single explicit side-by-side definition contrasting "Batch" vs. "Block" as concepts. The distinction above is assembled from the record layout references (A/Z for Batch envelope; B/Y for Block envelope) cited in [S2] and the usage notes in [S1] and [S3]. For the full narrative definitions and usage notes (sections "a) Using Batch Control" and "b) Using Block Control" listed in the [S1] Table of Contents), the complete text of those sections was not found in the provided sources.

TTB PGA Message Set — Applicable Commodities and ABI Transaction

Commodity Categories

Per [S1] 2022 - TTB Trade Filing Instructions 8.0, p.1-8, TTB regulates the following commodities: > "TTB regulates and collects excise taxes on distilled spirits, wines, beer, tobacco products, and cigarette papers and tubes under Chapters 51 and 52 of the Internal Revenue Code of 1986, as amended (IRC). Under the IRC, TTB also has regulatory authority over processed tobacco, which is not subject to tax." > "TTB regulates distilled spirits, wine, and malt beverages under the Federal Alcohol Administration Act (FAA Act)." Additionally, regarding permit-required importations [S1], p.1-8: > "All persons engaged in the business of importing distilled spirits, wine, malt beverages, tobacco products, and processed tobacco into the United States must have a permit issued by TTB, unless one of the enumerated exceptions applies. Accordingly, a TTB permit number must be filed at time of entry for all such importations into the United States."

ABI Transaction Attachment

Per [S1], p.1-8: > "REMINDERS: The PGA Message Set does not stand alone, and must be submitted with an ACE cargo release filing, including ACE Entry Summary certified for cargo release."

Important Note on HTS Flags

Per [S1], p.1-8: > "The HTS flags that prompt the filing of TTB Message Sets are provided by CBP as a courtesy to the import community. Importers are responsible for providing data required at the importation of all TTB-regulated commodities, whether or not an HTS flag is present."

Submission Deadline Not found in sources. The provided sources describe a "Periodic Monthly Statement Due Date" field (format MMDDYY) on Record Identifiers Q3 and Q5 [S5, S6], but they do not specify the actual submission deadline (e.g., a specific business day of the month) for the Periodic Monthly Statement. Record Identifiers Included Per [S2], the Periodic Monthly Statement output contains 10 record identifiers, with the following designations: Mandatory (M) records: - Q1 – "Daily Statements Listed on the PMS & Duty/Tax" (Loop Repeat: 1) - Q2 – "Daily Statement Total" (Loop Repeat: 1) - QA – "Daily Statement Fees" (Loop Repeat: 5) - Q3 – "PMS Payment Due – Statement Totals & Duty/Tax" (Mandatory within the Preliminary or Final PMS Grouping) - Q4 – "PMS Payment Due – Total" - QE – "PMS Payment Due – Fees" (Loop Repeat: 5) - Q5 – "PMS Payment – Statement Totals & Duty/Tax" (Mandatory within the Final Periodic Monthly Statement Grouping) - Q6 – "PMS Payment – Total" - QJ – "PMS Payment – Fees" (Loop Repeat: 5) Conditional (C) record: - Q7 – "Entry Summaries Deleted" (Loop Repeat: 9,999) Per [S2]: *"Record Identifiers Q1, Q2, and QA are mandatory detail payment records. Record Identifiers Q3, Q4, and QE are mandatory total payment due records for preliminary periodic monthly statements... Record Identifiers Q5, Q6, and QJ are mandatory paid amount totals for final periodic monthly statements and Record Identifier Q7 is a conditional record that provides entry summary numbers for entry summaries deleted from a periodic daily statement after the RM, ACH Payment-Entry Summary Presentation transaction has been processed."* Additionally, per [S2]: *"The application identifier on Record Identifiers A, B, and Y is MS."* Source: [S2] ACE-CATAIR-Periodic-Monthly-Statement, pp. 1-6.

Entry Number Check Digit Validation

The check digit algorithm is defined in the CATAIR specification as follows. The formula operates on a 10-position Numeric Base Value (3-position Entry Filer Code + 7-position transaction/sequence number), with alphabetic characters converted to numeric equivalents first.

Alphabetic-to-Numeric Conversion Table

Per [S1] p.1-3 and [S3] p.53-57:

A = 1   J = 1   S = 2
B = 2   K = 2   T = 3
C = 3   L = 3   U = 4
D = 4   M = 4   V = 5
E = 5   N = 5   W = 6
F = 6   O = 6   X = 7
G = 7   P = 7   Y = 8
H = 8   Q = 8   Z = 9
I = 9   R = 9

Algorithm (Six Steps)

From [S3] p.53-57 (Duty Deferral) and [S4] p.73-76 (Reconciliation), the formal steps are: Step ONE – "Derive a 'Numeric Base Value' by converting EACH and EVERY alphabetic value in the alphabetic portion(s) of the 'number' to a numeric value" using the table above. "The result is a 10-position number." [S3] Step TWO – "Multiply positions 2, 4, 6, 8, and 10 of the 'Numeric Base Value' each by +2. For each, if the product (P) is greater than +9, add +1 to adjust the product (AP)." [S3] Step THREE – "Disregarding the 'tens' positions for each product (or adjusted product), compute the 'Adjusted Even Sum Value' by adding the five products (or adjusted products) together." [S3] Step FOUR – "Compute the 'Odd Sum Value' by adding positions 1, 3, 5, 7, and 9 of the 'Numeric Base' together." [S3] Step FIVE – "Compute a 'Check Digit Base Value' by adding the 'Adjusted Even Sum Value' and the 'Odd Sum Value' together." [S3] Step SIX – "Determine the 'Computed Check Digit' by subtracting the 'ones' position of the 'Check Digit Base Value' from +10." [S3]

+10
- Check Digit Base Value (ones position ONLY) NN
--
N = Computed Check Digit

Per [S2] p.4: *"If the result of the subtraction is zero, the check digit is zero."*

Worked Example (from [S1]/[S5]/[S2])

For entry filer code B76 (transforms to 276) and transaction number 0324527, giving Numeric Base 2760324527: 1. Multiply odd positions (from the units/right) by 2 — "Start with the units position (right-most digit or, in this case, 7) and multiply every other position by 2… If the result of multiplication is greater than 9, add 1 to the units digit and disregard the tens digit." [S5]

7  5  2  0  7
   x2 x2    x2 x2
   14 10 4  0  14
   +1 +1    +0 +1
   5  1  4  0  5

2. "Add the results together." → 5 + 1 + 4 + 0 + 5 = 15 [S5] 3. "Total all the even positions in the entry number, starting with the position next to the units position." → 2 + 4 + 3 + 6 + 2 = 17 [S5] 4. "Add the two sums (15 and 17) together for a total of 32." → 15 + 17 = 32 [S2] 5. "Subtract the units digit (in this case 2) from 10. The result is the check digit." → 10 − 2 = 8 [S2] So entry number 2760324527 has check digit 8.

Modulus

The spec does not use the word "modulus" explicitly; it specifies subtracting the 'ones' position ONLY of the Check Digit Base Value from +10, with the clarification that "If the result of the subtraction is zero, the check digit is zero" [S2]. This is effectively a mod-10 operation on the final subtraction. Note also from [S2] p.4: filers nearing exhaustion of their ten million entry numbers may be authorized to use "either the check digit as calculated in step 5, or that check digit +1 (mod 10, so that 9+1=0)," extendable up to "+9 (mod 10)."

Validation

To validate an existing entry number, recompute the check digit using the 10-position Numeric Base Value (Filer Code + 7-position Sequence Number) via Steps ONE–SIX and compare it to the check digit on the entry number. Per [S3]/[S4], the Filer Identifier "may be both alphabetic and numeric" while the Sequence Number "is required to be ALL numeric."

Based on the verbatim sources provided, I can only see a portion of Appendix S. The visible error codes in [S1] range from 105 to 211, with the following distinct codes explicitly listed: 105, 106, 107, 108, 109, 110, 111, 114, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 153, 154, 157, 201, 203, 204, 205, 209, 210, 211 ([S1] pp.1-4) That is 43 distinct error codes visible in the provided excerpt. However, the source is truncated (ending mid-description at code 211 "Missing Carnet Country of..."), so the full Appendix S likely contains additional codes beyond what is shown. Exact total for the complete Appendix S: Not found in sources (excerpt is truncated).