In June, the General Insurance Code Governance Committee published this short review of how 20 Australian insurers disclose the cost of payment options at renewal. The headline finding is easy to summarize. Twelve of the twenty charge customers more for paying by installments, on the order of seven to eleven percent across the sample, and of those twelve, six were not clearly explaining the difference at the point the customer renews. They made a graphic even - but probably wasn't necessary:
The report has been read, fairly, as a transparency story. The Code requires insurers to be honest, efficient, fair, transparent and timely with customers, and six of them are falling short of that standard at one of the most consequential moments in the customer relationship. The GICGC has said it will follow up, that two of the six have refused to change, and that further action is on the table if they hold that line.
All of that is true and all of it matters. But if you have run insurance operations for any length of time, the report is also telling a quieter and more interesting story about why this keeps happening. The transparency problem is the symptom. The cause is sitting one layer down, in the systems that produce the renewal notice in the first place.
What the good examples actually have in common
The GICGC praises a very specific kind of disclosure. The cleanest example in the report reads roughly like this: if you pay monthly the total cost will be X, paying annually would cost Y, and you would save Z by paying annually. Three numbers, side by side, on the renewal notice itself, in dollars rather than vague language. The report is clear that supporting documents are fine for background, but the comparison needs to live on the renewal notice itself, close to the payment information, in a form the customer can read without doing any work.
That sounds like a copywriting exercise. It is not. To put those three numbers on a renewal notice you need the system that produces the renewal notice to know all three of them at the moment of generation. You need the annual premium, the instalment premium, the difference, and the underlying logic that explains why they differ, all available to the document template at the same time, for the right product, for the right customer, on the right date.
For some insurers that is straightforward. For others, it is genuinely hard, and the report tells you which is which without quite saying so.
The pattern the report describes, without naming it
Look at how the GICGC describes the six insurers that failed the test. One relies on disclosing instalment fees across multiple documents, with the key information split across schedules, inserts and webpages. Another uses general messaging that paying annually "may be cheaper" and directs customers to a Premium, Excess and Discount Guide to find the actual numbers. Across the six, the renewal communications focus on the customer's existing payment type and do not provide a clear comparison with the other options available, and in every case the information given to renewing customers was less clear than the information available to new customers.
That last detail is the giveaway. The information is clearer for new customers than for renewing ones. New business and renewals are almost always run through different paths in legacy insurance environments, often through different systems entirely, sometimes through different teams who have evolved their own templates over years. New business systems have to support quoting and comparison because that is the whole point of the journey. Renewal systems were often built to do one job, regenerate last year's policy with this year's price, and have never had the comparison logic added back in.
Splitting key pricing across schedules, inserts and webpages is not a strategy somebody chose. It is what happens when the renewal notice generator does not have access to the instalment calculation, so a human writer references the document where the calculation does live, and over time the references multiply because nobody owns the consolidation. It is the architectural equivalent of saying "see attached," repeatedly, because the actual numbers are somewhere else in the building.
Why this matters more than the transparency point itself
The disclosure question is settled. The GICGC has drawn a line, the better insurers are already on the correct side of it, and the four insurers who have agreed to change will rewrite their templates and move on. That part will sort itself out within the next renewal cycle for most of the industry.
The structural point is the one worth sitting with. If your renewal notice cannot show a clear total cost comparison without linking out, the limitation is almost never the template. The template is the surface. Underneath it is a question about whether your policy, billing and document systems are operating from a single source of pricing truth, or whether they are stitched together with integrations that have to be coaxed into agreeing every time you change a product. The same architecture that makes a clean renewal notice difficult tends to make a lot of other things difficult too. Launching a new product variant. Changing instalment terms. Responding to a regulator who wants to see how a specific customer's premium was calculated on a specific date. None of those are template problems either.
There is also a practical risk worth naming. The GICGC has said it will keep monitoring, and that it will consider further action against insurers who refuse to change. If your fix for this round is a template rewrite that papers over the underlying gap, you are likely to keep getting pulled up, because the regulator is now looking at exactly this kind of disclosure and the disclosure quality is downstream of how easily your systems can produce the right numbers in one place. A template can hide an architectural problem for one renewal cycle. It rarely hides it for two.
What to actually do about it
The honest version of the action list is not "update your renewal notices," because four of the six in the report are already doing that. The harder version is this. Look at how a renewal notice gets generated in your business. Trace where the annual premium comes from, where the instalment premium comes from, where the explanation of the difference comes from, and how many systems they have to pass through before they land on the same page. If that map has more than two boxes on it, you have a system-of-record problem dressed up as a disclosure problem, and the GICGC has just given you the cover to fix it.