Custom renewal software for policy administration
Appfront builds renewal software for insurers, managing agents and intermediaries: every policy that expires is in view on time, the new premium and terms are calculated per renewal, the customer is informed in good time, and the exceptions a person needs to see appear on a list before the expiry date. So the monthly renewal run no longer costs a weekend and no customer ends up with an unwanted renewal.
What is renewal software for policy administration?
Renewal means extending a policy on its contract expiry date: recalculating the premium based on current rates and the customer's details, updating the terms to the latest version, informing the customer in good time, and processing the new period in the administration and the collection. Renewal software does this per policy, every month, and puts everything that cannot be handled according to the rules on a list for a person to review: a claim in the past year, a changed risk, a premium increase above a threshold.
Without good software, the renewal run is a monthly operation with manual work: an export from the policy system, a spreadsheet with the new rates, letters merged by hand, and a check that not everyone passes. A customer receives a renewal with a wrong premium, or a cancellation deadline that was announced too late, and then the renewal can be challenged. With thousands of policies, a small percentage of errors becomes a large stream of complaints.
We build custom because the rules differ per product, per insurer and per authority, and because your policy system remains the source. The renewal software reads from it, calculates according to your rate rules, writes back and communicates in your house style. A policy system often has a renewal module for the standard case; the exceptions, the rate changes and the communication are where the manual work lies.
Flagging and planning
Every policy with an expiry date in view, a renewal run per month with the deadlines required by law and the policy terms, and a timeline per policy.
Recalculation and terms
Premium per policy from the current rates and customer details, terms updated to the latest version, with what has changed and why shown per policy.
Exceptions and communication
What falls outside the rules goes on a list for an underwriter, the customer is informed within the deadline, and the renewal is processed in the policy administration and direct debit.
How we build your renewal software for policy administration
We start with your last renewal run: what went automatically, what was done by hand, and where the complaints came from. The software follows from that.
Per product, the renewal rules, the premium rate sources, the deadlines towards the customer, and what the policy system already does. We look at the exceptions and complaints from the most recent runs.
Expiring policies from the policy system, the recalculation according to the rating rules, the policy terms version and the check for deviations.
Letters and emails in your house style within the deadline, the list for the underwriter with the reason per exception, and the handling with a decision.
The new period written back to the policy system and direct debit, reporting per run, and then ongoing maintenance and new products or rate changes.
What renewal software for policy administration actually does
The components below come up in almost every renewal. Which ones you need depends on your products and on what your policy system can already do.
Renewal calendar
All policies with their expiry date per month, with the steps and deadlines for each policy: calculation, communication, processing. Anything running behind is visible.
Rating rules
Premium calculation per product from rate tables and customer data, with versions per effective date, so that a rate change lands on the right policies.
Policy terms management
Per product, the policy terms version in force, with the transition at renewal and the text for the customer explaining what has changed.
Exceptions list
Policies that fall outside the rules, such as a claim, a premium increase above a threshold or a changed risk, go to an underwriter with the reason attached.
Customer communication
Letters and emails per policy in your house style, with the new premium, the changes and the option to cancel, sent within the statutory deadline.
Processing and reporting
The new period in the policy administration and direct debit, and a report per run: renewed, declined, cancelled, open.
Who we build renewal software for policy administration for
The software is intended for organisations where the monthly renewal is a major operation and where errors immediately lead to complaints or contestable renewals.
Managing general agents
Multiple insurers with their own rates and terms under one delegated authority. The rating rules per insurer and the reporting to the insurer are the core.
Insurers with niche products
Products the standard policy system doesn't handle well. The custom calculation and the exceptions matter most.
Large insurance brokerages
Renewal on behalf of customers across multiple insurers, with advice in the event of a premium increase. Flagging and customer communication are what is needed.
Insurers in transition
A policy system that is being replaced, while renewal has to keep running in the meantime. The software as a layer across two systems is the core.
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
This page is about renewing policies. For policy administration as a whole, see our page on policy administration software, and for the intermediary's office our page on insurance brokerage software. You can read about our approach on custom software development.
If you need to show, product by product, which target market it is intended for and when it was assessed, read more about our PARP file for product approval.
If you want customers to check their details before the policy is renewed, there is our app for renewal in policy administration.
For the file that demonstrates your duty of care in the event of a complaint or an investigation, there is our duty-of-care file software for insurance intermediaries.
Why Appfront for your policy administration renewal software?
Renewal is a process with deadlines and exceptions. The software handles the standard case and puts the exception in front of the right person, on time.
The deadline is the law
A renewal notice sent too late can be challenged. The calendar counts back from the expiry date and shows what needs to go out today.
Your pricing rules, version-controlled
A rate change per effective date, applied to exactly the policies that renew from then on. No spreadsheet with the new rates next to the old ones.
The underwriter only sees what deviates
A thousand policies renew automatically; the twenty with a claim or a large increase land on their list with the reason. That is where their time belongs.
Security and privacy in policy administration renewal software
Policy data contains personal and financial data, and for some products health data. Access is set up per role and every view and change is logged, so that in the event of a complaint or a regulator's enquiry it is clear who did what and when. Data is stored encrypted and no longer than the retention obligation requires.
The software runs in a European data centre, with encrypted storage and daily backups. Integrations with policy systems, direct debit and accounting use their own keys, which can be revoked per integration.
Frequently asked questions about policy administration renewal software
Questions that insurers and authorised agents ask before they get started.
It flags expiring policies, recalculates premiums and terms according to your pricing rules, informs the customer within the deadline, puts deviations on a list for an underwriter and processes the new period in the policy administration and direct debit. Each run produces a report of what has been renewed, rejected and left open.
No. The policy system remains the source of policies and customers; the renewal software reads from it, calculates, communicates and writes back. That also makes the software usable as a layer over two systems during a migration.
Rates have a version with an effective date. A change is applied to the policies that renew from that date, and the customer communication explains what has changed. The old version remains available for policies that were renewed earlier and for questions after the fact.
The ones you designate with rules: a claim in the past period, a premium increase above a certain percentage, a changed risk, an outstanding payment, a product that always goes manually. The underwriter sees the policy with the reason and decides; their decision is recorded in the log.
The calendar counts back from the expiry date per policy using the deadline required by law and the policy terms, and shows per day which communication needs to go out. Anything running behind is flagged. That way, a notice sent too late is a visible exception, not something you discover when a complaint comes in.
Yes. The new premium and period are passed to direct debit and accounting via the interface of your packages, and a cancellation or rejection is processed there too. We connect to what you use.
Often it does, for the standard case. Check that first. Custom software makes sense when the pricing rules of your products don't fit in the module, when the deviations and customer communication are currently manual work, or when you want to renew policies for multiple insurers or systems in a single run.
Your renewal run without weekend work and without complaints?
Tell us which policy system you use, how many policies renew per month and where the last runs got stuck. We'll show you what the calendar, the calculation and the deviations list look like.