Getting Data In
The file formats TransactIG ingests, the delivery mechanisms behind them, and how the platform handles the everyday reality that real files are messy. SWIFT MT940, bank exports across every major Indian bank, GSTR workbooks, Form 26AS, payment-gateway settlement files, NACH, TPA statements — the artifacts your systems already produce.
We ingest the files you already have
No data-warehouse project is required. TransactIG ingests the files your systems already produce and your teams already work with — bank statements exported from corporate banking portals, GSTR workbooks downloaded from the GSTN portal, Form 26AS from TRACES, settlement files from your payment gateways, ledger exports from Tally or SAP or Oracle. The listed formats below are public standards or well-known corporate exports; naming them is a capability statement, not an implementation detail.
Four families of inputs
The families below cover the four categories that turn up on almost every reconciliation engagement. Which subset you need depends on which reconciliation streams you enable — a manufacturer with export receipts and a payment gateway will draw from all four; an internal audit team running a monthly bank sweep may use only the first.
Bank Statements
- SWIFT MT940
The interbank standard for account statement messages. The format banks generate for corporate customers with treasury or ERP integrations.
- Bank CSV / XLSX exports
Every major Indian bank — HDFC, ICICI, SBI, Axis, Kotak, Federal Bank, IDBI, PNB, Bank of Baroda, Canara, IndusInd, RBL, Yes Bank — plus co-operative banks. Format-per-bank variance is handled.
Ledgers and Books
- Tally exports
Day-book, ledger, and voucher exports from Tally Prime and Tally ERP 9.
- SAP exports
FBL5N-style customer registers, FBL3N GL registers, and equivalent transaction reports.
- Oracle ledger CSVs
General ledger and AR/AP subledger extracts from Oracle Fusion and Oracle E-Business Suite.
Statutory
- GSTR-1
Outward supplies government workbook.
- GSTR-2B
Auto-drafted ITC statement.
- GSTR-3B
Summary return government workbook.
- Form 26AS (TRACES)
Annual tax credit statement.
- Form 26Q
Quarterly TDS return.
- Challan registers
TDS and GST payment challans.
Settlement and Side Feeds
- Payment-gateway settlement files
Razorpay, PayU, PhonePe, Cashfree, Juspay. Fee breakouts, refunds, chargebacks, and reserves as each PG documents them.
- NACH files
Mandate registration and bounce return files under the NPCI framework.
- TPA / insurer statements
For healthcare and insurance workflows.
- Registers
Invoice registers, advances, vendor masters, cheque registers.
Files are messy — that's expected
Real files carry banner rows the bank appends for legal disclaimers; column headers that shift position depending on which portal generated the export; bank-specific narrations that describe the same event five different ways. TransactIG's onboarding maps your exact file shapes once — the bank you use, the version of the ERP export you produce, the language conventions in your PG merchant identifier. After that mapping is in place, day-to-day uploads are drag-and-drop or fully automated. The finance team never sees the underlying variance.
Three delivery mechanisms, one contract
Every deployment starts somewhere on this ladder and can graduate at any time without changing the reconciliation configuration. The transport is separate from the contract — the same envelope is produced whether files arrived by drag-and-drop or by an overnight SFTP pull.
Manual upload
Drag-and-drop through the TransactIG UI. Suitable for month-end and quarterly cycles where the finance team runs reconciliation on a fixed calendar.
Scheduled SFTP pulls
TransactIG collects statements on a schedule. Illustrative pattern: statements collected nightly at 07:45 IST, results ready at desk-open. The schedule is set to match your bank's statement generation window and your team's working hours.
API push
Your ERP or ingestion pipeline pushes files directly. The transport changes; the file format families and the output contract do not.
Duplicate re-sends are detected and ignored automatically. If the same statement file is uploaded twice — because a scheduled job retried or an analyst re-ran the export — TransactIG recognises the duplicate and does not re-process it. The manifest fingerprints the input files so re-submissions are handled cleanly.
Format family, source system, typical industries
A quick index of which format tends to come from which source system, and which industry verticals draw on it most heavily. Use this to sanity-check that the reconciliation streams you are planning cover the file inventory your finance team actually produces.
| Format family | Typical source system | Typical industries |
|---|---|---|
| SWIFT MT940 | HDFC / ICICI / SBI corporate banking | Manufacturing, IT services, Real estate, NBFC |
| Bank CSV/XLSX | All major Indian banks | Across all industries |
| Tally export | Tally Prime, Tally ERP 9 | SMB manufacturing, Retail, Distribution, Professional services |
| SAP FBL5N | SAP S/4HANA, SAP ECC 6.0 | Auto components, FMCG, Pharma, Large manufacturing |
| Oracle ledger CSV | Oracle Fusion, Oracle E-Business Suite | IT services, BFSI, Utilities |
| GSTR-2B / 3B | GSTN portal | All GST-registered businesses |
| Form 26AS | TRACES portal | All TDS-deducted entities |
| PG settlement file | Razorpay / PayU / PhonePe / Cashfree / Juspay | E-commerce, D2C, Streaming, SaaS, EdTech |
| NACH file | NPCI, sponsor bank | NBFC, Insurance, Utilities, Recurring billing |
| TPA / insurer statement | Insurance TPAs | Healthcare, Insurance |
The industries column reuses the vocabulary from the industry pages — each vertical's page describes the reconciliation patterns typical to that sector and the file inventory that feeds them.
What files become, once they're in
Inputs are only half the picture. The output is the Recon Output Envelope — the canonical machine-readable result each run produces. The integration process page describes how the two ends connect.
The Recon Output Envelope
Section-by-section field reference with a worked example. What every run produces, in canonical form.
The integration process
Six stages from discovery to go-live and expansion. Format capture is stage two — inputs are locked once, then run.
How TransactIG delivers results
Deterministic infrastructure, the Recon Output Envelope, Discovered Money's four buckets, precision as a contract.
Bring us your files. We map the shapes once.
Share one real sample of each file type. Onboarding locks your exact shapes so day-to-day reconciliation is drag-and-drop or fully automated. ISO 27001:2022 certified.