Almost every carrier technology conversation eventually gets to the same question: doesn’t our policy administration system (PAS) already do claims? It’s a fair question because most PAS do include claims functionality. They can open a claim, hold the policy record, track basic activity, and support payment records or trigger the next step in the process.
The problem is that touching claims and managing the full claims journey aren’t the same thing, especially in life insurance, annuities and long-term care.
A PAS is one of the most important systems inside a carrier as the system of record, managing the operational backbone of the business. However, claims aren’t just records. They’re the moment when the promise of the policy becomes real, the moment when the carrier’s internal complexity becomes visible to the person on the other side of the transaction.
A beneficiary, policyholder or family member doesn’t care which system holds the policy record or which department owns a certain step. They care about what happens next, what’s missing, why they haven’t heard back yet, when a decision will be made, and when the benefit will be paid.
That’s where the gap usually shows up. Most systems can help a carrier receive a claim and record a payment. The harder part is everything in between where claims professionals spend their day. That could be document collection, beneficiary verification, eligibility review, medical or provider coordination, state-specific requirements, interest calculations, correspondence, payment approvals, tax questions, audit documentation, exception handling, claimant communication, or any number of things. Each one of those steps has rules around it and can create delays. Those steps can also introduce risk if they live in a spreadsheet, an inbox, a sticky note or someone’s memory.
I’ve sat with claims professionals with multiple monitors open and more applications than anyone should have to manage just to process one file. Policy administration, correspondence, document, payment, reporting systems and more, all separated and open in a multitude of windows across monitors. Claims work is complex and typically grows around systems built for different primary jobs.
This is where leaders can misunderstand the problem. From a distance, the process may look functional. Claims are opened and payments made, but the day-to-day experience of examiners tells a different story. The work may be getting done because good people are compensating for the gaps, not because the process is actually designed well. Claims teams are fantastic at finding a way to get the right claim paid to the right person. Claims professionals want to pay claims and protect families. They ultimately want to make the right decision in a thorough, fair and compliant way.
The friction often comes from the fact that we have made them carry too much of the process manually. That creates a problem for the claimant, but it also creates a problem for the carrier. Manual work affects cycle time. Cycle time affects interest obligations, customer experience and staffing pressure. Manual calculations create room for error. Undocumented decisions create audit risk. Tribal knowledge becomes dangerous when experienced examiners retire or move on. And when a claimant has to call for basic status updates, that’s not just a service issue. It’s a signal that the process is not giving people visibility when they need it most.
This is why I think carriers need to separate two questions that often get treated as one. The first question is, can our policy administration system (PAS) do claims? The second question is, can our current claims environment manage the actual work our claims team handles every day?
Those are different questions. It makes sense for a carrier to store its policy record in its PAS. A carrier may also decide that claims need a system of work around the record. It’s not a knock on the PAS. It’s simply an acknowledgment that policy administration and claims operations have different jobs.
The PAS should be trusted for what it was built to do. But claims teams need a place where the work can be orchestrated from submission through payout, where rules are visible, calculations are consistent, correspondence is triggered at the right time, documents are tracked, claimants can see what is happening, and leaders can spot bottlenecks before they turn into backlogs.
That kind of architecture isn’t about adding technology for the sake of technology. It’s about reducing friction for the people already doing the work. It’s about designing around the reality of the claim, not just the data attached to the policy.
One of the simplest exercises I recommend to executives is this: go through your own claims process. Put a policy in place with a small internal team that knows what you are doing, and then file the claim. As you fill out the forms and wait for the correspondence, you’ll see how many times you’re asked to re-fill information the company already has and where the process slows down. Most leaders who do that will see something they want to change.
Change isn’t needed because the team did something wrong. It generally becomes clear just how much the team is holding together. They will see where a PAS is doing its job and where the claims operation has outgrown the tools around it. They will see that the real question was never whether the PAS “does claims.” The real question is whether the claims process is designed well enough for the people depending on it. And that claim process flowing smoothly is vital; it’s the reason the policy exists in the first place.
