WhatsApp in accounting firms: how to turn messages into tasks, deadlines and owners

When the client sends an invoice, there may be an accounting period to close. When they ask about tax, there may be a form coming due. When they send new-hire paperwork, there may be a payroll deadline. When they chase a reply about pro-labore, a digital certificate, a simplified-tax payment (DAS), eSocial, or a DCTFWeb filing, there's a task behind the conversation.

The problem is that many firms still treat WhatsApp as informal support.

The client sends something. Someone sees it. Someone replies. Someone forwards it to the internal group chat. Someone promises to check. Then the deadline arrives, the form comes due, the document gets lost, and the team tries to reconstruct what happened.

This isn't a problem of goodwill. It's a problem of process.

Accounting runs on deadlines

Accounting work is recurring, technical, and tied to due dates.

Brazil's Federal Revenue Service maintains a Tax Calendar with deadlines and due dates for tax obligations. On top of that, a firm's routine involves the Simples Nacional and Lucro Presumido tax regimes, payroll, new hires, terminations, pro-labore, invoices, certificates, filings, installment plans, ancillary obligations, and reconciliations.

In other words: the client's message almost always needs to become something.

It needs to become a task, a pending item, an owner, a deadline, a checked document, a technical reply, or a follow-up.

When that doesn't happen, WhatsApp becomes a risky place to keep track of work.

Replying doesn't mean resolving

Replying quickly matters, but it doesn't resolve things on its own.

An agent can reply "we'll check on that" and the request still has no owner. They can confirm receipt of a document and no one still enters it into the system. They can explain a tax form and still not record that the client has an open item.

In accounting, the value lies in operational continuity.

The right question isn't just "was the message answered?" The question is:

• did it become a task?
• does it have an owner?
• does it have a deadline?
• does it depend on a document?
• is it in the right department?
• did the client get a final answer?

Without these answers, the firm confuses service with control.

A message needs a destination

The first adjustment is separating requests by department.

Tax, accounting, payroll, billing, and sales shouldn't compete for the same inbox without classification.

A question about an invoice doesn't follow the same flow as a new hire. A request for a duplicate bill doesn't require the same handling as a termination. A question about the Simples Nacional regime shouldn't land with whoever is handling billing collections.

Examples of routing:

• tax: invoices, tax classification codes, tax charges, DAS payments, calculations, forms;
• payroll: new hires, terminations, vacation, time tracking, eSocial, pro-labore;
• accounting: trial balance, statements, profit distribution, closing, documents;
• billing: monthly fees, invoices, due dates, negotiation;
• sales: new clients, proposals, contracts, onboarding.

This separation reduces interruptions and helps each request reach whoever knows how to resolve it.

A received document isn't a processed document

This is a critical point.

The client sends a document over WhatsApp and thinks it's handled. The firm replies "received" and also thinks it's handled. But operationally, it still needs to be reviewed, classified, entered into the system, saved, linked to the right accounting period, and flagged if there's a pending issue.

Between receipt and processing, there's work.

That's why every message requiring action needs to have:

• the client;
• the type of request;
• the accounting period, when applicable;
• an owner;
• a deadline;
• a status.

Without this, the firm provides service but doesn't have control.

Where Merge fits in

Merge helps accounting firms turn WhatsApp messages into queues, tags, owners and status. This way, the team stops relying on the memory of whoever saw it first and starts working with a process.

WhatsApp remains close to the client. Merge creates the organizational layer behind it.