Review the claim
Find the claim reference, shipment, vehicle, carrier and review status together. Keep proposed claim amounts distinct from approved amounts and completed payments.
Shippers & brokers / Exceptions & connected systems
Exceptions & connected systems
Follow the work that needs attention: shipment claims, partner requests, file exchange and integration failures. Keep the source record and the next decision visible to your team.
Native platform · Demo dataReview exceptions against the actual movement
The native claims workspace keeps the claim, shipment, vehicle, carrier, amount and review state together. Switch views to see partner requests and failed-file activity in GM Connect.
Explore connected exchange ↗About this capture
Source-rendered Prevayl Demo captures of unchanged Claims and shared OEM partner cockpit components, source 0087dac2, October 26 Eastern / October 27 UTC, 2026. Fictional local claim, connection, request and file records only. The demo connection remains inactive; no live GM exchange, connection test, accept/reject decision, claim approval or financial action occurred. Light-mode EDI captures use the native theme control. Partner setup and acceptance are required for a real connection.
What belongs together
Keep the context with the work.
Connections depend on partner acceptance, enabled message sets and your company configuration. Demo captures show review states, not proof of a live partner connection.
- Claims tied to orders, vehicles & carrier records
- GM partner requests awaiting dispatch decisions
- EDI file activity & failed-exchange details
- API, EDI, imports & accounting connections
- Team roles, permissions & configuration
Inside the workspace
The exception belongs with its operating record
Review the partner request
The OEM partner cockpit surfaces reconsign and divert requests for dispatch review alongside file activity. A pending request remains a decision for the authorized team.
Find the failed exchange
Review inbound and outbound file status and the recorded failure reason. Confirm partner mapping and enabled transaction types through the integration setup process.
How it fits your day
From the first review to the next handoff.
Identify the operational need
Bring the claim, damage workflow, source file or trading-partner requirement into the review.
Confirm the configuration
Agree supported formats, provider access, enabled modules and responsible team roles.
Keep the connection accountable
Review the available activity and exceptions against the operational records that the connection supports.
Explore this workflow
Open the product. Explore the details.
Loading the pages for your operation…
Continue with your operation
Put it in your company's context.
Feature access depends on your business, role, enabled modules and provider configuration. Review the workflow and permissions during setup.