FilFlo
ProductTeamsHow it worksCustomersFAQBlog
Sign in
ProductTeamsHow it worksCustomersFAQBlogIntegrationsSign in
filflo

AI replenishment for Indian D2C brands. Built by operators, in Gurugram.

Product
  • Features
  • Use cases
  • Industries
  • Integrations
  • Product overview
  • ROI calculator
Company
  • Team
  • About
  • Blog
  • Contact
Resources
  • FAQ
  • Security
  • Privacy
  • Terms
Get in touch
  • Book a demo
  • Sign in
  • LinkedIn
  • Twitter / X
FilFlo
© 2026 Tijora Software Private Limited. All rights reserved.
Made in India · Built for Indian brands
Back to Blog
Integrations
Integrations

FilFlo and Tally: How Your B2B Order Operations Connect to Your Accounts

Over 80% of Indian businesses use Tally for accounts. FilFlo is built to complement it — not replace it. FilFlo handles the operational layer (B2B orders from Blinkit, Zepto, distributors, IRN e-invoicing). Tally handles accounts and GST filings. Here's how the two work together without double-entry.

FilFlo Product Team
May 20, 2025
8 min read
~1,700 words
FilFlo Tally Integration

⚡ Key Takeaways

  • Tally handles accounts, GST filings, ledger entries, and financial reporting — it stays as your system of record.
  • FilFlo handles B2B order operations — receiving POs from Blinkit/Zepto/distributors, managing fulfilment, generating IRN e-invoices, tracking GRNs.
  • FilFlo generates the IRN e-invoice as part of the operational order workflow — the invoice data then exports to Tally as an accounting entry.
  • No double-entry: FilFlo is the operational source; Tally is the accounting record. The boundary is clear.

Why Indian Businesses Run Tally — and Why It's Not Enough for B2B Operations

Tally has been the backbone of Indian business accounting for three decades. It handles GST return computation, voucher entry, party ledgers, payment reconciliation, and financial reporting in a way that's deeply familiar to Indian CA firms and accounts teams. Most D2C founders we talk to have Tally running on someone's laptop in the office, maintained by an accountant or CA.

The problem arises when the same brand starts receiving B2B purchase orders from Blinkit or a distributor. Tally is an accounting tool — it records transactions. It doesn't manage an order workflow. It doesn't import a CSV from Blinkit's portal and turn it into a pick list. It doesn't track whether the goods were received and confirmed via GRN. It doesn't tell you your fill rate for the week.

This is the gap FilFlo fills — not by replacing Tally, but by running the operational layer that Tally was never designed to handle.

The Two Layers: Operations and Accounting

Accounting layer — Tally

  • GSTR-1 and GSTR-3B return filing
  • Journal entries and voucher management
  • Party ledger and outstanding receivables
  • Bank reconciliation and payment tracking
  • P&L, balance sheet, financial reports

Operations layer — FilFlo

  • B2B order intake (Blinkit CSV, distributor PO)
  • Order approval, stock allocation, picklist
  • IRN / e-invoice generation at invoicing step
  • In-transit tracking and gatepass
  • GRN confirmation and fill rate reporting

Where IRN Fits — and Why It Belongs in FilFlo

Under India's GST e-invoicing mandate, B2B invoices above certain thresholds must be registered with the Invoice Registration Portal (IRP) before dispatch. The IRP returns an IRN — a unique hash that validates the invoice. This IRN must appear on the physical invoice accompanying the goods.

In a manual workflow, an ops manager would: finish picking an order in FilFlo (or a spreadsheet), switch to a browser to log into the GST portal or Tally's e-invoice module, manually enter the buyer's GSTIN, invoice details, and line items, fetch the IRN, copy it back into the invoice document, and then print. This takes 5–15 minutes per order and is error-prone.

FilFlo's approach

When an order moves to the Invoiced stage in FilFlo:

  1. FilFlo calls the IRP API with the invoice details (buyer GSTIN, line items, tax breakdown)
  2. IRP returns the IRN and QR code
  3. FilFlo embeds the IRN and QR code in the e-invoice PDF
  4. Invoice is ready for dispatch — compliant, accurate, timestamped
  5. Invoice data exports to Tally as a sales entry for accounting

The ops team doesn't log into the GST portal. The accounts team doesn't re-enter the invoice in Tally — they import it. One source of truth, no double-entry.

See the Tally + FilFlo Workflow Live

Book a 30-minute demo to see how FilFlo generates IRN invoices and how the data flows to Tally — without any double-entry.

The Full B2B Order Lifecycle in FilFlo

This is the workflow that FilFlo manages — from Blinkit sending a PO to your account team seeing the closed order in Tally:

1. Open

Blinkit PO CSV uploaded to FilFlo. Line items mapped to product master. Order created.

2. Approved

Ops team reviews quantities vs available stock. Sourcing alert fires if stock is short. Order approved for picking.

3. Picked

Picklist generated for warehouse staff. Items scanned and picked. Ready for invoice.

4. Invoiced

IRN fetched from IRP automatically. GST e-invoice generated with QR code. Gatepass created for dispatch.

5. In Transit

Goods dispatched. In-transit ageing tracked. Logistics tracked against expected delivery.

6. Delivered

Goods arrive at Blinkit hub or distributor.

7. GRN

Buyer confirms receipt. Actual quantities vs ordered captured. Fill rate computed for the period. Invoice data exports to Tally.

What Tally Handles vs What FilFlo Handles

TaskTallyFilFlo
GSTR-1 / GSTR-3B filing✅ Primary tool❌
Journal entries and voucher management✅❌
Payment reconciliation with buyers✅❌
Party ledger✅✅ Operational party ledger (FilFlo)
P&L and balance sheet✅❌
B2B order intake (Blinkit CSV)❌✅
B2B order lifecycle (Open → GRN)❌✅
IRN / GST e-invoice generation⚠️ Via e-invoice module✅ Automatic at invoicing step
Picklist for warehouse❌✅
GRN confirmation from buyer❌✅
Fill rate reporting❌✅
Sourcing alerts❌✅
In-transit ageing❌✅
Procurement PO with supplier GRN⚠️ Basic tracking✅ Full PO lifecycle

The IRN→Tally Export Flow: How It Actually Works

Many Tally users ask: if Tally already has an e-invoicing module, why do I need FilFlo to generate IRNs? The answer is that Tally's e-invoicing requires you to manually create the invoice in Tally first, then push it to the IRP. FilFlo generates the IRN as part of the operational order workflow — no manual Tally entry required at that step. Here is the exact sequence:

IRN Generation Internals in FilFlo

1

Order Invoiced in FilFlo

Your ops team moves the order from Picked to Invoiced. FilFlo selects the appropriate invoicing profile based on the seller warehouse GSTIN.

2

IRP Payload Built

FilFlo assembles the IRP payload: seller GSTIN, buyer GSTIN (e.g., Blinkit = ZOMATO HYPERPURE PRIVATE LTD), HSN code per product line, GST slab (0/5/12/18/28%), CGST+SGST or IGST based on state codes, assessable value (AssVal), and total invoice value (TotInvVal).

3

Whitebooks API Call

FilFlo calls the Whitebooks IRP integration. Whitebooks authenticates with the IRP and registers the invoice. The IRP returns a unique IRN (a 64-character hash) and a signed QR code.

4

IRN Stored in FilFlo

FilFlo stores the IRN, acknowledgement number (ackNo), ack date, signed invoice, and signed QR code in the order record under irnDetails. Status is set to active.

5

Invoice PDF Generated

The e-invoice PDF is generated with: IRN printed on the invoice, QR code embedded, invoice number (e.g., INV0042), buyer/seller GSTIN, line items with HSN and GST breakdowns.

6

Export to Tally

Invoice data is exported in Tally-compatible format: party name, GSTIN, invoice number, date, line items, GST amounts, and the IRN. Your accountant imports this into Tally as a sales voucher. GSTR-1 data auto-populates from Tally's reconciliation.

What stays in Tally vs. what FilFlo generates

The clean boundary: FilFlo is the operational source of every B2B invoice. Tally is the accounting record. Here is the data that flows between them:

FROM FilFlo → TO Tally

  • • Invoice number, date, and IRN
  • • Party name and GSTIN
  • • Line items: product name, HSN, quantity, unit price
  • • GST breakdown: CGST, SGST, IGST per line
  • • Assessable value and total invoice value
  • • Credit notes (CRN series) with original invoice reference
  • • Procurement PO receipts (as purchase entries)

STAYS IN Tally

  • • GSTR-1 and GSTR-3B filing
  • • Journal entries and voucher management
  • • Party ledger (financial — outstanding receivables)
  • • Bank reconciliation
  • • Payroll and expense management
  • • P&L and balance sheet
  • • TDS/TCS deduction entries

Multi-entity GSTIN management

If your brand has multiple warehouse locations registered under different GSTINs (e.g., Maharashtra warehouse and Haryana warehouse), FilFlo handles this with multiple invoicing profiles — one per GSTIN entity. Each profile has its own invoice prefix, sequential counter, and Whitebooks credentials.

When an order is invoiced, FilFlo automatically uses the correct profile based on the dispatching warehouse. The Tally export tags each invoice to the correct ledger account matching that entity's GSTIN. No manual routing required.

Frequently Asked Questions

Does FilFlo replace Tally?

No. Tally remains your system of record for accounts, GST return filings (GSTR-1, GSTR-3B), payment reconciliation, and financial reporting. FilFlo handles the operational layer: receiving B2B orders from Blinkit/Zepto/distributors, managing the fulfilment lifecycle, and generating IRN e-invoices. These are two different layers with a clean boundary between them.

If FilFlo generates the e-invoice and IRN, does it duplicate what Tally does?

No. Many Tally users generate e-invoices through Tally's e-invoicing module or through a separate portal. FilFlo generates the IRN as part of the operational workflow — when an order moves to the Invoiced stage, the IRN is fetched automatically. The invoice data then flows to Tally as an accounting entry. There's no duplication: FilFlo is the operational source of the invoice; Tally records it as a transaction.

Is FilFlo compatible with TallyPrime and older Tally ERP 9?

FilFlo's data export and integration capabilities work with TallyPrime (the current version). For older Tally ERP 9 installations, data can be exported in Tally-compatible XML format for import. We recommend speaking with the FilFlo team about your specific Tally version during onboarding.

What data flows from FilFlo to Tally?

The key data flow is invoice/sales entry data: after FilFlo generates an IRN and invoices a B2B order, the invoice details (party name, GSTIN, line items, GST amounts, IRN) can be exported for Tally import. Procurement PO receipts (GRN from suppliers) can similarly flow as purchase entries. Tally then uses this data for GST return computation and ledger entries.

What stays in Tally and what stays in FilFlo?

In Tally: GST filings (GSTR-1, GSTR-3B), journal entries, payment receipts, bank reconciliation, payroll, P&L and balance sheet. In FilFlo: B2B order intake and lifecycle (Open → GRN), IRN e-invoice generation, picklist and dispatch management, fill rate reports, sourcing alerts, and procurement PO management. The two systems are separated by function — operations in FilFlo, accounting in Tally.

Running Tally for Accounts? Add FilFlo for B2B Ops.

See how FilFlo handles your Blinkit and distributor orders — from CSV import to IRN invoice — while your Tally setup stays exactly as it is.

See All Integrations