Claims Spec Example Submission File updated to 2026 Spec
Provide Zipped CSV and XLSX version and update specification and upload page.
Local & Statewide
- Select the module in CEDARS
- Select user type
Provide Zipped CSV and XLSX version and update specification and upload page.
Local & Statewide
Log in to comment and vote
Comments7
[deleted]
May 28
Roopa Reddy
May 28
@cedars team
Hi Sonja,
The example files are currently missing the 2026 Claim Specification updates.
Key gaps identified:
Measure: Missing FuelID and UnitTaxCredits fields
Claim: Missing Participant ID; IDSM_DR and IDSM_DER should be removed; rename CalEPA_Flag as DAC_Flag (note: ElectricMasterMeter_Flag and GasMasterMeter_Flag are included)
Participant: Not included
cedars team
May 28
Hi Roopa, apologies I had pulled those files off cedars-3 but it looks like the updated work was no longer there. I’ve attached again.
claim_2026_statewide_example_input-2.xlsx
21.4 KB• Spreadsheet
claim_2026_example_input-2.xlsx
26.5 KB• Spreadsheet
Roopa Reddy
May 28
@cedars team Hi Sonja, got it. Thanks for the corrected example files.
ggreen
Jul 8
Hi @cedars team,
The 2026 spec also appears to be available for download from cedars-3 (see attached file). This input spec file has the Participant table along with new Claims table fields. Can you confirm this is the 2026 spec even though the file name is 2025?
Claims_2025_Inputs.csv
31.9 KB• Spreadsheet
cedars team
Jul 8
Hi @ggreen,
I looked into this and reviewed the input spec file you attached. I can confirm that it aligns with the 2026 spec data rules, including the Participant table and the new Claims table fields.
Yesterday,
cedars-3was still set to 2025 for the claim year while we were applying some of the 2026 claim spec updates in preparation for UAT. The claim year has since been updated to the 2026. Since the filename is generated based on the active claim year at the time the file is downloaded, this leads me to believe that you may have downloaded the file before the claim year was updated, which would explain why the filename reflects 2025 even though the contents align with the 2026 spec.Thank you for bringing this to our attention, and please let me know if you have any additional questions.
Regards,
Erika
ggreen
Jul 15
Thank you Erika. This spec file is the best format for us to use in updating our internal system. Thanks for confirming everything is there.
Greg.