Ashby v. Wolfsburger: A Pay.gov Receipt Does Not Prove Timely Filing—Only a Notice of Electronic Filing (NEF) Perfects an ECF Notice of Appeal

1. Introduction

In Ashby v. Wolfsburger (10th Cir. May 11, 2026), the Tenth Circuit dismissed a state prisoner’s appeal from the denial (in part) and dismissal (in part) of his 28 U.S.C. § 2254 habeas petition. The dispositive issue was not the merits of the habeas claims, but whether the court of appeals had jurisdiction in light of an allegedly untimely notice of appeal.

The appellant, James Ashby, argued through retained counsel that his paralegal attempted to file the notice of appeal on the due date through the District of Colorado’s electronic filing system, paid the fee on pay.gov, and received “receipts.” The notice of appeal, however, was not docketed until a month later. The Tenth Circuit issued a jurisdictional show-cause order and ultimately held the appeal untimely because the only document proving a completed ECF filing—the court-generated Notice of Electronic Filing (NEF)— was not generated until the late filing.

2. Summary of the Opinion

The court held that the 30-day deadline to appeal in a § 2254 civil case is “mandatory and jurisdictional.” Although counsel produced payment receipts dated within the 30-day period, the court concluded those receipts reflected fee payment only and did not establish that the notice of appeal had actually been filed in ECF. Under the District of Colorado’s ECF procedures, filing occurs only upon electronic transmission and generation of an NEF.

Because no timely NEF existed and no motion to extend the time to appeal was filed under Fed. R. App. P. 4(a)(5), the Tenth Circuit determined it lacked jurisdiction and dismissed the appeal. It further rejected any equitable carve-out, relying on Supreme Court authority foreclosing equitable exceptions to jurisdictional appeal deadlines.

3. Analysis

A. Precedents Cited

  • Bowles v. Russell, 551 U.S. 205, 209 (2007)
    The cornerstone of the decision. The panel invoked Bowles twice: first to characterize civil appeal deadlines as “mandatory and jurisdictional,” and later to bar “equitable exceptions” to those deadlines. This foreclosed Ashby’s request that the court accept the appeal based on “good cause” or counsel’s belief that filing had occurred.
  • Browder v. Dir., Dep't of Corr. of Ill., 434 U.S. 257, 269 (1978)
    Used to situate § 2254 proceedings as civil matters for appellate-timing purposes, reinforcing that the 30-day civil appeal clock (not a criminal rule) governs.
  • Savage v. Cache Valley Dairy Ass'n, 737 F.2d 887, 889 (10th Cir. 1984)
    Cited for the proposition that the court of appeals cannot itself extend the time for filing a notice of appeal. This matters because Ashby effectively asked the Tenth Circuit to treat the appeal as timely (or excuse the lateness) absent a proper Rule 4(a)(5) extension granted by the district court.
  • United States v. Ceballos-Martinez, 387 F.3d 1140, 1143 (10th Cir. 2004)
    Cited for the appellant’s burden to establish appellate jurisdiction when timeliness is questioned. The panel used it to frame Ashby’s inability to prove timely filing via an NEF as a failure of that burden.
  • Jenkins v. Burtzloff, 69 F.2d 460, 464 (10th Cir. 1995)
    Quoted for the blunt jurisdictional consequence: once the time limit runs, the court is “without jurisdiction.” In context, it reinforces that the defect is structural, not discretionary.

B. Legal Reasoning

  1. The applicable deadline is jurisdictional.
    The court anchored the analysis in 28 U.S.C. § 2107(a) and Fed. R. App. P. 4(a)(1)(A), establishing a 30-day deadline from entry of judgment. Because judgment entered January 22, 2026, the deadline ran to February 23, 2026 (accounting for weekend/holiday counting under Fed. R. App. P. 26(a)(1)(C)).
  2. “Dated” is not “filed”; the docket and NEF control.
    Although the notice of appeal bore a February 23 date, it was not docketed until March 24. The court treated docketing supported by an NEF as the operative evidence of filing, consistent with the District of Colorado’s ECF rule: filing requires ECF submission plus issuance of an NEF.
  3. Pay.gov payment receipts are not filing confirmation.
    The key factual/legal pivot is the panel’s determination that the earlier “receipts” were merely pay.gov fee confirmations, not NEFs. The opinion emphasizes a practical ECF reality: fee payment can occur without completing the final filing step that triggers NEF generation and docket entry.
  4. Technical issues require a timely motion to extend—unless the clerk declares a system failure.
    The court distinguished between (a) a clerk-declared “technical failure” of ECF (which, under the cited local procedure, can push due dates), and (b) user-side difficulties not declared a system outage. Because the clerk did not deem ECF subject to a technical failure on February 23, Ashby had to seek relief via Fed. R. App. P. 4(a)(5) and the local ECF procedure requiring a motion for extension “as soon as practicable.” No such motion was filed, and the time to do so expired.
  5. No equitable safety valve.
    Even if counsel reasonably believed the earlier attempts succeeded, Bowles v. Russell barred the court from crafting an equitable exception to a jurisdictional deadline. The result is harsh but doctrinally straightforward: absent a timely filed notice or a timely granted extension under Rule 4(a)(5), the appellate court lacks power to proceed.

C. Impact

Operational rule for ECF practice: In the District of Colorado (and similarly situated ECF regimes), a pay.gov receipt is not proof of filing. The controlling artifact is the Notice of Electronic Filing (NEF), which both confirms submission and links the filing to a docket entry number and timestamp.

Jurisdictional triage in habeas appeals: § 2254 petitioners already face gatekeeping steps (including a certificate of appealability), but Ashby underscores that none of those issues matter if the notice of appeal is jurisdictionally late. The case warns habeas practitioners that “near-miss” filing errors can be fatal and unreviewable on equitable grounds.

Procedural discipline when ECF misbehaves: The opinion functionally instructs counsel that if an NEF does not arrive immediately, the correct response is not repeated fee payments alone, but prompt verification and—critically—filing a Rule 4(a)(5) motion within the extension window, documenting the issue.

Future litigation posture: Expect litigants facing similar circumstances to focus on producing (i) the NEF, (ii) evidence the clerk declared an ECF outage, or (iii) a timely filed motion for extension. Absent one of those, Ashby signals that the Tenth Circuit will treat the jurisdictional defect as non-curable on appeal.

4. Complex Concepts Simplified

  • “Mandatory and jurisdictional” deadline: A time limit that determines the court’s power to hear the case. If missed, the court must dismiss—even if dismissal seems unfair.
  • Notice of Electronic Filing (NEF): The court system’s automated confirmation that a document has been filed and entered on the docket. It is the electronic equivalent of a clerk’s “file-stamp.”
  • Pay.gov receipt: Proof that a fee was paid, not that the document was accepted and docketed. Payment is often only one step in the electronic filing workflow.
  • Rule 4(a)(5) extension: A mechanism to ask the district court for more time to file a notice of appeal if certain requirements are met and the motion is filed within a specified period. Without such a motion, the appellate court cannot “forgive” lateness.
  • “Technical failure” (ECF outage) vs. user error: If the court declares ECF down, deadlines may shift under local procedures. If the system is up but the filer does not complete the steps, the deadline generally does not move.

5. Conclusion

Ashby v. Wolfsburger establishes (and operationalizes) a concrete procedural rule: timely appellate filing in ECF is proven by an NEF, not by a pay.gov payment receipt. The decision applies longstanding jurisdictional doctrine—principally Bowles v. Russell—to modern electronic filing workflows and emphasizes that, when ECF filing is uncertain, the only viable safety mechanism is a timely Rule 4(a)(5) motion in the district court (absent a clerk-declared system outage). The broader significance lies in its warning to practitioners: ECF process compliance is not merely administrative; it can be jurisdiction-determinative.