How Precisa Cross-Analysis Reconciles GST and Bank Statement Data

Running a bank statement analysis and a GSTR analysis in separate passes is the standard approach for most credit teams. Precisa supports both. Each gives you something useful on its own. The problem is that neither tells you whether the two pictures of the borrower are consistent with each other. 

A business can show clean bank statements and clean GST filings in isolation. What a lender actually needs to know is whether those two datasets agree. That’s the gap Precisa’s Cross-Analysis feature addresses.

Key Takeaways

• Precisa’s Cross-Analysis compares GSTR data and bank statement data for the overlapping period, producing a single downloadable reconciliation report.
• The report checks sales and purchase reconciliation, customer and supplier banking activity, cyclic counterparty detection within GSTR, and payment irregularities.
• A borrower showing clean filings in isolation may still show significant gaps when the two datasets are placed side by side.
• The feature requires both a bank account and a GSTR entry for the same borrower in Precisa; the overlapping period is identified automatically.
• Results are partial when the overlap window is short or when payment aggregators consolidate multiple customer payments into a single bank credit. 

What Separate Analysis Can’t Tell You 

When you analyse a borrower’s bank account, you can see inflows, outflows, balance patterns, counterparties, and specific signals like circular transactions or bounce patterns. When you analyse their GSTR data, you can see declared sales, purchases, tax compliance ratings, and customer or supplier activity.

What neither analysis answers on its own:

• Are the bank account cash flows proportionate to the sales declared in GST filings?
• Do the customers named in GST returns appear in the bank statement as actual sources of payment?
• Are the suppliers claiming to supply this business genuinely transacting with them in their bank?

Manual reconciliation across both datasets is possible in theory. In practice, even a mid-sized business with 24 months of GSTR data and two or three active bank accounts can generate thousands of line items. GST filings use legal entity names; bank statements often carry abbreviated or informal labels for the same party. Matching these manually, for every applicant, isn’t sustainable.

Precisa’s Cross-Analysis brings both datasets into a single reconciliation report, covering the period where the bank statement and GSTR data overlap.

What the Cross-Analysis Report Shows 

The report is structured around five outputs, each covering a distinct dimension of the GST-to-bank relationship. 

Sales Reconciliation 

The first output is a side-by-side comparison of declared GST sales and credit activity in the bank account for the same period. If GSTR-1 reports ₹40 lakh in monthly sales but the bank account consistently shows ₹60 lakh in deposits, that gap has to be explained. The most common explanations are under-reported GST income or circular deposits being treated as revenue. Funds from a connected business flowing through the same account is another possibility worth ruling out. 

The reverse is also informative. If bank deposits are well below declared GST turnover, the borrower may be routing revenue through accounts not submitted for analysis, or the GST filings may be inflated.

Purchase Reconciliation 

On the purchase side, Precisa compares GSTR purchase declarations against outflows in the bank. If a business claims significant supplier purchases in its filings but those outflows don’t appear in the bank, the purchases may not have occurred, which in turn puts the associated ITC claims in question.

Customer and Supplier Banking Activity 

This is where cross-analysis tends to reveal the most operationally useful signals.

The platform identifies customer names from the GSTR filings and checks whether those same counterparties appear as inbound transaction parties in the bank statement. In practice, you might find a business that reports 33 customers in its GST filings, but only two of those names appear in bank transactions. That’s not automatically a red flag: some customers pay via cheque, or through intermediaries. But it’s a gap that warrants explanation before sanction.

The same check runs on suppliers. If a business lists 48 suppliers in its GSTR filings but none of them appear as outbound transaction parties in the bank, the question of whether those purchases actually occurred becomes difficult to ignore.

Cyclic Counterparty Detection Within GST 

One additional check that runs inside the GSTR portion is cyclic counterparty detection: identifying parties that appear as both a customer and a supplier in the GST data. Related-party transactions and revenue circulation within a connected network show up here. There are legitimate explanations for this in some business structures (subcontracting relationships, for instance), but the signal is worth reviewing.

Payment and Tax Irregularities 

The report also flags specific irregularities: for example, a tax payment in the bank account that doesn’t align with the expected GST liability declared in filings. These are the kind of mismatches that don’t rise to the level of a categorical red flag, but do indicate that the datasets aren’t telling the same story.

The Regulatory Context 

RBI’s updated digital lending directions require auditable credit decisioning with documented data sources. Running a GSTR analysis and a bank statement analysis separately, then reconciling them informally, creates a gap in the audit trail. Cross-Analysis generates a structured, downloadable report that documents which data sources were compared, the overlapping period covered, and what the outputs showed. That is what a defensible underwriting trail requires under current guidelines. 

RBI guidelines for NBFCs also require a Board-approved credit policy covering digital lending segments. GSTR verification is increasingly expected as a documented step within that policy. A single reconciliation report makes it easier to implement that requirement consistently at volume. 

How to Run a Cross-Analysis in Precisa 

You need both a bank account and a GSTR entry for the same borrower in a report. Once both are uploaded or fetched via the GST portal, the Cross-Analysis option becomes available from the dashboard. Precisa identifies the overlapping period automatically and generates the reconciliation for that window.

The report is downloadable. It also connects with Precisa’s counterparty detection, so customer and supplier matching runs against counterparty data already built during the bank statement analysis rather than starting from scratch.

Precisa is available as a standalone web application and via API. Lenders running high application volumes can push cross-analysis into their origination workflow programmatically, without manual report generation per case.

Frequently Asked Questions

1. What is cross-analysis in bank statement analysis?

Cross-analysis is a reconciliation method that compares a borrower’s GSTR data against their bank account activity for the same period. Precisa’s Cross-Analysis runs this comparison automatically and produces a single downloadable report covering sales, purchases, and counterparty matching across both datasets.

2. What does the Precisa Cross-Analysis report include?

The report covers four areas: sales reconciliation (GSTR declared sales vs bank credits), purchase reconciliation (GSTR declared purchases vs bank outflows), customer and supplier banking activity (whether GST-listed counterparties appear in the bank), and cyclic counterparty detection within the GSTR data. It also flags payment irregularities such as tax payments that don’t align with declared GST liability.

3. What if the bank statement and GSTR data cover different time periods?

Precisa identifies the overlapping period automatically. The reconciliation runs only for the window where both datasets are available. If the overlap is short, the output is limited to that window and should be interpreted with that constraint in mind.

Limitations to Consider When Interpreting Results 

Cross-analysis requires both datasets to cover a meaningful overlapping period. If a borrower submits one month of bank statements against 24 months of GSTR data, the reconciliation is limited to that one month. And if the business routes a significant portion of its income through payment aggregators or wallets that appear in the bank as a single consolidated credit, individual customer-level matching will be partial. The output is still useful in those cases, but the analyst should factor in these data structure realities when interpreting the results.

Precisa processes over 1.5 million bank statements for 1,000+ clients across 25+ countries, supporting 1,200+ bank formats. Try Precisa for free.