BuildNot yet confirmed elsewhere1 publisher3 min readPublished
Some SEC submissions files list acceptance times 4 or 5 hours late under a UTC label
Some SEC EDGAR submissions files list acceptance times exactly 4 or 5 hours late under a UTC label, according to a 450-filing check posted on dev.to. A pre-open results 8-K can then read as filed after the open.
The Engineer · Build desk
Key figures: 450 filings in the dev.to check. Affected files list daylight-time filings 4 hours late. A February filing in one file is listed 5 hours late. A flat 4-hour correction leaves standard-time filings 1 hour off.
| Figure | Value | Note | Claim |
|---|---|---|---|
| Filings checked | 450 filings | 3 | |
| Late, daylight-time filings | 4 hours | 5 | |
| Late, February filing example | 5 hours | 20 | |
| Still off after flat 4-hour fix | 1 hour | 21 |
What happened
- The author took 25 companies' submissions files on 2026-10-11, covering the 12 newest filings in each plus 6 from December to February, across 34 form types and 98 filing agents.
- Every file was either right for all its filings or off by one Eastern offset for all of them, +4 hours in daylight time and +5 in standard time, with no other offset in any form, agent or hour.
- An edgartools issue, dgunning/edgartools#1501, had already reported Apple four hours late on 8 October, and the author added the 450-filing data to it.
Why it matters
- exposure Any pipeline that sorts filings into pre-open and post-close buckets, or assigns an insider purchase to a trading day, from acceptanceDateTime inherits a 4 or 5 hour error whenever it reads an affected file.
- contradiction The API disagrees with itself. One Form 4 carries two acceptance times in two files under the same UTC label, so a consumer that joins company and insider data can see the conflict.
- decision Teams must pick between index-page reads at one request per filing and calibrating each file on two filings from different seasons, with a repeat on every re-download.
The check's reference is the Eastern "Accepted" time on each filing's index page, which matches the filing's SGML header [4]. Against that reference, the shifted value is the true UTC time plus one Eastern offset [5]. JPMorgan's results 8-K was accepted at 06:30 Eastern, which is 10:30 UTC, and its file lists 14:30Z, after the open instead of before it [6]. The gap is four hours, the daylight-time offset [19].
The same filing can carry two times. A Form 4 sits in both the company's file and the insider's file. For Apple's director Form 4s from 26 February, the directors' files are right and Apple's file is five hours late (February is standard time) [7]. In the post's worked example, Apple's file lists 2026-02-27T04:34:19.000Z for a filing whose index page says 2026-02-26 18:34:19 Eastern [8]. The true UTC time is 23:34:19 on 26 February. A pipeline that takes its calendar date from the stamp files the filing under 27 February [20].
Which files are wrong is not settled. According to the post, the deciding factor is the date of a file's most recent filing. Files whose latest filing was accepted on 2 October or earlier were correct, and files whose latest filing came on 5 October or later were shifted, including for their February filings [9]. The author's guess is that files rebuilt since early October are written with the extra offset [22]. "I can't see rebuild times (the API sends no Last-Modified header), so that is a hypothesis, not a finding," the author wrote [23]. The edgartools issue dgunning/edgartools#1501 had logged Apple's times running four hours late on 8 October, and on 7 October it logged some files carrying Eastern times with a UTC label [10].
The values in the post are those of 11 October, and the files change [16]. A copy downloaded before a rebuild can differ from one downloaded after [15]. The post does not say how many of the 25 files were off, and it reports no SEC statement on the cause.
The post's fix has two tiers. Where a filing's time matters, take it from the index page or the SGML header, which costs a request for each filing [11]. Since every filing in a file is off by the same amount, a single request per file will do: check one filing to find that file's error, then apply it to the others [12]. The post's file_shift helper accepts shifts of -1, 0 or 1 and raises ValueError on anything else [13]. The correction function tries 4 hours, then 5, and keeps the one that matches Eastern's offset at the corrected instant [14]. We think that is the right design. A flat four-hour subtraction would leave every standard-time filing one hour off [21].
The post advises calibrating on two filings from different seasons, falling back to index pages if they disagree, and recalibrating on every re-download [15]. canli-mcp's earnings_calendar already read times from index pages. Its event_study did not [17].
What to watch
- Whether the SEC comments on the cause or whether files re-downloaded after the next rebuild still carry the shift.
- Whether the next files to be rebuilt come out shifted, which would support the rebuild hypothesis; a Last-Modified header would settle it.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence58
- Adoption
- Insufficient
- Hype gap0
- Incentives30
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The submissions API at data.sec.gov returns an acceptanceDateTime for each filing, for example 2026-07-14T14:30:38.000Z, where the Z denotes UTC.
- [2]
According to the dev.to post, for a large share of companies the UTC label is not true, and which companies are affected depends on the file read, not on the filing.
- [3]
On 2026-10-11 the author took 25 companies' submissions files: the 12 newest filings in each plus 6 from December to February, for 450 filings across 34 form types, 98 filing agents and three years.
- [4]
For each filing the author compared acceptanceDateTime with the Accepted time printed on the filing's index page, which is in US Eastern time and matches the filing's own SGML header.
- [5]
Every file was either right for all its filings or off by exactly one Eastern offset for all of them: +4 hours for filings accepted in daylight time, +5 hours in standard time. No other offset appeared, whatever the form, filing agent or time of day.
- [6]
JPMorgan's results 8-K, accepted at 06:30 Eastern (10:30 UTC), shows up as 14:30Z in the file: after the open instead of before it.
- [7]
A Form 4 sits in both the company's file and the insider's own file. For Apple's director Form 4s from 26 February, the directors' files are right and Apple's file is five hours late (February is standard time).
- [8]
In the post's worked example, Apple's file lists 2026-02-27T04:34:19.000Z for a filing whose index page says 2026-02-26 18:34:19 Eastern.
- [9]
The split follows each file's newest filing: every file whose newest filing was accepted on or before 2 October was right, and every file whose newest filing was accepted on or after 5 October was off, including its filings from February.
- [10]
An edgartools issue (dgunning/edgartools#1501) reported Apple four hours late on 8 October, and on 7 October some files that gave Eastern time labelled as UTC. The author added the data there.
- [11]
The post advises reading the time from the index page or the SGML header when it matters, at a cost of one request per filing.
- [12]
Because a file is uniform, one request per file is enough: measure the file's error on one filing, then correct the rest.
- [13]
The post's file_shift helper accepts only file errors of -1, 0 or 1 Eastern offsets and raises ValueError for any other shift.
- [14]
The post's corrected function tries 4 hours and then 5 hours, and returns the value whose hour count matches Eastern's UTC offset at the corrected instant.
- [15]
The post advises calibrating on two filings from different seasons, reading every filing from its own index page if they disagree, and recalibrating whenever a file is re-downloaded, because a rebuild can change it.
- [16]
The values shown in the post are those on 11 October, and the files change.
- [17]
canli-mcp's earnings_calendar already read times from the index pages. Its event_study did not.
- [18]
The post says time of day matters for whether results came out before the open or after the close, which trading day an insider purchase belongs to, and an event study's day 0.
- [19]
The JPMorgan filing's 14:30Z stamp is four hours later than its true 10:30 UTC time, equal to the daylight-time Eastern offset.
- [20]
At 18:34:19 Eastern in February (UTC-5) the true UTC time is 23:34:19 on 26 February; the file's 04:34:19 on 27 February is exactly 5 hours later and falls on the next calendar date.
- [21]
A flat 4-hour correction applied to a standard-time filing, whose error is 5 hours, leaves it 1 hour off.
- [22]
The author's guess is that files rebuilt since early October are written with the extra offset.
- [23]
I can't see rebuild times (the API sends no Last-Modified header), so that is a hypothesis, not a finding.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toThe same SEC filing has two acceptance times, depending on which EDGAR file you read
1 article · October 11, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.