Skip to main content

Update CEDARS Data Validation Rules to Support New DEER Delivery Types (PY2026+)

Feature Request2026Claim Spec

Business Justification:
New DEER Delivery Types have been introduced for Program Year 2026 and must be incorporated into existing CEDARS data validation rules and business logic. This enhancement will ensure accurate validation, processing, and reporting of 2026+ claims while maintaining compatibility with legacy delivery types used for pre-2026 program years.

Request

  • Update all applicable CEDARS data rules and validations (e.g., DATE rules and other delivery type-dependent validations) to incorporate the new DEER Delivery Types.

  • Ensure the new delivery types are supported for Program Year 2026 and future years.

  • Maintain compatibility with the legacy delivery types for pre-2026 program years to avoid impacts on historical data and reporting.

  • Review all rules, calculations, and reporting logic that reference delivery type values and update them as needed.

Select the module in CEDARS
Posted by Roopa Reddy ·
Status: In Testing2 comments

Log in to comment and vote

Comments2

  • cedars team

    Team•

    Oct 30

    Hi @Roopa Reddy, @ecorona2 , @ggreen this one’s ready for you to test on cedars-2

    Cedars now recognises the new DEER Delivery Types for Claims. I’ve attached a copy of the updated Claims Date Rules.

    Claims_Date_Rules.csv

    4.2 KB• Spreadsheet

    What to test

    1. New types: Submit claims using Up-Manuf, Mid-Distr, Mid-Retail, Down, and DI. Check that the right date validates against the start and end dates for each measure.

    2. Fallback to Application Date: Leave the Shipment, Sales or Installation date blank. Check that Application Date is used instead.

    3. Permit Issuance Date: For Down and DI claims, add a Permit Issuance Date. Check that it’s used instead of the Installation or Compliance Cert date.

    Please reply here with what you find, and let us know if anything fails, and include the claim ID and delivery type.

    Thanks!

  • cedars team

    Team•

    Oct 14

    Additional Context: SavingsDate Dependency

    The 2026 Claims Specification Update changed the SavingsDate logic to support the new 2026 DEER Delivery Types. However, SavingsDate is still null in the Q1/Q2 Confirmed Claims output files for:

    • MeasImpactType = 'Deem' with DeliveryType in ('DI', 'Down', 'Mid-Distr', 'Mid-Retail')

    • MeasImpactType = 'Deem-WP' with DeliveryType in ('DI', 'DnDeemDI', 'Down')

    SavingsDate is calculated at claim upload, not at confirmation, so regenerating the output files alone won't fill in the missing values. The affected records need to be re-uploaded by PAs. Since SavingsDate is calculated from the date fields, PAs have should be advised to re-upload Q1/Q2 after this ticket is released. That way the date fields and SavingsDate are both checked and calculated with the latest logic, and the records only need to be re-uploaded once.