| This article is part of our series on Custom Insurance Agency Management System Development for US Independent Agencies and Brokers: Building a Policy, Commission, and Carrier-Download Platform |
Introduction: One Core, Then a Layer That Depends on What You Sell
A personal lines agency, a commercial agency, and a benefits practice share a core, then diverge sharply. That is why a list of agency management system features sold to all three usually fits none of them well.
The shared core is substantial. It spans the client and policy book with coverage history, renewals, activity records, documents, and commission tracking. Treat that core as the baseline for any custom software development in this category. Many agencies also plan client and producer portal development on top of that, for the self-service clients now expect. That self-service layer is core web application development work.
The divergence shows up in service work, placement, the calendar, and accounting. This article covers the core, marks where the lines separate, and closes with first-release scope. That scoping matters more than usual here because the underlying connectivity work is the expensive part. These features are the product layer of the full custom agency management system development guide.
The Data Model: Clients, Policies, and Coverage History
Four structures make up the data model, and each earns its place.
Clients as Structures, Not Records
A commercial account may combine several related entities that share ownership and operate multiple locations. A household holds drivers, vehicles, properties, and the relationships among them. A benefits client is an employer with an employee population and a plan year. Model the structure itself, because reporting, renewals, and certificates all depend on it.
Policies With Versioned Coverage
Each policy carries lines, limits, deductibles, forms, endorsements, dates, premium, the writing carrier, and the billing arrangement. Hold all of it as version history, not current state. Endorsements change coverage mid-term; renewals change it annually. The agency must reconstruct what was in force on a given date. That is the question a disputed claim asks, and a system that overwrites cannot answer it.
The Activity Record
Log every conversation, submission, quote, recommendation, declination, and confirmation against the account. Give each entry a date and an author. Allow corrections by addition, never by overwrite. This is the single most valuable output the system produces, for reasons covered later.
Assignment and Servicing
Track producer and account manager assignment and the servicing team on every account. Make a producer’s entire book visible in a single view. That view drives compensation, workload balancing, and eventually agency valuation.
Renewals, Marketing, and Remarketing
The renewal engine is where agency management system features either compound the book or leak it. A pipeline visible weeks ahead comes first, driven by configurable lead times that differ by line and account size. A large commercial account and a personal auto policy do not start at the same point.
The renewal workflow should automatically surface accounts approaching review, quoting, and binding milestones. Each account needs an owner, so nothing sits unassigned.
Remarketing needs its own workflow. Record which carriers were approached, what was submitted, what came back, and why an option was dropped. Recording that as the remarketing happens is native work, which is custom iOS app development and custom Android app development scope. That record serves service, retention analysis, and documentation at once.
Presentation tracking completes the loop. Capture what options were put to the client, what they selected, and what they declined. Capturing that at the meeting rather than afterward is native work, which puts it in custom iOS app development and custom Android app development scope.
Retention reporting belongs here too, cut by producer, line, carrier, and account size. Losing accounts at renewal is the most expensive failure mode in the business. It is usually concentrated somewhere identifiable.
Finally, handle cancellations and non-renewals with reason codes. Carrier-initiated non-renewals need remarketing on a compressed timeline, and the system should flag them loudly.
Service: Certificates, Endorsements, and Claims
Certificate issuance is the highest-volume repetitive task in most commercial agencies. That makes it the clearest automation win on the feature list.
Effective certificate-issuance software rests on three pillars. Holder records should persist, so repeat certificates are never rebuilt. Templates should draw on live policy data. And any additional insured or waiver of subrogation requests must align with what the policy actually provides.
Keep certificate history as a record: what was issued, to whom, when, and against which policy version. Renewal-driven reissue matters just as much. Holders should receive updated certificates without anyone needing to remember the list.
Endorsements and change requests need to be tracked from client request through carrier submission to confirmed issuance. Keep the unconfirmed state visible, because that gap is where exposure sits.
Claims intake often makes the agency first notice of loss. The system should report it to the carrier and keep status visible to the servicing team. First notice of loss usually reaches the agency from a job site or a roadside, which is where custom mobile app development earns its place.
One budget note: the standard ACORD forms this work relies on are licensed intellectual property. Price the license into the project rather than assuming the forms are free.
The connectivity behind this work is covered in ACORD Form Handling, IVANS Carrier Downloads, Real-Time Rating APIs, Commission Reconciliation and E-Signature Integration.
Accounting, Commission, and Producer Compensation
Commission tracking is where agency management system features turn into recovered revenue. Money leaks quietly here, and the right features surface the leak.
Handle agency bill and direct bill as the different processes they are. Under agency bill, the agency invoices, collects, and remits net to the carrier. Collected premium is fiduciary money under many state requirements. Under direct bill, the carrier bills the insured and pays commission afterward.
Hold expected commission at policy level. The agency should know what it is owed before any statement arrives, rather than accepting whatever appears.
Ingest commission statements in whatever form each carrier provides. Match automatically where possible, then route everything else to two exception queues. The first holds commission received but unmatched. The second holds commission expected but never received. That second queue is where agencies discover money they had silently written off.
Track contingent and profit-sharing income separately, with the volume and loss data the calculation depends on.
Producer compensation should be based on the same reconciled data, never on a parallel spreadsheet. Splits typically differ between new and renewal business and by line.
Round it out with standard reporting: book by carrier, line, and producer, premium and revenue trends, retention, and receivables.
Licensing, Compliance, and Security Features
Several features in this layer are required controls rather than preferences.
Track producer licenses and carrier appointments by state and line of authority. Show expirations and continuing education status at a glance. Then enforce the control where it matters: at the point of binding. Business placed by an unlicensed or unappointed producer is a problem the system should have prevented. Track agency entity licenses alongside individual ones.
Surplus lines support belongs in the same layer. The system should identify non-admitted placements, capture diligent search documentation, and track filing deadlines.
Access control should run by role and by book, so staff sees the accounts they service. Log access as well as changes.
A growing number of states require formal information security programs. Third-party oversight and incident response are architecture decisions, not policy documents. Add document retention rules by record type and state.
The obligations behind these features are set out in State Producer Licensing and NIPR Records, Surplus Lines Filings, GLBA, and the NAIC Insurance Data Security Model Law.
Where Property & Casualty and Benefits Diverge
Property and casualty work runs on certificate volume, coverage-level policy detail, endorsement tracking, and claims intake. Its year is shaped by expiration dates spread across the calendar. Renewals arrive continuously rather than in a season.
Employee benefits runs differently, and benefits agency management software has to reflect it. Plan years and open enrollment concentrate the work into predictable peaks.
The client is an employer with an employee population, so the data model needs census and eligibility structure. Commission is often calculated per employee per month rather than as a percentage of premium. That is a different calculation engine entirely. And much of the servicing happens on enrollment platforms the agency connects to, not on ones it owns.
Personal lines sits closer to property and casualty. It carries higher account volume, lower revenue per account, and heavier reliance on comparative quoting.
An agency running two or three of these needs one core and genuinely separate layers. Make that a deliberate scoping decision, not a discovery.
Conclusion
Build the requirements list in two parts: the shared core, then the layer your actual mix demands. That structure produces a specification you can evaluate honestly, feature by feature.
Then check the carrier connectivity question before falling in love with the list. It decides whether any of this is buildable in the form you imagine.
If you are defining requirements for an agency system, NewAgeSysIT, an AI software development company, approaches it in exactly that order. Separate the universal core from the property, casualty, or benefits layer your agency actually runs. Confirm connectivity first. That turns a feature list into a scope you can cost.
FAQ
What features should a modern insurance agency management system include?
A modern AMS should manage clients, policies, coverage history, renewals, activities, documents, certificates, endorsements, claims, commissions, producer assignments, licensing, and reporting. Agencies may also need carrier downloads, accounting workflows, client portals, producer portals, and automation. The final feature set should reflect the agency’s actual mix of personal lines, commercial P&C, and employee benefits business.
How should an AMS structure client and policy data?
The system should model relationships rather than treating every customer as one flat contact record. Commercial accounts may contain related entities and locations. Personal lines accounts can include households, drivers, vehicles, and properties. Benefits accounts center on employers, plans, and employee populations. Policies should retain coverage details, endorsements, premiums, dates, carriers, and billing arrangements as historical versions.
Why should an agency management system preserve policy history?
Insurance policies change through endorsements, renewals, cancellations, reinstatements, and other transactions. Preserving historical versions helps the agency determine what information and coverage were recorded at a particular date. Overwriting the current policy record can remove important context. Historical policy data also supports service investigations, certificate records, commission reconciliation, reporting, and documentation when disputes arise.
What renewal management features should an insurance AMS have?
Renewal management should identify upcoming expirations early, assign responsibility, track review and quoting milestones, and support different lead times by account type. Remarketing workflows should record carriers approached, submissions, quotes, declined options, and client decisions. The system should also track cancellations and non-renewals so accounts requiring urgent remarketing can be surfaced before coverage expires.
What certificate of insurance features should an AMS include?
Certificate workflows can maintain certificate holders, populate forms from current policy information, preserve issuance history, and support renewal reissuance. Additional insured or waiver requests should be checked against actual policy terms rather than assumed from the certificate request. ACORD explains that a certificate does not itself amend, extend, or alter the insurance policy’s coverage.
Why are carrier downloads important in an agency management system?
Carrier download reduces manual entry by bringing policy, claims, documents, and other supported carrier information into the agency system. IVANS Download connects agencies with participating carrier and MGA partners and supports multiple types of downloaded insurance data. Commercial, personal, claims, eDocs, and direct bill commission capabilities vary by carrier and line of business.
How should an AMS handle endorsements and claims?
Endorsement workflows should track the request from initial client instruction through submission and confirmed carrier issuance. Unconfirmed changes should remain visible instead of appearing complete prematurely. Claims workflows can capture first notice of loss, carrier reporting, documents, contacts, and status. Mobile access can be valuable for claims originating from job sites, vehicles, or other locations outside the office.
How should commission reconciliation work in an insurance AMS?
The system should store expected commission information at the policy level and compare it with downloaded or imported carrier statements. Matched transactions can be reconciled automatically. Unmatched payments and expected commissions that have not arrived should move into exception queues for review. IVANS supports Direct Bill Commission Statement download specifically to help agencies automate commission reconciliation and improve data accuracy.
