Statement Repairs

Arcadia is committed to delivering accurate, reliable utility billing data. Occasionally, after a statement has been ingested, processed and delivered, we may identify issues or improvements and proactively issue a corrected version. This process is known as a statement repair. Note that this is distinct from an Adjustment Statement issued by a provider.

What Are Statement Repairs?

A statement repair occurs when an already-ingested utility bill is reprocessed to correct or improve its data. These repairs do not indicate fraud or provider-issued adjustments, but instead reflect Arcadia’s ongoing efforts to refine extraction logic, fix template bugs, or correct data alignment issues.

Repairs may include:

• Updated charges or line items due to template or parsing improvements
• Adjusted usage proration when interval data becomes available
• Fixes for previously misaligned dates, units, or costs
• Re-extraction using new or corrected source files

Why instigate a Statement Repair?

We may initiate a repair for a variety of reasons, including:

• Proactive improvements to our data extraction or proration logic
• A fix for a known issue affecting specific providers or statement templates
• A customer-submitted ticket that leads to a systemic template correction

How Statement Repairs Appear in the API

When a statement is repaired:

• The statement’s statement_id remains the same
• The contents of the statement (such as totals, charges, and dates) may change
• The statements's lastModifiedAt date will be updated to the date-time that the bill was repaired

Webhook Behavior

When a statement is repaired and its data changes, Arcadia will emit the EXISTING_DATA_UPDATED EventType webhook event for the associated statement_id with a STATEMENT Entity Type. This webhook event signals that a previously-synced record has been updated and your systems may want to re-fetch the latest data. See this page for more details on Webhooks.

Known Limitations

• We do not version statements in the Plug API — only the most recent version is available.
• There is currently no way to preview or compare changes between the original and repaired version unless you fetch the new version and compare it to the previous version in your own database.
• Customers are not directly notified when a repair is triggered unless they are monitoring for EXISTING_DATA_UPDATED events.

Best Practices

To ensure you capture the latest billing data:

• Subscribe to the EXISTING_DATA_UPDATED webhook event
• Use the lastModifiedAt timestamp on the Statement entity to detect changes
• Design your systems to reprocess or reconcile repaired statements as needed
• If you see an issue with one of your Statements, please create a Zendesk ticket.