How do you handle assignments and invoices for самозанятые and ИП?

In Pachca

1. 1

   Create a Contractors chat

   + next to search → Chat. Add your accountant and the managers who work with contractors. Invite the contractors themselves as guests: Info → Add member → email. A guest only sees this chat and replies in the thread for their assignment.
2. 2

   Create the HR Assistant bot

   Automations → Integrations → Webhook → +. On the Incoming webhook tab, copy the Webhook URL: your КЭДО will send notifications about new invoices and receipts 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 → HR Assistant. 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. Trigger a reminder manually: a card with a Generate assignment button should appear in the chat.

Where reminders and documents come from

Assignment deadlines, the document template and sending to КЭДО all live in the handler. Pick one of three options, depending on your setup.

1. A

   No handler yet: a template and reminders in Pachca

   Pin a docx assignment template and a contractor table with deadlines in the chat. When a manager posts a new assignment, the accountant reviews it in the thread and sets a reminder on the message: message menu → Remind me → three days before the deadline. Signing, invoices and receipts go through КЭДО by hand, and the link to the document goes in the same thread. You don't get the buttons from the demo, but setup takes ten minutes.
2. B

   No code with n8n

   Two workflows. The first runs once a day on a Schedule Trigger, reads the contractor table (Google Sheets or your own database), finds assignments ending in three days and posts a card with a button through the Pachca node. The second takes button clicks through a Webhook: on Generate assignment, it fills in the docx template (an HTTP Request node calling a templating service like Carbone, or Google Docs) and drops the file in the thread; on Send for signature, it calls your КЭДО's API. The КЭДО notification about a new invoice or receipt hits the bot's incoming webhook with this template:

   📄 New {{document_type}} from {{employee_name}}
   @accountant @manager
   Open document: {{document_url}}

   Paste the second 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: deadlines, docx and КЭДО in one handler

   Give this skill to Claude, ChatGPT or Cursor. It covers the bot setup, the contractor table, scheduled reminders, generating the assignment from a docx template with the amount grossed up for tax, Send for signature and Edit buttons, integration with HR-Link or another КЭДО, receiving invoices and receipts, and where to host it all.

   Copy skillDownload SKILL.md

In your team

1. 5

   Agree on who reviews and who clicks

   The bot loops the contractor, the accountant and the manager into the thread. The accountant checks the dates and amount before anything goes out, and the manager clicks Send for signature only after they say “ok” in the thread. Once paid, the contractor uploads the invoice, акт and receipt from “Мой налог” to КЭДО, and the bot brings them into the assignment thread and updates the status card. The ✅ reaction goes on the card once all three documents are in, so you can see at a glance which assignments are closed.

Troubleshooting

• The reminder doesn't arrive: the contractor table has no end date for the assignment, the scheduled workflow is off, or the bot isn't in the chat.
• The Generate assignment 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.
• Invoices and receipts don't show up in the chat: КЭДО sends notifications to the wrong Webhook URL, or the message template isn't filling in the document link.