A new distribution partner signs, and the first question lands on the carrier’s Guidewire team: how does this partner’s data get into PolicyCenter? Each partner sends in its own format, so the default answer is another connector, scoped, built, and tested for that one sender.
That connector is where the cost of onboarding sits. Engineering hours, Guidewire test cycles, and rework after every payload change repeat for the next partner, and the repetition limits how many partners a carrier can open.
This article walks through onboarding in order, from the first call to the first live submission. It lists the cost drivers, names the five gates every partner passes, and shows who does what at each one.
What Drives the Cost of Onboarding a New Distribution Partner?
The cost of onboarding is a set of drivers that each partner brings with it. Naming them before the first call keeps scope honest and keeps the conversation with the partner specific.
The cost drivers to list before the first call
Every driver below exists whether the carrier builds a connector or uses a shared route. What differs is how many times the carrier pays for it.
Driver | What it means for the carrier |
|---|---|
Lines of business | Each line a partner sends adds fields, coverages, and rules to map. |
Payload shape | Nested or flat structures decide how much translation a partner needs. |
Mandatory fields and valid values | Each field needs a rule for what counts as present and correct. |
Value translation | A partner’s label for a coverage must become the code PolicyCenter expects. |
Testing cycles | Every partner needs test submissions before live data moves. |
Change handling | Guidewire releases and payload changes force retesting. |
Carrier-specific fields | Tenant differences add fields for one carrier and not another. |
Each row maps to a submission intake decision the carrier already owns. The first call is where those decisions get written down.
Why a custom connector repeats the same drivers for every partner
A broker, an MGA, and a TPA each build a module that maps fields and calls the carrier’s APIs. The carrier supports every one of those modules.
When an endpoint or a vendor release changes, each sender connector needs retesting. Carrier IT time goes to that retesting instead of the next partner.
What changes when the route is fixed and only the mapping varies
With a fixed route, the carrier defines the endpoint, the validation rules, and the target fields once. Each partner then brings only its own payload and its own mapping.
Brokers, MGAs, and TPAs can then send submission data into PolicyCenter without building a connector. The carrier’s work shifts from building per partner to defining what complete means.
The Five Gates From First Call to First Live Submission
Every partner passes the same five gates, in the same order. We call this the Partner Onboarding Path. It separates what the carrier decides from what the partner supplies.
Gate | What happens | Who owns it |
|---|---|---|
1. First call | Scope the lines of business, the submission types, and the partner’s admin contact. | Carrier underwriting operations |
2. Definition of complete | Set mandatory fields and valid values. | Carrier underwriting operations |
3. Mapping | The partner uploads a sample payload, a model suggests field mappings, and a person reviews each one. | Partner admin |
4. Sandbox testing | The partner runs clearance, account creation, and submission creation in a test environment. | Partner and carrier Guidewire team |
5. First live submission | The partner sends real data, and the carrier watches the dashboard. | Partner |
Gates one and two: scope the partner and define complete
The carrier invites the partner by email, and the partner onboards through self-service. It registers with a one-time password, receives an API username and key, and selects the lines of business it will send.
Before mapping starts, the carrier states which fields are mandatory and which values are valid. That definition decides what gets sent back to the partner.
Gate three: map the payload and review every mapping
The partner uploads a sample JSON payload and keeps its own data format. An insurance-trained model suggests how each source field maps to the carrier’s Guidewire fields and flags the fields it did not match.
A person reviews every suggested mapping and approves it before any submission is sent. Human-reviewed AI mapping means the model assists and a person decides.
Gate four: test in a sandbox before real data moves
The partner tests in a sandbox against the carrier’s route, using a test harness. It runs submission clearance, account creation, and submission creation, then verifies each result.
No live data moves until those tests pass. The carrier’s Guidewire team checks the results and does not write code for the partner.
Gate five: the first live submission
The first live submission follows the same route as the test, with real data. Nothing about the path changes between gate four and gate five.
Payloads with gaps go back to the sender to complete instead of entering the underwriting queue. The underwriter sees submissions that meet the carrier’s definition of complete.
What to Settle on the First Call
The first call sets the scope for everything after it. Four decisions belong on the agenda, and each one removes a question from a later gate.

Lines of business and submission types
Start with one line of business and one submission type. Name the target, such as Guidewire PolicyCenter, so the partner knows which fields apply.
Each additional line adds fields to map. The first call therefore decides how many mapping reviews the partner owes.
Mandatory fields and valid values
Underwriting operations owns this list. A submission is complete when every mandatory field is present and every value matches a code the carrier accepts.
Write the rule once. The route applies it to each partner’s payload and translates the partner’s values into the codes PolicyCenter expects.
Producer codes and clearance
Settle which producer codes the partner will send. Submission clearance in Guidewire checks producer codes before data reaches an underwriter.
Partners run clearance in the test environment at gate four. A producer code error found there never becomes an underwriter’s problem.
Policy, claims, or both
Some partners send claims, not submissions. TPAs and brokers send first notice of loss into ClaimCenter, and claims intake carries its own rules, such as a policy in force on the loss date.
Decide on the first call which flow the partner starts with. Scope the second flow as its own pass through the five gates.
Who Does What During Onboarding
Three groups take part in every onboarding. Clear roles keep the Guidewire team out of the critical path.

Underwriting operations
Underwriting operations defines complete and reviews the first test submissions the way an underwriter would read them. If a field an underwriter needs is missing, this group finds it at gate four.
The Guidewire team
The Guidewire team confirms the target fields and checks the test results in the test environment. It does not build a connector for the partner.
The partner’s admin
The partner’s admin uploads the sample payload, reviews the suggested mapping, runs the sandbox tests, and sends the first live submission. The partner owns its side of the route from sign-up to go-live.
What Happens After the First Live Submission
Onboarding ends at the first live submission, and operation begins there. Three things matter after go-live: visibility, change handling, and the next partner.
Trace every submission
A dashboard shows what was sent, what arrived, and what was rejected. Each request is logged, so a question from an underwriter or a partner gets an answer from the record.
Handle changes without reopening the build
When Guidewire or a partner’s payload changes, the mapping is updated in one place. New mandatory fields trigger an alert, and default values keep submissions flowing.
This is the work behind keeping integrations running when Guidewire or your own payload changes. It stops being a per-partner retest.
Add the next partner
The next partner invited by email passes the same five gates. The route, the rules, and the definition of complete stay as they are.
Capacity for new distribution partners then depends on how fast partners map and test, not on how many connectors the carrier’s team has built.
How InsOps Helps
Yazh (Yaal) is the InsOps Integration Gateway, a data exchange layer for carriers on Guidewire. A sender maps its payload once, and Yazh translates it to each carrier’s Guidewire format. LiLa, our insurance-trained model, assists with the mapping, and a person reviews every mapping before it is used.
Yazh connects to Guidewire PolicyCenter, ClaimCenter, and BillingCenter. It includes a self-service portal for senders, a test harness, and a sandbox for testing before real data is sent.
Guidewire also has a product called Integration Gateway, which is a developer framework. Yazh adds the sender-facing route, the mapping, and the testing beside it. Payloads with gaps go back to the sender, and changes to a payload or a Guidewire release are handled in one place.
If you are scoping how to open your Guidewire instance to a new distribution partner without a new build for each one, contact us to talk through what this path could look like for your operation.
Frequently Asked Questions
What does it cost to onboard a new distribution partner into Guidewire?
The cost depends on the drivers: lines of business, payload shape, mandatory fields and valid values, value translation, testing cycles, and change handling. A custom connector repeats each driver for every partner. A shared route sets the carrier-side rules once, and each partner adds its own mapping and testing.
What happens on the first call with a new distribution partner?
The carrier and partner agree on the lines of business, the submission types, and the partner’s admin contact. The carrier also states what a complete submission looks like. Everything after the call follows from those decisions.
Who reviews the field mapping?
A person reviews and approves every mapping before it is used. The insurance-trained model suggests how each source field maps to the carrier’s Guidewire fields and flags the fields it did not match. It never approves a mapping on its own.
How does a partner test before sending real submissions?
The partner uses a sandbox and a test harness. It runs submission clearance, account creation, and submission creation, then verifies each result. Live data moves only after those tests pass.
What happens to a submission that is missing required data?
It goes back to the sender to complete. It does not enter the underwriting queue. The carrier’s mandatory fields and valid values decide what counts as incomplete.
What happens when Guidewire or a partner’s payload changes?
The mapping is updated in one place. New mandatory fields trigger an alert, and default values keep submissions flowing. The carrier does not reopen a separate build for each partner.
How is Yazh different from Guidewire’s own Integration Gateway?
Guidewire’s Integration Gateway is a developer framework. Yazh is a data exchange layer with a self-service portal, human-reviewed mapping, a test harness, and a sandbox for senders. Yazh sits beside Guidewire’s gateway and does not replace it.

