A fintech ops team spent 40+ hours per week manually reconciling transaction discrepancies across three internal systems. Rule-based automation had been tried and failed - edge cases broke the rules constantly and the team was drowning in exceptions.
Reconciliation across three finance systems with compliance sign-off preserved and a full audit trail. The same problem an ERP finance team brings us, approached from the operations side.
In fintech operations, reconciliation is the work that never ends. Every transaction that doesn't match across systems becomes a discrepancy. Every discrepancy becomes a manual investigation. Every manual investigation takes 20–45 minutes of an ops analyst's time - pulling data from three systems, cross-referencing timestamps, checking counterparty records, and drafting a resolution action for compliance sign-off. At this company, 40+ hours per week of senior analyst time was consumed by a process that was fundamentally pattern-matching: most discrepancies had a known root cause, a known resolution, and a known compliance requirement. The team had tried rule-based automation once before. It had broken under the weight of edge cases and been abandoned.
The previous rule-based system had failed because rules can't handle ambiguity. Real-world reconciliation discrepancies don't follow a fixed taxonomy - they're edge cases, partial matches, timing anomalies, and data format inconsistencies that require judgment. We proposed a different framing: instead of trying to automate the resolution decision, automate the investigation and evidence assembly, and keep the resolution decision with a human reviewer. A well-designed system would reduce the time to resolution from 30 minutes to 2 minutes - not by eliminating the human, but by doing all the preparatory work the human was doing manually. That reframing carried the project: the compliance team approved it immediately because human sign-off was preserved.
The system is a LangGraph-based multi-step agent with direct API access to all three source systems. When a reconciliation discrepancy is flagged (by existing batch jobs or real-time triggers), the agent begins a structured investigation: it retrieves the transaction record from each of the three systems, normalises the data into a canonical schema, identifies the discrepancy type, queries relevant counterparty and timing records, and generates a draft resolution action with supporting evidence. The completed package - discrepancy summary, investigation trace, recommended resolution, and compliance documentation - is routed to a human reviewer who can approve in a single click or override with a note. Every decision is logged to an immutable audit trail in PostgreSQL.
Secure API connectors to all three source systems with schema normalisation. The agent translates each system's native data format into a canonical transaction schema before any reasoning step - eliminating the manual translation that made rule-based approaches brittle.
The agent's first reasoning step classifies the discrepancy into one of 15 defined categories (timing mismatch, partial settlement, counterparty format error, currency conversion delta, etc.) using a combination of rule-based classifiers and GPT-4o for ambiguous cases. Classification drives the investigation path - different categories trigger different evidence-gathering steps.
For each discrepancy category, the agent follows a defined investigation protocol: which counterparty records to retrieve, which timing windows to check, which reconciliation rules apply. The assembled evidence package includes all retrieved data, the agent's reasoning trace, and confidence scores for each conclusion.
GPT-4o generates a structured resolution recommendation in the format required by the compliance team - including the root cause classification, the resolution action, the regulatory basis for the resolution, and any follow-up requirements. Reviewers see the full evidence chain and can approve with one click or override with a free-text note.
A suite of 500+ test cases (built from 6 months of historical reconciliation records) validates agent performance on every deployment. The harness measures accuracy by discrepancy category, escalation rate, and false negative rate. Any model update that degrades accuracy on the test suite is blocked from production.
The 78% reduction in processing time wasn't achieved by replacing human judgment - it was achieved by eliminating the 90% of each case that was data gathering and formatting, not judgment.
Processing time dropped 78%. Escalation rate held below 5%. 35 hours per week returned to the team. 200,000+ cases processed without a data incident.
The first version of our proposal described the system as 'automated reconciliation.' The compliance team rejected it immediately - their mandate required human sign-off on every resolution. We reframed the system as 'automated investigation with human-approved resolution' and the same compliance team approved it the next day. The technical architecture was identical. The framing determined whether the project happened. Understanding what compliance teams can and cannot approve is as important as understanding what the technology can do.
The evaluation harness was built from 6 months of historical cases - including every case the team could recall where a rule-based system had failed or where a human had overridden an automated suggestion. Building the test suite from real failure modes, not invented edge cases, gave the ops team something concrete to review. When they could see the agent handling the specific cases that had previously defeated automation, adoption followed naturally.
We tracked escalation rate weekly from day one - not as a failure metric but as a health signal. A rising escalation rate indicates data drift (source systems have changed in ways the agent hasn't adapted to) or scope creep (new discrepancy types are appearing that the agent wasn't trained to handle). Keeping escalation rate below 5% as a weekly SLA gave the team a clear, actionable signal to trigger investigation before accuracy degraded in production.
More work
