Coop Annual Report Year in filing history being changed by system

**Describe the bug in current situation**
This issue originated with OPS ticket 1455. Staff have identified numerous examples of Coop A/R Years changing which prevents future A/Rs from being filed.

This ticket is to investigate why the BC Business Registry system sometimes changes the year of the Annual Report a coop files when it goes to the Filing History.

I'm not aware of any outstanding incidents of this right now, the several I have seen I sent tickets in for, and the IT team was able to fix. This ticket is to investigate the matter with the goal of preventing the issue from occurring again.

You can see an example of this situation on the closed Zenhub #1319 where CP1205 filed the 2021 Annual Report that was in the "to do list", and it then appeared in the filing history as the 2023 Annual Report. The system also removed the available 2022 Annual Report from the "to do" list, so the client was unable to file the 2022 AR until IT fixed the issue. here is a screenshot of the issue:

a5905a28-e9a0-4e3a-8504-fc18f2c6be82.png

Below is what I think the impact of this issue is:

This problem affects the “to do list” and in particular causes ARs that the coop still needs to file from appearing in the To Do List. The coop incorrectly thinks they are caught up on their AR filings, or the system is preventing them from doing their next required AR filing which is outstanding. This is a problem as it will mess up the dissolution runs that we do for failing to file ARs, and it will also affect the reporting of “Good Standing” for the coop. Our system will incorrectly think they are in good standing when in fact they are not. Being in good standing is often a requirement to carry on certain business transactions, or to apply for funding/grants. It is not good if the BC Registry starts to incorrectly report that a certain business is in good standing when in fact it is not.

My understanding is that each individual coop issue I have sent in has been resolved, but I have not heard that a system issue has been identified and is being proposed to be fixed. Is there any information on this that I am not aware of?

Here is a list of past impacted coops and related zenhub numbers:
• CP0001205, zenhub #1319. 2021 AR was showing as the 2023 AR
• CP0001939 zenhub #729 2021 AR was showing as the 2024 AR.
• Both CP0001225 and CP0001272 both filed 2022 ARs where the filing history did not even report a year for the ARs. I had submitted a ticket to sbc it ops back in April 2022 for those two before I was able to submit zenhub tickets.

There might be other instances but these are the only ones that I have caught or that clients have reported to me.

**Link bug to the User Story**

**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.

**Chance of Occurring (high/medium/low/very low)**

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Actual/ observed behavior/ results**

**Expected behavior**
A clear and concise description of what you expected to happen. Use the gherking language.

**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.

No source file, test, or entry point is identified. Start by tracing the filing-history and annual-report to-do processing using the CP0001205, CP0001939, CP0001225, and CP0001272 examples. Done means the filed year remains correct, the next outstanding annual report stays in the to-do list, and filing-history records without a year are prevented.

Written by the indexing model from the issue text.