IT operations for accounting and audit firms.
If your firm keeps the books for foreign-owned companies in Hungary, your clients' head offices expect their financial data to be handled with the same care as at home. We run the IT behind that: servers, backups, access and the Hungarian accounting software, with tighter response times in filing season.
Tighter response in filing season
From 1 January to 31 May, accounting and audit firms get a 2-hour response to P1 issues (server-level or office-level outages) during business hours, and an on-site visit the next business day if needed. The rest of the year the standard 4-hour response applies.
| Case | What it covers | Response time |
|---|---|---|
| P1: outage | A server-level or office-level failure that stops several people working | 4 hours, within business hours |
| Single-user issue | A problem affecting one person, such as one PC or one monitor | Next business day |
| P1 in filing season (1 January to 31 May) | Server-level or office-level failure at accounting and audit firms | 2 hours within business hours, on site the next business day |
Response time means that within this time an engineer starts working on the issue and tells you the next step. It is not a resolution time: how long a fix takes depends on the fault. Business hours are defined in the contract.
The software environment we run
We look after the server, backups, updates and access for the programs below. If the application itself fails, we work on it together with the software vendor, so your staff do not have to sit between two technical parties.
Users inside the software are normally managed by your firm, because that is a professional decision; we can take this over on request.
- NEXON
- NOVITAX
- BKS
- SmartERP
- Kulcs-Soft
- RLB
- Naturasoft
- DATEV
- CaseWare IDEA
- Metrum Referencia
Client data your clients' auditors will ask about
Parent companies and group auditors may ask how client data is protected, so we suggest having three things in place and documented, so the answer can be given in writing.
- Backups following the 3-2-1 rule, verified by test restores.
- Multi-factor authentication for Microsoft 365 and remote access.
- An access register: who can reach what and how, including removal of leavers' access.
Two projects from accounting and audit environments
Shown without client names, using only figures recorded in the project documentation.
Microsoft 365 migration
Exchange 2019 to Microsoft 365 via a hybrid migration, for a 43-user accounting firm
Starting point
The firm ran its email on an on-premises Exchange 2019 server that had fallen behind on updates. Microsoft support for the product ended on 14 October 2025, so the move needed to happen soon, without disrupting day-to-day work.
What we did
- Before the migration we installed the last cumulative update and security fix on the existing server, so it ran on the latest available patch level during the transition.
- We set up a full hybrid configuration and Entra Connect directory synchronisation between the on-premises environment and Microsoft 365.
- Mailboxes moved in waves using remote moves, after the archive PST files had been slimmed down.
In numbers
- users, 45 Microsoft 365 Business Standard licences
- 43
- of mailbox data, plus 6 GB of shared mailboxes
- approx. 622 GB
- of downtime for the pilot moves, with a “Perfect” data consistency score
- 41 s
- from the pilot to the last migration wave
- approx. 10 days
Outcome
All user mailboxes are in Exchange Online; decommissioning of the on-premises Exchange server is in progress.
Copilot data-handling audit
Copilot and AI data-handling audit in the shared Microsoft 365 tenant of an audit-firm group
Starting point
The member firms of the group share one Microsoft 365 tenant, where 13 users ran 3,662 Copilot interactions over 180 days and 9 users uploaded 178 files. The purpose was a read-only picture of data-boundary risks before policy work began.
What we did
- Using read-only Graph, Exchange and Purview queries only, we processed 180 days of Copilot usage.
- We also checked four portal settings by hand; no tenant setting was changed during the audit.
In numbers
- Copilot interactions by 13 users over 180 days
- 3,662
- file uploads by 9 users
- 178
- retention policies, retention labels and sensitivity labels
- 0 / 0 / 0
- decision points in the report
- 4
Outcome
A report on open data-boundary risks, used as the basis for drafting a policy.
Frequently asked questions
Does the 2-hour filing-season response apply to every issue?
No, only to P1 issues, meaning server-level or office-level outages, between 1 January and 31 May during business hours. Single-user issues get a next-business-day response all year. Response time is not resolution time.
Do you fix bugs in the accounting software?
Application bugs are fixed by the software vendor. We handle the server, backups, updates and access, and work through the issue with the vendor on your behalf.
Can our staff speak Hungarian and our reports be in English?
Yes. Your staff can call their named engineer in Hungarian, and reports can be prepared in English where your clients or partners need them.
Worth reviewing before filing season
The quick-check report shows the main risks within 48 hours, leaving time to fix them before January.