Busy Accounting WhatsApp Integration - Invoices, GSTR-1 Statements & Hindi Templates

No, your Busy database never leaves your premises. The ERPPlugs Busy-WhatsApp connector installs a signed Windows agent on the same machine (or a machine on the same LAN) as your Busy installation. The agent reads only the fields required to send a WhatsApp message — invoice number, party name, phone, amount, due date, GSTR-1 outward supply summary — and transmits those over TLS 1.3 to the ERPPlugs cloud for delivery. Ledger detail, purchase register, general journal, and payroll data never leave the agent. This is important because most Busy customers are traders and MSMEs who explicitly do not want their books on the cloud.

Yes, all WhatsApp Business Message Templates are pre-approved in Hindi, English, and Hinglish, and the connector auto-selects the language based on the state code in each customer's Busy party master. A party in Uttar Pradesh receives Hindi templates by default; a party in Karnataka receives English; a party in Mumbai receives Hinglish. Language selection is overrideable per party from the ERPPlugs dashboard for customers who explicitly prefer one language, and new custom templates can be submitted in any Meta-supported language on request. This matches how North Indian traders actually communicate with their downstream buyers.

Multi-branch Busy installations — where head office and branch offices share a database — are directly supported. Each Busy branch can bind to its own WhatsApp Business phone number, so a Delhi head office sends from its registered WABA and a Kanpur branch sends from its own. Party masters, invoice numbering series, and aging reports remain per-branch as configured in Busy, and the ERPPlugs dashboard shows delivery stats per branch. This is important for traders with multiple GST registrations across states, where mixing WhatsApp senders across state boundaries can cause customer confusion.

Yes. On the 11th of every month (or a date you configure), the ERPPlugs Busy-WhatsApp connector pulls your Busy GSTR-1 register — B2B outward supplies, B2C large invoices, credit notes, HSN summary — and delivers a formatted summary to your CA's WhatsApp with the raw JSON or Excel attached. This is a genuine time-saver for the CA workflow, which currently involves the trader emailing an export or the CA remote-desktopping into the Busy machine on the 10th of every month. The template can be routed to multiple CAs and can include a link to a shared Google Drive folder if you prefer file drops.

The ERPPlugs Busy-WhatsApp connector supports BUSY 21 (latest), BUSY 18, and BUSY 17. Any Busy version that exposes the standard ODBC driver is compatible. The Windows agent auto-updates when Busy releases a maintenance patch — you do not need to reinstall the agent after a Busy upgrade. Perimattic's solutions team maintains a compatibility matrix and will notify you in advance if a major Busy upgrade requires an agent-side change. Windows Server 2016 and later, and Windows 10/11 on the accountant's desktop, are supported host OSes.

No. The agent uses read-only ODBC queries and never holds a write lock on the Busy database. Concurrent voucher entry by your accountants is unaffected. The polling window is configurable (default every 5 minutes for invoices, every 15 minutes for masters) and can be scheduled around your peak entry hours if your database is very active. Busy's own multi-user session limits are unchanged — the agent counts as a read-only connection and does not consume a Busy user seat.