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

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 PO file from Blinkit and turn it into a FIFO picklist. It doesn't track whether the goods were received and confirmed via GRN, or what happens when the channel receives less than you invoiced. It doesn't tell you your fill rate for the week.

This is the gap FilFlo fills: not by competing with Tally, but by handling the order lifecycle that happens before the transaction becomes an accounting entry.

The Two Layers: Operations and Accounting

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 — along with an acknowledgement number and a signed QR code. The IRN must appear on the physical invoice accompanying the goods.

In a manual workflow, an ops manager would: finish picking an order, 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 — and every error surfaces later as a mismatch your accountant has to untangle.

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.

Per-GSTIN Invoicing Profiles and Per-FY Series

This is the part multi-state brands feel first. GST registration is per state, so a brand dispatching from warehouses in Haryana and Maharashtra is, for invoicing purposes, two sellers. Each GSTIN needs its own invoice series, and each series resets per financial year. Run this by hand across two or three entities and a shared Excel numbering sheet, and sooner or later two invoices collide on a number — or a Haryana dispatch goes out on a Maharashtra series, which is the kind of error a GST audit notices.

FilFlo models this directly with invoicing profiles — one per GSTIN, each carrying its own legal name, address, state code, invoice prefix, and sequential counter per financial year. When an order is invoiced, FilFlo selects the profile from the dispatching warehouse automatically: a Haryana warehouse dispatch must use the Haryana series, and does, every time. The same profile logic decides the tax split — CGST plus SGST when buyer and seller are in the same state, IGST when they are not — across the standard slabs, including the 40% slab that applies to sweetened beverages.

For the accounts team, this means every invoice that reaches Tally already belongs to the right entity, on the right series, with the right tax heads. The Tally-side work is recording, not repairing.

The Full B2B Order Lifecycle in FilFlo

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

E-Way Bills: Auto-Generated on Dispatch, Reconciled with NIC

The e-invoice is only half the compliance story; the truck needs an e-way bill. In FilFlo, the EWB is generated automatically at dispatch for inter-state movement, with the transport distance computed from an internal pincode directory rather than typed in by hand. The transporter, vehicle number, and AWB recorded at dispatch flow straight into the bill.

E-way bills expire, and an expired EWB on a moving truck is a detention risk. FilFlo's E-Way Bills screen tracks the whole fleet's compliance in one place: every active bill with a live validity countdown ("2d 14h left"), KPI cards for bills expiring within 24 hours and bills already expired, and a one-click Reconcile with NIC action that matches FilFlo's records against the government portal so the two never quietly drift apart.

For the accounts team, this means the EWB trail — which GST officers can and do ask for — lives alongside the invoice it belongs to, not in a separate portal login someone checks occasionally.

Credit Notes and Debit Notes: The Corrections Layer

B2B distribution generates corrections constantly — a truck refused at the DC, a partial delivery, goods coming back. Each of those is a financial event that must eventually land in Tally, and FilFlo types them explicitly so the paper trail is unambiguous.

Credit notes in FilFlo carry a type — RTV (return to vendor, from the buyer's perspective), RTO (return to origin), Partially Delivered, or Undelivered — and each credit note generates its own IRN, because under GST a credit note is a registrable document like the invoice it corrects. A "Material return expected" checkbox links the financial credit to a physical return inward when goods are actually coming back; a pure pricing adjustment leaves it unchecked, so the warehouse isn't waiting for a truck that will never arrive.

On the purchase side, the same discipline applies. When supply arrives short, damaged, or gets rejected, ops records a purchase return against the supplier's PO, and FilFlo auto-generates a supplier debit note for the recovery. Sales credit notes and supplier debit notes both travel to Tally with references to the documents they correct — so the party ledger your accountant maintains reconciles line by line against what operations actually did.

What Tally Handles vs What FilFlo Handles

The IRN→Tally 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 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:

Frequently Asked Questions