Acceptance & premium Value accumulation & payout Traceable calculation

Custom policy administration software development

Appfront builds custom policy administration for insurers: acceptance, policy issuance, premium collection, value accumulation, changes during the term, surrender and payout. For organisations with a portfolio that runs for decades, where every calculation must still be explainable years later to a customer, an accountant or a regulator.

What is policy administration software?

Policy administration software is the insurer's own system: it keeps track of which policies are in force, what has been agreed, what premium is coming in, how the value develops and what needs to be paid out when an event occurs. It differs from an intermediary's software, which manages the customer relationship and the portfolio across multiple insurers. For that side, we have a separate page on insurance broker software.

What makes this category special is its lifespan. A life insurance or pension product taken out today may run for forty years. Over that period, rates, regulations, mortality tables and calculation interest rates change several times, while a policy taken out in 2004 must still be handled under the terms of 2004.

That means the core question is not whether the system can calculate, but whether it can still explain, twenty years from now, how it calculated at the time. Everything on this page comes down to that. See also our broader approach to building custom software.

The policy holds on to its own rules

Terms, rates and calculation rules are version-bound and attached to the policy, not to the system. A change made today therefore does not alter what was agreed in 2004.

Every calculation traceable

For every valuation, premium determination and payout, we record which rules, rates and bases were used. A question from a customer or an accountant then becomes a lookup instead of a reconstruction.

Changes as events

Making a policy paid-up, surrender, divorce, value transfer and death are not fields you overwrite but dated events. The policy can therefore be read back as it stood at any point in the past.

How we build your policy administration software

We start with your product terms and your existing portfolio, not with a feature list. Actuarial, administration, compliance and IT are at the table early on, because the first sets the calculation rules and the second brings the exceptions.

1
Discovery and scope

We map your products, variants and historical terms, including the ranges that are no longer sold but are still in the portfolio. It is precisely these older variants that determine how flexible the model needs to be.

2
Design

We design the policy model with version control on terms and rates, the event model for changes, the calculation layer and the integrations with direct debit, accounting and reporting. Your actuary reviews the calculation rules before any code is written.

3
Build & integrate

We build in short iterations and run each iteration against your existing portfolio, so that differences from the current administration become visible. An unexplained difference is a blocker, not a rounding issue.

4
Go-live & migration

A controlled migration with a period in which old and new systems calculate in parallel and the results are compared per policy. After that, ongoing maintenance and further development as products or regulations change.

What policy administration software actually does

A provider of funeral insurance has a different process from a party offering income protection or retirement products. These are the functions we deliver most often.

Underwriting & policy issuance

Application, medical and financial underwriting according to your own guidelines, setting the premium and any loadings, and issuing the policy with the terms that apply at that moment, recorded with the policy itself.

Premium collection & arrears

Periodic direct debit, integration with payment files and follow-up on arrears, including the statutory and contractual steps involved. Ties in with our financial reconciliation.

Value build-up & costs

Build-up of the value per policy with the cost and risk components shown separately, so you can explain to a customer where their money is going and to your regulator how you calculate it.

Changes during the term

Making a policy paid-up, changing the beneficiary, divorce, value transfer and adjusting the sum insured, each recorded as an event with an effective date and a calculation that is retained.

Surrender & payout

Determining the surrender value or the payout on maturity or death, with checks on the required documents, the tax treatment and the deductions that go with it.

Reporting & accountability

Portfolio overviews, technical provisions and the data submissions you need for your annual accounts and regulatory reporting, built from the same policy data rather than from a separate administration.

Who we build policy administration software for

How demanding the challenge is varies greatly with the product's term and the size of the portfolio. These are the types of clients we build for most often.

Life insurers

Organisations with long-term contracts where value build-up, tax treatment and historical terms come together. For them, traceability over decades matters most, including for products that have not been sold for years.

Funeral and in-kind insurers

Providers with a large portfolio of small policies and a payout in services rather than cash. They need a model that can hold in-kind benefits and monetary values side by side.

Income protection and absence insurers

Organisations where the payout is periodic and depends on a changing situation of the insured. See also our broader software for the financial sector.

Administrators and managing agents

Organisations that run the administration for one or more risk carriers. For them, separation per client and watertight accountability per portfolio are the key requirements. See also our insurance app.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

We build with a modern, maintainable stack and integrate with the systems that handle your direct debit, accounting and customer communication.

If you also want to record the approval and periodic review of your products, take a look at our PARP file for product approval.

For claims handling, with insurer messages added to the file automatically, there is our claims file software with insurer messaging.

For policy renewals, including recalculation, customer communication and exceptions, there is our renewal software for policy administration.

Node.js / Python / .NET React / Vue front end PostgreSQL / SQL database Version-controlled calculation model Event-driven policy model SEPA direct debit files Accounting integration Document generation Integration with intermediaries Reporting and data submissions SSO via OAuth 2.0 / SAML Role-based authorisation Immutable audit logging Reproducible calculations Migration and comparison tooling CI/CD pipelines

Why choose Appfront for your policy administration software?

Appfront builds custom software and starts with your products and your existing portfolio. In policy administration, the difficulty is rarely new sales but the tail: the variants nobody sells any more, the exceptions that were once resolved by hand, and the question of how to carry them over correctly.

We build the policy so that it holds its own rules. Terms and rates are versioned and attached to the policy, so a change made today alters nothing about what was agreed at the time. That is the only way to still be able to explain, twenty years from now, how a payout was arrived at.

The calculation rules come from your actuarial team, not from us. We build the environment in which those rules become explicit, testable and executable, run them against your existing portfolio so that deviations become visible, and make sure every outcome retains the bases used.

Also take a look at our broader services: custom software development and AI automation for insurers. Questions about your situation? Get in touch.

  • Terms and rates versioned and tied to the policy
  • Changes recorded as events, not as overwritten fields
  • Every calculation retains the bases used
  • Historical product variants included in the model
  • Calculation rules from your actuarial team, explicitly documented
  • Migration with parallel comparison per policy
  • Separation per client when operating under delegated authority
  • Immutable logging for auditors and regulators
  • Clear documentation that your own team can manage
  • Ongoing maintenance when products or rules change

Security, privacy and accountability

A policy administration holds financial data and, for life and income insurance, often health data from the underwriting process as well. This is special category personal data subject to a strict regime. We separate this data from the rest of the file and set up authorisation so that a premium collection employee cannot access it.

Retention periods here are unusually long, because a policy runs for decades and the records may still be needed afterwards. For each data flow, we document what is retained, for how long and why, in line with the GDPR, and delete anything that falls outside that basis.

Technically, we build to the OWASP security standards, with encryption in transit and at rest, role-based access and immutable audit trails on calculations and changes. More about our approach: information security policy and CVD policy.

  • Health data kept separate and authorised separately
  • Retention periods defined per data flow
  • Immutable logging of calculations and changes
  • Reproducible outcome for each closed period
  • Portfolios kept separate between clients
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least privilege
  • Building to the OWASP standards

Frequently asked questions about policy administration software

Answers to the questions we get asked most often about custom policy administration.

It is the insurer's own system, which keeps track of which policies are in force, what has been agreed, what premium is coming in, how the value develops and what is paid out when an event occurs. It covers underwriting, policy issuance, collection, changes during the term, surrender and payout.

An insurance brokerage manages the client relationship and a portfolio across multiple insurers, with commission, renewals and claims handling at its core. Policy administration is the other side of the chain: the risk carrier's system, which runs the policy itself and calculates the liability. They integrate with each other but solve different problems.

Because a policy from 2004 must be handled under the terms of 2004, even if your rates, mortality tables and technical interest rate have changed several times since. That is why we link terms and rates to the policy by version rather than to the system, so that a change today does not alter the past.

Yes, and it is usually the hardest part of the project. We run the new model against your existing portfolio and compare the results policy by policy with your current administration. We investigate any differences before anything goes live; an unexplained difference is a blocker, not a matter to be tidied up at the end.

They shape the design. Almost every portfolio contains product lines that stopped being sold years ago but run on for decades, sometimes with exceptions that were once resolved by hand. We map these early, because a model that only fits your current products will still get stuck during migration.

Your actuarial team, not us. We build the environment in which those rules are defined explicitly and can be tested, run them against your historical data so that deviations become visible, and make sure every result retains the bases used. Actuarial responsibility stays with you.

We treat it as special category personal data with its own regime: kept separate from the rest of the file, with authorisation based on necessity and logging of every access. An employee working on premium collection then cannot see it, even if they otherwise have broad permissions.

We build custom. Product terms, calculation rules and the exceptions in a long-established portfolio are exactly where off-the-shelf packages break down, and that long tail determines whether a migration succeeds. After an intake conversation, we decide together which products to set up first and in which order to migrate.

Ready to build your policy administration software?

Tell us which products you offer and where your current administration hits its limits: with legacy variants, with changes, with reporting or with a migration that was postponed earlier. We are happy to think along with you on the policy model, versioning and the approach to your existing portfolio. In a no-obligation first conversation you will get a clear picture of the possibilities.

Edit content