TARANGFINANCIAL FORENSICSDemo case Open app
USE CASES

Tarang for Financial Investigators

The difficulty in a financial investigation is rarely the arithmetic. It is that the answer lives across eleven statements from six banks in four formats, and every hour spent making those files comparable is an hour not spent on the question.

The working day this is shaped around

  1. Statements arrive in whatever the bank sent. Some scanned, some exported, some with a missing page nobody mentions. They import as a case; each file is verified against its own printed balance and the incomplete ones are named rather than quietly averaged in.
  2. Work out who you are actually looking at. Account holders, and the counterparties each account deals with, consolidated so one person is one name. Before this, every ranking is a ranking of spellings.
  3. Find the movement worth looking at. Largest transactions, cash activity, round figures, activity outside the account's normal pattern — each one opening the rows behind it.
  4. Establish which transfers are real. Two statements printing the same reference number is a proven transfer. A same-day, same-amount pair is a lead. Keeping those separate is what stops a trail collapsing under questioning.
  5. Follow it. Forward from a deposit or an inflow, hop by hop, with the portion that can honestly be attributed stated at each step and the remainder reported as untraced rather than assumed.
  6. Correct what the software got wrong. Rename, merge, split, re-attribute. Every edit is recorded and flows into the report.
  7. Produce the document. The report matches the screen, and every figure in it can be opened to its transactions.

The parts that usually cost the most time

Statements that will not open cleanly

Scanned pages, wrapped narrations, columns in an unexpected order. Extraction is by page geometry rather than header keywords, so an unseen format is not an unseen bank.

The same name six ways

Consolidated automatically and correctable by hand, with over-merging treated as the more dangerous error — an under-merge is visible in the list; an over-merge hides money under the wrong person.

Double-counted internal transfers

Money between the subject's own accounts is identified as internal and kept out of external totals instead of being counted on both sides.

"Where did the number come from?"

Everything drills to rows, and the corrections made during review are part of the report rather than a separate note.

Case isolation

Each case has its own storage. A view opened under one case cannot read another case's data, and the case in context is part of every request rather than a screen setting that can drift.

(Where the software stops. Tarang does not decide that a transaction is suspicious, and it makes no claim of official standing. It organises the material and points at specific rows. The determination, the corroboration and the document are the investigator's.)