Security assignment in insolvency: disclosure, collection and proceeds accounting

Section 48 IO describes a secured creditor as a creditor entitled to separate satisfaction from specified assets of the debtor. In a security assignment, the relevant reference point is therefore the particular receivables pool. The secured party should show receivables, payments and asserted priority separately from the personal claim.

The fact that a receivable was assigned does not automatically authorise payment of every incoming amount to the secured party. The review must establish whether the receivable is covered, whether the assignment was validly created, whether competing rights exist and whether the proceeds originate from the secured pool.

Notify the insolvency administrator of the agreement, schedule and notice position. An ordinary proof of the personal claim does not establish the security right. Conversely, an asserted security proceeds position does not replace proof of an uncovered balance.

Disclosure is a separate control point. For every account debtor, preserve the assignment notice, dispatch, delivery, questions and payments received afterwards. A schedule without evidence of notice shows the asserted pool but does not settle who may collect or receive payment.

After notice, compare the payment route with the agreement and the actual insolvency process. Check whether the account debtor paid the former creditor, the secured party or an account named by the insolvency administrator. Every payment needs an unambiguous allocation; an unexplained pooled amount should not be assigned prematurely to one receivable.

Maintain a collection list with receivable number, account debtor, due date, notice and delivery dates, receipt, recipient and onward transfer. Where collection authority is disputed, agree the interim payment route in writing. The article on insolvency proceedings and litigation addresses a different procedural issue.

Prepare a traceable proceeds statement for collected receivables. Gross receipts, refunds, collection costs, other deductions, transfers and the remaining balance must remain identifiable for each receivable. Section 49 IO shows why costs and priority in a special pool must be reviewed before treating the nominal amount as available proceeds.

Security proceeds reduce the economically open personal claim. If the proceeds are insufficient, calculate the shortfall separately from amounts already received. Sections 48 and 132 IO contain rules relevant to reconciling secured creditors and shortfall creditors in distributions. The same amount must not be counted twice.

Create a new balance after every payment and distribution. It should show which claim is admitted or disputed, what was received from the security and which balance remains an insolvency claim. The creditor document check helps prepare the claim and security records.

Proof of an insolvency claim and reliance on a separate-satisfaction right pursue different objectives. The file should therefore keep the personal claim, assignment, account debtors, collections and shortfall visible as separate but connected entries. This supports reconciliation with the insolvency administrator.

The agreement, schedules, invoices, performance records, notices, delivery evidence, bank statements and proceeds statements belong together for the proof and any later supplement. Mark disputed amounts specifically. An unclear pooled item makes both the assignment review and the shortfall calculation harder.

For the general procedure of proving a claim, the examination hearing and disputes, read proof of an insolvency claim. That process does not replace the separate presentation of the security right.