Keep Modulbank balances and transactions under control in chat

The work starts from the reference on companies and accounts: the agent requests account-info, gets the list of legal entities and settlement accounts the token can reach, and moves on to the transaction history from there. Then it calculates balances as of a date, movements for a day or a month, splits outgoing payments by counterparty and category and matches incoming funds against CRM deals to show the won deals the money never arrived for.

Modulbank returns the transaction history page by page and by date rather than in one lump, so a month is collected in parts and kept in the order of the posting date. Foreign-currency and rouble accounts are counted separately instead of being added into a single figure, and money in and money out are told apart by the direction of the payment, not by the sign of the amount in the statement.

On the write side the agent goes only as far as a draft: it assembles a payment order, checks the details, the amount and the purpose and shows it to you, but signing and sending stay in the Modulbank online bank. That is not a connector limitation but how the bank is built — money leaves only after your confirmation on its side. Everything else, from the daily digest to the monthly spend breakdown, the agent does read-only.

The agent holds the request rate itself and spreads a long statement over time instead of firing parallel calls. A period it has already shown is re-read on the next run, because the bank posts entries with a back date and yesterday's balance changes by morning. If there are no transactions for the period or the token lacks access, the agent says so directly instead of showing an empty table.