Guides

IT in Debtor-in-Possession and Protective Shield Proceedings

The demands that debtor-in-possession and protective shield proceedings place on IT, and how management ensures proper bookkeeping, transparency and data security vis-à-vis the Sachwalter.

In debtor-in-possession proceedings (Eigenverwaltung), management remains at the helm. That is the great advantage of the procedure and, at the same time, its weak point where IT is concerned. Nobody takes over the systems from outside, and nobody preserves them automatically. Meanwhile, the Sachwalter, the creditors' committee and the court demand reliable figures at short notice, while experienced staff leave the company and IT service providers point to unpaid invoices. This guide sets out the requirements placed on IT in debtor-in-possession and protective shield proceedings and how management can meet them without jeopardising ongoing operations.

Debtor-in-possession and protective shield: who is responsible for IT?

Under §§ 270 et seq. InsO (German Insolvency Code), the insolvency court (Insolvenzgericht) may order that the debtor itself administers and disposes of the insolvency estate. The power of administration and disposal therefore does not pass to an insolvency administrator. Instead, a (custodian) Sachwalter is appointed who, under § 274 InsO, examines the debtor's economic position and supervises the management of the business as well as expenditure on living costs. A special form is the protective shield proceedings under § 270d InsO. Among other things, they require that the debtor is not yet illiquid and that the intended restructuring is not obviously futile. The court sets a deadline for submitting an insolvency plan.

For IT, this results in a clear allocation of responsibility: management remains responsible. It decides on systems, contracts and access rights and must, in doing so, fulfil the duties that insolvency law attaches to the administration of the estate. The Sachwalter does not intervene in the systems personally, but needs reliable insight in order to perform the supervisory role.

In debtor-in-possession proceedings, there is no point at which a third party takes over and preserves the IT. Management must organise and document this task itself from the very beginning.

Management's IT duties at a glance

The duties in debtor-in-possession proceedings go beyond normal business operations. For IT, four areas take priority.

Proper bookkeeping

Bookkeeping obligations under commercial and tax law continue to apply. Financial accounting must be kept promptly, completely and traceably. In practice, this means clearing bookkeeping backlogs, recording all supporting documents without gaps and cleanly separating reporting dates. It is particularly important to separate the periods before and after the insolvency petition, because claims and liabilities are treated differently under insolvency law. How to preserve accounting data from DATEV or from the tax adviser completely is described in the guide DATEV data in insolvency.

Transparency towards the Sachwalter and the creditors' committee

The Sachwalter and the creditors' committee regularly need up-to-date information on revenue, incoming orders, open items and costs. Anyone compiling these reports manually from several systems loses time and produces errors. Fixed reporting formats generated from accounting and the merchandise management system, with documented data sources, are advisable.

Liquidity planning

Liquidity planning is the most important management tool in debtor-in-possession proceedings. Under § 270a InsO, a debtor-in-possession plan, which includes a financial plan covering a period of six months, must be submitted together with the petition. This plan is only as good as the data on which it is based. Open items, payment terms, payroll runs and ongoing contract costs must be reliably retrievable from the systems.

Data access for the Sachwalter

Under § 274(2) InsO in conjunction with § 22(3) InsO, the Sachwalter may enter the business premises, make enquiries and inspect books and business papers. With digital bookkeeping, this in practice means regulated read-only access to the relevant systems or complete exports. A dedicated account with read permissions has proven effective: it is logged and does not rely on employees' personal logins.

Restructuring plans and insolvency plans need reliable data

The aim of debtor-in-possession proceedings is, as a rule, the restructuring of the legal entity, frequently by way of an insolvency plan. In protective shield proceedings, submitting a plan within the court-set deadline is even a central element of the procedure. The descriptive part of the plan describes the company's situation and the planned measures; the constructive part describes the changes to creditors' rights. Both are based on figures: comparative calculations, planned balance sheets, planned profit and loss statements and liquidity forecasts.

Creditors only approve a plan if they trust the figures. Data quality is therefore not a technical detail but a prerequisite for acceptance. Pay particular attention to the following points:

  • Complete master data: customers, suppliers, items and contracts should be cleansed and consistent.
  • Traceable reports: every key figure in the plan should be traceable to a data source and a reporting date.
  • Historical data: comparative calculations and plausibility checks often require several financial years, including data from replaced systems.
  • Documented clean-ups: correcting entries and data clean-ups should be recorded so that auditors can follow them.

IT security in a crisis

A corporate crisis changes the IT risk situation considerably. Typical weak points arise not from new attacks but from changed circumstances.

  • Staff departures: administrators and key personnel leave the company, often at short notice. System knowledge is lost with them, and login credentials are sometimes known only to them.
  • Insider risk: unsettled employees, or those who have already been given notice, still have access to customer data, cost calculations and design documents. The risk of data leaking to competitors or future employers increases.
  • Backups: in a crisis, maintenance contracts are terminated or no longer paid. Backups fail unnoticed, storage is not expanded and restores are not tested.
  • Outstanding updates: when service providers restrict their services, security updates are left undone.

This gives rise to simple yet effective measures: review access rights according to the principle of least privilege, disable rather than delete the accounts of departing employees, change administrator passwords and store them securely, and create an independent insolvency data preservation held outside the production systems. Ongoing technical support during the proceedings is described on the page IT support in insolvency proceedings.

IT service providers in preliminary debtor-in-possession proceedings

Many companies depend on external IT service providers, whether for hosting, maintenance, ERP support or cloud services. In the opening proceedings, the question arises as to how new services can be secured. Service providers who are already sitting on claims from the period before the petition frequently demand security for future services.

In preliminary debtor-in-possession proceedings, the court may, on application, authorise the debtor under § 270c(4) InsO to incur liabilities of the insolvency estate (Masseverbindlichkeiten). Without such authorisation, liabilities from the opening proceedings do not, in principle, automatically become liabilities of the estate. Whether and to what extent authorisation is necessary and advisable depends on the individual case. It is advisable to identify at an early stage the IT services that are indispensable for continued operations and data preservation, and to coordinate them with the Sachwalter and the legal advisers to the proceedings.

Clarify early which IT contracts are essential for continued operations and how their remuneration is secured. An abrupt suspension of services by a hosting provider or ERP service provider can jeopardise both operations and the data situation at the same time.

For contracts outside the ordinary course of business, § 275 InsO must also be observed. Under this provision, the debtor should only enter into such liabilities with the consent of the Sachwalter.

When debtor-in-possession ends: transition to regular insolvency proceedings

Debtor-in-possession proceedings are not a guaranteed path. The court may revoke preliminary debtor-in-possession proceedings under § 270e InsO and debtor-in-possession in opened proceedings under § 272 InsO, for example on application by the creditors' meeting or if circumstances become known that suggest disadvantages for the creditors. An insolvency administrator is then appointed and takes over the administration.

For IT, this moment is critical. The new administrator must get a picture quickly and depends on an orderly data situation. If nothing was documented and preserved during debtor-in-possession, the administrator starts from scratch under time pressure. Management should therefore work from the outset as if a handover could be due at any time:

  1. Maintain an up-to-date overview of systems, contracts and service providers.
  2. Store login credentials centrally, securely and ready for handover.
  3. Create regular, complete backups of accounting, the merchandise management system and email mailboxes.
  4. Archive reports to the Sachwalter and the creditors' committee together with their underlying data.
  5. Record decisions on terminations, deletions and hardware sales in writing.

These precautions also protect the debtor's governing bodies. Anyone who can prove that data was properly preserved is better protected against later allegations. The liability issues that can arise from data loss are explained in the guide Liability for data loss in insolvency proceedings. For the first days after the petition, the checklist for IT preservation after the insolvency petition offers compact guidance that can also be applied in debtor-in-possession proceedings.

How Beweisanker supports debtor-in-possession proceedings

Beweisanker creates independent, documented backups of the systems without interrupting ongoing operations. Management retains control, the Sachwalter receives regulated read-only access where required, and in the event of a transition to regular insolvency proceedings a reliable data basis is available. If you would like to discuss your situation, please get in contact.

Frequently asked questions

Must management give the Sachwalter access to IT in debtor-in-possession proceedings?

Under § 274 InsO, the Sachwalter has extensive rights of inspection and information. With digital bookkeeping, this is implemented in practice through read-only access to the systems or through complete exports.

May the debtor conclude new IT contracts in preliminary debtor-in-possession proceedings?

In principle, yes, within the ordinary course of business. Whether the remuneration is secured as a liability of the estate depends, among other things, on a court authorisation under § 270c(4) InsO. For unusual contracts, the consent of the Sachwalter must be obtained.

What happens to the data if debtor-in-possession is revoked?

The data remains part of the estate and passes into the responsibility of the newly appointed insolvency administrator. What matters is that it can be handed over completely, accessibly and with documentation.

Are there special IT requirements in protective shield proceedings?

The legal duties essentially correspond to those in debtor-in-possession proceedings. Because of the short deadline for submitting the insolvency plan, however, it is particularly important that data can be analysed quickly and reliably.

This guide 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 →

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.

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