Reconciling a business partner
Receipts posted in 20 minutes, without blocking the operation
Business partners in production, each with its own file format
2008
HDI writes the core procedure of its receipt lookup. Its collections operation will grow on top of it.
2009–2016
Different HDI developers sign off more than 30 changes on the same foundation.
2016
HDI's developers add indexes so the system can handle the growing volume.
2024
In February 2024, HDI entrusts us with modernizing its collections, with a replacement under development that had not yet gone into operation.
THE MISSION.
Nearshore software development for your operation
Income clean-up
IncomeReceipt lookup
ReportsBusiness partner application
IncomePayroll deduction and direct debit
IncomeUNDERSTAND FIRST.
01
Starting point
We started with a technical inventory of the repositories and the database of the system we received.
02
Diagnosis
We rebuilt the business logic module by module, from the code and in sessions with HDI's teams, including modules that were not visible in the system.
03
Execution
We cut the scope down to a working minimum and put it into operation, to measure progress with running software.
With that knowledge we proposed rebuilding the system. The most complex modules, business partners and payroll deduction, needed a new foundation.
USE WHAT ALREADY EXISTS.
+1,000
Lines of SQL assembled at the moment it ran
The filter was serialized to XML, travelled to the server, was taken apart there and concatenated into text variables. Impossible to index, because the query did not exist until it ran.
HDI had solved that problem in 2008, in the stored procedure its developers had spent fifteen years tuning.
We didn't build a faster query. We stopped reinventing the one that already existed.
BACK TO THE FOUNDATION.
~50
Analysts and coordinators using it every day
12 MONTHS
Of rebuilding to take the complex modules to production
+10,000
Agents with access to the portal
In June 2025 we began the rebuild with two advantages: the infrastructure already deployed and the domain knowledge from the months of stabilization.
2025
We rebuilt from the ground up
Business partners and payroll deduction, the most complex modules, now run in production.
First we built a base template: data access, email, notifications and errors with traceability. Then the modules, starting with the ones carrying the least business logic.
Insurance software development
OPERATIONAL IMPACT.
The analyst received the client's file and checked it receipt by receipt, adding up by hand. In user testing, one analyst spent two hours on a single partner. Today the analyst uploads the file and the system checks it in seconds, with the discrepancies flagged and the totals calculated.
Posting more than 50,000 receipts took over an hour and locked the table: the rest of the operation waited. Today it takes 10 to 20 minutes, without stopping the rest of the operation.
The agent would call or email a photo of the payment slip, and follow-up depended on email; resolving it took anywhere from a few hours to two days. Today the agent files the request from the portal with the slip attached and it is resolved the same day.
More than 20 business partners configured in production, each with its own file structure. A portal open to a roster of more than 10,000 agents. Around 50 analysts and coordinators working inside the system every day.
OPERATIONAL DISCIPLINE.
2D → MIN
To rebuild the test environment
+300
Versioned procedures, each with its execution plan
We wrote down HDI's database standard and codified it. We built a tool that checks every delivery against that standard before it is released.
OPERATIONAL AUTONOMY.
The new collections system is now run by the HDI team. We stabilized it, rebuilt it and handed it over for their people to keep running.
Let's talk — 30 minutes
