Skip to content
Testaroo
md6.3 KB

Pine Property Services: insurance document set README

Document set README for Pine Property Services. 27 files, 2 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

Preview, first 50 linesmd
# Pine Property Services: certificate of insurance, policy schedule, claim and settlement documents

The insurance paperwork a property maintenance business holds and produces: the policy schedule with its endorsements and premium chain, the certificates of insurance its clients demand, a first notice of loss, the settlement statement that follows it, the loss run, the broker account and the renewal application that declares all of it back to the insurer.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Records are derived from the shared operating model `trades-property`, so identifiers join across this set, across the other commercial document sets, and across every fixture built on the same model.

## Reconciliation identities this set asserts

- Property premium is 2,700,000.00 USD of insured value at 0.85 per 1000, which is 2,295.00 USD.
- Base premium 7,040.00 plus endorsements 590.00 plus fees 115.00 plus tax at 3.5 percent equals 8,016.08 USD payable.
- The 5 instalments sum to the total payable exactly, with the rounding remainder taken off the final instalment rather than spread.
- The six apportioned location shares sum to exactly 100.0000 percent, not 100.0002.
- Assessed loss 18,400.00 less depreciation 2,760.00 less deductible 1,000.00 is the 14,640.00 USD net first payment; total recovery is 17,400.00 USD.
- Incurred equals paid plus reserve on every claim and in the loss run total: 17,890.00 plus 2,760.00 is 20,650.00 USD.
- The renewal application declares the same claims, dates and incurred total as the insurer loss run.
- Every valid certificate is issued before the cover it certifies expires.

## Parameters this set introduces

These are properties of the document class, not of the operating model. They are declared once and every file in the set agrees with them.

- The policy itself: POL-2026-GL-0001, 2026-04-01 to 2027-03-31, insurer Fictional Mutual Insurance and broker Sample Broking Partners, all fictional.
- Limits and deductible: 1,000,000.00 each occurrence, 2,000,000.00 aggregate, 1,000.00 deductible.
- Insured values by property kind: Office 450,000, Workshop 380,000 and Retail 520,000 USD. The trades-property model carries a property kind but no value.
- Rating: 0.85 per 1000 of insured value, 620.00 per vehicle, flat general liability and tools charges, 3.5 percent premium tax and 12.5 percent broker commission.
- The four endorsements, the three claims and the depreciation rate applied to the open claim.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `policy-schedule.pdf` | pdf | valid | Policy schedule with endorsements (PDF) |
| `policy-schedule.docx` | docx | valid | Policy schedule with endorsements (DOCX) |
| `schedule-of-locations.csv` | csv | valid | Schedule of insured locations |
| `schedule-of-vehicles.csv` | csv | valid | Schedule of insured vehicles |
| `coverage-limits.csv` | csv | valid | Coverage limits |
| `endorsement-schedule.csv` | csv | valid | Endorsement schedule |
| `premium-breakdown.csv` | csv | valid | Premium breakdown |
| `premium-instalment-schedule.csv` | csv | valid | Premium instalment schedule |
| `policy-workbook.xlsx` | xlsx | valid | Policy workbook |
| `certificate-of-insurance-COI-2026-0001.pdf` | pdf | valid | Certificate of insurance (PDF) |
| `certificate-of-insurance-COI-2026-0001.docx` | docx | valid | Certificate of insurance (DOCX) |
| `certificate-of-insurance-COI-2026-0007-expiry-before-issue.pdf` | pdf | invalid | Certificate of insurance whose expiry precedes its issue date |
| `certificate-of-insurance-register.csv` | csv | valid | Certificate of insurance register |
| `certificate-of-insurance-register-expiry-before-issue.csv` | csv | invalid | Certificate register with a certificate that expired before it was issued |
| `certificate-holders.csv` | csv | valid | Certificate holder register |
| `claim-form-FNOL-2026-0003.pdf` | pdf | valid | First notice of loss claim form (PDF) |
| `claim-form-FNOL-2026-0003.docx` | docx | valid | First notice of loss claim form (DOCX) |
| `claim-settlement-statement-CLM-2026-0003.pdf` | pdf | valid | Claim settlement statement |
| `claim-settlement-lines.csv` | csv | valid | Claim settlement lines |
… 73 lines total: download for the full file.

Specifications

Document Set
insurance
Industry
trades-property
Source Kit
trades-property
Entity
Pine Property Services
Synthetic
true
As Of
2026-09-08
Documented Files
27
Documented Defects
2

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 27 entries including this README, and the deliberate-defect section names 2 file(s) with the measured size of each discrepancy.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Pine Property Services: insurance document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 6,429 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.