Loss runs for submissions
Five carriers' loss runs, one claims schedule that ties to every report
Upload each carrier's loss run. LossRun Pro maps the columns by their headings, builds one claims schedule and a policy-year summary, then adds up the claims for every policy period and compares the sums with the totals the carrier printed. Where a total does not tie, the difference is shown to the cent.
Your claims schedule
Claims schedule
Swipe the table sideways to see every column.
Tie-out to the carrier's totals
Definition
What is a claims schedule built from loss runs?
A loss run is a carrier's report of the claims on a policy: for each claim, the dates, the status, and what has been paid, what is reserved and what is incurred as of a stated valuation date. A claims schedule is the single table a broker builds from several of them for a submission, with the same columns for every carrier and policy year, so an underwriter can read five years in one place.
The schedule is only as good as its totals. Each loss run prints its own total for the policy period. If the claim rows you carry into the schedule do not add up to that total, something was dropped, doubled or misread. LossRun Pro makes that check on every period and shows the result beside the figures, so the proof travels with the schedule.
Worked example
What the tie-out looks like
The first sample is a general liability loss run for Harbor Point Roofing, LLC, valued as of 10/15/2026, with 3 policy periods and 11 claims. For each period the table compares the claim rows with the carrier's printed total. The figures were produced by the same code that reads your upload.
| Policy year | Claims | Paid loss | Paid expense | Reserve | Incurred | Printed incurred | Result |
|---|---|---|---|---|---|---|---|
| 2024-25 GL-7730412-00 | 4 | 83,550.00 | 23,585.00 | 0.00 | 107,135.00 | 107,135.00 | Ties |
| 2025-26 GL-7730412-01 | 4 | 31,800.00 | 12,740.00 | 70,500.00 | 115,040.00 | 115,040.00 | Ties |
| 2026-27 GL-7730412-02 | 3 | 1,875.00 | 3,160.00 | 42,500.00 | 47,535.00 | 47,535.00 | Ties |
| All periods | 11 | 117,225.00 | 39,485.00 | 113,000.00 | 269,710.00 | 269,710.00 | Ties |
One policy year, claim by claim
The 2025-26 period has 4 claims. The rows below add up to the figures the carrier printed for that period.
| Claim number | Status | Paid loss | Paid expense | Reserve | Incurred |
|---|---|---|---|---|---|
| GL-25-0066 | Closed | 9,800.00 | 2,310.00 | 0.00 | 12,110.00 |
| GL-25-0214 | Open | 14,250.00 | 6,480.00 | 22,000.00 | 42,730.00 |
| GL-25-0359 | Closed | 2,150.00 | 0.00 | 0.00 | 2,150.00 |
| GL-25-0447 | Open | 5,600.00 | 3,950.00 | 48,500.00 | 58,050.00 |
| Carrier printed total | 31,800.00 | 12,740.00 | 70,500.00 | 115,040.00 |
When a period does not tie
The second sample is a workers' compensation loss run (insured: Ridgeline Concrete Services, Inc.). It has a claim description that wraps onto a second line, one claim whose incurred was left blank, and one period that does not tie. For the 2024-25 period (WC 5521908-24) the checks read:
| Check | Claim rows add to | Carrier printed | Difference | Result |
|---|---|---|---|---|
| Claim count | 3 | 3 | 0 | Ties |
| Paid loss | 40,440.00 | 40,440.00 | 0.00 | Ties |
| Paid expense | 9,505.00 | 9,505.00 | 0.00 | Ties |
| Reserve | 53,750.00 | 55,000.00 | −1,250.00 | Variance |
| Incurred | 103,695.00 | 103,695.00 | 0.00 | Ties |
The blank incurred is computed as paid plus expense plus reserve and marked as computed, so the schedule never presents a figure the carrier did not print as if it had. Open either sample above to see the full schedule, the flags and the downloads.
Show the loss run text the general liability sample was built from
# Commercial General Liability Loss Run <!-- image --> Insured: Harbor Point Roofing, LLC Carrier: Alder Creek Mutual Valued as of: 10/15/2026 ## Policy Period 01/01/2024 to 01/01/2025 Policy Number: GL-7730412-00 | Claim Number | DOL | Report Date | Claimant | Status | Loss Paid | ALAE Paid | O/S Reserve | Total Incurred | Description | |---|---|---|---|---|---|---|---|---|---| | GL-24-0113 | 02/14/2024 | 02/20/2024 | Brightline Property Mgmt | Closed | $18,450.00 | $4,120.00 | $0.00 | $22,570.00 | Water damage to tenant unit from roof leak during tear-off | | GL-24-0271 | 05/09/2024 | 05/09/2024 | R. Delgado | Closed | $3,200.00 | $850.00 | $0.00 | $4,050.00 | Customer vehicle struck by dislodged shingles | | GL-24-0388 | 08/22/2024 | 09/03/2024 | Marlowe Dental Group | Closed | $0.00 | $1,275.00 | $0.00 | $1,275.00 | Alleged overspray on adjoining parking lot; closed without indemnity | | GL-24-0502 | 11/18/2024 | 12/02/2024 | T. Okafor | Closed | $61,900.00 | $17,340.00 | $0.00 | $79,240.00 | Fall from ladder, third-party bodily injury | | Total (4 claims) | | | | | $83,550.00 | $23,585.00 | $0.00 | $107,135.00 | | ## Policy Period 01/01/2025 to 01/01/2026 Policy Number: GL-7730412-01 | Claim Number | DOL | Report Date | Claimant | Status | Loss Paid | ALAE Paid | O/S Reserve | Total Incurred | Description | |---|---|---|---|---|---|---|---|---|---| | GL-25-0066 | 01/27/2025 | 02/05/2025 | Cedarwood HOA | Closed | $9,800.00 | $2,310.00 | $0.00 | $12,110.00 | Interior ceiling damage after flashing failure | | GL-25-0214 | 04/30/2025 | 05/12/2025 | Pinecrest Storage LLC | Open | $14,250.00 | $6,480.00 | $22,000.00 | $42,730.00 | Hail-related leak claim, workmanship disputed | | GL-25-0359 | 08/06/2025 | 08/08/2025 | M. Whitfield | Closed | $2,150.00 | $0.00 | $0.00 | $2,150.00 | Scaffold dropped debris onto parked car | | GL-25-0447 | 10/11/2025 | 10/29/2025 | Eastgate Medical Plaza | Open | $5,600.00 | $3,950.00 | $48,500.00 | $58,050.00 | Water intrusion to suite 210 after membrane install | | Total (4 claims) | | | | | $31,800.00 | $12,740.00 | $70,500.00 | $115,040.00 | | ## Policy Period 01/01/2026 to 01/01/2027 Policy Number: GL-7730412-02 | Claim Number | DOL | Report Date | Claimant | Status | Loss Paid | ALAE Paid | O/S Reserve | Total Incurred | Description | |---|---|---|---|---|---|---|---|---|---| | GL-26-0031 | 02/03/2026 | 02/17/2026 | L. Nguyen | Closed | $1,875.00 | $420.00 | $0.00 | $2,295.00 | Downspout damaged landscaping | | GL-26-0189 | 06/12/2026 | 06/25/2026 | Summit Ridge Apartments | Open | $0.00 | $2,740.00 | $35,000.00 | $37,740.00 | Alleged defective flashing, under investigation | | GL-26-0240 | 09/04/2026 | 09/14/2026 | D. Ferraro | Open | $0.00 | $0.00 | $7,500.00 | $7,500.00 | Slip on wet decking, urgent care visit | | Total (3 claims) | | | | | $1,875.00 | $3,160.00 | $42,500.00 | $47,535.00 | | ## Summary | Claim Number | DOL | Report Date | Claimant | Status | Loss Paid | ALAE Paid | O/S Reserve | Total Incurred | Description | |---|---|---|---|---|---|---|---|---|---| | Grand Total (11 claims) | | | | | $117,225.00 | $39,485.00 | $113,000.00 | $269,710.00 | | Page 1 of 1
Steps
From five PDFs to one schedule
The order matters: ask for the right loss runs first, and read the tie-out before the figures.
- Ask each carrier for currently valued loss runsRequest five years of policy periods plus the current term, all valued as of a recent date. The request letter page has plain wording you can send.
- Upload one carrier's PDFDrop the file on the card above. A scan is read with OCR, which can misread a digit, so check its tie-out closely.
- Add the next carrierEach upload joins the same schedule. Every report keeps its own tie-out, and a claim number repeated across uploads is flagged.
- Read the tie-out before the numbersGreen means the claim rows add up to the printed total. Red shows the difference. A red line is usually a page that was missed or read twice, or a misread digit.
- Review the flags, then downloadWork through the flagged claims, then download the CSV or Excel file for the submission and the policy-year summary for the loss narrative.
Comparison
Re-keying, a generic PDF-to-Excel tool, or LossRun Pro
The difference is not speed. It is whether the schedule arrives with proof that it matches the carrier's report.
| What you need | Manual re-keying | Generic PDF-to-Excel | LossRun Pro |
|---|---|---|---|
| Working a five-carrier submission | Every figure typed by hand, then checked by hand. | A quick conversion, followed by cleanup of split cells, repeated headers and merged columns. | One upload per carrier. Columns are mapped by their headings into one fixed layout. |
| Same columns for every carrier | As consistent as the person typing. | Each carrier's own headings and column order, side by side. | One layout of 20 columns. Claim #, File No. and Claim Number land in the same column. |
| Proof that the totals match the report | A calculator tape, when someone makes one. | Usually none. The tool does not know which row is a total. | Claims, paid, expense, reserve and incurred summed per policy period and compared with the printed total. Variance shown to the cent. |
| Totals rows and wrapped descriptions | Typed in or skipped. | Totals rows often land among the claims, and a wrapped line becomes an extra row. | Totals rows are read as totals, not claims. A wrapped line is merged into the claim above. |
| Dates and amounts in Excel | Often left as text. | Frequently text, so (1,250.00) and 03/21/2023 will not sort or add. | Real dates and numbers in the workbook. Parentheses are negative. European decimals are read as such. |
| Things an underwriter will ask about | Found if someone happens to notice. | Not looked for. | Open claims over three years old, incurred below paid, duplicate claim numbers, loss dates outside the policy period, one claim carrying a year. |
Review aids
What gets flagged for your review
Flags are prompts, not judgments. An alert marks something that is probably wrong in the report or in the read. A note marks something an underwriter is likely to ask about.
| Flag | Type | When it appears |
|---|---|---|
| Does not tie | Alert | Paid, reserve, incurred or claim count from the claim rows differs from the total the carrier printed for that policy period. |
| Incurred below paid | Alert | A printed incurred figure is smaller than paid on the same claim. |
| Duplicate claim number | Alert | The same claim number is listed more than once, for example repeated across a page break. Identical rows are an alert; differing rows may be separate coverages. |
| Loss date outside the policy period | Alert | The date of loss falls before the effective date or after the expiration date of the policy period the claim sits under. |
| Open more than three years | Note | An open or reopened claim whose loss date is more than three years before the valuation date (or today's date if none is printed). |
| Large single claim | Note | One claim is more than 25% of its policy period's incurred (periods with at least two claims). |
| Incurred computed | Note | The report left incurred blank for the claim, so it is paid plus expense paid plus reserve. |
| Closed with a reserve | Note | A closed claim still shows an outstanding amount. |
| Ambiguous dates | Note | Slash dates with both numbers 12 or less, when nothing else in the report shows whether it is MM/DD or DD/MM. |
| Mixed date formats | Note | The report holds both MM/DD/YYYY and DD/MM/YYYY dates. Each date is read from its own evidence; slash dates that stay ambiguous are read as MM/DD. |
| No policy period on the page | Note | A claim sits under no policy heading or term, so it is grouped as Unassigned and cannot be tied out or checked against a loss date. |
Plans
Start free, then pay for volume
Free: 1 file per day, up to 10 pages, no account. That is enough to read one carrier's loss run and see how the tie-out works on your own file.
- Pro, $99 a month: 150 loss runs a month, files up to 150 pages.
- Agency, $199 a month: 5 seats and 600 files a month, files up to 150 pages.
A paid plan is a page code sent by email, entered once in the field above; there is no account. Compare the plans
FAQ
Questions brokers ask about loss runs and the schedule
What is a loss run?
A loss run is a report from an insurance carrier that lists the claims made under a policy over a stated period. Each line gives the claim number, the dates, the status, and what has been paid, what is still reserved and what is incurred, all as of a valuation date.
Brokers collect one from every carrier an insured has used, because an underwriter will ask for them before pricing a new submission or a renewal. How to read a loss run defines each term.
How does LossRun Pro prove that the totals match the carrier's report?
Most loss runs print a total for each policy period, and many print a grand total. For every printed total, LossRun Pro adds up the claim rows that belong to it (claim count, paid loss, paid expense, reserve and incurred, in whole cents) and compares the sum with the printed figure. The difference is shown as the sum of the claim rows minus the printed figure.
A line either ties exactly or shows its variance. Nothing is rounded away, and nothing is adjusted to force a match. If a report prints no totals, the tie-out says so, and the totals you see are sums of the claim rows with nothing to compare them against.
Which carriers does it work with?
Any carrier whose loss run is a table with one row per claim and a claim number. There are no carrier-specific templates: columns are mapped by their headings, so Claim #, Claim No., Claim Number and File # all become Claim Number, and DOL, Loss Date and Accident Date all become Date of Loss.
A heading the mapping does not recognize is left out rather than guessed. A loss run that is laid out as narrative text with no claim table cannot be read, and the page reports that as an error instead of showing an empty schedule. The first time you use a carrier's format, compare the schedule with the PDF.
What happens when a total does not tie?
The policy period is marked Variance, in red, with the amount. In the second sample on this page, the 2024-25 reserve adds up to $53,750.00 from the claim rows while the report printed $55,000.00, a difference of $1,250.00.
Common causes are a page that was not read, a page read twice, a digit misread in a scan, or a printed total that was struck before a late adjustment. LossRun Pro does not decide which side is right. Check the PDF for that period, and if the carrier's own total is wrong, ask the carrier for a corrected run.
Can it read scanned loss runs?
Yes, with a caution. The conversion engine applies OCR to pages that have no text layer. OCR can misread a digit, and the tie-out is how you find out, because a misread amount usually shows up as a variance. A file read with OCR carries a warning that says so. A text PDF exported from the carrier's system gives the most dependable result.
Can I combine loss runs from several carriers into one schedule?
Yes. Upload one carrier's PDF at a time and each result is added to the same schedule, up to twelve loss runs in one session. Every report keeps its own tie-out, so a variance is traced to the report that caused it. A claim number that appears in two uploads is flagged as a duplicate, which also catches a PDF that was uploaded twice. The policy-year summary groups claims by year across all carriers.
On the free allowance (1 file per day) a five-carrier schedule takes five days. Pro raises the limit to 150 loss runs a month.
What does the Excel file contain?
Four sheets, and a fifth when the read produced warnings. Claims Schedule has one row per claim in 20 fixed columns, with dates as real Excel dates and amounts as numbers. Policy Year Summary has one row per policy year and a total row. Tie-out lists each check with the claim-row total, the carrier's printed total and the variance. Flags lists every flag with its explanation. Notes appears only when there is something to say, such as a merged continuation row or a file read with OCR.
The claims schedule and the summary can also be downloaded as CSV, which opens directly in Excel.
How many files can I convert for free, and what do the paid plans add?
Free: 1 file per day, up to 10 pages, no account. Pro is $99 a month for 150 loss runs a month, files up to 150 pages. Agency is $199 a month for 5 seats and 600 files a month, files up to 150 pages. Paid access is a page code, not an account: after you subscribe the code arrives by email, you enter it once in the field beside the converter, and it is used only when the free allowance cannot cover a file. The CSV, Excel and JSON downloads are the same on every plan; the plans differ in how many files and pages you can convert. See pricing.
What happens to my loss run and the claimant names in it?
Loss runs name claimants, and LossRun Pro does not mask them: the schedule shows names as printed. The file is processed in memory and deleted after conversion, and uploads are not used to train models. Pages that need a second look may be sent to Google's Gemini API, which can keep them for up to 55 days under Google's terms.
If a carrier agreement or a client contract limits where claim data may go, read the privacy page before you upload.
Is the schedule ready to send to an underwriter as it is?
It is ready to build from. A tie shows that the claim rows add up to the carrier's printed total. It does not show that the carrier's total is right, and it cannot reveal a claim missing from both.
Before the schedule goes into a submission, check the valuation date against what the market asked for, read the flagged claims, and confirm that the first and last page of each PDF were read. The summary template page shows what underwriters usually look for next to the schedule.