Trading Parties¶

The trading party definition is the mandatory first step for any Send Workbench implementation. Without it, Workbench will not start or load any data. This is not optional and cannot be deferred.

What is a trading party?¶

A trading party is the insurer organisation using Workbench. It provides the identity context for all risks created on the platform — every risk knows which insurer is writing it.

Creating the trading party file¶

Create the file at:

config/{client}/trading-parties/{client}-insurer.json

Based on the verified base repository file (demo-insurer.json):

Field	Description
`status`	`ACTIVE`
`activationDate`	ISO date from which the party is active (e.g. `2025-07-01`)
`partyName`	Your client organisation's display name
`partyId`	Unique identifier in DUNS URN format: `urn:duns:{DUNS}`. DUNS numbers are 8–9 digits in practice — use the exact value provided by the client
`partyRole`	Typically `Insurer`
`tradingPartyDetail.amsEndpointUrl`	AMS WSDL endpoint URL used for ACORD/AMS policy integration
`tradingPartyDetail.contact`	Nested object: `personName`, `telephone`, `email` (and optionally `fax`)
`tradingPartyDetail.address`	Nested object: `numberAndStreet`, `cityName`, `postalCode`, `country` (ISO alpha-2)

Linking to be_config.json¶

After creating the trading party file, set homePartyId in applicationconfig/be_config.json to the same partyId value:

{
  "homePartyId": "urn:duns:123456789"
}

Danger

The partyId in trading-parties/{client}-insurer.json and homePartyId in be_config.json must match exactly. A mismatch prevents Workbench from starting. This is one of the most common causes of a blank or broken local environment.

Example file¶

{
  "status": "ACTIVE",
  "activationDate": "2025-07-01",
  "partyName": "Acme Insurance Ltd",
  "partyId": "urn:duns:10838357",
  "partyRole": "Insurer",
  "tradingPartyDetail": {
    "amsEndpointUrl": "https://riskwire:8443/testharness-soap-api/AcordMsGSvc_v1_43_Endpoint?wsdl",
    "contact": {
      "personName": "Ops Contact",
      "telephone": "+44 2012 345678",
      "email": "ops@acme.com"
    },
    "address": {
      "numberAndStreet": "1 Acme Street",
      "cityName": "London",
      "postalCode": "EC1A 1AA",
      "country": "GB"
    }
  }
}

Verifying it works¶

After the Send Partner Portal deployment has completed and Workbench has picked up the config on its next periodic refresh, verify the setup by:

Confirming Workbench starts cleanly — a mismatch between partyId and homePartyId causes the service to fail to start
Checking that the party is visible in the UI contexts that reference the insurer

Consult your delivery lead for any current trading-party inspection endpoints on your active core platform version.

Next step¶

With the trading party in place, you can configure your first Business Class.