Policy administration
The contract's system of record. Issue, endorse, renew, lapse and cancel, each change dated by when it took effect.
Most insurance software problems are not interface problems. They are modelling problems that surface years later, when a claim has to be judged against a policy as it stood on the loss date and nobody kept that version. We build the parts where getting the model wrong is expensive to undo.
Tell us what you are building
Insurance software development builds the policy, rating and claims systems an insurer, MGA, broker or TPA runs on. The decision that sizes the project is modelling: a policy record that can reproduce the cover in force on any past date, and a reserve ledger that keeps every movement rather than the current balance.
Our work
We have no insurer, MGA or TPA among our clients, and saying so is cheaper than you finding out on the second call. The adjacent work is below: deciding where a book of record lives, isolating several businesses on one codebase, and delivering inside Oman, whose Financial Services Authority licenses insurers, brokers, agents, reinsurers and health insurance third party administrators and runs Dhamani, per fsa.gov.om read 17 November 2026.
Systems
Nine system types, and they are separate products. A core purchase covers two or three of them, and assuming it covers the rest is the planning error we are most often asked to unpick.
The contract's system of record. Issue, endorse, renew, lapse and cancel, each change dated by when it took effect.
Prices the risk from product configuration and rating tables. A separate product, and usually a separate licence.
Submission intake, risk scoring, referral rules and authority limits, with each decision stored beside the rule version behind it.
Quote, document, payment and issue in one flow, with a degraded path for the moment a carrier API stops answering.
First notification of loss, or FNOL, through adjustment, payment and recovery. The reserve history is the part that is hard to add later.
Instalment schedules, dunning, grace and lapse, broker commission, and reconciliation against the cash that actually arrived.
Schedules, certificates and letters, generated from the record and retrievable later in the version that was issued.
Returns, actuarial extracts and the audit trail, taken from a reporting layer rather than the path serving customers.
Self service for people outside your building. The hard part is deciding what each audience may see and change.
Scope
Eight pieces of work beyond the list above. Most engagements are three or four. Not a fit if you want a core replaced end to end inside a quarter, or a partner to carry underwriting risk or file your returns.
An effective dated record, so the cover in force on a loss date is reproduced rather than reconstructed from documents.
Referral rules and authority limits held as data, with each decision stored next to the rule version that made it.
Instalments, dunning, grace and lapse, commission and bank reconciliation, so an unpaid premium cannot quietly stay in force.
A batch file route for policy and commission feeds, and a request and response route where a quote must come back inside a session. One mapping layer per carrier, not a fork.
Eligibility, pre-authorisation, submission and reconciliation as one flow, built against the published R4 release, v4.0.1, per hl7.org read 17 November 2026.
Generated from the policy and claims record rather than rebuilt monthly, with treaty layers and retentions as structured data.
The evidence pack your compliance function will be asked for, produced during the build rather than assembled afterwards.
The model
A claim is judged against the cover in force on the loss date, not today. Six consequences, every one cheap now and expensive later.
Answers what cover is in force now and nothing about any past date, which is the only question a claim asks.
A vehicle added on the twelfth and keyed on the twentieth was covered from the twelfth. Store both dates, resolve cover on the first.
A mid term change is a new version of the contract, not an edit to the old one. Overwriting is what makes history unrecoverable.
An occurrence wording asks one date question. A claims made wording asks two, because the retroactive date can sit earlier than the policy itself.
Quick to ship, impossible to replay, because the deployment that decided a claim two years ago is long gone. Hold rules as dated data.
The ledger
Overwriting a case reserve gives a correct current balance and no history. Loss development needs the history and cannot infer it from the balance.
A reserve change is a new row with its own date and reason. The current value is the latest entry, not a field you write over.
Loss development needs the reserve as it stood at each valuation date. Keep only the current figure and the triangle gets rebuilt in spreadsheets.
Separate movements on one claim. Netting them early loses the detail reporting and reinsurance ask for later.
Every movement carries an actor and an authority limit, because reserving history is something an audit asks about directly.
Building the ledger is bounded work. Recovering history that was overwritten is not, and is sometimes not possible.
By operation
What breaks decides what gets built. The detail behind each of these is in the integration guide linked under the systems table.
Cover can be owed to a third party even where the insured breached a condition, so a valid or declined flag cannot express it. Telematics adds a usage feed that prices and renews unattended.
The same clinical question gets answered differently by every payer portal, and the claim carries codes, authorisation and eligibility as it stood on the date of service.
A contract outlives several generations of the system administering it, and surrender and bonus arithmetic is often documented only in the code implementing it.
Risks are schedules, not single items. Workers' compensation rates on payroll and cyber on the records you hold, so the exposure basis changes per product.
The submission goes out as a spreadsheet and the quote comes back as a PDF. ACORD exists for exactly this and is usually implemented one way only.
Cessions get computed after the fact from a report, so the ceded position is a monthly estimate rather than a current figure.
Integration
Guidewire is a core insurance platform a carrier runs its business on: PolicyCenter for policy administration, BillingCenter for billing, ClaimCenter for claims. It is configured rather than programmed. The same is true of Duck Creek and Sapiens, which is why nearly all of this work is integration and extension rather than replacement.
| System family | What it is | The constraint that decides the plan |
|---|---|---|
| Enterprise property and casualty | Guidewire PolicyCenter, Duck Creek Policy, Insurity. What large carriers consolidate on. | Which extension points the vendor supports at your version, not at the current one. |
| Life, annuity and mid market | Sapiens, Majesco, FINEOS, Equisoft. Decades of product definitions held in one place. | Which product variants are still genuinely computable, rather than the shape of the API. |
| Cloud native, MGA and embedded | Socotra, EIS, Instec, BriteCore, INSTANDA, Origami Risk. Built for fast product launch. | They trade depth on reinsurance and complex products for speed, which holds until the programme grows into the part traded away. |
Policy administration, rating, billing and claims are four products, and buying one does not give you the other three. The extension points that matter are the ones your installed version exposes, not the ones on the vendor's current documentation page, and that gap is the most common mid build surprise. On the adjudication side, see how insurance claims automation actually works.
Compliance
Not a badge wall. These are the instruments that alter the data model, the retention policy or the delivery date, United States first because that is where most of this demand sits. Every row names the source we read and the day we read it, and the two rows where we read no primary source say so.
| Instrument | What it forces the software to do | When |
|---|---|---|
| NAIC Insurance Data Security Model Law (#668) | An information security programme, an investigation record for any cybersecurity event, and a notification path to the state insurance commissioner. In build terms an event record and a workflow, not a document. | State by state as adopted. The NAIC states 21 states have adopted the model to date, on content.naic.org read 17 November 2026. |
| NYDFS 23 NYCRR Part 500 | Cybersecurity requirements for DFS covered entities, which include New York licensed insurers and producers, so access control, logging and an incident path become build items. | DFS promulgated Part 500 on 1 March 2017, per dfs.ny.gov read 17 November 2026. We do not restate the amendment phase dates, which sit in a file that site serves as a download. |
| HIPAA, where health data is in scope | Decides whether claims, clinical detail and eligibility responses may sit in the same store as the rest of the book, and what the trail over them records. Settle the boundary before the schema is drawn. | Ongoing, wherever protected health information is processed. No date here: we read no primary source for it on 13 November 2026. |
| GLBA, for the financial side | Customer financial information drives retention, access control and what a processor may hold for you. A data classification exercise before it is a control. | Ongoing for United States licensed entities. No date, for the same reason as the row above. |
| IFRS 17 Insurance Contracts | Measurement and disclosure of insurance contracts, which decides what the policy and claims record has to reproduce for reporting long after the event. This lands in the extract layer, not the transaction path. | Effective for annual reporting periods beginning on or after 1 January 2023, per ifrs.org read 17 November 2026. |
| DORA, Regulation (EU) 2022/2554 | ICT risk management, incident reporting, resilience testing and third party risk for in scope financial entities, insurers and reinsurers included. Intermediaries that are microenterprises or small or medium sized enterprises are carved out by the text itself. | Article 64 states it shall apply from 17 January 2025. Done at Strasbourg on 14 December 2022. Read on eur-lex.europa.eu, 17 November 2026. |
| Directive (EU) 2025/2, amending Solvency II | Amends Directive 2009/138/EC on proportionality, supervision, reporting, long term guarantee measures, macro-prudential tools, sustainability risks and group supervision. The reporting changes are why a build page cares. | Article 4 requires Member States to adopt and publish by 29 January 2027 and apply from 30 January 2027. Read on eur-lex.europa.eu, 17 November 2026. |
| HL7 FHIR R4 | The exchange format a health claims interface is built against: eligibility, pre-authorisation, submission and the response that comes back. | The published R4 release is v4.0.1, per the title of hl7.org/fhir/R4 read 17 November 2026. |
On certifications the useful question is scope: whether policyholder and claims data sit inside a certified boundary at all. We hold none. ISO 27001 issues certificates and we have none. SOC 2 issues no certificate to anyone, being an AICPA attestation examination rather than a certification, and we have not been through one either. We build to the controls, keep card data out of the estate by tokenising at the gateway, and hand you the evidence for your audit. We are not an insurer and not a licensed intermediary, so you or your provider file the returns and we build the systems that produce them.
Transparency
The vendor page ranked top on this keyword when we read it on 14 November 2026 publishes no price, no effort figure and no duration, across 731,030 characters of HTML. Here are the hours, module by module, so you can argue with any line. Scope: a general insurer keeping its core and taking claims in house.
Phase one scope
1,420 hours
The worked example across seven modules.
Typical timeline
16 to 24 weeks
As a squad. A deadline inside the window compresses scope, not the calendar.
Useful hours
1,160 to 1,980
Every module at its minimum, through to every module at its maximum.
| Driver | Hours |
|---|---|
| Whether underwriting and billing are in scopeA workbench with referral rules and authority limits is its own module, and so is a billing cycle with dunning and lapse. Neither sits inside the seven below. | Scoped separately |
| Which core you keep, and what it really exposesVendor API surface at your version, not the version in the current documentation. The most common source of a mid build surprise. | 80 to 200 each |
| How many in force policies migrateValue equivalence testing scales with contract variety rather than policy count, so a small book of unusual contracts can take more than a large uniform one. | Rarely small |
| Module | Hours |
|---|---|
| Policy data model with versioning and effective dating | 200 to 320 |
| Product and rating configuration | 180 to 300 |
| Quote and bind flow | 140 to 240 |
| Claims intake, reserve ledger and adjudication | 220 to 380 |
| Document generation and the repository path | 100 to 180 |
| Integrations: core, payments, ACORD or FHIR | 180 to 320 |
| Reporting, regulatory extracts and audit trail | 140 to 240 |
Delivery
Five phases, each named by the artifact it produces rather than by a stage in a generic waterfall.
Phase 01
How the policy handles time, written down before anything is built on it. Later arguments resolve against this document.
Phase 02
Every integration point named, with its payload, direction, failure behaviour and mapping owner.
Phase 03
The core build, with rating configuration and effective dating present from the start rather than added over the top.
Phase 04
Value equivalence results per contract variety, the cutover sequence and a rollback position at each step.
Phase 05
The extracts, audit trails and control documentation your compliance function will be asked for.
Nine separate products: policy administration, a rating engine, an underwriting workbench, quote and bind, claims management and reserving, premium billing and collection, document generation, reporting and regulatory extracts, and portals for policyholders, brokers and providers. Most carriers run a core platform covering two or three and integrate the rest around it.
It is a carrier's core platform, split into PolicyCenter for policy administration, BillingCenter for billing and ClaimCenter for claims. You configure it rather than program it. So integrating starts by establishing which extension points your installed version exposes, because the vendor's documentation describes the current release and not necessarily yours.
Yes, and that is the usual shape of the work. These systems are configurable rather than programmable, so we integrate and extend rather than replace. What we establish first is which extension points your installed version exposes, because that decides the plan.
Two different integration shapes rather than two versions of one thing, and we design for them differently. AL3 is the batch file route, where policy and commission data moves from carrier to agency on a schedule. XML is the request and response route, for the case where a quote has to come back inside a session. A broker integration needing an answer in the session cannot be served by the batch route, and a nightly commission feed does not need the session route. Treat that as the architectural difference and not as a reading of the standard: ACORD publishes the specifications, and acord.org returned HTTP 403 to us on 17 November 2026, so nothing here is quoted from it.
Four, in build terms. The NAIC Insurance Data Security Model Law (#668) asks for an information security programme, an investigation record for any cybersecurity event and a notification path to the state insurance commissioner, and the NAIC states 21 states have adopted the model to date, on content.naic.org read 17 November 2026. NYDFS 23 NYCRR Part 500 covers New York licensed insurers and producers and was promulgated on 1 March 2017, per dfs.ny.gov read the same day. HIPAA decides where health data may sit and GLBA decides how customer financial information is classified and retained. IFRS 17 is the reporting standard, effective for annual reporting periods beginning on or after 1 January 2023, per ifrs.org read the same day.
The worked example above is 1,420 hours across seven modules, and those seven ranges sum to 1,160 hours at every minimum and 1,980 at every maximum. Sixteen to twenty four weeks as a squad. Every module shows its own range, so you can move any line and see the effect. A fixed price follows discovery, once the integration inventory exists.
Because everything on it is checkable without trusting us. Each instrument names the source and the day we read it, the hours are broken out module by module, and the three case studies say what transfers and what does not. Two compliance rows say outright that we read no primary source for them.
Four steps with a shape attached to each.
Bring how your policy record handles time, and one claim you had to defend. Those two answers size the project.
We establish whether your policy record can reproduce a past state, and what it costs you when it cannot.
Module by module against the ranges on this page, with anything excluded named as excluded.
You choose whether we build it, your team does, or your incumbent extends. The document is yours either way.
Bring your current policy record and one claim you had to defend. Thirty minutes on those two usually tells both of us whether this is a fit, and you leave with the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
The versioned policy store and the reserve ledger
Portals, agent consoles and quote flows
Rating, adjudication rules and extracts
Claim documents and submission packs
Reserving signals and fraud scoring
Adjudication queues and case routing
Payment rails under a premium
Property risk and the policy on it
Every sector we build for
Practical guides and analysis on the systems insurers run on, written by the team that builds them.