Ten years of systems for a Puerto Rico health insurer.

01Context

A health insurer runs on a handful of processes that have to be right every month: claims come in from providers and get paid in phases, brokers earn commissions on the policies they place, Medicare Advantage members enroll and disenroll on federal timelines, and at year end the tax forms and check runs have to reconcile to the cent.

The group's finance stack is SAP. Each of those processes needed its own system of record, one that fits how the business actually works, keeps the ledger in step, and produces the reports its regulators expect. Buying five packaged products would have meant five vendors and five integrations. Building them in-house needed an engineer the group could keep for years, not a project team that leaves.

Bermudez Systems has been that engineer since 2016. This page is what we can say about the work without naming the client or showing its screens.

02Constraints

• Confidentiality. Member, provider, and financial data never leaves the company's systems. Everything is built and run on company infrastructure, onshore, under US jurisdiction.
• SAP is the ledger. Nothing the operational systems do is final until it agrees with SAP. Integration is not a feature, it is the acceptance test.
• Month end and year end. The systems have real deadlines: commission runs, enrollment files, tax forms. A late fix is a missed filing.
• Four divisions, one bridge. Several corporate divisions needed the same SAP connectivity. Solving it once was the only sane option.
• One engineer. The work is done by a single accountable person. That is a strength for continuity and a constraint on scope: every system has to be simple enough to maintain alone.

03Decisions

1. 01

   One SAP bridge, not five integrations

   An SAP NCo service layer sits between the operational systems and the ERP and serves four corporate divisions. Each new system talks to the bridge, not to SAP, so a change on the SAP side is absorbed in one place.

2. 02

   Payments tracked in phases, not as a single status

   The claims and invoice system models every payment as a sequence of phases with its own reporting. Finance can answer "where is this payment" from the system instead of from a spreadsheet reconciliation.

3. 03

   Pipelines and reports in the tools finance already trusts

   Commission processing and Medicare Advantage enrollment run as SSIS pipelines with SSRS reporting on top, so the outputs land in a format auditors and regulators already accept.

4. 04

   One stack across all five systems

   Angular front ends over .NET services on SQL Server, everywhere. Each system after the first was cheaper to build and, more importantly, cheaper to keep. There is nothing exotic for the next engineer to learn.

5. 05

   One system at a time, each to production before the next

   No big-bang program. Every system was scoped, built, and put into production on its own before the next one started. The group always had working software, never a half-finished platform.

04Architecture

The shape is deliberately plain. Five operational systems share one database platform and one integration path into SAP. Regulatory outputs come off the same data through SSIS and SSRS.

05Outcome

All five systems are in production in 2026. The oldest has been running for a decade. The group has had the same engineer for the whole period, so no system has ever been handed to a team that had to relearn it.

What we cannot show: the screens, the volumes, and the client's name. If you are evaluating us for similar work in a regulated business, we can walk you through the architecture in more detail on a call, under NDA.