Who this is for, and the moment
Two reports on your desk, both signed off, that should say the same number and might not. Checking means opening both, finding the matching line and doing the subtraction yourself. Most of the time they agree and the ten minutes are gone. The one time they don’t is the one that matters.
The question, as typed
“Do the December FY26 route results agree with the MTD P&L on year-to-date total operating expense?”
The answer
GroundedNEAR-MISS — they do not quite agree. The December FY26 Route Results show YTD SSR total operating expense of $1,158.1M 169170, while the MTD P&L shows YTD total expense of $1,159.5M 171172: a $1.4M gap.
| Line item | Route Results by Service Line - 1225 | MTD P&L - 1225 | Difference |
|---|---|---|---|
| YTD Dec FY26 total operating expense | $1,158.1M | $1,159.5M | $1.4M Σ |
Materiality: $1.4M on the larger reported value of $1,159.5M = 0.12%.
Likely cause shown in the notes: there was a known December/January timing issue around the Meridian winter-cycle true-up: the central P&L accrual route was considered fine, but late items could slip the route-level extract, especially on “Non-Corridor Special Trains & Adjustments” 24. Since the MTD P&L is the anchor when reports disagree, I would treat the P&L as the control total and follow up on the route extract.
Material mismatch. The P&L shows YTD total expense of $1,159.5M. The Route Results by Service Line report totals $1,158.1M. The difference is $1.4M, and it sits in Non-Corridor Special Trains & Adjustments, which the route report understates. Chips: MTD P&L Dec FY26, SSR Consolidated A24:J24 · Route Results Dec FY26, By Route A64:J68. Verdict vocabulary: TIES · NEAR MISS · MATERIAL MISMATCH · CANNOT RECONCILE.
The citation clicked
Both workbooks open on the rows that carry the values, the P&L first, then the route report. You can read $1,159.5M and $1,158.1M straight off the cells and check that the answer didn’t touch them on the way through.
The trust chain
A short chain this time: two cited inputs, one subtraction run in the calculator, one verdict. The guard confirms both figures trace back to a cell and that the $1.4M was computed rather than quoted from anywhere.
The follow-up
“What explains the $1.4M?”
The difference is explained by the Meridian FY26 winter-cycle true-up for the non-corridor fleet.
- The P&L includes YTD total expense of $1,159.5M 187.
- The December route results total only $1,158.1M 208.
- The difference is $1.4M, and the Meridian true-up statement is also $1.4M 209.
The underlying timing issue is that Meridian’s true-up statement was issued on 9 January 2026 for the winter cycle completed 31 December 2025 216217. Under the agreement, SSR’s payment obligation arises on completion of the winter cycle on 31 December, regardless of when the statement or invoice is received 211. So it belongs in December expense.
The statement breaks the $1.4M into:
- $0.6M — unscheduled wheelset and bogie overhauls
- $0.5M — winter-cycle labor above allowance
- $0.3M — materials escalation true-up
for a $1.4M total FY26 winter-cycle true-up 209.
The route report’s likely miss is on the Non-Corridor Special Trains & Adjustments line: analyst notes explicitly say the central P&L accrual was fine, but route-level extracts cut before the January statement needed checking because late items on that line had slipped the route report before 24. In the December route results, that line shows only $2.1M of operating expense before the SSR total rolls up to $1,158.1M 189208.
So: the P&L accrued the $1.4M December obligation; the December route results were cut before the Meridian statement and appear not to have picked it up.
The Meridian Rail Services FY26 winter-cycle true-up: wheelsets and bogies $0.6M, labour $0.5M, materials escalation $0.3M, under §4.3 of the fleet maintenance agreement, Annex A. The obligation arose on completion of the winter cycle, 31 December, so the P&L carries it. The statement is dated 9 January, after the route-level extract was produced. A late-posted adjustment the route report missed. From January the reports agree again. Chips: Meridian agreement §4.3, §4.4, Annex A · P&L Dec FY26 · Route Results Jan FY26.
What to notice
TIES — the April FY26 route results show YTD total operating expense of $2,630.0M on the SSR Total row 143, and the April FY26 MTD P&L shows $2,630.0M as YTD Actual Total Expense 144. Difference: $0.0M.
| Line item | Route Results by Service Line - 0426 | MTD P&L - 0426 | Difference |
|---|---|---|---|
| YTD Apr FY26 total operating expense / total expense | $2,630.0M | $2,630.0M | $0.0M |
Materiality: the gap is $0.0M on $2,630.0M — 0.0%.
- The same question on April returns TIES, $2,630.0M both sides. The tool doesn’t find a gap just because you asked for one.
- Asked to reconcile the Annual Report to the capital spend reports, it answers CANNOT RECONCILE: the Annual Report has no capital figure. It names the missing side instead of forcing a comparison.
- The explanation came out of a contract, not a spreadsheet. That’s why I put the contracts in alongside the workbooks.
Video
“Watch one $2.1 million travel through an entire close” (the Super Fancy Bio film), the same pattern on a biotech corpus.
Related
Use cases: Check the board pack · Hard queries · Which version is real.
Posts: The $2.1 million that was only in one of your reports · Citations aren’t verification.
