An MGA signs a carrier that runs Guidewire PolicyCenter. The carrier wants submissions to arrive inside PolicyCenter, not as PDFs in an inbox. The MGA's engineers have never worked with Guidewire APIs, and the build estimate runs to months.
TPAs and brokers hit the same wall. Every carrier customer asks for its own route into its own PolicyCenter, and every route looks like another custom build with its own upkeep.
This article covers what PolicyCenter expects from a sender, why a custom connector costs more than its first build, which options exist, and how to get a submission in cleanly on the first send.
What Does It Take to Send Submission Data Into Guidewire PolicyCenter?
Sending a submission into Guidewire PolicyCenter requires secured access, a payload the carrier's APIs accept, a field mapping to PolicyCenter's structure, and a producer code the carrier recognizes.
Each requirement is simple alone. The work sits in meeting all four for every carrier you serve.
What the Payload Carries
A submission payload holds the insured, the risk, the coverages requested, and the producer. Every field lands in a defined PolicyCenter structure.
A field in the wrong place fails the send, or worse, reaches the underwriter wrong.
Why Every Carrier's PolicyCenter Looks Different
Each carrier configures its own instance. A field that is mandatory for one carrier is optional for another, and a coverage one carrier models as a single line another splits across several.
That is why a mapping built for one carrier does not carry to the next.
Who Sends and Who Receives
MGAs, MGUs, TPAs, brokers, agencies, and underwriting workbench and rating vendors send submission data. Underwriters at the carrier receive it.
Both sides want the same result: a complete submission in front of an underwriter without a round of email to fix it.
Why Does a Custom Connector Cost More Than Its First Build?
A custom connector costs more than its first build because it needs upkeep through every Guidewire and carrier upgrade, and each new carrier adds another mapping to maintain.
Months of Guidewire Learning Come First
Before a single submission moves, your engineers learn Guidewire's APIs, its data structures, and the carrier's configuration. That learning takes months, and none of it goes into your own product.
Upgrades Change the Ground Under a Working Connector
Guidewire releases and carrier changes alter the structures a connector writes to. A newly mandatory field turns accepted submissions into rejected ones.
Someone finds out only when sends start failing, and by then submissions are already waiting.
Every New Carrier Multiplies the Work
A sender serving five carriers on Guidewire holds five mappings, five sets of mandatory fields, and five upgrade calendars. Each carrier brings its own change schedule that your team has to track.
The carrier side faces the mirror image. Each new partner is one more connection into core systems, which is why standardized API gateways are replacing point-to-point connections there.
What Are Your Options for Sending Submission Data Without Building a Connector?
Three options exist: build a custom connector, run an integration project on general-purpose middleware, or use a prebuilt gateway that handles access, validation, and logging for you.
The table compares them by what your team owns, not by brand.
Option | What your team builds | Who maintains it | Best fit |
|---|---|---|---|
Custom-built connector | Access, validation, mapping, logging, and error handling | Your engineers, through every Guidewire and carrier upgrade | One carrier, a stable schema, and in-house Guidewire skill |
Integration project on general-purpose middleware | Routes and mappings on a tool built for many industries | Your team, plus whoever administers the tool | A broad integration estate where insurance is one part |
Prebuilt gateway with human-reviewed mapping | Your payload and a confirmed mapping | The gateway provider owns access, validation, and logging; your administrator owns the mapping | Several carriers on Guidewire and a small engineering team |
How to Read the Table
The first two options make your team the owner of Guidewire-specific logic. The third moves that logic to a prebuilt layer and leaves your team with the one thing only you know: what your own data means.
The same logic applies to any insurance data exchange between a carrier and its partners.
Questions to Ask Any Option
Ask whether the route validates the payload before the send, whether a person confirms the mapping, where your data runs, and whether every request leaves a record.
A route that cannot answer all four moves the risk back to your team.
What Each Sender Asks First
Different senders open with different questions. Carriers that add partners at volume face the same math, covered in partner onboarding without custom engineering per partner.
Sender | First question | Why it comes first |
|---|---|---|
MGA | Can one setup serve every carrier I write for? | Each carrier adds a mapping and a set of mandatory fields |
TPA | Can my existing data export map without a rebuild? | Rebuilding an export for each carrier repeats work |
Broker | Will my submission land complete the first time? | Rework after a bounce costs time the placement does not have |
What Does the Submission Path Look Like, Step by Step?
A reliable submission path passes four gates: access, payload, mapping, and producer. A submission that clears all four lands in PolicyCenter on the first send.
We call this the Four-Gate Submission Path. Each gate stops one kind of failure before it reaches the underwriter.
Gate | Question it answers | Who owns it | Failure it prevents |
|---|---|---|---|
Access | Can this sender authenticate to the carrier's environment? | Sender and carrier | Rejected calls |
Payload | Is the data well formed? | Sender | Syntax errors reaching the carrier |
Mapping | Does each field match the PolicyCenter field it belongs in? | Sender's administrator confirms | Misfiled or missing data |
Producer | Does the carrier recognize the producer code? | Carrier setup | Submissions with no valid owner |
The Steps in Order
The gates unfold in eight steps.
Register the sender and verify its identity.
Receive credentials for the carrier's environment.
Select the line of business.
Upload a sample payload and fix syntax errors.
Review the drafted mapping, edit it, and confirm it.
Check the producer code.
Send the submission.
Watch the record of requests, responses, and errors.
Where First Sends Fail
Three failures to design against: a field mapped to the wrong place, a producer code the carrier does not recognize, and a mandatory field left empty.
Fix each at its own gate. A gap caught at the producer check is cheaper than the same gap caught at an underwriter's desk, where it costs a round of email.
Who Owns Each Gate
The sender owns the payload and the mapping. The carrier owns access and producer setup. Agree on both before anyone builds, because a gap on the carrier side stalls the first send no matter how clean the payload is.
How Do You Get Clean Submission Data to the Underwriter?
Clean submission data reaches the underwriter when gaps are flagged before the send, a person confirms the mapping, and the sender tracks acceptance by carrier.
Incomplete Submissions Stall at First Review
Canadian Underwriter reported in July 2026 that about 60% of submissions an insurer or MGA receives never get quoted. The commentary, written for Canadian commercial brokers, names incomplete submissions as the reason that rises above all others.
Read it as a signal about submission quality, not a US benchmark. It matches what broker submissions that fail on first receipt look like in practice.
The fix is flagging gaps before the file reaches an underwriter, so underwriters evaluate risk on complete information instead of chasing it.
Why a Person Confirms Every Mapping
A mapping drafted by software is a proposal. Your administrator knows which source field holds the effective date in your own system and which one only looks like it.
That person confirms or corrects the mapping before data moves. Accountability stays with the sender, and mismatches that software cannot see get caught.
What to Track
Track first-send acceptance rate by carrier, mapping edits per new carrier, submissions flagged incomplete before the send, and days from registration to the first accepted submission.
Falling edits per carrier show the setup is stabilizing. A rising rejection rate after a carrier change signals a new mandatory field or a changed structure.
How InsOps Helps
InsOps builds an insurance-trained AI that assists with moving submission data into Guidewire. LiLa, our insurance-trained LLM, drafts the field mapping from your payload to the PolicyCenter structure, and a person on your team reviews and confirms every mapping before data moves.
The InsOps Integration Gateway gives MGAs, TPAs and brokers a prebuilt route into Guidewire PolicyCenter. Senders register in a self-service portal, bring their payload, and configure it without building their own connector. The gateway runs inside the carrier's own environment, so PII and PHI stay in controlled infrastructure.
The gateway checks the producer code before a submission is sent, flags incomplete data before it reaches an underwriter, and records every request, response, and error in a dashboard. A sender that serves several carriers keeps a separate mapping for each one.
InsOps is a Guidewire technology partner, with prebuilt connectors to PolicyCenter, ClaimCenter, BillingCenter, UnderwritingCenter, PricingCenter, and Quoting Services. If you are evaluating how to exchange submission data with Guidewire without a custom connector build, contact us to talk through what this looks like for your operation.
Frequently Asked Questions
What is a Guidewire PolicyCenter submission integration?
It is a route that moves a submission from an outside system, such as an MGA's or broker's, into PolicyCenter as structured data. The route handles access, the payload, the field mapping, and the producer check.
Why does an MGA, TPA or broker need its own route into a carrier's PolicyCenter?
Each carrier configures its own PolicyCenter, so submissions emailed as documents get retyped by hand on the carrier side. A direct route puts complete data in front of the underwriter and removes that retyping.
How do you send submission data into PolicyCenter without a custom connector?
Use a prebuilt route that handles access, payload validation, and logging, then bring your own payload and confirm the mapping. Your engineering time goes to your product instead of to Guidewire APIs.
Why do first submissions fail to land in PolicyCenter?
Three causes stop first sends: a field mapped to the wrong place, a producer code the carrier does not recognize, and a mandatory field left empty. Each one is caught earlier and cheaper at its own gate than at the underwriter's desk.
What should you track to know the route is working?
Track first-send acceptance rate by carrier, mapping edits per new carrier, submissions flagged incomplete before the send, and days from registration to the first accepted submission.
How does the InsOps Integration Gateway help?
It gives senders a prebuilt route into Guidewire, where LiLa drafts the field mapping and the sender's administrator edits and confirms it before any data moves. The gateway runs inside the carrier's environment and records every request, response, and error.
How long does it take to get a first submission into PolicyCenter?
Two things set the timeline: how long your team needs to learn Guidewire's structures, and how fast the carrier confirms producer setup and mandatory fields. A prebuilt route removes the first, and only an early conversation with the carrier settles the second.