GREENWAY HOUSING COOPERATIVE CP1582 missing annual report

sienna-oldaccountdontuse commented 3 years ago

ServiceNow incident:

INC0084392

Contact information

Staff Name: Mark Lau

Description

GREENWAY HOUSING COOPERATIVE CP0001582 was restored in COBR on Mar 11, 2020 and the CP submitted Annual Reports up to 2019 with the last AGM as Nov 29 2019.

Their co-ops online To Do list only has 2021 Annual Report.

Please insert the 2020 Annual Report into the To DO list and update the last effective date to November 29 2019.

Tasks

[x] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
[x] Add entity or relationships label to zenhub ticket
[x] Add 'Priority1' label to zenhub ticket
[x] Assign zenhub ticket to milestone: current, and place in pipeline: sprint backlog
[x] Reply All to IT Ops email and provide zenhub ticket number opened and which team it was assigned to
[x] Ask Mark to confirm whether they actually filed the ARs or if they just updated the last AR date.
[x] Assign service now ticket for David/Siddharth to see if the AR's didn't come across from COBRS. If there weren't any, they'd need to create filings for them in CPRD and push them to us
[ ] We'd load them into Postgres and that would update the ledger with the missing 2017, 2018, 2019 ARs
[ ] We where the dust settles on ARs in the To Do list - maybe the 2020 & 2021 would both be there now.
[ ] Author of zenhub ticket to mark ServiceNow ticket as resolved or ask IT Ops to do so

pwei1018 commented 3 years ago

I didn't see the 2019 annual report filing in both Oracle and Lear database

pwei1018 commented 3 years ago

@Sienna-Blumstengel @kialj876 @thorwolpert

lmcclung commented 3 years ago

@pwei1018 @thorwolpert I'm thinking the next steps are:

1) Ask Mark to confirm whether they actually filed the ARs or if they just updated the last AR date. 2) Raise a service now ticket for David/Siddharth to see if the AR's didn't come across from COBRS. If there weren't any, they'd need to create filings for them in CPRD and push them to us 3) We'd load them into Postgres and that would update the ledger with the missing 2017, 2018, 2019 ARs 4) Then we can see where the dust settles on ARs in the To Do list - maybe the 2020 & 2021 would both be there now.

Would this be right?

I've emailed Mark.

lmcclung commented 3 years ago

Emailed Mark Lau Apr 7th Hi Mark,

When this restoration was filed in 2020 did you guys actually file the 2017-2019 ARs or just update the last AR date?

I seem to recall that you don’t always file multiple ARs, but that the team was asked to do so when we went over to the new app so that we’d have ledgers for each filing.

Please confirm what the process would have been in March 2020. It doesn’t appear there are filings in the database – so wanted to clarify before we figure out how to rebuild them.

Also, could you confirm what the AGM dates were for the 2017, 2018 and 2019 ARs?

Once we have these in the ledger it should resolve our To Do list issue.

Thanks.

lmcclung commented 3 years ago

From: Lau, Mark CITZ:EX Mark.Lau@gov.bc.ca Sent: April 13, 2021 9:50 AM To: McClung, Linda CITZ:EX Linda.McClung@gov.bc.ca Subject: FW: GREENWAY HOUSING COOPERATIVE CP1582 missing annual report

Hi Linda,

Sorry for the delay as the co-ops record was hard copy only so the information wasn’t readily accessible.

This co-op had listed 2017 Annual report - Dec 13 2017 AGM 2018 Annual Report – Nov 6 2018 AGM 2019 Annual Report – Nov 29 2019 AGM

The restoration process has not been changed. The Annual reports were filed in bulk and entered as a ledger comment.

However the last annual report agm date for the restoration was entered into virtel. The last As At date, shown as the Last Annual Report Date in COBR, was Nov 29 2019.

lmcclung commented 3 years ago

Friday Apr 16 - mark filed 2017-2019 ARs in COBRS

Three Annual reports have been ledgered separately. I did have to U CO and changed the last as at date field to the 2016 AGM date before I could enter the 2017 AGM date otherwise I would get the error message of unable to enter an AGM date prior to the last as at date.

lmcclung commented 3 years ago

Assigned to DBAs on April 16th

lmcclung commented 3 years ago

throwing an estimate of 2 on it for sprint planning purposes.

lmcclung commented 3 years ago

This is ready for person working on ops. Although might want to wait for data loader being pushed with alterations.

lmcclung commented 3 years ago

Waiting for data loader - May 11th

kialj876 commented 3 years ago

@Sienna-Blumstengel @amit4610 this one is ready to be reviewed

sienna-oldaccountdontuse commented 3 years ago

Looks like the 2020 AR is available, but the 2017, 2018, and 2019 ARs still have incorrect effective dates. Is that an issue @lmcclung ? Mark requested that we update the 2019 AR effective date in his original request.

lmcclung commented 3 years ago

@Sienna-Blumstengel let's send it back to Mark the way it is. The filed date is the date that Mark went back into COBRS to file the 2017-2019 annual reports. It's the system date that was brought over. If he's concerned about having the filed by date displayed as April 15th, 2021 then he could add a registrar's notation to the filings saying something like "due to system migration issues, the filed by date is displayed as April 15, 2021 however, were stamped filed on March 10, 2021.

The Last As At Date he references is the AGM date from the 2019 report and goes in the code in the background (not displayed anywhere). Kial would have updated the last AR date in our coding so that the 2020 AR now displays in the to do list.

sienna-oldaccountdontuse commented 3 years ago

Ohhh I see! Thanks Linda!

bcgov / entity