Skip to main content
About · Patents

Patents and research at Terra Insight

Terra Insight runs a small, India-anchored research practice. Our work is grounded in real customer statement corpora, real Indian regulatory texts, and the operational reality of running reconciliation infrastructure at enterprise scale. This page covers our patent posture and the research artefacts we publish openly.

Filed patent

Variance taxonomy framework for reconciliation

Terra Insight has filed a patent on its variance taxonomy framework — the structured classification of every reconciliation variance into a named, recoverable category. The taxonomy is the layer that turns "the books don't match the bank" into an actionable list: this many rupees are stuck in timing differences, this many are TDS reclassifications, this many are statutory deductions still pending recovery, this many are platform fee decompositions that need a credit note.

The taxonomy is what makes TransactIG audit-ready by default. Each variance carries evidence, a category, and a recovery path — not just a difference figure. We have chosen not to publish the application number on the public site; reviewers and procurement teams can request the reference under NDA.

Categories the taxonomy covers
Timing variances
Statement-vs-book cut-off mismatches across month and quarter ends.
Statutory deductions
TDS, TCS, GST TDS, equalisation levy — including section-level reclassification cases.
Platform decompositions
MDR, gateway fees, GST on fees, marketplace commission, ad-spend recoveries.
Batch & return variances
NACH return reasons, partial settlements, mandate-level mismatches.
Currency & rounding
Multi-currency book-vs-bank, rounding bands, fractional unit reconciliation.
Recoverable leakage
Variances where money is recoverable but no current process surfaces it.
Research culture

India-specific data, customer corpora, no synthetic benchmarking

Our research practice has three commitments. The first is India-specific data primacy. We do not borrow models or evaluation sets from US or European reconciliation vendors. Indian bank narrations, NACH return codes, GST tax structures, TDS sections, and platform settlement formats are not edge cases we adapt to — they are the design surface from day one. Every preset, every parser, every taxonomy entry is built against Indian source documents.

The second is customer-statement-corpus learning. The improvements we ship come from working through real customer bank statements, real ERP exports, and real settlement files — with consent, under our ISO 27001:2022 data-handling controls. This is the only way to make progress on the messy long tail: PSU bank narration patterns, co-op bank statement quirks, marketplace fee schedules that change quarterly, NBFC mandate mismatches. None of this surfaces in clean public datasets.

The third is a refusal to publish synthetic benchmarks. We do not run our internal accuracy numbers against generated or scrubbed statement data and call it a benchmark. The numbers we publish — like the 51% to 88% match-rate improvement on a customer engagement — are real outcomes on real corpora. We would rather publish one honest customer outcome than ten manufactured benchmarks.

Compliance posture
ISO 27001:2022
Certified
DPDP Act 2023
Aligned
RBI IT-governance
Aligned
AWS Mumbai
Data residency

Talk to the team

Reviewers, procurement teams, and prospective customers can request our patent reference, ISO 27001:2022 certificate, and security documentation under NDA.