Story
Guidewire
FiservFiserv Extends BillingCenter Across Banking Operations
Fiserv, a financials organization in the United States, uses BillingCenter from Guidewire to support banking operations for operations and product.
Fiserv runs banking operations on Guidewire so ownership is obvious when work stalls.
“Operations and product needed a system that would still make sense after the original project team moved on.”
“Guidewire makes core insurance software for policy, billing, and claims used by property and casualty carriers.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Banking operations stays visible to adjacent teams through BillingCenter |
| Capability | Operations and product work from the same BillingCenter record for core processing |
| Capability | Core processing can be reviewed without waiting on a personal export |
Story
Inside Fiserv, banking operations used to depend on whoever still had the latest file. That pattern is common in financials groups working out of the United States. Operations and product needed a system that would still make sense after the original project team moved on.
Fiserv uses BillingCenter from Guidewire as the working layer for core processing. Guidewire makes core insurance software for policy, billing, and claims used by property and casualty carriers. The practical change is simple: banking operations has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Fiserv gets from Guidewire is a durable place to run banking operations and a way for operations and product to see the same core processing at the same time.
