How it happens today
Once a month an employee merges tax certificates, 1C turnovers and bank movements for 20–50 entities into one table. It takes days. Errors surface at the worst moment — when the company fails the zero-arrears requirement.
What the digital employee does
Pulls turnovers and postings from 1C for each entity through a read-only connection. Reads statements and certificates. Matches by tax and period. Produces an Excel reconciliation: accrued, paid, difference, arrears — with a source log behind every number.
What the business gets
Reconciliation in hours instead of days, before tender documents are filed. A separate list of entities and taxes with missing data — instead of "it seems to add up".
Where the person stays
Obtaining certificates from the tax authority. Deciding on each discrepancy. Correcting the books — in 1C, by the accountant.
What we do not promise
Automatic retrieval of certificates from government systems. Correcting postings. Operation without a connection to the accounting system.
How the effect is measured
Hours per reconciliation. Entities per run. Discrepancies found before filing. The next period is run by the accountant without the developer.
What is needed as input
Entity and tax list, period, read-only 1C connection inside the perimeter, certificates and statements as files by email or into a folder.