Keep the three dates as three separate claims
A trade date records when a trade is assigned to the trading calendar. A settlement date on a confirmation states the scheduled settlement associated with that record. A separately reported actual-settlement date is evidence of a later account event, if the record really supports that meaning. They can agree, but they are not interchangeable fields.
This worksheet keeps all three visible and compares them with one exact schedule row. It does not decide that the confirmation must be wrong, rewrite it to fit a calendar or treat an entered actual date as an independent receipt. The result is a bounded evidence comparison, useful before investigating a discrepancy with the original records.
Canadian currency columns can give different answers
The CSE 2026 Holiday Settlement Schedule lists separate CAD and USD columns for the Juneteenth example on page 2. For a trade dated 18 June on T+1, it shows 19 June for CAD securities and 22 June for USD securities. For a trade on 19 June on T+1, both columns show 22 June. The default excerpt preserves those four specific rows.
Those four rows are the full sourced calendar excerpt used by this worksheet. They do not define the treatment of another holiday, venue, currency or year. The tool matches an exact supplied key; it does not generate a settlement date from a general open/closed label or assume that T+1 means the following calendar day.
| Trade date | Term | CAD schedule date | USD schedule date |
|---|---|---|---|
| 18 June 2026 | T+1 | 19 June 2026 | 22 June 2026 |
| 19 June 2026 | T+1 | 22 June 2026 | 22 June 2026 |
Sources: Canadian Securities Exchange — 2026 Holiday Settlement Schedule, page 2.
Match the complete key before comparing a date
The lookup uses venue, trade date, security currency and term together. Changing USD to CAD in the worked example changes the selected row, while the underlying personal records remain unchanged. That is why a plausible date copied from the neighbouring column is not sufficient.
No row in the supplied excerpt means the schedule date is unknown. The tool does not use the next row, the nearest date or a general next-weekday shortcut. A different venue label is a different key. The term is also explicit: T+0 and T+1 must not be merged merely because their dates sometimes coincide.
Read the fictional discrepancy without turning it into a diagnosis
The example chooses CSE, USD, 18 June 2026 and T+1, selecting 22 June from the dated excerpt. Its fictional confirmation instead says 19 June. Confirmation minus schedule is therefore −3 calendar days. This is a documented difference between supplied fields, not a conclusion about the broker or a live account.
The fictional actual-settlement record says 22 June. Compared with the entered confirmation, that is +3 calendar days. The date happens to equal the selected schedule row, but the tool does not use that agreement to authenticate either record. Check the original currency, term, booking convention and evidence before deciding what the discrepancy means.
Calendar-day differences do not count settlement business days
The subtraction uses calendar dates at UTC midnight solely as a stable way to count whole calendar-day differences. It does not convert an account’s date into a trade timestamp, interpret midnight as a cutoff or claim that three calendar days mean three missed settlement days.
The worksheet has no holiday engine. It will not extend the June excerpt into July, infer a future year’s schedule or treat every Canadian public holiday as an exchange closure. If you need another date, save the applicable source row first and enter its exact key. A missing date remains unknown rather than becoming the next Monday.
A scheduled date may be future; an actual event needs evidence
A confirmation may legitimately contain a settlement date later than the report date, because it describes a planned obligation. The worksheet preserves that scheduling possibility. A reported actual-settlement date later than report as-of is rejected: an earlier report cannot claim that later event as already observed.
Both optional records need a date and a saved reference before the relevant comparison is available. Leaving a reference blank keeps the typed date in the CSV but makes the comparison unknown. A reference label itself is still supplied by you; the browser does not inspect an account, verify a file or confirm that the label describes an actual completed settlement.
An excerpt must keep its source version
A schedule row should travel with a document name, page or section and the saved source version. If two rows have the same venue/date/currency/term key, the worksheet stops rather than choosing one. This includes identical duplicates: a repeated row may indicate that two extracts were combined without a clear version boundary.
For a corrected schedule, preserve the earlier capture and compare the revision explicitly. Do not silently replace one date and leave a previous report looking as though it always used the newer source. The worked table is labelled 2026 and is not an automatically refreshed feed. Its absence of other dates is intentional.
Use the method only for the record’s actual settlement scope
The source excerpt concerns the stated CSE security categories and terms. It does not supply a universal settlement rule for a crypto transfer, token withdrawal, an OTC agreement, foreign exchange or every instrument labelled Canadian. The optional separate crypto-offer link does not make those products share this securities schedule.
An exchange being open, a depository supporting a currency and a particular trade being due to settle are different facts. A date difference also does not establish a failed transfer, a penalty, a regulatory breach or an available cash balance. Those outcomes require their own records and applicable procedure; they stay unknown here.
Export the evidence without changing the original record
The report retains every schedule row, the exact selected key, original optional dates and their references. Blank fields export as unknown, while a genuine zero-day difference remains zero. Values that could act as spreadsheet formulas are escaped as text. The underlying confirmation and source PDF are never changed.
Calculation and CSV download happen locally, without account credentials or network submission. Changing an input clears the stale export until the comparison is rerun. The dated example and method remain readable without JavaScript. Once the review is complete, you may choose to explore the site’s separate offer; that step is optional.
Worked examples
Example 1
For a CSE trade dated 18 June 2026 on T+1, the sourced excerpt lists 19 June for CAD securities and 22 June for USD securities. The fictional USD confirmation says 19 June, three calendar days earlier than the selected schedule row. The fictional reported actual date is 22 June, three calendar days after that confirmation. Neither the mismatch nor the date agreement authenticates the account or proves a settlement failure.
Inspect example inputs
{
"venue": "CSE",
"currency": "USD",
"term": "T+1",
"trade_date": "2026-06-18",
"as_of_date": "2026-06-23",
"confirmation_date": "2026-06-19",
"confirmation_reference": "DEMO fictional trade confirmation",
"actual_date": "2026-06-22",
"actual_reference": "DEMO fictional reported settlement record",
"rows": "venue|trade_date|currency|term|settlement_date|reference\nCSE|2026-06-18|CAD|T+1|2026-06-19|CSE 2026 schedule page 2 Juneteenth row\nCSE|2026-06-18|USD|T+1|2026-06-22|CSE 2026 schedule page 2 Juneteenth row\nCSE|2026-06-19|CAD|T+1|2026-06-22|CSE 2026 schedule page 2 Juneteenth row\nCSE|2026-06-19|USD|T+1|2026-06-22|CSE 2026 schedule page 2 Juneteenth row"
}Questions about the method
Does T+1 mean tomorrow on the calendar?
Not by itself. Use the exact applicable schedule and term. This worksheet reads a supplied dated row and does not construct a holiday calendar.
Does a mismatch prove failed settlement?
No. It shows a difference between entered schedule and confirmation fields. Cause and account completion are not verified.
Why is a typed actual date still unknown without a reference?
The comparison needs a saved evidence record. A date alone should not be promoted into a completed account event.
Primary sources and scope
- Canadian Securities Exchange — 2026 Holiday Settlement Schedule, page 2Checked 2026-10-21. Exact Juneteenth rows: trade 18 June 2026 T+1 settles 19 June for CAD securities and 22 June for USD; trade 19 June T+1 lists 22 June for both. Visually checked column alignment. Dated excerpt only, not a universal calendar.
Examples explain a method. They do not predict prices or establish where a trading service is available. Check the named source before relying on future schedules.