Guides

Continuation of business operations: keeping IT running in insolvency

How insolvency administrators keep IT stable during the continuation of business operations: critical systems, service providers and estate liabilities, key personnel, data preservation and an emergency plan.

A company that is to keep operating in insolvency proceedings needs working systems from day one. Orders are entered in the ERP, wages are calculated with the HR software, invoices are sent by e-mail. If one of these building blocks fails, it is not only operations that are at stake but also the chance of restructuring. At the same time, in a crisis IT is often the area where invoices are the first to go unpaid and staff are the first to leave. IT in the continuation of business operations therefore belongs in the first hours after the appointment. This article shows how to identify critical systems, retain service providers, classify the costs as liabilities of the insolvency estate (Masseverbindlichkeiten) and set up a robust emergency plan.

Why IT determines whether continuation succeeds

Continuing operations until the report hearing (Berichtstermin) is the norm. Under § 157 InsO (German Insolvency Code), it is only the creditors' meeting that decides whether the company is shut down or provisionally continued. Until then the value of the business is to be preserved, because a going concern can as a rule be sold or restructured more easily than a collection of individual assets.

In a modern business, this value is closely tied to IT. Customer relationships live in the CRM, supply chains depend on electronic orders, production machines receive their jobs from the planning software. Even in small trade businesses, quotations, site measurements and invoicing run through an industry solution. An outage of just a few days can drive customers to competitors and deter investors.

Then there is the administrator's perspective: without reliable figures from the systems, neither liquidity planning nor a going-concern forecast can be prepared. IT is therefore not only a tool of the business but also the basis for steering the proceedings.

Identifying critical systems in the first days

Not every system is equally important. For the continuation of business operations, what matters is quickly finding the applications without which the business actually comes to a standstill. A proven method is to ask about failure: what happens if this system is no longer reachable tomorrow morning?

Typical business-critical applications

  • ERP and merchandise management: Order intake, stock levels, delivery notes and invoicing.
  • Financial accounting and payments: Account reconciliation, payment approvals, receivables management.
  • Payroll and HR administration: Pre-financing of insolvency benefit (Insolvenzgeld) and ongoing payroll require correct master data.
  • E-mail and telephony: Communication with customers, suppliers, the court and creditors.
  • Production control and specialist software: Machine control, scheduling, industry-specific programs.
  • Online shop, customer portals and interfaces: Sales channels that cost revenue immediately when they fail.

Making dependencies visible

A system rarely runs on its own. The ERP needs a database server, the database server a virtualisation host, the host power, cooling and network. Many applications also depend on a central directory service for login, on licence servers or on external services. For each critical application, record which components it requires, where they are operated and who looks after them. Only with this overview does it become clear which contracts and people are indispensable for operations.

Prioritisation in three tiers

A rough classification helps with the further work. Tier one covers systems whose failure brings operations to a standstill within a day, such as order processing, payments and production control. Tier two concerns applications without which operations can continue for a few days with restrictions, for example time recording or document management. Tier three comprises systems used only for reports or historical data. This classification determines where contracts are secured, access clarified and backups checked first. Tier-three systems are often candidates for early cost reduction, provided their data has been preserved beforehand.

A simple list with system, location, service provider, contact person, contract status and last successful backup is more valuable in the first week than any detailed IT documentation. It can be updated later.

Retaining service providers: contracts, right of election and estate liabilities

Most companies do not run their IT entirely themselves. IT system houses, software vendors, hosting providers and cloud providers are an integral part of operations. In a crisis, these partners often already have outstanding claims and react cautiously.

Preliminary proceedings

In the preliminary proceedings (Eröffnungsverfahren), the treatment of new liabilities depends on the powers of the preliminary insolvency administrator. If the power of disposal passes to them under § 22(1) InsO, the liabilities they incur are deemed estate liabilities after the opening pursuant to § 55(2) InsO. For a preliminary administrator without a general power of disposal, this is not automatically the case. Here, individual authorisations by the court can be considered, securing specific liabilities, for example for hosting or software maintenance. Which arrangement makes sense in the specific proceedings should be agreed with the court at an early stage.

After the opening

After the proceedings have been opened, the insolvency administrator decides under § 103 InsO, for mutual contracts not yet fully performed by either party, whether to demand performance. If they elect performance, the counter-performance for the period after the opening constitutes estate liabilities under § 55(1) no. 2 InsO. § 108 InsO contains special rules for certain continuing obligations. How individual IT contracts are to be classified depends on the type of contract: a software maintenance contract, a data centre contract and a managed services contract may need to be treated differently. This must be assessed in each individual case. For more on software, see the article Software licences in insolvency.

Keeping liability risk in view

Anyone who incurs estate liabilities must also be able to pay them. § 61 InsO provides for personal liability of the administrator if an estate liability incurred by a legal act cannot be satisfied in full and they could have recognised this when incurring it. For IT contracts this means: commission only the services that are genuinely necessary for operations, keep terms short and reflect the costs in the liquidity planning. A maintenance contract with a long minimum term is rarely the right choice during continuation.

Holding talks with service providers

In practice, the first conversation is often decisive. Service providers want to know whether new services will be paid for. A clear statement on remuneration, a short written order with a manageable scope of services and a fixed contact person build trust. Old claims from the period before the filing, by contrast, generally have to be filed in the schedule of claims (Insolvenztabelle). Linking new services to the settlement of old invoices is problematic under insolvency law and should not be promised without legal review.

Cloud services and subscriptions

Services billed via company credit cards or direct debits deserve particular attention. With the filing, cards are frequently blocked or direct debits returned. Many cloud providers respond to this automatically: after a short period the account is restricted, later suspended and finally deleted. A personal contact with whom a solution could be negotiated is often lacking. Check early, therefore, which services are paid in this way, and switch payment for the services needed to an account of the insolvency estate. For Microsoft 365 and similar platforms, an independent backup is also advisable, as described on the page Cloud and Microsoft 365 backup.

Securing key personnel and knowledge

The greatest weakness of IT during continuation is often not the technology but the staff. The in-house administrator knows the passwords, the quirks of the systems and the arrangements with service providers. If they resign or become unavailable, this knowledge is lost at a stroke.

The following steps have proven effective:

  1. Establish who, internally and externally, holds administrative access.
  2. Have the credentials for central systems handed over in a secure procedure and then change the most important passwords.
  3. Document the recurring tasks: month-end closing in the ERP, payroll run, certificate renewals, backups.
  4. Designate a deputy for each critical system.
  5. Check whether insolvency benefit and, where appropriate, retention bonuses, coordinated with the planning of the proceedings, can help keep key personnel until the report hearing.

The duties of the company's officers to cooperate under § 97 InsO also cover information about IT. This does not apply directly to employed administrators. Here, open communication about the prospects of the business tends to help more than formal demands.

Data preservation as the basis of any continuation

Continuing operations without a current, independent backup is a risk to both the business and the proceedings. If a server fails, an employee deletes data or an attacker encrypts systems, the backup determines whether operations resume after hours or not at all. Then there is the evidential function: the data as at the time of filing will later be relevant for the insolvency avoidance review, expert reports and taxes.

Distinguish, therefore, between two levels. The operational backup keeps ongoing operations recoverable and must run regularly. The cut-off date preservation freezes the data as at the filing or the opening and is stored separately. An insolvency data preservation covers the second level and can be carried out without interrupting operations. How backup, archiving and evidence preservation differ from one another is explained in the article Data preservation, archiving and evidence preservation.

Also check whether the existing backups actually work. In a crisis, backup jobs often fail for weeks because nobody reads the alerts or the storage is full. A restore test on a non-critical file quickly provides clarity.

IT emergency plan for the continuation of business operations

An emergency plan in insolvency proceedings does not need to be extensive. It should, however, exist before the first incident. The following components are sufficient for IT in the continuation of business operations and can be drawn up quickly:

  • Contact list: Internal responsible persons, service providers with emergency numbers, the administrator's office, contact persons at the court.
  • Restart sequence: Which systems must be available again first, for example directory service, database, ERP, then e-mail.
  • Fallback procedures: How orders, delivery notes and payments are temporarily processed manually if systems fail.
  • Security incident: Who decides on disconnecting systems, who informs the data protection supervisory authority, who informs the insurer.
  • Emergency credentials: Where the administrator accounts are deposited under seal and who may open them.

A practical example

In a typical case involving a mid-sized manufacturing business, the only database server fails shortly after the filing. The maintenance contract with the IT system house has been terminated because of unpaid invoices, and the in-house administrator is on holiday. With an existing contact list, a short-term individual order to the system house and an intact backup, operations in such situations can usually be resumed within one working day. If one of these elements is missing, a hardware fault can quickly turn into a production standstill lasting several days.

Controlling costs and preparing for realisation

Continuation is not an end in itself. It is intended to preserve the value of the business until a decision is made on restructuring, sale or closure. For IT, this means stabilising and slimming down at the same time.

Reviewing costs

Many companies pay for licences, cloud subscriptions and maintenance contracts that are no longer used. A review of current direct debits and credit card charges quickly shows which services are active. Unused contracts should be ended after review, but only once the data stored there has been preserved.

Preparing the later transition

An acquirer in a transferring restructuring (asset deal) generally takes over the systems, the data and the staff. Already during continuation, it should therefore be clear which data must remain with the insolvency estate, for example for accounting, tax audits and insolvency avoidance, and which passes to the acquirer. The data remaining behind must still be readable after the transition. For older applications, the virtualisation of legacy systems is a suitable option.

Closure as the alternative

If the creditors' meeting resolves to close the business, the task changes. Orderly shutdown, archiving and realisation of the hardware then take centre stage. These steps are described on the page IT wind-down in insolvency.

How Beweisanker supports the continuation

Beweisanker helps insolvency administrators gain an overview of systems, service providers and access in the first days, and creates an independent cut-off date preservation without interrupting operations. If the continuation lasts longer, we take on technical tasks during the proceedings on request. Details of our services for administrators can be found on the page for insolvency administrators.

For an initial conversation about your proceedings, you can reach us via the contact form.

Frequently asked questions

Does the insolvency administrator have to continue existing IT maintenance contracts?

No, not necessarily. For contracts not yet fully performed by either party, the administrator generally has the right of election under § 103 InsO after the opening. They should check which services are actually needed for continuation.

May an IT service provider suspend its services because of old invoices?

Service providers frequently invoke rights of retention or rights to refuse performance. Whether these prevail in insolvency proceedings depends on the contract and the stage of the proceedings and must be assessed in each individual case. In practice, a clear commitment to pay for future services often helps.

Which IT costs are estate liabilities during continuation?

After the opening, in particular the remuneration under contracts whose performance the administrator demands, and under newly concluded contracts. In the preliminary proceedings, it depends on the powers of the preliminary administrator and any authorisations by the court.

How quickly should a cut-off date preservation be created?

As early as possible after the appointment, ideally in the first days. The longer you wait, the greater the risk that data is altered, deleted or made inaccessible by an outage.

What happens to the IT if continuation fails?

The business is then closed down. The data must nevertheless remain available for retention obligations, tax audits and the insolvency avoidance review. Systems are archived, contracts ended and the hardware realised after secure erasure.

This article is for general information only and does not replace legal advice in individual cases.

Direct line

Urgent preservation?

Call us. We usually agree the scope and next steps during the first conversation.

  • Response usually on the same working day
  • Preservation on site or remotely
  • Binding quotation in advance

Read more

More guides

Liquidating a GmbH: checklist for IT and data from the dissolution resolution to custody of the records

What managing directors and liquidators should do with accounts, cloud, accounting, servers, website, hardware and paper records in each phase of the liquidation, so that nothing is missing once the GmbH has been deleted.

Read article →

Selling customer data in insolvency: value, permissibility, process

How insolvency administrators realise a customer database in an asset deal, which data may be transferred without consent and how the value of a customer base can be estimated reliably.

Read article →

GDPR: insolvency administrators as data controllers

Why the insolvency administrator becomes the controller under data protection law, which legal bases they can rely on, and how to organise access requests, data processing and safeguards.

Read article →

Every day counts.

Talk to us as soon as proceedings are on the horizon. Together we establish which systems are affected and what needs to be preserved first.

Operating nationwide (Germany) · on site at short notice in Baden-Württemberg and German-speaking Switzerland