Quotes, policies, claims status, producer licensing and commissions flow between Salesforce and the core insurance platforms that underwrite and pay.
Insurance integration connects Salesforce to the core platforms that issue and service coverage: policy administration, rating and quoting engines, claims, billing and producer management. For carriers and MGAs, that often means submissions in Salesforce feeding underwriting workbenches, bound policies flowing back, and producer appointments and licensing data governing who can sell what. For agencies, it means linking the agency management system so producers see policies, renewals and carrier communications in one place. We decide where each insurance record is mastered, and design each flow so an auditor could trace a policy from quote to bind to claim.
Insurance cores are typically old, heavily customized and central to the regulated business, so integrations have to go around them gently rather than through them. Much of the data is hierarchical: a policy has terms, each term has coverages, locations and endorsements, and a renewal is a new term rather than an update. Relationships multiply as well, because carriers, wholesalers, agencies and individual producers all sit between the insurer and the policyholder. Producer licensing and appointment status determine whether a submission can even be accepted. And because rating and underwriting decisions can be examined by regulators, the data a Salesforce user saw when acting must be reconstructable later.
Commercial submissions captured in Salesforce, including applications, loss runs and schedules of values, are packaged and sent to the underwriting workbench or rating engine. Quote status, premium indications and referral reasons return to the opportunity, so distribution teams know which submissions are moving and which need broker follow-up. Documents are referenced rather than duplicated when the policy system already stores them.
Bound policies, terms, coverages and premium summaries flow from policy administration into Salesforce, typically as read-only records related to the insured and producer. Renewal dates drive tasks and campaigns in advance of expiration, and mid-term endorsements update the record as they are issued. Term history is preserved, so account teams can compare this renewal against prior years and explain premium movement to the broker with confidence.
Producer licenses, appointments and lines of authority from a producer management system or licensing database are synchronized to agency and producer records. Submissions from producers without an active appointment in the relevant state are flagged before underwriting sees them. Commission statements and production summaries flow in afterward, so distribution managers can review each agency's performance, appointment status and growth in one place.
Claim open dates, status and reserve bands from the claims platform are summarized on the policy and account in Salesforce. Producers and account managers see loss activity before renewal conversations, without receiving adjuster notes or sensitive claimant details. Large losses can trigger alerts to the relationship owner, who can then speak with the insured before the broker hears it elsewhere.
Insurance integration starts with a system-of-record map signed off by underwriting, distribution, claims and IT, because disagreements about ownership surface quickly once data starts moving. We then connect in value order: producer and agency data first, since it governs submissions; policy and renewal data next; then submissions outbound and claims summaries. Integration is built against copies of the core systems with realistic multi-term policies. Cutover plans include a fallback to existing intake methods, and core system change windows set the release calendar rather than the other way around.
Policies, terms, coverages, endorsements and premiums arrive as read-only records tied to insureds and producers, with renewal dates driving retention workflows in Salesforce.
Submissions and supporting documents go out for rating and review, and quote status, indications and referral reasons return to the distribution team's opportunity records.
Licenses, appointments, commission statements and, for agencies, policy and client lists synchronize so every submission is checked against current selling authority.
A renewal is a new policy term, not an edit to the old one. Model terms separately so prior coverages, premiums and endorsements stay intact, supporting retention analysis, broker conversations and any regulatory inquiry that asks what the insured bought in a specific period.
Selling or placing coverage without a valid license and appointment creates regulatory exposure. Use synchronized licensing data to validate submissions automatically, and decide with compliance how to handle expirations mid-pipeline, rather than leaving the check to an underwriter's memory or a manual lookup.
Claims files contain medical, financial and personal information about claimants who are not your customers. Bring only the status and summary figures distribution needs, protect nonpublic personal information under GLBA and state privacy rules, and leave adjuster notes in the claims system.
Client names are anonymized.
Yes, though the approach depends on what the core exposes. Newer platforms offer APIs; older ones may offer database views, message queues or batch files. We often place an API layer in front of the core so Salesforce never calls it directly, protecting the core from load and making a later policy system replacement far less disruptive.
Usually the portal submits to Salesforce first. That gives distribution a record of every submission, including declined or incomplete ones, and lets Salesforce validate producer authority and required documents before anything reaches underwriting. Salesforce then passes complete submissions on, and brokers see status in the portal as underwriting progresses. Incomplete submissions go back to the broker with a specific list of what is missing.
Commission calculation should stay in the system that pays it, often a commission or billing platform that finance audits. Salesforce receives statements and production summaries so distribution managers and producers see results. Keeping calculation out of Salesforce avoids two versions of a producer's earnings and disputes about which one is correct. Producers can still drill into statement lines from their Salesforce record when a question comes up.
Agencies usually integrate the agency management system for clients, policies and renewals, plus comparative rating tools and carrier download feeds. Salesforce then handles prospecting, cross-sell, service tracking and marketing, while the agency system remains the book of record for accounting and carrier communications, including direct-bill commission reconciliation. Carrier download feeds then keep policy data current without manual entry by account managers, which frees service staff for client conversations.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.