There is a very specific kind of silence that follows a last-minute goal.
If you watch enough football, you know it well. Your team has controlled the game from kickoff. Possession is solid. Passing is clean. The scoreline reflects it. And then, in injury time, something shifts. Decisions get rushed. Structure breaks. One careless touch, one lapse in judgment, and the game you dominated slips away.
I have seen the same pattern play out in XBRL filings more times than I can count.
Ninety percent of the process is disciplined, controlled, and accurate. Then the final stretch begins. Deadlines close in. Reviews overlap. And suddenly, teams start making decisions they would never make earlier in the cycle.
Mistakes are rarely dramatic in isolation. But together, they are enough to cost you the filing.
Here are the five patterns I see most often and what they look like if you think about them on the pitch.
1. Showing Up in Last Season’s Kit: Incorrect Taxonomy Version
Using an outdated taxonomy is like walking onto the field in last season’s jersey. The rules have changed, and the system will not accept it.
The league updates its rules every season. Elements get added, deprecated, and restructured. Regulator does not care that your kit used to be correct. Confirm the required taxonomy version at the start of the filing cycle. Showing up in the wrong strip is embarrassing and entirely avoidable.
2. The Scoreboard Malfunction: Calculation Errors from Late Revisions
The fans see 2-1. The official record says 1-1. Why? Because someone logged a goal in the wrong column, and now the scoreboard and the match report flatly contradict each other. That is a calculation inconsistency in XBRL form. In the final weeks, financial statements get revised constantly. A rounding tweak here, a reclassification there. When the statements update but the XBRL tags do not follow, total assets stop summing to their components. The official record and the live data disagree, and regulator will notice even if your QA team does not. Run validation after every material revision, not just once before the final whistle.
3. Inventing a New Position Because You Could Not Be Bothered: Overusing Custom Elements
I have a certain affection for tactical creativity in football. But there is a difference between intelligent innovation and making up a position because you could not be bothered to study the existing playbook.
It’s like deciding that the team needs a completely new tactical position that has never existed in the history of the sport. It is creative. It is also unnecessary, confusing to everyone watching, and gets flagged by the officials. Custom XBRL elements (or extensions) are the same thing. They exist for disclosures that genuinely have no standard equivalent. Under deadline pressure, they get created because finding the right standard tag takes effort. The regulator notices excessive extensions and sends comment letters. That is the officiating equivalent of a yellow card that costs you the next match. Search for the standard taxonomy first. Every time.
4. Offsides: Wrong Context and Period References
The offside rule exists to put players in the right position at the right moment. XBRL context references do the same thing. Every fact needs the correct value, the correct period, and the correct dimension. Tag a current-year revenue figure with a prior-year context, and you have scored a goal that the linesman will disallow. Tag a balance sheet item with a duration period instead of an instant period, and the replay will be embarrassing. Build your context map before tagging begins and check every comparative and restatement figure against it. No goal counts if you were offside.
5. Not Checking VAR: Skipping the iXBRL Review
VAR exists because what looks fine from the stands can look completely different on close review. iXBRL is the same story. The rendered document looks perfect. The table is clean. The numbers are right. But the structured data layer embedded underneath can be carrying the wrong sign, referencing the wrong element, or missing a required attribute, and none of that shows up when you are just reading the page. Sign errors are the classic VAR moment: a loss reported as positive looks fine on screen and fails every downstream data check. Using an iXBRL viewer is not optional, and skipping it is how you celebrate a goal that gets overturned.
I have learned this the hard way over the years. Strong teams do not lose in injury time because of capability. They lose because discipline breaks under pressure.
The same is true for XBRL.
If your process only becomes rigorous in the final weeks, you are already exposed. The teams that file cleanly are the ones that treat XBRL as a continuous process, not a last-mile activity.
Because in both football and reporting, the last few minutes do not create mistakes. They expose them.
