Month-end close in an accounting firm starts with what is missing. The accountant opens the client's folder in SharePoint or their Outlook mailbox and tries to work out what is absent: a supplier invoice that appears in the SAF-T data but whose original never arrived, the bank statement for the last week, the director's expense report with receipts. Then they write the client an e-mail, a second one three days later, and the client sends everything in one message with twenty attachments that have to be sorted. Ten clients are still manageable, a hundred are not: reminders go out late, the VAT return is filed on the last day, and some invoices turn up after the deadline and end up as amendments.
The agent takes over the chasing. The firm's month-end close calendar and each client's list of expected documents are described in SharePoint. Following it, the agent sends the client an e-mail from the accountant's Outlook with a concrete list: which invoices are missing, which period needs a statement, whose expense report has not arrived. It builds the invoice list not from memory but by comparing what suppliers reported in the e-invoicing and SAF-T data on that client's behalf with what is already in the client folder and in SAP Business One or Sage. The agent reads incoming files, sorts them into the client's SharePoint folders by document type and period, renames them according to the firm's convention and marks what has arrived. The remaining gaps go into a list for the accountant in Teams, with each client's status and the next reminder date. The chief accountant approves the wording and frequency of the reminders, e-mails to clients go out only from an approved template, and the agent does not answer tax questions but passes them to the accountant. We build the agent in Copilot Studio in your Microsoft 365 tenant, and the content of e-mails and attachments, which contains clients' financial data, is processed by a model in MDP CLOUD's private GPU cloud in Lithuania (EU), with no training on your data and with a GDPR-compliant log.