Gain More Control, Flexibility, and Transparency Across the Claims Lifecycle
Snapsheet’s May release introduces powerful enhancements that help carriers adapt quickly, reduce manual friction, and improve data quality across critical claims workflows.
With new configuration options, smarter field controls, and improved payment visibility, these updates are built to support faster decisions and more consistent outcomes, without added complexity.
Here’s what’s new:
- Configurable Emergency Services questions based on loss type for more consistent triage data
- Permission-based control for Date of Loss edits, giving teams more flexibility without IT involvement
- New “Pending Print” status in SmartPayables for clearer visibility into payment timing
- Custom fields for vendor tasks, configurable by service type, to improve task clarity and coordination
Scroll down to explore the full May release notes and see how these enhancements can support your team’s success.
May 2025 Release Notes
API Updates
Attachments Usage API Leaving Beta - Enhancement
On December 11, 2024, we announced the beta release of a new Attachments Usage API as part of our financial attachments initiative. That API has left beta and is now generally available to all customers.
Claim APIs | Syncing Fire-related Emergency Service and Incident Details Data (Property Claims Only) - Enhancement
Property claims include information about whether the fire department was present at the scene of an incident in two places: a propertyClaimFireIncidentDetail object and an emergency_services_detail object. The specific fields that contain those values are as follows:
- propertyClaimFireIncidentDetail
- did_fire_dept_come
- emergency_services_detail
- fire_attended
Despite their similarities, these weren’t technically linked previously. This meant that values for these fields did not have to match.
Now, when a new claim is created using the V1 Claim API, the following scenarios will take place:
- If a value is provided for fire_attended but not for did_fire_dept_come, the fire_attended value will be used for both.
- If a value is provided for did_fire_dept_come but not for fire_attended, the did_fire_dept_come value will be used for both.
- If a value is provided for both fields, the fire_attended value will be used for both. 1
Additionally, if the fire_attended field is updated with the V2 Claim API, the did_fire_dept_come field’s value will be updated to match it.
Additionally, we intend to deprecate the did_fire_dept_come field in a future release. Keep an eye on release notes and monthly previews for more information!
V2 Claim API (PATCH) | Initial Claim Open and Closure Times Added - Enhancement
The V2 Claim API now supports the following attributes in PATCH requests, allowing them to be updated via the API:
- first_opened_at: The timestamp indicating when the claim was first opened. This value must be earlier than or equal to the opened_at timestamp.
- first_closed_at: The timestamp indicating when the claim was first closed. This value must be later than or equal to the closed_at timestamp. It must also be later than the opened_at timestamp.
Additionally, if a PATCH request includes opened_at or closed_at values that are earlier than the existing first_opened_at or first_closed_at, and the corresponding first_opened_at or first_closed_at attributes are not explicitly provided, the API will automatically update these fields to reflect the earlier timestamps. For more information, click here to check out the API reference.
Claims Management Updates
Total Loss Feature Leaving Beta - New Feature
On May 14, 2025, we announced the beta release of new total loss support within Snapsheet Cloud. That feature has left beta and is now generally available to all customers. To enable this feature, reach out to your Snapsheet contact.
Financials Updates
Sending International Check Payments - Enhancement, Beta
This feature is currently in beta and can be enabled upon request. For more information, please reach out to your Snapsheet contact.
Snapsheet Claims users now have the option to send check payments to international addresses. They can do so by selecting the new “International” option in the Shipping Option field. This option appears when the country in the shipping address differs from the customer’s default country configuration.
This enhancement is only available in Snapsheet Claims environments integrated with Snapsheet Payments for payment disbursement and through banks integrated with Snapsheet Payments. Environments integrated with third-party payment disbursement systems will not have access to this option. Additionally, the shipment options may vary by bank. Configuring those shipping options may also require contacting a Snapsheet account manager.
Metrics Updates
OFAC History Dashboard Added - Enhancement
A new OFAC History dashboard has been added to Metrics. Its purpose is to log transactions sent to OFAC. It includes the following information:
- Financial transaction IDs
- Request bodies sent to OFAC
- Responses received from OFAC’s APIs and HTTP status codes
- Resulting OFAC statuses (e.g., passed, failed)
- Associated claim numbers
- Account codes
Additionally, a new permission called OFAC History Report has been added. This provides Snapsheet Claims users with access to the OFAC History dashboard.
