Withdrawal business-day calculator: count the right interval

Use a start event, not just the oldest date

A request date, approval date and dispatch date can describe different stages. If a stated transfer window begins after dispatch, entering the original request date measures a longer interval that the statement did not describe. If dispatch is unconfirmed, mark it missing and ask for confirmation.

Record the policy’s wording, method, timezone and any cutoff separately. The counter uses calendar dates, not hours. It cannot infer whether a late-day request falls after a provider’s cutoff or convert that request into the provider’s next processing day.

How the counter treats your dates

• Start date is excluded. Start and as-of on the same date therefore produce zero.
• As-of date is included if it is a Monday-to-Friday date and is not among your exclusions.
• Saturdays and Sundays are excluded. This is the tool’s counting convention, not a claim about every payment service.
• Enter applicable holiday or closure dates manually. There is no built-in universal Ontario banking calendar.
• Dates are handled as civil dates using UTC arithmetic, so a daylight-saving clock change does not add or remove a day. This does not establish the provider’s timezone.
• The result counts dates under these rules; it does not check a policy, confirm dispatch or determine whether a payment is overdue.

Worked example: Friday to Wednesday

Choose Friday 30 October 2026 as the start date and Wednesday 4 November 2026 as the as-of date. With no manual exclusions, the eligible dates are Monday 2, Tuesday 3 and Wednesday 4 November: three days. Friday is the excluded start; Saturday and Sunday are weekends.

If the applicable provider explicitly treats 3 November as a closure, enter 2026-11-03 and the result becomes two. This is a hypothetical closure example, not a claim that any Ontario provider observes that date. If the policy instead starts counting after a later dispatch event, change the start date rather than deleting arbitrary days.

OLG example: preserve the separate stages

OLG states an aim of processing withdrawal requests within one business day. Its FAQ then describes bank-controlled transfer after processing as generally taking one to five business days, with possible delays. It tells players without funds after five business days to contact their bank first and OLG for further help if needed. These are OLG’s statements, not guaranteed deadlines or rules for private operators.

The FAQ target differs from the conditional processing wording in section 7.4 of OLG’s Player Agreement. The OLG-specific guide compares both; neither gives a guaranteed bank-arrival date.

Do not add those figures into a universal total or assume verification has already finished. Reopen the current OLG FAQ when applying its wording to an OLG request.

Make the result useful in a support message

Write down the event you used, both dates, the excluded dates and where the calendar assumption came from. For example: “I counted three weekdays after the confirmed dispatch date, excluding the start date and weekends; I have no confirmed holiday exclusions.” This gives support something specific to correct.

An unexplained total such as “seven days late” conceals the assumptions. If the provider’s counting rule differs, preserve your original calculation and record the corrected rule beside it.