Bamboo · Guidewire Systems Map

The eight systems in the MBR programme and what actually passes between them. Everything drawn with a solid line is described in the PolicyCenter or BillingCenter application guide. Hubspot and Sircon appear nowhere in either guide, so their connections are drawn dashed and need confirming against Bamboo's own integration inventory before anyone plans work against them.

Two things the picture leaves out. BillingCenter also links to Contact Manager, but only for account contacts in the base configuration, so it is listed in the table below rather than drawn. OneInc is not on the map because it was not in the list of eight; it is a live payment path into BillingCenter and should be added.

What moves on each connection

Direction, payload and mechanism, as the application guides describe them

Connection	What moves	How	Source
Agent portal → PolicyCenter	Quotes, binds, endorsements, renewals and policy service, raised by agents.	Jutro front end against PolicyCenter's Cloud API and app events.	PC guide
Consumer portal → PolicyCenter	Policy, coverage and document views for the policyholder.	Cloud API. Product data can also come through Advanced Product Designer endpoints.	PC guide
Consumer portal → BillingCenter	Payments, balances and invoice history.	BillingCenter Cloud API and the SOAP BillingAPI.	BC guide
PolicyCenter → BillingCenter	Accounts, policy periods, charges and itemised charges, producer organisations and producer codes, account holder and billing contacts, service tier, invoice stream and installment plan selections. If a record is to be shared, it has to be created in PolicyCenter.	Billing System plugin sending to web services BillingCenter publishes.	PC guide, ch. 78
BillingCenter → PolicyCenter	Billing options, installment and invoicing plans, calculated payment schedules, commission and agency bill plans, delinquency notices, cancel as soon as possible for non-payment, rescind cancellation when late payment arrives, and not-taken cancellation on unpaid renewals.	Web services PolicyCenter publishes. Calls are asynchronous, and PolicyCenter falls back to its own cached plans if BillingCenter cannot be reached.	PC guide, ch. 78
PolicyCenter ↔ Contact Manager	Contacts in both directions. Contact Manager is the system of record and broadcasts changes to every application; PolicyCenter takes all updates from it. A new contact is only pushed once it sits on an account with a bound policy.	Contact management plugin. All updates are asynchronous, so the guide states conflicts are possible when both sides edit the same contact.	PC guide, ch. 80
BillingCenter ↔ Contact Manager	Account contacts only. The base configuration shares a narrow set of contact types, so this is a much thinner link than PolicyCenter's.	Contact management plugin.	BC guide
PolicyCenter → Forms	Document creation from templates, attached to accounts, policies, policy transactions and contingencies.	Smart Communications for PolicyCenter (SmartCOMM). Binding timing is set by `DocumentProductionBindingType`; the base configuration binds early.	PC guide, ch. 77
BillingCenter → Forms	Invoice details, line item grouping and delivery method. BillingCenter does not produce the invoice document — a document management system downstream does, and BillingCenter only influences how it is built and sent.	`IDocumentMetadataSource` and `IDocumentContentSource` plugins. Delivery follows the account's Send Invoices By setting and the contact holding the Invoice correspondence type.	BC guide, ch. 52
Sircon → PolicyCenter	Producer, agency and licensing data feeding organisations and producer codes.	Not documented. The PolicyCenter guide does anticipate the pattern: it says the integration can be customised so a producer management system owns producers and producer codes for both PolicyCenter and the billing system.	Not in the guides
Hubspot → Contact Manager	Leads and contact records.	Not documented. Direction and system of record both need confirming — if Hubspot writes contacts, it is writing into a store that already has one declared owner.	Not in the guides

Where the nine initiatives sit on this map

Each MBR workstream against the connection it depends on

Initiative	Sits on	What that means for it
MBR-01	PolicyCenter → BillingCenter	Return premium is a charge PolicyCenter sends on a cancellation or endorsement. The calculation is PolicyCenter's; the application is BillingCenter's.
MBR-02	BillingCenter → PolicyCenter	Renewals and grace period run on the delinquency loop. Not-taken cancellation is a BillingCenter workflow that tells PolicyCenter to flat cancel.
MBR-03	BillingCenter → Forms	Billing statements are produced outside Guidewire. Fixes may sit with the document vendor, not in BillingCenter.
MBR-04	PolicyCenter ↔ Contact Manager	Addresses run on the two-way asynchronous contact sync the guide itself flags as conflict-prone.
MBR-05	PolicyCenter → BillingCenter	Commission follows the producer code. Producer codes are created in PolicyCenter and propagated down, and probably originate in Sircon before that.
MBR-06	PolicyCenter → BillingCenter	Incorrect premium reaches billing as a wrong charge total or a wrong itemisation. Same path as MBR-01.
MBR-07	PolicyCenter → Forms	Quote and bind document production is the SmartCOMM integration, including when documents bind in the process.
MBR-08	Agent portal → PolicyCenter	Quote and bind tech errors surface at the portal but are raised against PolicyCenter's API and rules.
MBR-09	Dashed links	Bypassing third party integrations is analysis against exactly the connections this map cannot source from the guides.

What to settle before this is used for planning

Five open items, in the order they matter

Name the document system. Two of the nine initiatives — billing statements and document production — land on a system neither guide names, because Guidewire does not supply it. Until it is named and owned, MBR-03 and MBR-07 have no clear fix path.
Confirm the Sircon direction. If Sircon owns producer codes, PolicyCenter is not their system of record and the commission chain in MBR-05 starts one system further upstream than the map shows.
Confirm what Hubspot writes. Reading contacts is low risk. Writing them puts a second writer against a store with a declared system of record, which is the same shape as the address problem in MBR-04.
Add OneInc. It is a live payment path into BillingCenter and is missing from this map entirely.
State whether ClaimCenter is in scope. Both guides describe integrations to it. If Bamboo does not run it, say so on the map so nobody plans around a system that is not there.

Drawn from the PolicyCenter and BillingCenter Application Guides for Guidewire Cloud 2026.07.0. The four release notes files supplied were byte-identical copies of the same combined InsuranceSuite document, so only one was used. Solid connections are stated in those guides; dashed connections are Bamboo's own and are unverified.