Launching a new line of business: what happens to the senders' payloads

Launching a new line of business: what happens to the senders' payloads

Craig Hangartner

Saba Gobal, CPCU

When a carrier adds a new line of business in Guidewire, every sender that will write to that line must send a payload the carrier has never received before. The new product brings new fields, new coverages, and new valid values. Senders already live on other lines now face a second payload shape.

The carrier’s product team decides how the line is designed. The senders’ payloads follow, and nobody owns the gap between the two until the first submission fails. That gap is where launch dates slip.

This article covers what changes in a payload when a new line launches, which senders are affected, who owns each change, and how to carry the new line’s payloads without rebuilding the integrations that already run.

What actually changes in a sender’s payload when a carrier adds a new line?

A new line changes the payload in three places: the fields a sender must supply, the values those fields accept, and the structure that groups them. Payloads for existing lines stay as they are.

Each change traces back to the product model the carrier configures in PolicyCenter. The sender sees the result as rejected or incomplete submissions.

Four-step infographic on new line payload changes: new required fields, changed values, new grouping, what stays the same.

Fields the sender never had to send

Every line carries mandatory fields the other lines do not. A commercial auto line needs a vehicle schedule, and a workers’ compensation line needs payroll by class code.

The sender’s existing payload has no place for these fields. Someone adds them to the source mapping before the first new-line submission goes out.

Valid values and coverage terms that change

Fields that look familiar often accept different values on the new line. Limits, deductibles, coverage codes, and typecodes belong to the product, not to the sender.

A sender that maps “liability limit” to the old line’s codes sends a value PolicyCenter rejects on the new line. The field exists, but the valid values do not match.

What stays the same

Insured, producer, and address blocks keep their shape across lines, so those mappings carry over. Endorsements and other policy updates on existing lines keep their current payloads.

A product launch is a planned business change. A Guidewire release is a platform change, and keeping integrations running when Guidewire or your own payload changes is a separate problem with its own plan.

Which senders are affected, and when do they find out?

Only senders that will write to the new line must change their payloads. Senders that stay on existing lines keep sending what they send today.

The carrier controls the launch date. Each sender controls how fast its own mapping gets done, and that pace sets the real go-live.

Senders that write to the new line

These senders need the new payload specification, a mapping for the new fields, and a place to test. Each one repeats that work on its own schedule.

The carrier learns how ready each sender is only when test payloads arrive. A sender that starts late pushes the whole line’s rollout.

Senders that stay on existing lines

Their payloads do not change at all. The test of a clean launch is that these senders notice nothing.

Any change that reaches them is a defect in how the new line was added, not a feature of the launch.

How MGAs, brokers, TPAs, and vendors each feel the change

The four sender types meet the new line differently. Knowing which type you have tells you where the mapping work lands.

MGAs and brokers meet the change as new mandatory fields in a form or spreadsheet. The route they use to send submission data into PolicyCenter decides how much work the new line adds.

Software vendors pass every field through from their own data model. Workbench vendors open a mapping task in their product for every carrier that adds a line.

A vendor that serves many carriers faces a different version of the new line at each one. That is the core of multi-tenant integration.

On the claims side, a new line brings new loss types and coverages to first notice of loss. TPAs sending claims on the new line need a payload that claims intake accepts with those loss types in place.

Who owns each change, the carrier or the sender?

The carrier owns the definition of the new line’s payload. The sender owns the mapping from its own data to that definition.

Splitting ownership this way keeps the carrier from editing sender systems and keeps senders from guessing at carrier rules. The table shows where each change lands.

Change

Where it shows up

Who owns it

How it is caught

New mandatory fields

Product model in PolicyCenter

Carrier defines, sender maps

Submission rejected as incomplete

New valid values

Typecodes and coverage terms

Carrier defines, sender maps

Value rejected during test

New structure

Coverables and groupings

Carrier defines, sender restructures

Mapping review

Change in the sender’s own data

Sender’s source system

Sender

Retest in the sandbox

The carrier’s side: publishing the target

Before senders map anything, they need a specification of what the new line expects. That specification is the carrier’s deliverable.

When product configuration changes, the specification changes with it. A late fix to the specification sends every sender back to its mapping.

The sender’s side: mapping once

Each sender maps its payload to the specification one time. Without a shared layer, the sender writes that mapping again for every carrier it serves.

The handoff: one reviewed mapping per sender

A person reviews each mapping before real data moves. The review catches wrong value pairs while the price of a mistake is a failed test, not a rejected policy.

How do carriers carry the new line’s payloads without rebuilding existing integrations?

Carriers have three routes: extend each sender’s existing connector, build a new connector per sender, or have each sender map its payload once and translate it to the Guidewire format. The right route depends on how many senders write to the new line.

Each route puts the work in a different place. The comparison below follows what each route asks of the carrier’s Guidewire team.

Extending existing connectors

Existing connectors already know the carrier’s other lines. Adding the new line means changing code that live lines depend on.

Every change to that code carries regression risk for the lines already in production. The Guidewire team retests lines that were not part of the launch.

Building a new connector per sender

A new line at a carrier with many senders opens a build for each one. Maintaining a Guidewire connector then continues for every sender after launch.

The build also repeats when the next line arrives, because each connector is written against one version of the carrier’s product.

Mapping once and translating

A mapping layer separates the sender’s payload from the carrier’s Guidewire format. The new line adds one new target definition, and each sender adds mappings for the new fields only.

Existing lines are not touched. Senders already live keep their current mappings and add the new ones beside them.

How do you test the new line’s payloads before launch day?

Test each sender’s payload against the new line in a sandbox before any real data is sent. Real data moves only after the mapping passes review and test.

Testing is where the ownership split pays off. Failures point to either the specification or the sender’s mapping, and each has a clear owner.

Sandbox before real data

A sandbox gives each sender a place to send test payloads against the new line’s definition. Failures show up as test results, not as rejected policies in production.

Reject incomplete data at the door

Incomplete payloads should stop at intake with a reason attached. The sender sees which mandatory field or valid value is missing and fixes it before anything reaches an underwriter or adjuster.

Stage the senders

Launch senders in an order the carrier controls. Five steps cover most launches:

Four-step infographic of a staged sender launch: share spec, map and test, open to one sender, then add the rest.
  1. Publish the new line’s payload specification to every sender writing to it.

  2. Have each sender map the new fields and submit the mapping for review.

  3. Test each reviewed mapping in the sandbox until it passes.

  4. Open the line to the first sender and watch rejections by reason.

  5. Add the remaining senders as their mappings pass.

How InsOps Helps

Yazh (Yaal) is the InsOps Integration Gateway, a data exchange platform for inbound data into Guidewire PolicyCenter, ClaimCenter, and BillingCenter. A sender maps its payload once, and Yazh translates it to the carrier’s Guidewire format. LiLa, the InsOps insurance-trained model, assists with the mapping, and a person reviews every mapping before it is used.

When a new line launches, the carrier adds the line’s definition and each sender maps the new fields in the self-service portal. Senders test in the sandbox with the test harness, and Yazh rejects incomplete data with a reason. Large payloads move by file location, and mappings stay specific to each tenant.

The InsOps Guidewire integration gateway sits beside Guidewire’s own Integration Gateway, which is a developer framework. Yazh adds the sender-facing layer: the portal, the mapping editor, the sandbox, and gap rejection. New-line payloads reach your Guidewire configuration without a new connector for each sender.

If you are scoping a new line launch and want to see how senders’ payloads move without a build per sender, contact us to talk through what this looks like for your operation.

Frequently Asked Questions

What is a payload change when launching a new line of business?

A payload change is any difference between what senders send for existing lines and what the carrier’s Guidewire configuration expects for the new line. It covers new mandatory fields, new valid values, and new structure.

Why does a new line affect senders that already integrate?

A sender’s mapping is written against the carrier’s current product definitions. A new line adds definitions the mapping does not cover, so senders writing to the new line must extend it, while senders on existing lines keep their current mappings.

How should a carrier prepare senders for a new line?

Publish a payload specification for the new line before senders start mapping, and give each sender a sandbox to test against it. Name one owner on the carrier side for specification questions so changes reach every sender at once.

What is the hardest part of adding a new line for existing senders?

Valid values. Fields with familiar names accept different codes on the new line, and a mapping that passes on field names still fails on values. Sender teams find this only when test data runs against the new definition.

What should a carrier measure during a new line launch?

Track first-pass acceptance per sender, rejections by reason, and the number of senders live on the new line against the number planned. A rejection reason that repeats across senders points to the specification, not to the senders.

How does InsOps assist when a new line launches?

LiLa assists with mapping each sender’s fields to the new line’s definition, and a person reviews every mapping before it is used. Senders test in the sandbox, and incomplete data is rejected with a reason before it reaches Guidewire.

How long does it take to bring senders onto a new line?

The timeline depends on the number of senders and how closely their source data matches the new line’s fields. The first sender sets the pattern for the rest, and the most common delay is a specification that changes after senders have started mapping.

Do claims payloads change when a carrier launches a new line?

Yes. A new line brings new loss types and coverages, so first notice of loss payloads for that line need new fields and values. Claims senders follow the same steps as policy senders: specification, mapping, review, and sandbox test.

Craig Hangartner

Saba Gobal, CPCU