An underwriter opens a broker or MGA submission and finds the loss runs missing, the location schedule split across two tabs, and a payroll figure that disagrees with the application. Submissions like this fail on first receipt, and the file goes back to the sender while the quote clock keeps running.
The cause is often the format, not the broker. A flat file carries rows and columns, with no structure that tells the sender what the carrier requires. A payload carries labeled, structured data that a schema checks before it is sent.
This article explains why submissions arrive incomplete, what a payload keeps that a flat file loses, how the delivery options compare, and the steps to move senders from one to the other.
Why do broker and MGA submissions arrive incomplete?
Broker and MGA submissions arrive incomplete because the sender cannot see the carrier's required fields before sending, and a flat file does nothing to enforce them.
The sender cannot see the carrier's requirements
Each carrier, line of business, and risk class asks for different fields. Senders learn the list through rejected submissions, not through a schema. Standard forms such as ACORD cover the shared fields, while carrier-specific requirements sit outside them.
A spreadsheet accepts any column in any order. Nothing stops a blank cell at the moment of sending.
The same gap repeats at every sender
A carrier that receives submissions from many brokers and MGAs sees every sender's format and every sender's omissions. The underwriter reconciles all of them against one carrier checklist, so the effort grows with each sender added.
The underwriter absorbs the gap
The Underwriting Edge 2026 survey of 350 senior commercial P&C underwriters in the US and UK, fielded in June 2026, found that 44% named inconsistent submission data as a major obstacle to better decisions. Manual data entry between systems was the most frequently cited workflow problem, selected by 42%.
An underwriting software vendor sponsored the survey, so read it as underwriter sentiment, not a measured completeness rate. Poor submission quality slows underwriting before risk evaluation starts, because the first pass goes to assembling the file.
How does a payload change what arrives?
Payload mapping matches each field in a sender's data to the field the target platform expects, so a submission or claim lands in the right place on the first send.
Flat files carry rows, not relationships
A flat file holds one row per record. A commercial account with many locations, coverages, and prior losses must repeat across rows or spread across tabs, and each sender names the columns differently. The carrier then rebuilds the relationships by hand.
Payloads carry structure that is checked before sending
A JSON payload nests locations, coverages, and losses under the account, so the relationships travel with the data. A schema defines the required fields, and a check against it flags syntax errors and blank required fields before the submission leaves the sender.
The gap surfaces at the sender's desk, not in the underwriter's queue.
What this looks like on one account
Take a hypothetical 12-location property account. As a flat file, it arrives as a location tab, a coverage tab, and a loss tab, joined only by an insured name that one tab spells two different ways. As a payload, the 12 locations sit under one insured, each with its own coverages and loss history, and a mismatched name has nowhere to hide.
Flat file or payload: how do the delivery options compare?
An integration gateway is a single, secured entry point that lets outside systems send data into a carrier's core platform without building a separate connector for each sender.
Three ways to deliver a submission
Flat file by email or upload | Payload, hand-built connector | Payload, prebuilt gateway | |
|---|---|---|---|
Structure | Rows and columns, one layout per sender | Nested, labeled fields | Nested, labeled fields |
Check before send | None, or manual | Built for each carrier | Schema and required-field checks |
Setup per carrier | None | Months of platform learning | Registration and configuration |
Upkeep | Reformatting each cycle | Rework through every upgrade | Alert when a required field is added |
Flat files cost nothing to start, which is why they persist. The cost shows up later, in follow-up requests and rework on the carrier side.
Where the build option stalls
A hand-built connector means learning each carrier's platform and maintaining the connector through every platform and carrier upgrade. A vendor or MGA that serves several carriers repeats that work for each one.
This is the constraint behind onboarding partners without custom engineering.
How do you move senders from flat files to payloads?
Start with the fields underwriters chase most, then give senders a structure and a check they can run before every send.
Five steps
List the fields underwriters request after first receipt, by line of business.
Agree a payload structure for one line of business.
Check syntax and required fields at the sender before each send.
Map each sender field to the carrier field, with a person confirming the mapping.
Log every request, response, and error so each gap traces to its source.
Keep a person in the mapping review
Mapping is where meaning gets decided. A field called "value" can mean insured value, replacement cost, or vehicle value. An administrator at the sender confirms each mapping, so accountability stays with the people who know the data.
Pick a narrow pilot
Choose one line of business and the two or three senders with the highest volume. A narrow pilot shows which fields still arrive blank before you widen the rollout. Fix those fields in the payload structure first, then add the next line of business with the corrected structure already in place.
How InsOps Helps
InsOps builds an insurance-trained AI that assists with moving submission data into your core platform. LiLa, our insurance-trained LLM, drafts the field mapping from your payload to the platform's structure, and a person on your team reviews and confirms every mapping before data moves. This work sits alongside our insurance AI for underwriting.
The InsOps Integration Gateway gives MGAs, brokers, and underwriting vendors a prebuilt route into your policy administration system. Senders register in a self-service portal, bring their payload, and configure it without building their own connector. The gateway flags incomplete data before it reaches an underwriter, and it runs inside your own environment, so PII and PHI stay in controlled infrastructure.
InsOps is a Guidewire technology partner with prebuilt connectors to the core platforms carriers run. If you are evaluating how to exchange submission data with your core platform without a custom connector build, contact us to talk through what this looks like for your operation.
Frequently Asked Questions
What is a payload in insurance data exchange?
A payload is the structured data a sender transmits, usually JSON, with fields labeled and nested by account, location, coverage, and loss. The receiving system reads each field by name instead of by column position.
What makes an insurance submission complete?
A complete commercial submission includes a description of operations, loss runs, a location schedule for multi-site accounts, and figures that agree across the application, schedule, and narrative. Payroll and revenue match wherever they appear.
Why do ACORD forms still leave gaps?
Standard forms cover the fields most carriers share. Carrier-specific requirements, such as an equipment schedule or prior coverage details, sit outside the template, and the form never tells the sender what a given carrier needs.
How can brokers and MGAs reduce back-and-forth on submissions?
Keep entity names, addresses, and schedules identical across every document, send currently valued loss runs, and label unknown values as unknown. Add a check before sending so blanks surface at the sender.
Which metrics show whether submission quality is improving?
Track follow-up requests per submission, the share of submissions complete on first send, and the time from receipt to the first underwriter touch. Set a baseline on flat files first and compare sender by sender.
How long does the move from flat files to payloads take?
The first line of business takes longest because the field mapping is built from scratch. Scope the pilot to one line and a few senders, and keep the mapping review in place so errors do not carry forward.
How does the InsOps Integration Gateway help?
It gives senders a prebuilt route into the carrier's core platform, with LiLa drafting the field mapping from their payload. A person at the sender reviews and confirms every mapping before data moves.