One Reconciliation Run, Balanced to the Ledger
Thread AI Editorial · July 20, 2026
At a large financial services firm, analysts start each day reconciling fund expenses, the gains and losses that have been booked but not yet explained. Until every number ties out, no one can start researching what caused each gain or loss.
With Lemma, a Worker runs that reconciliation end to end. It pulls every source, balances the results to the ledger, groups related incidents, and holds a checked report for an approver before it goes out.
What Lemma delivers
Tie every figure to the ledger
With totals and detail balanced to the cent.
Report each incident once
Even when it affects many participants.
Keep a person in charge
So nothing reaches leadership without a named sign-off.
The Challenge
When a fund records a gain or loss that hasn’t been explained yet, someone has to reconcile it before anyone can research the cause. At most firms, that work happens by hand every morning.
Analysts pull the general ledger and recordkeeping extracts from separate systems, rebuild the same pivot tables, and tie the detail back to the ledger. Each person works in a local copy and pastes their piece into a shared file.
The firm also reports incidents to external partners, who want that detail more often. A process that depends on hand-built spreadsheets makes that hard to deliver.
The Solution
The Worker pulls from every source system in parallel, then applies the incident threshold and the rules for positive and negative amounts in code instead of in a workbook. It balances each stream to the general ledger to the cent, classifies whether incidents are part of a group or stand alone, and adds research details from reference data so analysts don’t have to look them up.
AI writes the narrative summary, but every number in it comes from the code, and each figure is checked against the computed results before the report moves on. The Worker then runs the daily reporting-threshold review and holds the consolidated report for a named approver. Once approved, it’s emailed to leadership.
Lemma Capabilities
Keeps one outage from stopping the run.
Each source system is pulled as its own stream. If one goes down, the Worker pauses only that source and alerts the team, and the ledger and recordkeeping work continues.
Balances in whole cents.
All math runs in integer cents to avoid rounding drift, and an out-of-balance day is flagged in the report’s subject line.
Groups incidents by root cause.
When one processing error touches many participants, it’s reported as a single incident, which is the level of detail external partners ask for.
Holds the report for a named approver.
Nothing goes to leadership until a reviewer signs off, and every run is logged so any past report can be replayed.
What’s Next
With the reconciliation running on its own, analysts can spend their mornings finding and fixing the causes of each gain or loss. The firm can also give its external partners incident-level reporting as often as they need, without the team rebuilding spreadsheets to produce it.
Does this sound familiar?
Your daily reconciliation starts with several logins and ends with a copy-and-paste.
The rules that drive it live in a spreadsheet only one person understands.
You find out a source system is down when your report breaks.
Partners want more detailed reporting, more often, than your team can produce.