Extract data from annuity applications
Unstract reads fixed, variable and deferred annuity applications, rollover and 1035 exchange paperwork and withdrawal requests, scanned, faxed or e-signed, and returns checked, structured data to your policy administration system.
401(k) release sent to Kestrel 10/27, confirm w/ client — DM
CM-VA-APP (03/2025) · PAGE 1 OF 12
{ "form": "Individual annuity application", "application_no": "CM-A-2610-55193", "owner": "Grace L. Holloway", "date_of_birth": "09/02/1961", "ssn": "***-**-3047", "product": "Variable", "tax_status": "Traditional IRA", "initial_premium": 185000, "source_of_funds": "Rollover", "primary_beneficiary": "Robert J. Holloway", "confidence": 0.96}
Trusted by insurance teams around the globe
Annuity paperwork from reps, plan sponsors and the mailroom
An e-signed ticket from the firm's order system needs no help. Most of the annuity queue arrives in one of these states instead.
Signed in the rep's office, faxed, then scanned twice
Fixed, indexed and variable forms, each with its own layout
Exchange amounts written in, crossed out and initialed
Application, suitability form, replacement notice and transfer request in one file
A retiree list from the plan sponsor beside each benefit election
A case manager types every owner, premium source and suitability answer into the admin system by hand, and the client's rollover money sits in transit until someone does.
Unstract reads each application and withdrawal request, pulls the owner, contract, funding, beneficiary and suitability fields, compares them across the packet and posts the contract to your policy administration system.
Read, extract and route every annuity contract
LLMWhisperer parses each annuity form, Document Studio turns it into a record and Flow runs annuity new business around them. Start with any one of the three and add the others when you need them.
Turn faxed and scanned annuity applications into text that keeps every box
An annuity application packs a product checkbox, a tax status checkbox, a funding source and a beneficiary table onto one page. LLMWhisperer reads them with the layout intact, so ROLLOVER stays marked and 1035 EXCHANGE stays blank, and each contingent share stays on its own name.
Send the text to an LLM of your choice, or feed it straight into extraction.
Learn more about LLMWhispererGet one consistent record from every annuity application and withdrawal form
List the fields your new business team needs, from owner and annuitant to tax status, premium source, beneficiary shares and the suitability answers. Annuity application data extraction then returns the same JSON record for fixed, variable and indexed contracts, and a withdrawal or surrender request returns its own record with amount, tax withholding and payee bank details. A value that disagrees with another form in the packet comes back flagged with the page that contradicts it.
Call it as an API from your order-entry platform, or run it as an ETL pipeline over the folder where scanned mail lands.
Learn more about Document StudioRun annuity new business from a signed application to an issued contract
Describe your annuity application intake in plain English and Flow's agents build the workflow: applications come in from the order-entry feed, rep faxes and the mailroom, get matched against pending cases and existing contracts, are read, and are checked against your suitability, replacement and premium limits. Clean cases move on to issue, and the contract data lands in your policy administration system. You approve the workflow once, and every application then runs through it the same way.
Name the cases a person must see, such as a yes on replacement, a growth objective that clashes with the client's age and liquidity, a premium above your review limit, a missing transfer form or a low-confidence read. Those stop for a suitability reviewer or case manager with the reason attached; the rest keep moving.
Learn more about FlowTry extraction on a few annuity applications first
The free plan lets you parse and extract your own annuity forms today. Automating annuity new business starts with a consultation.
Annuity applications, withdrawals and the forms that fund them
Documents
- Individual annuity applications
- Fixed deferred annuity applications
- Variable annuity applications
- Deferred variable annuity applications
- Fixed indexed annuity applications
- Immediate and income annuity applications
- Retirement annuity application forms
- Applications for retirement benefits
- Annuity account withdrawal applications
- Surrender and partial withdrawal requests
- 1035 exchange and transfer requests
- IRA and 401(k) rollover forms
- Suitability and best-interest questionnaires
- Replacement notices and comparison forms
- Beneficiary designation and change forms
- Other carrier annuity forms and state versions
Fields captured
Built for the teams that open, review and pay out annuity contracts
Each application opens as a case on the day it arrives, with a missing transfer form or blank beneficiary share listed at the top.
Income, net worth, objective and the replacement answer set out side by side, so a reviewer can judge suitability without paging through the packet.
Applications checked for unsigned pages and blank suitability answers before they go to the carrier, so fewer come back as not in good order.
Retirement benefit applications and withdrawal requests read with the payout option, start date and withholding elections captured for each participant.
Contracts issued sooner, with less keying in annuity new business
Protected like the retirement savings it moves
An annuity application lists the owner's Social Security number, household income and net worth in the suitability answers, the bank account a premium or withdrawal moves through, and who inherits the contract. Together that is enough to impersonate a retiree and redirect their savings.
- Encryption in transit and at rest for every annuity form and attachment.
- Annuity applications you send are never used to train models.
- Role-based access, so suitability answers and bank details reach the reviewers who need them, with each correction logged against the case.
- Retention set by you: application and withdrawal files are deleted on your schedule.
- Self-hosted deployment for carriers and broker-dealers that keep client data in their own environment.
What annuity operations teams ask first
In three layers. LLMWhisperer parses the scan or PDF with every checkbox and table kept in place, Document Studio maps the text to your fields as a JSON record, and Flow runs the intake around them, from collecting the application to posting the contract.
Annuity application OCR has to read marked and unmarked boxes, a beneficiary table and handwritten amounts on the same page. Plain OCR returns loose lines of text. LLMWhisperer keeps the layout, so the product, tax status and funding source come out tied to the box that was marked.
Yes. Document Studio deploys an endpoint for your schema: post the PDF and get the record back as JSON, including subaccount allocations and death benefit riders where the form has them. The same endpoint serves fixed and indexed applications.
Yes. Annuity withdrawal form processing covers partial withdrawals, full surrenders, required minimum distributions and systematic withdrawal requests. Each one is read for the amount, the tax withholding elections and the payee bank details, and posted against the contract they draw from.
It reads the transfer request alongside the application and compares them: releasing company, contract or plan number and amount. When the application says rollover and the packet holds a 1035 exchange form, or the replacement answer is no while a transfer is attached, the case is flagged for review.
It gathers the inputs a reviewer looks at, such as age, income, net worth, liquid assets, objective and time horizon, into one record with the source page for each. Your rules decide what needs a reviewer, and the reviewer makes the call.
Yes. LLMWhisperer reads handwriting and print together, so an exchange amount written in the margin or a share percentage corrected in pen is captured. A value read with low confidence goes to a person with the page beside it.
Yes. Describe the intake in plain English and Flow's agents build the workflow: collect applications, parse, extract, check suitability and replacement rules, and post the contract. You review and approve it first, and it then runs the same way on every application, stopping only where you said a person must decide.
Yes. Applications for retirement benefits are read for the participant, benefit start date, payout option, spousal consent and withholding, so plan administrators can set up payments without retyping each election.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Annuity files are encrypted in transit and at rest, never used to train models and kept only as long as you choose, and carriers or broker-dealers can self-host. The Trust Center has the details.
Start for free and upload a few applications to test extraction the same day. For the full intake, a consultation maps your annuity forms, your suitability rules and your policy administration system, and most teams see a first live run within days.
Bring a week of annuity applications and withdrawal requests
Fixed, variable and indexed applications, rollover packets and handwritten ones included. We run them live and show every field, check and referral.