A veterinary supply company answers a receivership application with its own paper trail

The situation

The notice of application arrived by process server on a Tuesday morning, while Bikash was reviewing quarterly numbers with the company's bookkeeper. A lender was asking a court to appoint a receiver over the company's accounts receivable and inventory, on the basis that a loan covenant had been breached for three consecutive reporting periods. The document gave the company ten days to respond before a hearing date was set, and it named an insolvency firm the lender had already lined up to take over if the application succeeded.

Bikash and Prakash had built the company together over roughly a decade. Bikash, a veterinarian by training, had started it as a small diagnostics supply operation serving clinics in the region; Prakash, who taught animal science at a university, had come on as a co-owner a few years later, bringing research contacts and a second product line in laboratory equipment. By the time of the receivership notice, the company had grown to somewhere between five and twenty million dollars in annual revenue, with a term loan from an asset-based lender secured against its receivables and inventory, and a staff of several dozen people across sales, warehousing and technical support.

The company was, at that exact moment, in the middle of hiring its first outside executive. For a decade the two owners had run operations themselves, but the business had outgrown that model, and the board had spent months recruiting a chief operating officer from outside the veterinary sector to professionalize the back office and oversee a planned expansion into a second facility. The hire was meant to signal the company had matured past a founder-run shop, and the search had already reached the stage of a signed offer letter with a start date roughly six weeks out.

Instead, the covenant breach — driven mostly by one-time capital spending on new lab equipment ahead of the expansion, plus the onboarding costs of the executive search itself — had tipped a routine financial ratio below the threshold set in the loan agreement. Under the loan documents, that breach on its own gave the lender the right to demand repayment or seek court-appointed control over the company's working capital, regardless of whether the company was actually able to make its regular payments, which it was. Ravi, the lender's regional relationship manager, had signed the affidavit supporting the application, framing the covenant dip as evidence the company's expansion plans had outrun its financial discipline.

What the documents showed

The company's own instinct was to focus on the loan agreement itself, arguing over what the covenant language meant and whether the equipment purchase should have been excluded from the calculation. That argument existed, but it was a hard one to win outright, because the covenant language was reasonably clear and the numbers had, in fact, dipped below it. Bikash's first draft response leaned entirely on that theory, and it was a thin one.

The stronger argument turned out to live somewhere nobody had thought to look first: the company's own sent-mail folder. For roughly fourteen months, the bookkeeper had been emailing a standard monthly reporting package to Ravi's team as a condition of the loan — a package that included the same financial ratios now cited as the default. Pulling that correspondence together showed the ratio had already dipped below the covenant threshold twice in the prior year, without any notice of default, any reservation of rights, or any comment from the lender at all beyond a routine acknowledgment reply thanking the bookkeeper for sending the numbers on time.

That pattern mattered because a lender who repeatedly accepts a borrower's performance without objecting to a known shortfall can be found to have waived its right to treat that same shortfall as a sudden emergency justifying receivership. It does not erase the underlying breach, but it undercuts the claim that the situation had become so urgent, so suddenly, that a receiver was the only answer available. The monthly emails, none of which had been drafted with litigation in mind, turned out to be a more persuasive record than anything the company's own lawyers could have written after the fact, precisely because nobody had shaped them to make a legal argument.

There was a second detail buried in the same correspondence: an email from a member of Ravi's team, sent nine months earlier, describing the earlier dip as 'within the range we'd expect given the equipment cycle' and recommending no action. That single line, never meant to be read by a judge, became the centrepiece of the company's response. It directly contradicted the affidavit's framing of the shortfall as a sudden, alarming departure from the company's normal performance, and it came from inside the lender's own file rather than from anything the company had produced after the fact.

Pulling the full correspondence together also surfaced a pattern in how the lender's internal file had been handled: the account had passed between two different relationship managers during the fourteen-month period, and Ravi, who signed the affidavit, had only taken over the file eight months before the application was filed. He had inherited a relationship history he had not fully reviewed, which helped explain why the affidavit described the shortfall as unprecedented when the company's own records showed otherwise.

What we did

1. Reviewed the loan agreement and the affidavit line by line to identify exactly which covenant was said to be breached, over what periods, and what remedy the lender was claiming under the loan documents — this told us precisely what evidence would matter to a court and let us rule out arguments that were emotionally satisfying but would not actually move the outcome one way or the other.
2. Requested the company's own correspondence file with the lender going back to the start of the loan, rather than starting from the loan agreement alone, because we suspected — correctly, as it turned out — that a receivership application like this one usually turns as much on the lender's conduct over time as on the strict wording of the contract.
3. Built a chronological timeline of every monthly reporting package the company had sent, cross-referenced against any response, objection, or silence from the lender's team, to establish a documented pattern of acceptance rather than relying on memory or general impressions of a relationship that had spanned several years and two different relationship managers, so the argument would stand on dates and attachments rather than on anyone's recollection of how the relationship had felt.
4. Identified the internal handover between relationship managers and requested the lender's own file notes through the correspondence, which surfaced the earlier email describing the prior dip as expected — a detail that would never have been produced voluntarily, that the company would never have known to ask for by name, and that materially undercut the urgency the supporting affidavit was built around once it was placed alongside the sworn account.
5. Prepared a responding record setting out the waiver argument as the lead position, with a secondary argument on the covenant calculation itself kept in reserve, so the company was not relying on a single theory if a judge weighed the waiver point differently than expected, and so the record would hold up even if the hearing proceeded on a narrower question than the one we hoped to argue.
6. Opened a direct, structured conversation with the lender's counsel before the hearing date, sharing the correspondence timeline and the internal email, and proposing a negotiated cure period instead of a contested hearing — receivership applications are expensive and genuinely uncertain for lenders too, and a documented waiver argument gave them a real reason to prefer a quiet settlement over the risk of a public loss on the record.
7. Negotiated a refinancing structure that reset the covenant calculation going forward on more realistic terms, added a short cure period for any future dip before it could trigger default rights, and avoided any admission on the company's part that the earlier breach had been a genuine, unexcused default rather than a technical dip the lender itself had treated as routine.
8. Coordinated the resolution timeline with the executive hire already underway, keeping the incoming chief operating officer's start date on track so the new hire began the role with a resolved lender relationship on file rather than inheriting an open court application, an unresolved covenant dispute, and a company distracted from the onboarding plan on their very first day in the role.

The outcome

The lender withdrew the receivership application roughly six weeks after it was filed, once the correspondence timeline had been shared and a revised financing arrangement agreed. No receiver was ever appointed, and the company's receivables and inventory stayed under its own control throughout, with no interruption to payroll, supplier payments, or client deliveries during the period the application was outstanding.

The refinancing came with modestly tighter reporting requirements than the original loan and a small increase in the interest margin, which the company accepted as a reasonable cost of resolving the matter without a contested hearing. It was not a cost-free result, but it was a fraction of what a receivership, or even a fully litigated response to one, would have consumed in fees, management time, and reputational disruption with suppliers and clinics who relied on the company staying open and predictable. The company also avoided the public record a contested receivership hearing would have created, which mattered for a business whose customers were watching for exactly that kind of instability.

The incoming chief operating officer started on the original schedule, arriving to a company with a cleaner lender relationship and a documented reporting discipline that became part of the standard onboarding package for future financing conversations. One of the new hire's first initiatives was formalizing the monthly reporting process the litigation had relied on, turning what had been an informal bookkeeping habit into a structured internal review that flagged covenant metrics well before they approached any threshold.

Bikash and Prakash kept a version of the correspondence timeline on file afterward, as a reminder that the routine paperwork a business generates every month can matter as much as the contract it is measured against. Neither owner had thought of the monthly reporting emails as anything more than an administrative obligation until the dispute made clear how much weight that record could carry.

What you can learn from this