I want to switch loan systems, but I can’t risk loading a single balance wrong.
The migration happens loan by loan, with proof: every amortization schedule is read, every balance is reconciled against your current system’s report, and anything that doesn’t tie out is set aside before loading.
Done at a Mexican lender: amortization schedules that arrived as images were read and tied out to the cent, and the loans were left ready to load with balances matching the client’s report.
What it looks like from operations.
-
Amortization schedules don’t come in a loadable format.
They’re PDFs, images or spreadsheets built by hand over the years.
-
One balance loaded wrong is a portfolio reported wrong.
The error doesn’t show on load day: it shows at the next close, in collections or in the report.
-
Nobody wants to sign off on the load.
Because nobody checked loan by loan; they checked totals.
-
Migration stalls the operation.
While it’s underway, you collect on two systems and reconcile by hand.
What changes when migration comes with reconciliation?
Every loan goes in with proof. Amortization schedules are read one by one, even when they arrive as images or PDFs; dates, principal and interest are extracted, and every loan is tied out to the cent against your current system’s report. The ones that don’t match are set aside with their difference for a person to review. Only what matches gets loaded.
And the operation in the meantime?
Your current system stays the source until cut-over. Reading and reconciliation happen on the side, without touching it, and the load is scheduled for an agreed cut-off. After loading, the reconciliation runs again against the new system to confirm that what went in is what came out.
- The agent
- An agent that reads amortization schedules in any format, extracts their data, reconciles it against your current system’s report and prepares the load file for the new system. It doesn’t write to either system without authorization.
- The accountable person
- Your head of operations owns the migration, and your controller validates the reconciliation. For the first 4 weeks, the agent checks with a person on every decision and action. After that, anything high-stakes —every loan that doesn’t tie out, the authorization to load— always goes through a person; simple things it handles with what it learned, and every action is logged.
- The evidence
- For every loan: which document it came from, what data was read, which report it was reconciled against and with what result. It’s auditable: if someone asks about a migrated balance, the answer is that loan’s reconciliation.
- The stop button
- Nothing loads without reconciliation and authorization. Your team can halt the migration at any point, and the current system keeps running.
Portfolio reporting doesn’t pause for a migration.
The portfolio gets reported every month, migration or not.
Regulated SOFOMs report their portfolio, loan-loss reserves and risk stages to the CNBV every month in the R04 A series. A mid-year migration doesn’t pause that report, and a balance loaded wrong shows up in the next one. For an unregulated SOFOM, the same error reaches the funder’s report and the credit bureau.
Source: CNBV, CUIFE SF R04 A Loan Portfolio support guide (updated August 3, 2023).
Done at a Mexican lender.
We share it without names, because the client is under an NDA. Reading and reconciliation are done; loading into the new system depends on that system’s vendor and on the cut-off the client sets.
- 25 of 25 amortization schedules read from images and tied out to the cent. Measured in live operations; client confidential.
- 191 of 196 loans ready to migrate, with balances matching the client’s report; the ones that didn’t tie out were set aside for review. Measured in live operations; client confidential.
- The same reconciliation method runs every night in production at two lenders.
Talk to Luz. Right now.
Luz runs InnovaBlack's sales conversations — not a recorded demo, the same one that answers our clients. Write to her the way you'd write to anyone.
Prefer WhatsApp? +52 33 3246 1111
Luz
Head of Sales · InnovaBlack
Tell me what your operation needs and I’ll point you to where to start.
If we’re not the right fit, she’ll tell you.
What a lender asks before starting.
- How do you migrate a portfolio when amortization schedules are PDFs or images?
- Each one is read, and the dates, principal and interest of every payment are extracted. That rebuilds each loan’s balance, which is reconciled against your current system’s report. What matches to the cent is ready to load; what doesn’t is set aside with its difference for a person to review. That way the migration catches errors instead of carrying them over.
- What happens to loans that don’t tie out?
- They don’t get loaded until someone reviews them. Each one comes out with its difference and the document it was read from, so your team can decide whether the error is in the schedule, in the current system or in the reading. That decision is logged next to the loan. No balance enters the new system without someone answering for it.
- Do I have to stop operating to migrate?
- No. Your current system keeps running while loans are read and reconciled, because that work happens on the side without touching it. The load is scheduled for an agreed cut-off, and the reconciliation then runs against the new system. Time spent on two systems in parallel shrinks to what that cut-over takes.
- What does it cost, and how do we start?
- You start with a free diagnostic: we look at what formats your portfolio is in, how many loans there are and which system will receive them, and tell you which parts can be read and reconciled automatically and which need review. Pricing comes in a formal proposal. There is a one-time activation fee and, if we then run the portfolio, a monthly operations fee.
Tell Luz which system you’re moving to.
Luz, InnovaBlack’s Head of Sales, asks what she needs and sets up the free diagnostic. If your migration doesn’t need an agent, she’ll tell you.