Business Central Consultant in India

GST setup in Business Central: locations, registrations and item tax data

The India localization of Business Central, supplied by Microsoft, adds GST, TDS and TCS handling to the standard product. Its logic depends heavily on master data. Each location carries a state and a GST registration number. Items and services carry a GST group code and an HSN or SAC code. Customers and vendors carry their own registration details and type, such as registered, unregistered, export or SEZ. The system then works out whether a transaction is intra-state or inter-state and which components apply.

That is why I start with a location and registration map rather than with screens. A manufacturer with plants in two states, depots in three more and a head office elsewhere needs every one of those mapped correctly before the first transfer order is posted. Stock transfers between your own registrations are a frequent source of errors, so I walk through them step by step with your chartered accountant.

I also define how GST posting is set up against your chart of accounts, so input credit, output liability and any reverse charge payable sit in accounts your finance team can reconcile each month. Treatment of specific supplies is a question for your chartered accountant; I make the configuration follow their guidance and then test it with documents they recognize.

TDS, TCS and the e-invoice and e-way bill connectors

TDS in the India localization is driven by sections, assigned to vendors and to the accounts or items that attract deduction, with rates and thresholds maintained in setup. TCS works in a similar way on the customer side. I build a matrix with your chartered accountant covering contractor payments, professional fees, rent, purchases of goods where applicable and any TCS cases, then define who maintains rates, how lower deduction certificates are recorded and how data for returns and certificates is extracted.

E-invoicing and e-way bills usually involve something outside the core product. Many projects use a GST Suvidha Provider or an AppSource app to send invoice data, receive the IRN and signed QR code, and generate e-way bills for dispatches. The details vary by provider, so I ask each bidder to name the connector, show its error handling, confirm who pays the provider and who adapts the integration when the government systems revise their specifications.

Some companies file returns through a dedicated GST compliance product that reads data from Business Central. Where that applies, I define the data extract and the reconciliation between the ledger and the returns, including input credit matching. UAT then includes a cancelled invoice, an amended invoice, a credit note raised in a later month than its original invoice, and a dispatch requiring an e-way bill.

Bank payment uploads, receipts and reconciliation

Indian finance teams typically pay vendors through bulk NEFT or RTGS uploads to the bank's corporate portal, sometimes through a host-to-host link, and still issue some checks. Business Central supports payment journals and vendor payment suggestions, but each bank has its own upload format and approval flow. Bank by bank, I gather the formats and have the partner state whether a configurable file layout, an app or a custom extension will produce them, and how TDS deducted at payment is reflected in the amount sent.

Receipts need equal care. Customers often pay several invoices in one transfer with a short reference, distributors may pay against a running account, and export receivables arrive in foreign currency with bank charges deducted. I define how statements are imported, how matching rules will handle these patterns and how realized exchange differences on export collections are posted.

Indian companies also work with a heavy voucher culture: cash, bank, contra and journal entries reviewed and approved by different people. I check how the localization's voucher configuration and Business Central's approval workflows will reproduce the controls your auditors expect. UAT includes a bank-accepted upload file, a month of statements reconciled and a check run printed on your stationery.

Foreign parents, intercompany and moving off Tally or Busy

Indian subsidiaries of foreign groups often join a Business Central tenant run by the parent. Because a Business Central online environment carries a single country localization, the Indian company typically sits in its own environment on the India localization while the parent uses another. That shapes how intercompany invoices, recharges and royalty or service fees are exchanged and how consolidation runs, so I have the partner demonstrate the approach for your version. I also align the Indian chart of accounts with the group's reporting structure through mapping or dimensions, while keeping the April to March statutory year intact. The multi-company ERP page explains the wider pattern.

For domestic groups, the usual starting point is Tally or Busy. Ledgers there tend to mix party names, locations and purposes. I redesign masters before anything moves: a lean chart of accounts with dimensions for plant, branch, department or product line; items with clean units, GST groups and HSN codes; and parties linked to the right registrations. Then we agree what converts as open items, such as unpaid bills on both sides, pending orders, batch-wise stock at each location and TDS not yet deposited, while older vouchers stay in the archive.

I plan cutover away from return deadlines and the year-end close. My data migration service describes reconciliation and sign-off in detail.

Questions for Indian bidders, and when a lighter system is wiser

Bids for Indian Business Central work differ sharply in team experience, in how much custom code they propose and in how they treat statutory change. I read each statement of work and estimate for the points that move cost and risk later: whether statutory updates to GST, TDS and connectors are inside the support fee, whether the connector provider's charges are listed, how much of the effort is customization to recreate Tally screens, whether migration includes open transactions and stock by batch, and how many rounds of UAT are supported. Every gap goes back to the bidder as a written query; my vendor proposal review page lists what I examine.

Equally, I flag it when Business Central is a larger step than the business needs:

• A trader with one GST registration and uncomplicated inventory may do perfectly well with disciplined use of Tally or a cloud accounting tool.
• A company that expects every Tally habit to be rebuilt will end up with a costly, fragile system.
• Without a finance owner for GST masters and TDS setup after go-live, errors will build up quietly.

For the wider Microsoft picture, read Dynamics 365 in India. Platform-neutral advice is on my India ERP consultant page, alternatives are covered under Zoho in India, and the India hub explains how remote engagements work. The ERP evaluation service compares options formally.