How do you send invoices and track payments in chat?

In Pachca

1. 1

   Create an Invoices chat and an accounting tag

   + next to search → Chat. Add your managers and accountant. Then go to Members → table view → the tag icon: create an "Accounting" tag. An @Accounting mention in an invoice thread reaches everyone who handles payments.
2. 2

   Create the Invoices bot

   Automations → Integrations → Webhook → +. On the Incoming webhook tab, copy the Webhook URL: your client portal or CRM will send invoice requests to it. Copy the token from the API tab: your handler will need it.
3. 3

   Add the bot to the chat

   Chat settings → Add members → the Integrations tab → Invoices. Only an administrator or the chat's creator can do this.
4. 4

   Turn on the outgoing webhook

   Bot settings → the Outgoing webhook tab. Paste your handler's address from option B or C below into the Webhook URL field and select the Button clicks event. Send a test request to the incoming webhook: a card with a Request invoice button should appear in the chat.

Where requests come from and who issues the invoice

The card comes from your client portal, website or CRM, and a handler issues the invoice when someone clicks the button. Pick one of three options, depending on your setup.

1. A

   No handler yet: a card from your CRM, invoices by hand

   Bitrix24, amoCRM and most CRMs can send a webhook when a deal moves to a new stage. Give them the Webhook URL from step 2 and a message template with the deal fields:

   🚀 {{company}} requested an invoice
   Legal entity: {{legal_name}}
   ИНН: {{inn}}
   Email: {{email}}
   Plan: {{plan}} · {{users}} users
   Period: {{months}} mo · pay by {{pay_by}}

   The accountant issues the invoice in 1С or the bank as usual, drops the PDF in the card's thread and marks the payment with a ✅ reaction. You don't get the buttons from the demo, but setup takes ten minutes.
2. B

   No code with n8n

   A four-node workflow: Webhook receives the button event from Pachca, an HTTP Request node creates the invoice through your bank's API (Tochka and T-Bank both have methods for issuing invoices and pulling statements) or in 1С through an HTTP service, and the Pachca node posts the PDF and a report to the card's thread. A second workflow on a Schedule Trigger pulls the bank statement every hour, finds the payment by ИНН and amount and posts "Paid" in the thread. Paste the first workflow's Production URL into step 4. How to install n8n and the Pachca node is covered in the n8n article in our Help Center.
3. C

   Your own code: bank, 1С and ЭДО in one handler

   Give this skill to Claude, ChatGPT or Cursor. It covers the bot setup, a card with Request invoice and Edit details buttons, a form for fixing billing details, issuing the invoice through your bank's API or 1С, uploading the PDF to the thread, sending it by email and ЭДО, scheduled bank statement matching, the акт after payment and where to host the handler.

   Copy skillDownload SKILL.md

In your team

1. 5

   Agree on who clicks and who keeps an eye on it

   The deal's manager clicks Request invoice and answers the client's questions about it. The accountant follows the thread: if the client is new and hasn't set up ЭДО, they invite them to Diadoc or SBIS and note it in the thread. The ✅ reaction goes on the card only after the акт is sent, so the chat shows at a glance which invoices are closed.

Troubleshooting

• The card doesn't show up in the chat: the CRM has the wrong Webhook URL, or the bot isn't in the Invoices chat.
• The Request invoice button does nothing: Button clicks isn't selected in the outgoing webhook, or the handler is off. n8n needs the Production URL, not the Test URL.
• The invoice is created, but the payment never gets marked: the handler is looking for a different ИНН or amount. Match on the payer's ИНН and the amount without kopecks, since clients write whatever they like in the payment reference.