Integrations
AMS360 Loss Runs With LossRunReports
LossRunReports works with AMS360 through file import and export. Export a customer or policy list from AMS360, map the columns once and send loss run requests for every renewal. Summaries come back as PDF or XLSX attachments for the customer record, and Agency and Enterprise plans add a REST API and webhooks.
What moves between AMS360 and LossRunReports
LossRunReports connects to your agency management system by export file with saved column mappings, plus our REST API and webhooks. It is not a certified partner app or a native connector.
Book import from an AMS360 report export with saved column mappings for client name, FEIN, lines of coverage, policy numbers, prior carriers and expiration dates
Expiration dates drive renewal queues, so requests go out well before the renewal date
Loss run files and five-year summaries exported as PDF or XLSX for the customer record
REST API and webhooks on Agency and Enterprise for custom sync
Set up AMS360 loss run requests
-
1
Run a report
Export a customer or policy expiration report from AMS360 to CSV or XLSX.
-
2
Map columns
Upload it and match client name, FEIN, lines, policy numbers, prior carriers and expiration dates. LossRunReports saves the mapping.
-
3
Request loss runs
Select the renewals and send requests with the signed letters of authority.
-
4
Return summaries
Attach the PDF or XLSX summary to the customer in AMS360, or pull it by API.
Columns LossRunReports maps
Map them once. The mapping is saved and reused for every later export.
| Field | Used for |
|---|---|
| Client name | Named insured on the request and the letter of authority |
| FEIN | Matching at the carrier, especially for workers comp |
| Lines of coverage | Which loss runs to request |
| Policy numbers | Every term the carrier must report |
| Prior carriers | Where each request is sent |
| Expiration dates | Renewal queue and request timing |
After import, requests follow the process in how to request loss runs, and every reply is read and reconciled by the loss run software.
From request to summary
| Carrier | Policy | Status | Last action |
|---|---|---|---|
| Northfield MutualCA 4471902 | CA 4471902 | Received | Oct 4 |
| Keystone CasualtyGLP 0088213 | GLP 0088213 | Follow-up 2 sent | Oct 9 |
| Granite State CompWC 2215560 | WC 2215560 | Acknowledged | Oct 7 |
| Bayline SpecialtyPKG 771045 | PKG 771045 | Sent | Oct 10 |
| Crestmark IndemnityUMB 30981 | UMB 30981 | Drafted | n/a |
5-yr loss ratio
27.7%
Frequency
2.4 / yr
Open reserves
$61,500
AMS360 loss run questions
Does LossRunReports write directly into AMS360?
No direct write. Summaries are exported as PDF or XLSX for attachment, and the REST API lets your team automate the transfer.
Can I reuse the AMS360 mapping?
Yes. The column mapping is saved per agency, so the next export uploads without remapping.
Which plan includes the API?
The REST API and webhooks are included on Agency and Enterprise plans.
See your own loss run read in under a minute
Upload one carrier report or use our sample. No account needed for the first read.