ZEVA 2 - Compliance Reporting (Model Year Report)

Goal
Enable supplier users to submit Model Year Reports (MYRs) and government analysts to generate and issue assessments in compliance with legislative requirements, while ensuring data integrity and immutability through secure file storage.

User Roles
- Supplier (Regulated Party)
- Government Analyst
- Director (Decision Maker)

Functional Elements

1. Supplier Actions
- Enter Supply Data: Input the number of new vehicles supplied (used to calculate compliance ratio reductions).
- Generate MYR Spreadsheet: System generates a spreadsheet containing all required MYR data (per Section 17 of the legislation).
- Review and Edit: Supplier reviews the spreadsheet, adds sales forecast information, and makes any necessary changes.
- Submit MYR: Upload the completed spreadsheet. File is saved with a legal hold to ensure immutability. The “number of new vehicles supplied” is also stored separately in the system.
2. Analyst Actions
- Generate Assessment: System generates an assessment spreadsheet based on internal ZEVA2 data (not the supplier’s file), aligned with Section 19 of the legislation.
- Review and Adjust: Analyst reviews the assessment and may apply Section 21 adjustments.
- Upload and Parse: Upload the adjusted assessment file. System parses the file and displays new ZEV unit transactions and the supplier’s balance at the end of the compliance period.
3. Director Actions
- Review and Issue Assessment: Analyst submits the assessment file to the director. File is saved with a legal hold. Upon issuance, the system records new ZEV unit transactions and updated supplier balance.

Workflow Summary
1. Supplier enters supply data → generates MYR spreadsheet.
2. Supplier reviews, edits, and submits spreadsheet → file saved with legal hold.
3. Analyst generates assessment → reviews and applies adjustments.
4. Analyst uploads assessment → system parses and displays results.
5. Analyst submits to director → director issues assessment → transactions and balances recorded.

Data Integrity Measures
- All uploaded files (MYRs and assessments) are stored with legal holds to ensure immutability.
- Files are retrievable for audit and compliance purposes.
- System maintains a history of all submissions and actions.

The issue describes a multi-role MYR and assessment workflow, including spreadsheet generation, uploads, parsing, legal holds, audit history, and balance updates, but names no files, tests, or entry points. Start by locating the existing supplier, analyst, director, spreadsheet, and file-storage workflows; done means the complete workflow and data-integrity requirements are implemented and verifiable.

Written by the indexing model from the issue text.