MPEP § 2412.05(a) — Use of Sequentially Numbered Sequence Identifiers in the “Sequence Listing XML” (Annotated Rules)

§2412.05(a) Use of Sequentially Numbered Sequence Identifiers in the “Sequence Listing XML”

USPTO MPEP version: BlueIron's Update: 2026-01-17

This page consolidates and annotates all enforceable requirements under MPEP § 2412.05(a), including statutory authority, regulatory rules, examiner guidance, and practice notes. It is provided as guidance, with links to the ground truth sources. This is information only, it is not legal advice.

Use of Sequentially Numbered Sequence Identifiers in the “Sequence Listing XML”

This section addresses Use of Sequentially Numbered Sequence Identifiers in the “Sequence Listing XML”. Primary authority: 37 CFR 1.831(b), 37 CFR 1.832(a), and 37 CFR 1.832. Contains: 5 requirements, 1 guidance statement, 1 permission, and 2 other statements.

Key Rules

Topic

Sequence Listing Content

6 rules
StatutoryInformativeAlways
[mpep-2412-05-a-729d177a66aec510515c6b80]
Requirement for Sequence Listing XML
Note:
This rule requires the use of sequentially numbered sequence identifiers in the 'Sequence Listing XML' for applications filed on or after July 1, 2022.

[Editor Note: This section is applicable to all applications with a filing date, or, for national phase applications, an international filing date, on or after July 1, 2022, having disclosure of one or more nucleotide and/or amino acid sequences as defined in 37 CFR 1.831(b). Formatting representations of XML (eXtensible Markup Language) elements in this section appear different than shown in Standard ST.26, which may be accessed at: www.wipo.int /export/sites/www/standards/en/pdf/03-26-01.pdf.]

37 CFR 1.77 · 37 CFR 1.831(b)Sequence Listing ContentSequence Listing RequirementsSequence Listing Format
StatutoryRequiredAlways
[mpep-2412-05-a-f18caf6b84780846828ddf1e]
Nucleotide and Amino Acid Sequences Must Be Separately Identified
Note:
Each disclosed nucleotide or amino acid sequence that meets §1.831(b) requirements must appear separately in the ‘Sequence Listing XML’ with a unique sequential identifier.

(a) Each disclosed nucleotide or amino acid sequence that meets the requirements of § 1.831(b) must appear separately in the “Sequence Listing XML.” Each sequence set forth in the “Sequence Listing XML” must be assigned a separate sequence identifier. The sequence identifiers must begin with 1 and increase sequentially by integers as defined in paragraph 10 of WIPO Standard ST.26 (incorporated by reference, see § 1.839).

Jump to MPEP Source · 37 CFR 1.831(b)Sequence Listing ContentSequence Listing FormatSequence Listing Requirements
StatutoryRequiredAlways
[mpep-2412-05-a-6ca62dbf9cc477913648ddac]
Each Sequence Must Have Unique Identifier
Note:
Each nucleotide or amino acid sequence in the 'Sequence Listing XML' must be assigned a separate and unique identifier starting from 1.

(a) Each disclosed nucleotide or amino acid sequence that meets the requirements of § 1.831(b) must appear separately in the “Sequence Listing XML.” Each sequence set forth in the “Sequence Listing XML” must be assigned a separate sequence identifier. The sequence identifiers must begin with 1 and increase sequentially by integers as defined in paragraph 10 of WIPO Standard ST.26 (incorporated by reference, see § 1.839).

Jump to MPEP Source · 37 CFR 1.831(b)Sequence Listing ContentSequence Listing FormatSequence Listing Requirements
StatutoryRequiredAlways
[mpep-2412-05-a-0c9e97fda38afe00c4864e5e]
Sequences Must Have Separate Identifiers
Note:
Each nucleotide and amino acid sequence, including identical regions of longer sequences, must be assigned a unique identifier.

Each nucleotide and/or amino acid sequence that meets the definition in 37 CFR 1.831(b) and is enumerated by its residues must be assigned a separate sequence identifier, including a sequence which is identical to a region of a longer sequence. See MPEP § 2412.02 for further description of a “sequence”.

Jump to MPEP Source · 37 CFR 1.831(b)Sequence Listing ContentSequence Listing FormatSequence Listing Requirements
StatutoryRequiredAlways
[mpep-2412-05-a-f22a3668d0a293ea6a8d07a3]
000 Placeholder for Skipped Sequences
Note:
When a sequence is intentionally skipped, '000' must be used in place of the missing sequence identifier in the Sequence Listing XML.

Where no sequence is present for a sequence identifier, i.e. an intentionally skipped sequence, “000” must be used in place of a sequence in a “Sequence Listing XML”. The total number of sequences indicated in the “Sequence Listing XML” must equal the total number of sequence identifiers, whether followed by a sequence or by “000”.

Jump to MPEP Source · 37 CFR 1.832Sequence Listing ContentSequence Listing FormatSequence Listing Requirements
StatutoryInformativeAlways
[mpep-2412-05-a-840b6aa6a547c051a8f12716]
Intentionally Skipped Sequences Must Be Represented as '000'
Note:
WIPO Standard ST.26 requires that intentionally skipped sequences in a ‘Sequence Listing XML’ be represented with the value of INSDSeq_sequence set to '000'.

WIPO Standard ST.26 paragraphs 58 and 59 require that an intentionally skipped sequences in a “Sequence Listing XML” must be represented as follows:

(d) the value of the element INSDSeq _sequence is the string “000”.

Jump to MPEP Source · 37 CFR 1.832Sequence Listing ContentSequence Listing RequirementsSequence Listing Format
Topic

Sequence Listing Format

6 rules
StatutoryPermittedAlways
[mpep-2412-05-a-1892003e525e2964b5c5a9e1]
XML Formatting for Sequence Listings Required
Note:
This rule requires the use of XML formatting for sequence listings in applications filed on or after July 1, 2022.

[Editor Note: This section is applicable to all applications with a filing date, or, for national phase applications, an international filing date, on or after July 1, 2022, having disclosure of one or more nucleotide and/or amino acid sequences as defined in 37 CFR 1.831(b). Formatting representations of XML (eXtensible Markup Language) elements in this section appear different than shown in Standard ST.26, which may be accessed at: www.wipo.int /export/sites/www/standards/en/pdf/03-26-01.pdf.]

37 CFR 1.77 · 37 CFR 1.831(b)Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
StatutoryRequiredAlways
[mpep-2412-05-a-2b89a0830598a4b7db070bde]
Sequence Identifiers Must Start at 1 and Increment Integers
Note:
Nucleotide or amino acid sequence identifiers in the 'Sequence Listing XML' must begin with 1 and increase sequentially by integers as defined in WIPO Standard ST.26.

(a) Each disclosed nucleotide or amino acid sequence that meets the requirements of § 1.831(b) must appear separately in the “Sequence Listing XML.” Each sequence set forth in the “Sequence Listing XML” must be assigned a separate sequence identifier. The sequence identifiers must begin with 1 and increase sequentially by integers as defined in paragraph 10 of WIPO Standard ST.26 (incorporated by reference, see § 1.839).

Jump to MPEP Source · 37 CFR 1.831(b)Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
StatutoryRequiredAlways
[mpep-2412-05-a-29bca11953cc3bb0f2b5f86f]
Sequence Identifiers Must Be Sequential
Note:
The sequence identifiers in the ‘Sequence Listing XML’ must start with 1 and increase by integers.

In accordance with 37 CFR 1.832(a), the sequence identifiers in the “Sequence Listing XML” must begin with 1 and increase sequentially by integers. The requirement for sequence identifiers, at a minimum, requires that each sequence be assigned a different number for purposes of identification. However, where practical and for ease of reference, sequences should be presented in the “Sequence Listing XML” in numerical order and in the order in which they are discussed in the application.

Jump to MPEP Source · 37 CFR 1.832(a)Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
StatutoryRecommendedAlways
[mpep-2412-05-a-9cadf1e5ff12fbaaa1a0d6f6]
Sequence Identifiers Must Be Unique and Numerical
Note:
Each sequence must have a unique number for identification, but should be listed in numerical order when practical.

In accordance with 37 CFR 1.832(a), the sequence identifiers in the “Sequence Listing XML” must begin with 1 and increase sequentially by integers. The requirement for sequence identifiers, at a minimum, requires that each sequence be assigned a different number for purposes of identification. However, where practical and for ease of reference, sequences should be presented in the “Sequence Listing XML” in numerical order and in the order in which they are discussed in the application.

Jump to MPEP Source · 37 CFR 1.832(a)Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
StatutoryRequiredAlways
[mpep-2412-05-a-45f5a9efc36a6abed6b868c5]
Sequence Listing XML Must Match Sequence Identifiers
Note:
The total number of sequences in the 'Sequence Listing XML' must match the total number of sequence identifiers, including those marked as '000' for skipped sequences.

Where no sequence is present for a sequence identifier, i.e. an intentionally skipped sequence, “000” must be used in place of a sequence in a “Sequence Listing XML”. The total number of sequences indicated in the “Sequence Listing XML” must equal the total number of sequence identifiers, whether followed by a sequence or by “000”.

Jump to MPEP Source · 37 CFR 1.832Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
StatutoryRequiredAlways
[mpep-2412-05-a-bafc33d2a20cbd5b68f2e873]
Intentionally Skipped Sequences Must Be Represented as Specified in XML
Note:
Sequences intentionally skipped must have their identifiers, features, and sequences represented with specific elements omitted and a placeholder value provided.
WIPO Standard ST.26 paragraphs 58 and 59 require that an intentionally skipped sequences in a “Sequence Listing XML” must be represented as follows:
  • (a) the value of the element SequenceData and its attribute sequenceIDNumber, is the sequence identifier of the skipped sequence;
  • (b) no value is provided for the elements INSDSeq _length, INSDSeq _moltype, and INSDSeq _division;
  • (c) the element INSDSeq _feature-table is not included; and
  • (d) the value of the element INSDSeq _sequence is the string “000”.
Jump to MPEP Source · 37 CFR 1.832Sequence Listing FormatSequence Listing RequirementsSequence Listing Content

Citations

Primary topicCitation
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.831(b)
Sequence Listing Format37 CFR § 1.832(a)
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.839
Sequence Listing ContentMPEP § 2412.02

Source Text from USPTO’s MPEP

This is an exact copy of the MPEP from the USPTO. It is here for your reference to see the section in context.

BlueIron Last Updated: 2026-01-17