Asked, and answered plainly.

No. You download the reports your marketplaces already give you, drop them in, and get a JSON file to upload on the GST portal. Where something needs a decision, fynxIQ explains what the decision is in plain language rather than asking you to know a table number.

No. It prepares and checks the return and gives you the JSON. You upload it on the GST portal yourself and submit it there. Nothing is filed on your behalf and your portal password is never asked for.

Amazon, Flipkart, Meesho and Myntra, each read by rules written for its own reports and checked against real seller months and the portal’s TCS statement, including Amazon’s GST ready-to-file workbook. Anything else at all, another marketplace, an accounting export or a register you keep in Excel yourself, can be read on request or mapped by hand once. A GSTR-1 exported from Tally, Busy or Marg in the offline tool’s template is read too; that path is built from the published template and says so. A TallyPrime Day Book export is read as vouchers, so a client who keeps books in Tally needs no other file for the GSTR-1.

No. GSTR-1 is where it started and where most of the checks are, but the app also holds your purchase register and bills against the GSTR-2B to show which credit you can claim, drafts the GSTR-3B from the GSTR-1 and the GSTR-2B, compares the portal’s TCS statement with your sales, and works with Tally both ways: a Day Book export read as vouchers, and the checked month sent back as sales and purchase vouchers. A practice gets a firm workspace on top: a board and a calendar of every client, the GSTR-1 and the GSTR-3B marked filed with their ARNs, and upload links for clients. All of it is on every plan, the free one included.

Yes, six, all running in your browser with nothing sent anywhere: a GSTR-1 converter for Amazon, Flipkart, Meesho and Myntra reports that shows the return and every check, a GSTR-1 JSON validator, an HSN code checker, a GST late fee calculator, a TCS calculator and a GSTIN checker. They are listed at /tools.

Yes. Upload it and fynxIQ will tell you what every sheet in it turned out to be, one word each: orders, a finished return, a cover page, a purchase register, or unknown. For anything it cannot place, press the button and it works out what each column holds, then asks you about whatever it genuinely cannot settle, in whichever language you picked, as buttons rather than a form. Every arithmetic check still runs afterwards and can still refuse the return, so a wrong answer to a question costs you a corrected mapping, not a wrong filing.

Yes. Pick from fourteen languages beside the Ask box, including Hinglish written in Roman letters. Every question fynxIQ asks about your file in the column mapper, every plan it writes for a check, and the whole of the AI second opinion (what is wrong, what it costs and the steps to fix it) come back in that language. GST terms like GSTIN, HSN and taxable value stay in English because that is how they are printed on your own reports, and all numbers stay in Latin digits so you can check them against your marketplace dashboard.

It works, and fynxIQ converts it to the JSON the portal accepts. But it is worth knowing what it is: a finished return that somebody else prepared, in which the invoices have already been collapsed into state and rate totals. fynxIQ checks it agrees with itself, and it can check nothing beyond that, because the orders behind it are no longer in the file. Upload the transaction report for the same month as well and it reconciles the two and tells you every figure they disagree on. On a real July 2025 report, the workbook’s own HSN summary declared twenty-one rupees more tax than the rest of the same workbook.

Read what it says it will change first; it always says. A repair is only ever offered where a figure the file got wrong can be proved wrong from figures the same file got right: for instance an HSN summary whose tax is not its own rate times its own taxable value, where the sheet’s other columns agree with the correct figure. No repair touches a sales figure, none is applied unless you press the button, and what it changed is stated on the return afterwards. If your file came from a marketplace, the same fault will be in next month’s file, so it is worth telling them.

Tables 4 to 9 and Table 12 describe the same month from two directions, so their totals must be identical. fynxIQ compares them in integer paise with no tolerance. If the difference is not exactly zero, the download stays closed and the app names the amount and the rows behind it.

Because a blocker means a specific figure in the return does not agree with another figure in the same return. Filing it would put a number on record that you would later have to explain. Every blocker names the amount and where it came from so it can be settled at source.

The engine says so rather than guessing. Unrecognised columns produce a warning, unrecognised values produce a blocker, and you can point the fields at the new columns yourself in a minute using the mapper.

It drafts it, to hold against the portal’s before you submit. Table 3.1 and 3.2 come from the month’s GSTR-1, Table 4 from the GSTR-2B, the reversals you state go in the rows Circular 170/02/2022-GST gives them, credit pays tax in the order the Act fixes, and the tax your marketplaces collected at source is applied to the cash. Drop the portal’s own 3B PDF beside it and every figure is compared. It does not work out interest, late fee or imports of services, and it says so.

It holds your GSTR-2B, as the portal’s JSON or Excel, against your purchase register and your photographed or PDF bills, and says of every bill whether it is in the statement, missing from it, or different. Credit can be taken only on what the GSTR-2B carries (section 16(2)(aa), rule 36(4)). Whether a credit is blocked under section 17(5) is your judgement: mark the bill, and its tax goes into its cost in the Tally files and its total is offered for Table 4(B)(1) on the GSTR-3B draft, where you can also state any other reversal.

Yes, both ways. In: a TallyPrime Day Book exported as XML is read and the GSTR-1 built from its vouchers, each line traced to its voucher. Out: the checked return exports as Tally’s XML import files, one voucher per invoice to a registered buyer, consumer sales as one summary per marketplace per state, credit and debit notes, and from the Purchases page a purchase voucher for each bill with the ledgers they post to. It posts only to ledgers you have named, once per client, and holds back any voucher whose ledgers are not named rather than guess. A bill whose input tax cannot be claimed, because the portal says so or because you marked it as blocked under section 17(5), goes with its tax in its cost. The sales files were tested by importing into a TallyPrime 7.1 company and reading back its Day Book and GSTR-1, and the purchase files by importing them and reading back its Day Book and GST reports; import into a copy of your company the first time.

No. The checks prove the return agrees with itself, with the files you gave it and, when you add it, with the portal’s TCS statement. They cannot prove your files are complete, or that a tax treatment is right. That judgement stays with you and your accountant.

Nothing is counted twice. Every line carries a key made from its source, its document type, its own line id and its rate, and a second copy of a line is dropped. Where two copies of one line disagree, as a marketplace’s B2B and B2C exports sometimes do, the first is kept and the return says the two differed.

Both. Set each GSTIN as monthly or quarterly under the QRMP scheme, and the GSTR-1 is built for the month or for the whole quarter, with the quarter’s last month as its period, which is what the portal’s JSON carries.

A practice workspace, chosen at sign-up on any plan; the plan sets how many GSTINs and logins. Every client sits on one board per period: nothing yet, blocked, ready, nil, or filed. Above it, a calendar of every return by due date, overdue first, then the next seven days, then the rest; a PMT-06 is listed by its date and never called overdue. Staff are assigned client by client and see only their clients, the client list imports from Excel, every change is in the activity log, and the owner signs in with a second factor. Everything can be taken out as one zip, and a deleted client can be restored for seven days.

Yes. Each client’s month has a GSTR-1 mark and a GSTR-3B mark, each with its own ARN and date, and a return leaves the calendar the moment its ARN is recorded. Reminder emails go out three days before a due date, stop for a return once it is marked, and can be turned off in Settings. The status workbook for the period carries both ARNs.

Yes, on a practice. Make an upload link for a client and a period and send it. The client opens it, drops the month’s files, sees the return and its checks built on their own device, and sends. The files are read on the client’s device and never sent; what reaches you is the prepared return, its checks, their note and each file’s fingerprint. A link lasts fourteen days and can be revoked.

Marketplace reports, registers, a Tally Day Book and your GSTR-2B are read in your own browser, and their invoice lines, customer states and order references do not reach our servers. What we store is your account, your plan, and a record of the totals you prepared. Two things are different and you choose both: a photographed or PDF bill is sent to be read when you ask for it, and a month a client sends a firm through an upload link arrives as the prepared return, which carries registered buyers’ invoices the way the portal’s JSON does.

It is sent through our server to Anthropic’s Claude API, or Google’s Gemini API when Claude cannot answer. Neither may train on it; Google’s paid tier does not keep it, and Anthropic deletes it within 30 days. That happens only after you agree to it once, in writing, and the agreement can be withdrawn in Settings. We keep no copy of the image. What was read is shown to you beside the picture and counts only once you confirm it.

A summary of derived totals, HSN codes, your own product titles and the findings the rules produced. No GSTIN, no buyer, no address, no order reference. The app shows you the exact bytes before anything is sent, and asks first.

No. Deterministic rules decide whether a return can be filed. The model reads their findings back and points at things rules cannot express. It cannot clear a blocker, cannot change a figure, and is never allowed to report that a return is correct.

Never. There is no field for it and no route that takes one. By default fynxIQ does not connect to the portal at all. Portal access through a GST Suvidha Provider is built and not offered yet; once it is offered, it is switched on for one registration at a time with the taxpayer’s own OTP, used once and never stored, and only reads; Revoke ends it at once. You upload the JSON and submit it on the portal yourself.

Yes. The owner can take everything out as one zip from Settings, then delete the organisation there. It is hidden at once and purged seven days later, and until then the owner can restore it. Payment records are kept, because we are required to keep them.

Yes. The free plan covers 2 GSTIN profiles and 6 prepared returns a month, with every validation rule running in full, the GSTR-2B, the GSTR-3B draft and Tally, and the same GSTN-ready JSON the paid plans produce. The checks are the product, and they are not held back on the free plan.

The account falls back to the free plan’s limits. Returns you have already prepared stay readable, your filing history stays intact, and the GST profiles you have created keep working; you simply cannot add more. Nothing is deleted for non-payment.

Within one working day, Monday to Saturday, Indian time, on every plan including the free one. Write to official@fynxiq.com or raise a ticket from the Ask box in the app; the person answering is the one who built the checks, so a question about a figure gets an answer about the figure.

Yes. Paid yearly, every paid plan costs at least 16 per cent less than twelve monthly payments. Each plan’s yearly price is on the pricing page.