Keep tax response deadlines in view across all organisations
Connect Kontur.Extern to the AI agent: organisations, report drafts, docflows, certificates. The agent tracks response deadlines and the status of filed reporting.
How the agent works with Контур.Экстерн
The agent calls the Extern API across every organisation in the account at once: it reads report drafts and the documents attached to them, the docflows with the tax office and the funds together with their response receipts, and the list of signer certificates. Out of that it builds the picture the account never shows on one screen: where the deadline to answer a regulator runs out first, which reports were accepted, which were rejected and which drafts never left before the filing date.
In electronic reporting a submission is not an event but a chain: the report goes out, then the operator confirmation arrives, then an acceptance receipt or a refusal, with hours passing between the steps. A submitted report is therefore not yet a filed one, and the agent keeps those states apart, gathering the rejection reasons into a single list instead of leaving each one buried inside its own docflow. An expiring signer certificate is surfaced early, before it blocks a submission.
The agent does not take on submitting a report for you: filing runs as a chain of asynchronous tasks and requires a qualified electronic signature, which Extern does not create by itself. The agent checks that a draft is complete, verifies the organisation and the form, raises the errors it finds and stops before signing — from there a person with the certificate acts. The whole scenario can be walked through without filing anything on the separate testkontur.ru sandbox with a test certificate.
Every request carries both keys at once — the short-lived token and the permanent api-key — and when the token's hour runs out the agent refreshes it itself without interrupting the analysis. It sees exactly the organisations the account has access to, and walks each of them separately: a summary across a group of companies is assembled from several passes and takes longer than a question about one legal entity. If there is nothing for an organisation over the period, the agent says so directly instead of showing an empty table.
Integration scenarios
Response deadlines for regulators
The agent collects docflows across every organisation in the account and shows where the deadline to answer the tax office or a fund runs out first.
Status of filed reporting
For each submitted report the agent shows whether it was accepted, rejected or is still waiting for a receipt, and gathers the rejection reasons into one list.
Signing certificates about to expire
The agent finds organisations whose signer certificate expires within the next month — before it blocks submissions.
Drafts that were never sent
The agent aggregates report drafts by organisation and form and shows which ones are still unsent as the filing date arrives.
A draft before signing
The agent checks that the draft and its attached documents are complete, verifies the organisation and the form, raises the errors it finds and stops before signing.
A dry run in the sandbox
The agent walks the whole reporting path on the testkontur.ru sandbox with a test certificate — filing nothing with the tax office and touching no production data.
Контур.Экстерн examples
По 11 организациям принято 34 отчёта, 2 отклонены, 3 ждут квитанцию.
- Оба отказа — расхождение ИНН подписанта с сертификатом
- По «Гранд-Логистике» требование ФНС: срок ответа истекает через 2 дня
Показать черновики, которые так и не ушли?
Отчётность по 11 организациям
Table · XLSXHow to connect
Before you connect
- A contract with Kontur — without it production stays closed
- A Kontur account with access to the organisations you need
- A valid electronic signature certificate for the signer
- 1
Submit the request at kontur.ru/extern/api
Use the «Отправить заявку» (Submit request) form at kontur.ru/extern/api. A manager emails the client_id and a key-issuing link.
- 2
Press «Выпустить ключ» on the emailed link
The link opens integrations.kontur.ru — press «Выпустить ключ» (Issue key). The value is a GUID: 8-4-4-4-12 hex characters separated by hyphens.
- 3
Get an Access Token at identity.kontur.ru
The token comes from Kontur's OpenID provider: scope “openid extern.api”, client_id from the email, client_secret is your api-key.
FAQ
With two keys: an access token with the extern.api scope issued by the Kontur OpenID provider, and a GUID-style api-key from the integrations account. Both are opened by a manager after a request on the Extern website — you cannot issue the keys yourself.
Organisations in the account, report drafts and the documents attached to them, docflows with the regulators and their response receipts, plus the list of certificates — within the permissions of the account.
Submission runs as a chain of asynchronous tasks and requires a qualified electronic signature, which Extern does not create by itself. The agent checks and assembles the data, and leaves signing and submission to a person with the certificate.
Yes, the connection supports a separate sandbox address on testkontur.ru with its own account and a test certificate. The production environment is opened under a contract with Kontur.
The agent finds the demand among the docflows, shows the response deadline and assembles the picture around it: what was asked for, which documents already exist, what is missing. Signing with a qualified certificate and the submission itself stay with a person who holds the certificate.