Insolvency and Restructuring Administration Software: What It Costs to Run Appointments Where the Statutory Account Has to Reconcile to the Penny

Why an appointment breaks generic case management

A practitioner takes an appointment on a Friday. From that moment a clock runs that belongs to statute rather than to her diary. Notices must go out within fixed periods. A statement of affairs must be sought. Employees have claims that will be routed to a government scheme and then subrogated back as creditor claims she must recognise. Assets have to be secured, insured and realised. Creditors will write, and some will be represented by solicitors who will scrutinise everything. At the end, money has to be distributed in a strict order of priority, and the account has to reconcile to the last unit because she is personally liable for it.

What most practices run this on is a case management product plus a bookkeeping package plus a shared drive. Turnkey IPS is a serious system built specifically for the profession. Stretto and Epiq operate at large scale in claims administration and noticing for major cases. Those are real tools with real depth. Where they stop is the same place every time: they encode one regime and one way of working well, and a practice handling cross border appointments, unusual security structures, mass consumer creditor volumes or a bespoke distribution waterfall ends up doing the interesting part outside the system in Excel. The interesting part is the part that carries personal liability, which is precisely the wrong part to be doing in a spreadsheet.

Problem 1: the statutory diary belongs to the appointment type

An administration, a liquidation, a bankruptcy and a receivership are not the same case with a different label. Each has its own sequence of statutory acts, its own reporting intervals, its own extension mechanisms and its own consequences for missing a date. In England and Wales the Insolvency (England and Wales) Rules 2016 set out much of this, and progress reports run on fixed anniversaries of appointment. In the United States a Chapter 7 trustee operates under a different structure entirely, with reporting to the United States Trustee and its own forms. A practice that works in both is running two rulebooks.

The build has to treat the diary as generated, not typed. On appointment, the system instantiates the correct statutory task set with dates computed from the appointment date, the case facts and the regime, assigns owners, and recalculates when a date moves because an extension was granted or a court order changed something. Every generated date carries the rule that produced it, so when a junior asks why a report is due on a particular day the answer is a citation rather than a convention. This is not glamorous work and it is the highest value part of the system, because the practitioner's personal exposure is concentrated in dates missed rather than judgements made.

Problem 2: claims arrive as post and have to become a ranked ledger

Proofs of debt arrive by email, by post, on the creditor's own letterhead, from solicitors, from factoring companies who have bought the debt, from a government department claiming preferential status, and from a landlord claiming an amount that includes future rent. Each has to be recorded, checked against the company's books, adjudicated, admitted in whole or part or rejected with reasons, and then ranked. Ranking is where the money is decided: secured creditors, then the statutory order of priority, then unsecured, with the specific classes and any prescribed fund set by the regime.

Generic case management stores documents. What is needed is a claim ledger with adjudication state, evidence attached, a decision with reasons and the person who made it, an appeal or objection path, and an audit trail nobody can rewrite. Duplicate claims are common at volume, and so are assignments where the original creditor sells the debt mid-case and both parties then claim. The system must handle a transfer of claim as an event on the same claim rather than as a new one, or the distribution will pay twice. Extraction tooling has an honest role at high volume: reading a proof of debt into structured fields for a human to confirm removes real clerical cost, but the admission decision stays with a person and the record must show who made it.

Problem 3: estate money is not the firm's money

Every appointment holds funds that are not yours, frequently across multiple accounts, sometimes in more than one currency, sometimes bearing interest that belongs to the estate. Bank statements have to be reconciled per estate, not per firm. Payments require dual authorisation. Receipts and payments accounts have to be producible on demand in the statutory format and must agree with the bank to the unit.

Practices that bolt this onto a general bookkeeping package end up with a chart of accounts per case and a reconciliation ritual that consumes a cashier's week. The right model is an estate ledger as a first-class object with its own bank accounts, its own opening position, postings that carry the case, the transaction type and the statutory classification, and automated bank feed reconciliation with exception handling. Build the receipts and payments account as a generated statutory output from that ledger rather than a report someone formats. When the account and the bank disagree, and they will, the system should show the unmatched items and their age rather than requiring a human to find them.

Problem 4: time costs are how you get paid and how you get challenged

Remuneration on a time cost basis is approved by creditors or a committee and then scrutinised. In the United Kingdom, Statement of Insolvency Practice 9 sets expectations for the information provided to those approving and reviewing fees, including disclosure by grade and by category of work. That means time recording is not an internal management tool, it is evidence, and narrative quality on a time entry has consequences months later when a creditor committee questions the charge.

The system should capture time against the case and a defined work category, hold the charge-out rate applicable at the date the work was done rather than today's rate, and produce the fee analysis in the format required for approval. Write-offs and write-ups need to be visible with reasons. The report a committee sees should be generated from the same data the practice manages itself with, because the moment those diverge somebody is reformatting numbers under time pressure and errors enter there.

Problem 5: creditor communication at volume is its own system

A trading business failure can produce thousands of creditors, many of them consumers with deposits, all of whom write, call and want to know when they will be paid. The default handling is an inbox and a spreadsheet, and it collapses at exactly the moment public attention is highest.

Build a creditor portal with claim submission, status visibility and document access, backed by a bulk noticing capability that records what was sent, to whom, when and by what channel. Proof of service matters: in a contested case the question of whether a creditor received a notice is not academic. Keep an inbound correspondence log linked to the claim so that a query from a creditor's solicitor can be answered with the history rather than a search of somebody's mailbox. For large consumer cases this is the difference between a practice that can take the appointment and one that cannot.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape for insolvency administration software. A focused first release covering case creation with generated statutory diaries, claim capture and adjudication, and the estate ledger with receipts and payments runs $90,000 to $180,000 and ships in 14 to 20 weeks. A full platform adding time recording with fee analysis, the distribution engine with priority waterfalls, creditor portal and bulk noticing, bank feed integration, statutory report generation and migration of live cases runs $250,000 to $550,000 phased over 9 to 15 months.

What drives price up in this sector: the number of regimes and jurisdictions, because each is a separate rule set for diaries, priority order and reporting formats. Bank integration, since estate accounts often sit with specialist providers whose feeds are not standard. Creditor volume, because a case with fifty creditors and a case with fifty thousand are different engineering problems. And migration of live appointments, which is unavoidable and delicate: you cannot pause an administration while you move it, so expect parallel running per case with a reconciliation sign-off before each one is cut over.

Build versus buy, and when Turnkey IPS is the right answer

Buy, and do not call us, if you are a practice working in one jurisdiction with conventional appointment types and creditor volumes in the ordinary range. Turnkey IPS was built for exactly that and covers the statutory apparatus properly, and no bespoke build will reach that depth for the money. If your volume is in large corporate cases with mass claims administration and noticing, Stretto and Epiq exist because that scale is a specialised operation and outsourcing it is often the commercially sound choice.

Build when two or more of these are true. You take appointments under more than one regime or in more than one jurisdiction and your current system covers one properly. Your distribution waterfalls include structures a standard priority ordering does not express, which is common where security packages are layered or where an estate spans entities. Your practice handles high consumer creditor volumes and the correspondence load is capping how many appointments you can accept. Your cashier team is reconciling estate accounts through a general bookkeeping package with a chart of accounts per case. Or you are already doing the adjudication and distribution modelling in Excel, which is the moment to stop, because that is the work you are personally liable for.

How to choose a developer for insolvency software

Ask them how a statutory date is calculated and what happens when it moves. The answer should describe rules attached to appointment type and regime, dates generated with the rule recorded, and cascade recalculation when an extension is granted. If they propose a task template someone copies per case, they have built a to-do list and you will still be checking dates by hand.

Ask how they model a claim that is assigned to a third party halfway through the case. If the answer creates a second claim, the distribution will double pay and someone will notice at the worst possible moment. You want a transfer event on the existing claim with the full history preserved.

Ask about the estate ledger specifically. Multiple bank accounts per estate, dual authorisation on payments, statutory classification on every posting, and a receipts and payments account generated rather than formatted. Ask to see how unmatched bank items are surfaced and aged.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire another firm. At Digital Heroes the code is yours from the first commit. Cases outlive software vendors, and a system holding the statutory records of appointments that may be reviewed years after closure should not be something you can lose access to because of a commercial dispute.