How run-done works
run-done registers tax invoices and adjustments in ERPN automatically — straight from your accounting system, with no manual DPS-cabinet logins and no middlemen. Below: how it works and the ways to connect.
How it works
- Creation. The invoice/adjustment is created in your accounting system (1C, BAS, SAP, Odoo and others) as usual.
- Transfer. The document is pushed to run-done through the integration — no manual file exports.
- Signing. The document is signed with your KEP locally. The key never leaves your computer or server.
- Registration. The signed document goes to ERPN. Receipts (#1/#2) return to your database, status arrives in Telegram.
On failures, registration retries automatically until a receipt arrives — no action needed from you.
Ways to connect
Add-in for your accounting system
An external add-in for your configuration (1C / BAS and compatible). Installs without touching stock objects — adds a register button right in the document. Fits teams where accountants register invoices from their workstations.
Get the add-inrun-done CLI
A console client for automation: bulk registration, scripting and scheduler integration, unattended server mode. Fits high invoice volumes or scheduled registration.
Get CLI accessSelf-hosted (your own server)
For teams that keep everything inside their own perimeter: run-done deploys on your server in a container (Docker), behind your firewall. KEP and data never leave your infrastructure — maximum control and protection.
Discuss self-hostingSecurity
- KEP stays local. Signing happens on your machine; the private key is never transmitted.
- Your own perimeter. In self-hosted mode, traffic stays inside your network behind the firewall.
- Isolation. Container deployment separates the service from the rest of the system.
- No middlemen. Documents go straight from your system to ERPN.
Need help connecting?
We will suggest the option that fits you and help set it up.