COGS1 - Certificate of Good Standing requirements for data loading historical filings

lmcclung commented 3 years ago

Background:

This ticket was opened to identify requirements for COGS1 filing type code in Oracle. BC Online users could go to BC Online and order a certificate of good standing, pay the fee and get the certificate sent to them. Non-BC Online users could fill out a form and send it with payment (routing slip) to staff to create.

This is just a request for an output and no corporate data is changed. This was a historical filing for an entity which wished to be a Benefit Company so we needed to load the filing history. Can't load this filing until these requirements are know.

Information collected:

Where the certificate should be sent (mailing address, email address or pickup). If pickup we needed PICKUP_BY name and phone number.
Payment information - BCOL info, but could also be paid by routing slip.

What needs to be displayed in the ledger:

Nothing!

Do we need to bring this info over in any way shape or form?

Not sure - asking home team.

lmcclung commented 3 years ago

Info from David Roberts https://app.zenhub.com/files/157936592/1c612462-e5bc-43a8-814f-553d285b56e4/download

lmcclung commented 3 years ago

@thorwolpert I had a quick chat with Claudine.

COGS should not be in the filing ledger as it does not update the corporate record
COGS can be requested by anyone - not necessarily the company (For example, an employee applying for permanent residency needs to be provide a COGS for their employer to the feds).
Currently, they do not store the certificate in any fashion, just make a note what date request was received, how much was charged and how the certificate was sent to them (email/mail/pickup). If someone says they didn't get it and staff noted it had been sent, the client has to pay again because the service had been provided.
Currently, they do not issue receipts for cash or cheque payments as we don't have a mechanism for this. BCOL users get a copy of the DAT slip.
also, this is a very in-demand product - more government organizations are asking for these COGS.

I think when we build this feature in the UI we should look at building this on the same dashboard where third parties can order business summaries, letters under seal and other products we sell.

jdyck-fw commented 3 years ago

This is one of the backlog items no longer in Ops that is tagged to our sprint that I mentioned today @lmcclung

bcgov / entity