TFRS - BUG- Incorrect effective date shown for transfer # 3067 in TFRS

[Grulin]

Describe the Bug
In TFRS, the Effective Date for a transfer is incorrectly pulling a different date than the Date Recorded by the Director. For Transfer #3067, the Effective Date is displayed as January 1st, 2025 in the UI and the downloaded Excel sheet, even though the director recorded the transfer on December 31st, 2024. This discrepancy can cause reporting issues for suppliers, particularly in edge cases where the effective date determines the reporting quarter (e.g., Q4 2024 vs. Q1 2025).

Expected Behaviour

• The Effective Date for a transfer should match the Date Recorded by the Director in both the UI and the downloaded Excel sheet.
• For Transfer #3067, the Effective Date should be December 31st, 2024, as that was the date the transfer was recorded.

Actual Behaviour

• The Effective Date is pulling January 1st, 2025 instead of December 31st, 2024 in both the UI and the Excel sheet.
• This discrepancy affects reporting periods and compliance calculations.

Screenshots below:

Implications

• Suppliers may report the transfer in the incorrect quarter, leading to compliance and reporting inaccuracies.
• Business processes reliant on accurate effective dates (e.g., credit market reports) may be disrupted.
• Potential disputes or confusion over credit transfer timelines could arise as well as reporting out in the credit market report.

Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: IDIR

• Navigate to the TFRS Transfer View for Transfer #3067.
• Observe that the Effective Date in the UI shows January 1st, 2025, despite the director recording the transfer on December 31st, 2024.
• Download the Excel report for credit market data and confirm the same discrepancy in the effective date column.

Notes: The transfer was recorded by the director quite late in to Decmeber 31st, 2024, indicating that this may be a time zone inconsistency issue? Unsure if this is the problem, but worth mentioning that all time stamps in the systems (TFRS and LCFS Portal) should be in the same time zone.

[airinggov]

@Grulin there is no set Effective date unless the transfer was entered using the historical data entry. Could this be the case for this transfer? If so it could likely be an issue in all historical entry transfers

[Grulin]

@Grulin there is no set Effective date unless the transfer was entered using the historical data entry. Could this be the case for this transfer? If so it could likely be an issue in all historical entry transfers

Hi Al, No, unfortunately this transfer was initiated by the supplier. I believe the effective date usually defaults to the recorded date in TFRS. I think this is why we have no explicit "effective" date in the LCFS Portal because the recorded date is the date the credits become available for use to the supplier (ie. effective). The only reason this is an issue for TFRS is that the C&E team just completed the December credit market report and this transfer should have been part of that, but was exclude because the Excel sheet download of all the transfers categorized this as a January 2025 transfer. Edit: It looks like the C&E team flagged this and did include it in the December report, but it still needs to be fixed in TFRS so they don't have to manually change this every month

[Grulin]

Effective date on this transfer is still displaying January 1, 2025 when it should be displaying the recorded date of December 31st, 2024: