You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actyval Payment Limited: incorporate date is not the same as on our Certificate file. It should be 19th not 20th.The correct date should be 19 June, 2022. Why it shows 20th here?
Please help to check it. This problem has caused difficulties in our normal work.
Ideally, we figure out the timezone of each systems (COLIN, LEAR) and align them in OrgBook BC. Not easy though...
My guess and the response I sent:
Checking further I see that the issue is a timezone issue. When I look at it now, it shows the 19th. My guess is that the company was registered late in the day and in one of the systems along the way the time is being processed as in a different time zone. Between the various systems, the display of the time stamp varies -- made more complicated because it also depends on the time changes. I'll put in an issue to see if we can determine what systems are using what timezone settings, but it's surprisingly complicated and may be difficult to unravel.
I suspect if you check OrgBook BC before 4PM Vancouver time, it will be the 19th, and sometime after, it will display the 20th.
Sorry for the inconvenience.
Not sure of the priority of this one. It's annoying (at least) and rarely important, but can cause problems for some. On the other hand, with the multiple systems involved and the annual time change, it's complicated to fix...
The text was updated successfully, but these errors were encountered:
We received this comment:
Depending on the time of day, when you go to https://orgbook.gov.bc.ca/entity/BC1368169, you see a Registration date of 19th June (correct) or 20th June (incorrect).
Ideally, we figure out the timezone of each systems (COLIN, LEAR) and align them in OrgBook BC. Not easy though...
My guess and the response I sent:
Not sure of the priority of this one. It's annoying (at least) and rarely important, but can cause problems for some. On the other hand, with the multiple systems involved and the annual time change, it's complicated to fix...
The text was updated successfully, but these errors were encountered: