BillingCenter Configuration Developer
Most RequestedBuilds account, policy and producer screens, entity extensions, typelists and validation across the billing lifecycle.
- Gosu
- PCF
- Studio
- Billing data model
Hire configuration, billing plan, delinquency, commissions and integration specialists for Guidewire BillingCenter — on-premise or Guidewire Cloud. Every profile we send has worked a live billing programme, so the conversation starts at invoice streams and payment allocation rather than at Gosu syntax.
For insurers, MGAs and Guidewire delivery partners. Contract, contract-to-hire and dedicated pods.
BillingCenter is the smallest of the three core modules and the least commonly staffed, so the pool is genuinely thin. It is also the one where a configuration mistake shows up as money in the wrong place — a misallocated payment, a delinquency that fires early, a commission paid twice.
We screen on the ledger, not the UI. How were invoice streams structured for direct versus agency bill? What drove the payment allocation order? How was delinquency configured, and what happened on reinstatement? How were commissions calculated and reconciled with producer statements? What did the finance team have to correct manually after go-live?
All Guidewire TalentMix and match into a squad, or add one specialist to a team you already have.
Builds account, policy and producer screens, entity extensions, typelists and validation across the billing lifecycle.
Owns billing plans, payment plans, invoice streams, instalment schedules and direct versus agency bill behaviour.
Payment allocation, suspense, reversals, write-offs, charge holds, delinquency processes and reinstatement.
Commission plans, producer statements, payables, holdbacks and the reconciliation finance actually signs off.
Payment gateways, bank files and lockbox, general ledger and finance systems, plus the PolicyCenter handoff.
Sets configuration standards, reviews ledger-affecting change, sizes work and keeps the build upgrade-safe.
Translates billing, credit control and producer compensation policy into requirements a developer can configure.
Version upgrades and moves to Guidewire Cloud — configuration remediation, retrofit and financial regression.
Requirements get mapped against this grid before we send anyone, so you can see depth by area instead of reading it out of a CV.
Named specialists for a defined period — a release, a delinquency rework, a reconciliation clean-up.
DetailsWork together first, convert to permanent once the fit is proven on your codebase.
DetailsA standing pod — developers, BA, QA, lead — that stays with your billing roadmap.
DetailsA scoped outcome — new billing implementation, upgrade wave, payments or GL workstream.
DetailsFour steps, and you hear from us at each one.
Version, on-prem or cloud, direct or agency bill in scope, and whether the work sits in billing, payments, commissions or integration.
A Guidewire-experienced reviewer probes ledger decisions: allocation order, delinquency design, reconciliation defects owned.
Profiles arrive with a written view on depth by area, notice period, rate and known gaps.
We coordinate panels, handle paperwork and stay involved through the first weeks on your codebase.
Representative profile structures for the three most common briefs.
Personal lines billing · on-premise and cloud
Commercial lines · remediation and clean-up work
Guidewire Cloud · payments and finance estate
These are representative profile structures, not live availability. Current availability, notice periods and rates are shared against a specific requirement.
The pool is smaller than PolicyCenter or ClaimCenter, and we say so on the intake call rather than after three weeks of silence. Where dedicated BillingCenter depth is genuinely scarce for a niche requirement, we will tell you what a realistic near match looks like — usually a strong InsuranceSuite configuration developer with billing exposure and an accounting instinct — and let you decide.
Yes, and it is the more common ask. See PolicyCenter, ClaimCenter and integration talent.
Yes. For payments, delinquency and commissions roles we probe how the engineer worked with finance and credit control, and whether they can trace a discrepancy from a producer statement back to the configuration that caused it.
It does, and we screen for it. Cloud programmes constrain what can be customised, so engineers used to unrestricted on-premise customisation need evidence of working inside cloud guardrails. We flag this on the shortlist rather than letting it surface in interview.
Yes — a single specialist is a common starting point. If the scope grows, the same engagement can extend into a dedicated team without re-contracting from scratch.
A JD if you have one. If not: Guidewire version, cloud or on-prem, direct or agency bill in scope, which area the work sits in, seniority, engagement type and location expectations.
Send a JD or a two-line outline. We come back with the roles that fit, what the market looks like for them, and a shortlist against your requirement.
Two minutes now, a shortlist conversation next.