Follow the daily cash movement on Tochka accounts in chat

The agent works with the Tochka open banking API at enter.tochka.com/uapi: the list of accounts and balances, statements and operations for a period, payments and SBP. Out of that it builds the morning cash movement summary, looks for doubled charges and forgotten subscriptions over the month and puts together a payment calendar where mandatory charges meet expected incoming funds, so a cash-flow gap is visible in advance rather than on the day money runs short.

Data in Open Banking is laid out per account: a statement is requested for a specific account over a specific period, so the agent first lists the accounts of the company and then walks each one — the picture across all accounts is assembled on our side, it does not arrive ready-made. The counterparty name in a statement is whatever the payer typed, so when reconciling against accounting the agent relies on the amount, the date and the requisites, and treats the name string as a hint.

The agent does not handle money: payment signing stays on the bank side, and it cannot withdraw funds by the design of the access, not by agreement. It shows duplicates and stray charges but does not cancel them itself; it matches the Tochka statement against 1C entries and lays out discrepancies in amounts and counterparties, leaving the decision to you. Anything that changes a balance ends with your confirmation in the internet bank.

Statements come back page by page and with a small delay after a transaction is posted, so the agent assembles the morning summary from the closed previous day rather than from the current hour. Account and statement permissions are baked into the key itself, and when they are missing the answer is Forbidden by consent — the agent names that reason instead of passing the emptiness off as an absence of operations. The access period is fixed at issue time and the scheme has no refresh token.