Extract data from travel insurance claim forms
Unstract reads travel insurance claim forms and the receipts, boarding passes and foreign medical bills stapled to them, scanned or photographed on a phone, and returns checked, structured data to your claims system.
HARBORLINE TRAVEL ASSURANCE · CLAIMS · PO BOX 2290, HARTFORD, CT
hospital bill in Portuguese, receipts + boarding pass att.
HTA CLAIM FORM TC-100 (REV 03/2025)
{ "policy_number": "HTA-TRV-7730415", "insured": "Okafor, Nneka", "departure_date": "09/14/2026", "return_date": "09/28/2026", "destination": "Lisbon, Portugal", "claim_type": "medical", "date_of_incident": "09/19/2026", "currency": "EUR", "total_claimed": 622.5, "confidence": 0.94}
Trusted by insurance teams around the globe
Travellers file claims from wherever the trip went wrong
A typed form with three receipts in the traveller's own currency is the rare case. Most claims are put together in a hotel room or an airport, and look like this.
Photographed on a hotel bed at night, skewed and in shadow
Cancellation, medical and baggage claims on different pages of the form
Filled in by hand at the airport, the amount crossed out and raised
Form, boarding passes, receipts and a doctor's report in one upload
Hospital bills in the local language, receipts in three currencies
An examiner keys each expense, converts each currency and matches each receipt by hand, and the traveller waits weeks for money they already spent abroad.
Unstract takes that work off the desk — it reads the claim form and every attachment, pulls the trip, incident and expense fields you name, checks them against the policy and the receipts, and opens the claim in your claims system.
One platform for reading, extracting and routing travel claims
Three products, each able to stand alone: one reads the form and its receipts, one turns them into data, one runs the claim from upload to decision. Pick the layer your claims desk needs first.
A travel insurance claim parser for forms, receipts and boarding passes
Get the full text of a travel claim form and everything attached to it, from a phone photo of a taxi receipt to a three-page hospital bill in Portuguese, with each layout intact. Expense lines keep their date, currency and amount together, the ticked claim type stays beside its label, and a flight number on a boarding pass is never read as a booking reference.
Send the text to your own LLM, or make parsing the first step of a travel claims workflow.
Learn more about LLMWhispererTurn travel insurance claim forms into one checked record per claim
Name the insured, trip, incident and expense fields you want, and every claim comes back as the same JSON record, whether it was a cancellation with a supplier's refund letter, a medical claim with a foreign bill or a baggage claim with an airline report. Each amount keeps its original currency beside it. A receipt dated after the trip ended, or a total that the receipts don't support, arrives flagged with the reason.
Call it as an API from your claims portal, run it as an ETL pipeline from the claims mailbox, or make it one step of an orchestrated claims process. Used on its own, it is a travel insurance claim data extractor that fits in front of the system you already run.
Learn more about Document StudioRun travel claims from the upload to the payout decision
Describe your travel claims intake in plain English and Flow's agents build the workflow. Claims are picked up from the web form, email and the assistance company's case files, every attachment is sorted into form, receipt, boarding pass or medical report, and each one is read. The policy is checked as in force for the trip dates and the claim type as covered, receipts outside the trip are flagged, and the claim opens in your claims system, such as Guidewire ClaimCenter or Duck Creek Claims. You approve the workflow once, and it then runs the same way on every travel claim.
Decide in advance when a person takes over: coverage in question, a fraud flag, an amount above an adjuster's authority, a read that isn't certain. Those claims wait for an adjuster, or for the special investigations unit when fraud is the reason. The rest keep moving.
Learn more about FlowExtract from travel claims now. Add the automation when you're ready.
Start for free to parse and extract your own travel claim forms today. Automating travel claims intake starts with a consultation.
Every travel claim type, and the paperwork that proves it
Documents
- Travel insurance claim forms
- Trip cancellation and interruption claims
- Emergency medical claims from abroad
- Baggage loss and damage claims
- Travel delay and missed connection claims
- Boarding passes and e-tickets
- Airline delay and cancellation letters
- Property irregularity reports
- Foreign hospital bills and medical reports
- Pharmacy and clinic receipts
- Hotel, taxi and meal receipts
- Booking confirmations and supplier invoices
- Doctor's certificates for a cancelled trip
- Police reports for theft abroad
Fields captured
For the teams that pay travellers back
Claims from every plan and destination opened with the trip, incident and expenses already in, so the examiner starts at the coverage decision.
Foreign hospital bills and doctors' reports read as they reach the case file, so the costs owed abroad are known before the traveller is home.
Claims for several travel insurers read into one record, whichever insurer's form, language or currency each one arrived in.
Receipts dated outside the trip, edited amounts and repeat claimants surfaced with the documents side by side.
Travellers reimbursed sooner, with fewer receipts keyed by hand
Built for passports, medical records and bank details
A travel claim puts a passport number, medical records written abroad and the bank account for the reimbursement in one file. Together they are enough to impersonate the traveller or redirect the payout, so the file needs the same care as the money.
- Encrypted in transit and at rest.
- Travel claims and their attachments are never used to train models.
- Access by role and by claim type, with every review and correction logged against the claim it touched.
- Retention set by you: claim files and attachments are deleted when your schedule says.
- Self-hosted deployment for insurers and administrators that keep traveller data in their own environment. Ask us what yours requires.
What travel claims teams ask before they start
Treat it as a pipeline, not a pile. Uploads land in a folder, bucket or mailbox, each claim and its attachments are read as they arrive, and records go to your claims system one by one or in batches. A spike after a storm or an airline strike makes the queue longer; it doesn't add steps.
Look for one that reads the whole claim, not just the form. LLMWhisperer is built to scan travel insurance documents of every kind, from the claim form to phone photos of receipts and foreign hospital bills, with their layout kept. Document Studio then pulls the fields you defined and checks them, so the analysis starts from a record, not a stack.
The signed claim form, proof of the trip (a booking confirmation or boarding passes), itemized receipts for each expense, and the document that proves the incident: a doctor's report, an airline delay letter, a property irregularity report or a police report. When each one is read and matched to the form on arrival, a missing item is caught the same day, not on the examiner's first look.
Yes. LLMWhisperer reads printed text in 300+ languages, so a hospital bill in Portuguese or a pharmacy receipt in Thai comes through with its layout intact. Each amount is extracted with its currency, and the conversion is applied by your rules, never guessed.
Each claim is classified first: cancellation, medical, baggage or delay. The fields that belong to that type are then pulled, such as non-refundable costs for a cancellation or hours of delay and the airline's letter for a delay, and every type lands in the same record shape.
Yes. Flight numbers, dates and passenger names come off boarding passes and e-tickets, and the delay or cancellation reason comes off the airline's letter, so a delay claim is checked against the flight it names.
Yes. Document Studio deploys an endpoint per document type: send a claim form with its attachments and get the claim back as JSON, expense lines included. The same extraction also runs as an ETL pipeline from a mailbox or bucket.
The claim stops in a review queue with the reason, such as a receipt dated after the return flight or a total the receipts don't reach. The adjuster sees the field and the receipt it came from, approves or corrects it, and the decision is recorded on the claim.
Yes. Describe the process in plain English and Flow's agents build the workflow: intake, sorting the attachments, reading, coverage and fraud checks, triage and opening the claim. You approve it before it runs, and it then runs identically on every claim.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Passports, medical records and bank details are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosting is available; the Trust Center has the details.
In a consultation we set the intake up around your claim types, your coverage checks and your claims system, and most teams see a first live run within days. To test the extraction today, start for free and upload one of your own claim forms.
Bring a month of travel claims to the consultation
Cancellations, medical claims from abroad, lost bags and delayed flights, with their receipts in every currency. We run them live and show each field, each check and every claim that stopped.