MPEP § 2415.03 — Improper Submissions of “Sequence Listing” under 1.821(c) When a “Sequence Listing XML” was Required (Annotated Rules)

§2415.03 Improper Submissions of “Sequence Listing” under 1.821(c) When a “Sequence Listing XML” was Required

USPTO MPEP version: BlueIron's Update: 2025-12-31

This page consolidates and annotates all enforceable requirements under MPEP § 2415.03, 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.

Improper Submissions of “Sequence Listing” under 1.821(c) When a “Sequence Listing XML” was Required

This section addresses Improper Submissions of “Sequence Listing” under 1.821(c) When a “Sequence Listing XML” was Required. Primary authority: 37 CFR 1.57(b), 37 CFR 1.182, and 37 CFR 1.821(c)(1). Contains: 5 requirements and 3 other statements.

Key Rules

Topic

Sequence Listing Format

3 rules
StatutoryRequiredAlways
[mpep-2415-03-7b075f10e259f363c7351ee3]
TXT Sequence Listing Allowed for XML Requirement
Note:
In applications filed on or after July 1, 2022, a plain text 'Sequence Listing' may be used to support the submission of compliant 'Sequence Listing XML' if an earlier application contains a proper 'Sequence Listing' in .txt format.

While implementing regulations and procedures for WIPO Standard ST.26, the USPTO recognized that an applicant might erroneously provide a “Sequence Listing” in ASCII plain text file format even though a “Sequence Listing XML” is required. Therefore, in the rare circumstance in which a “Sequence Listing”.txt file is submitted in an application filed on or after July 1, 2022, the “Sequence Listing” present in the Office file wrapper of the application at issue may be used to provide support for the submission of a compliant “Sequence Listing XML.” The applicant’s reliance on the “Sequence Listing” to support the compliant “Sequence Listing XML” would be by way of the safeguard under 37 CFR 1.57(b), if an earlier filed application contains a proper “Sequence Listing” in.txt file format, or via a grantable petition under 37 CFR 1.182, only if the application does not have a proper benefit or priority claim present on the filing date to an earlier filed application.

Jump to MPEP Source · 37 CFR 1.57(b)Sequence Listing FormatSequence Listing RequirementsAccess to Patent Application Files (MPEP 101-106)
StatutoryInformativeAlways
[mpep-2415-03-97380a226aeba76792ee543d]
Support for Sequence Listing XML via Earlier File
Note:
An applicant can use an earlier filed application’s proper .txt Sequence Listing to support a compliant Sequence Listing XML, if no proper benefit or priority claim is present on the filing date.

While implementing regulations and procedures for WIPO Standard ST.26, the USPTO recognized that an applicant might erroneously provide a “Sequence Listing” in ASCII plain text file format even though a “Sequence Listing XML” is required. Therefore, in the rare circumstance in which a “Sequence Listing”.txt file is submitted in an application filed on or after July 1, 2022, the “Sequence Listing” present in the Office file wrapper of the application at issue may be used to provide support for the submission of a compliant “Sequence Listing XML.” The applicant’s reliance on the “Sequence Listing” to support the compliant “Sequence Listing XML” would be by way of the safeguard under 37 CFR 1.57(b), if an earlier filed application contains a proper “Sequence Listing” in.txt file format, or via a grantable petition under 37 CFR 1.182, only if the application does not have a proper benefit or priority claim present on the filing date to an earlier filed application.

Jump to MPEP Source · 37 CFR 1.57(b)Sequence Listing FormatSequence Listing RequirementsPetition Not Otherwise Provided For (37 CFR 1.182)
StatutoryInformativeAlways
[mpep-2415-03-3c58d66f39e6f08e5bfcb807]
ASCII Sequence Listing Must Be Retained
Note:
When a 'Sequence Listing' is submitted as an ASCII plain text file, it must be retained in the official record for the application.

A petition under 37 CFR 1.182 would require: (1) a compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying the nucleotide and/or amino acid sequence information of the “Sequence Listing” erroneously submitted as an ASCII plain text file that is relied on for submission of a compliant “Sequence Listing XML,” (i.e., identifying the nucleotide and/or amino acid sequence information found in the “Sequence Listing XML” within the erroneously submitted ASCII “Sequence Listing”) see 37 CFR 1.835(a)(3); and (3) a statement that the “Sequence Listing XML” does not introduce new matter into the application, as required by 37 CFR 1.835(a)(4). In such circumstances, for record retention purposes, any “Sequence Listing” submitted as an ASCII plain text file will be retained in the official record for the application.

Jump to MPEP Source · 37 CFR 1.182Sequence Listing FormatSequence Listing RequirementsSequence Listing Content
Topic

Components Required for Filing Date

3 rules
StatutoryRequiredAlways
[mpep-2415-03-215fe428f70239cd3db36365]
Requirement for Inadvertently Omitted Sequence Listing XML
Note:
An applicant must submit a compliant Sequence Listing XML and supporting documents if a portion of the specification was inadvertently omitted.

An applicant may rely on the provisions in 37 CFR 1.57(b), as described in the MPEP § 217, to support the required “Sequence Listing XML” as an “inadvertently omitted portion of the specification or drawing(s).” To rely on 37 CFR 1.57(b), a compliant “Sequence Listing” must have been submitted in an earlier filed application to which the present application makes a proper benefit or priority claim, and the “Sequence Listing” was present on the filing date of the earlier filed application (i.e., the earlier filed application contains a compliant “Sequence Listing” submitted under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) on physical sheets of paper). An applicant would be required to submit: (1) A compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying where the inadvertently omitted portion of the specification can be found (e.g., identifying the nucleotide and/or amino acid sequence information in the compliant “Sequence Listing” from the earlier filed application that forms the basis for the “Sequence Listing XML”), see 37 CFR 1.835(a)(3); (3) a statement identifying the nucleotide and/or amino acid sequences of the “Sequence Listing,” submitted (in the earlier filed application) under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) as physical sheets of paper, which forms the basis for the compliant “Sequence Listing XML”; (4) a statement that the “Sequence Listing XML” does not introduce new matter into the application, see 37 CFR 1.835(a)(4); and (5) a statement that all or a portion of the specification or drawings, as found in the “Sequence Listing XML,” were inadvertently omitted from the application. The availability of relief under 37 CFR 1.57(b) precludes the filing of a grantable petition under 37 CFR 1.182 seeking the same relief.

Jump to MPEP Source · 37 CFR 1.57(b)Components Required for Filing DateSequence Listing FormatPatent Application Content
StatutoryRequiredAlways
[mpep-2415-03-080ed87bbbbef30cd9a97306]
Sequence Listing Must Be Present in Earlier Filed Application
Note:
A compliant Sequence Listing must be present on the filing date of an earlier filed application to which the current application claims benefit or priority.

An applicant may rely on the provisions in 37 CFR 1.57(b), as described in the MPEP § 217, to support the required “Sequence Listing XML” as an “inadvertently omitted portion of the specification or drawing(s).” To rely on 37 CFR 1.57(b), a compliant “Sequence Listing” must have been submitted in an earlier filed application to which the present application makes a proper benefit or priority claim, and the “Sequence Listing” was present on the filing date of the earlier filed application (i.e., the earlier filed application contains a compliant “Sequence Listing” submitted under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) on physical sheets of paper). An applicant would be required to submit: (1) A compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying where the inadvertently omitted portion of the specification can be found (e.g., identifying the nucleotide and/or amino acid sequence information in the compliant “Sequence Listing” from the earlier filed application that forms the basis for the “Sequence Listing XML”), see 37 CFR 1.835(a)(3); (3) a statement identifying the nucleotide and/or amino acid sequences of the “Sequence Listing,” submitted (in the earlier filed application) under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) as physical sheets of paper, which forms the basis for the compliant “Sequence Listing XML”; (4) a statement that the “Sequence Listing XML” does not introduce new matter into the application, see 37 CFR 1.835(a)(4); and (5) a statement that all or a portion of the specification or drawings, as found in the “Sequence Listing XML,” were inadvertently omitted from the application. The availability of relief under 37 CFR 1.57(b) precludes the filing of a grantable petition under 37 CFR 1.182 seeking the same relief.

Jump to MPEP Source · 37 CFR 1.57(b)Components Required for Filing DateFiling Date RequirementsSequence Listing Format
StatutoryRequiredAlways
[mpep-2415-03-b32f126ac941d0280ed36663]
Requirement for Sequence Listing XML and Supporting Documents
Note:
An applicant must submit a compliant 'Sequence Listing XML', identify the omitted portion, provide the original sequence information, confirm no new matter is introduced, and state that the omission was inadvertent.

An applicant may rely on the provisions in 37 CFR 1.57(b), as described in the MPEP § 217, to support the required “Sequence Listing XML” as an “inadvertently omitted portion of the specification or drawing(s).” To rely on 37 CFR 1.57(b), a compliant “Sequence Listing” must have been submitted in an earlier filed application to which the present application makes a proper benefit or priority claim, and the “Sequence Listing” was present on the filing date of the earlier filed application (i.e., the earlier filed application contains a compliant “Sequence Listing” submitted under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) on physical sheets of paper). An applicant would be required to submit: (1) A compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying where the inadvertently omitted portion of the specification can be found (e.g., identifying the nucleotide and/or amino acid sequence information in the compliant “Sequence Listing” from the earlier filed application that forms the basis for the “Sequence Listing XML”), see 37 CFR 1.835(a)(3); (3) a statement identifying the nucleotide and/or amino acid sequences of the “Sequence Listing,” submitted (in the earlier filed application) under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) as physical sheets of paper, which forms the basis for the compliant “Sequence Listing XML”; (4) a statement that the “Sequence Listing XML” does not introduce new matter into the application, see 37 CFR 1.835(a)(4); and (5) a statement that all or a portion of the specification or drawings, as found in the “Sequence Listing XML,” were inadvertently omitted from the application. The availability of relief under 37 CFR 1.57(b) precludes the filing of a grantable petition under 37 CFR 1.182 seeking the same relief.

Jump to MPEP Source · 37 CFR 1.57(b)Components Required for Filing DateSequence Listing ContentSequence Listing Format
Topic

Sequence Listing Content

2 rules
StatutoryInformativeAlways
[mpep-2415-03-dd415231d8db7ef8b9b7a384]
Disclosure of Nucleotide and Amino Acid Sequences Required
Note:
All applications filed on or after July 1, 2022, must disclose one or more nucleotide and/or amino acid sequences as defined in 37 CFR 1.831(b).

[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).]

37 CFR 1.77 · 37 CFR 1.831(b)Sequence Listing ContentSequence Listing RequirementsSequence Listing Format
StatutoryRequiredAlways
[mpep-2415-03-67d5ec0ac688df16187c19cf]
Petition for Sequence Listing XML Submission
Note:
A petition requires a compliant 'Sequence Listing XML', identifying erroneous ASCII sequence information, and confirming no new matter is introduced.

A petition under 37 CFR 1.182 would require: (1) a compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying the nucleotide and/or amino acid sequence information of the “Sequence Listing” erroneously submitted as an ASCII plain text file that is relied on for submission of a compliant “Sequence Listing XML,” (i.e., identifying the nucleotide and/or amino acid sequence information found in the “Sequence Listing XML” within the erroneously submitted ASCII “Sequence Listing”) see 37 CFR 1.835(a)(3); and (3) a statement that the “Sequence Listing XML” does not introduce new matter into the application, as required by 37 CFR 1.835(a)(4). In such circumstances, for record retention purposes, any “Sequence Listing” submitted as an ASCII plain text file will be retained in the official record for the application.

Jump to MPEP Source · 37 CFR 1.182Sequence Listing ContentSequence Listing FormatSequence Listing Requirements
Topic

Petition for Filing Date

1 rules
StatutoryInformativeAlways
[mpep-2415-03-a5c9c28946d37ac7b0619a45]
Same Relief Cannot Be Sought Twice
Note:
An applicant cannot seek the same relief under both 37 CFR 1.57(b) and a grantable petition under 37 CFR 1.182.

An applicant may rely on the provisions in 37 CFR 1.57(b), as described in the MPEP § 217, to support the required “Sequence Listing XML” as an “inadvertently omitted portion of the specification or drawing(s).” To rely on 37 CFR 1.57(b), a compliant “Sequence Listing” must have been submitted in an earlier filed application to which the present application makes a proper benefit or priority claim, and the “Sequence Listing” was present on the filing date of the earlier filed application (i.e., the earlier filed application contains a compliant “Sequence Listing” submitted under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) on physical sheets of paper). An applicant would be required to submit: (1) A compliant “Sequence Listing XML” under 37 CFR 1.835(a)(1); (2) a statement identifying where the inadvertently omitted portion of the specification can be found (e.g., identifying the nucleotide and/or amino acid sequence information in the compliant “Sequence Listing” from the earlier filed application that forms the basis for the “Sequence Listing XML”), see 37 CFR 1.835(a)(3); (3) a statement identifying the nucleotide and/or amino acid sequences of the “Sequence Listing,” submitted (in the earlier filed application) under 37 CFR 1.821(c)(1) as an ASCII plain text file (with a proper incorporation by reference statement in the specification), 37 CFR 1.821(c)(2) as a PDF file, or 37 CFR 1.821(c)(3) as physical sheets of paper, which forms the basis for the compliant “Sequence Listing XML”; (4) a statement that the “Sequence Listing XML” does not introduce new matter into the application, see 37 CFR 1.835(a)(4); and (5) a statement that all or a portion of the specification or drawings, as found in the “Sequence Listing XML,” were inadvertently omitted from the application. The availability of relief under 37 CFR 1.57(b) precludes the filing of a grantable petition under 37 CFR 1.182 seeking the same relief.

Jump to MPEP Source · 37 CFR 1.57(b)Petition for Filing DateComponents Required for Filing DateFiling Date Requirements

Citations

Primary topicCitation
Components Required for Filing Date
Petition for Filing Date
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.182
Components Required for Filing Date
Petition for Filing Date
Sequence Listing Format
37 CFR § 1.57(b)
Components Required for Filing Date
Petition for Filing Date
37 CFR § 1.821(c)(1)
Components Required for Filing Date
Petition for Filing Date
37 CFR § 1.821(c)(2)
Components Required for Filing Date
Petition for Filing Date
37 CFR § 1.821(c)(3)
Sequence Listing Content37 CFR § 1.831(b)
Components Required for Filing Date
Petition for Filing Date
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.835(a)(1)
Components Required for Filing Date
Petition for Filing Date
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.835(a)(3)
Components Required for Filing Date
Petition for Filing Date
Sequence Listing Content
Sequence Listing Format
37 CFR § 1.835(a)(4)
Components Required for Filing Date
Petition for Filing Date
MPEP § 217

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: 2025-12-31