Request Delay to Present Financial Statement Template

In plain language: Identifies the requesting party (company or individual) and the receiving party (lender, board, regulator, or counterparty) and confirms that the person signing the request has authority to bind the requesting party.

Common mistake: Signing the letter with a personal name only, without confirming the signer's corporate authority. If the signer lacks authorization, the request may not bind the company and the extension may not be legally effective.

In plain language: Cites the specific agreement, covenant, or regulatory provision that imposed the financial statement deadline, and states the exact date by which statements were originally due.

Common mistake: Referencing the agreement by informal name or approximate date. If the citation doesn't match the counterparty's records exactly, they may dispute which obligation the request covers.

In plain language: Clearly states that the company will not meet the original deadline and provides a specific, factual reason for the delay — such as an ongoing audit, a staffing gap, or a material accounting determination.

Common mistake: Giving a vague reason such as 'administrative delays.' Counterparties and regulators expect a specific, documented explanation — vague language signals poor financial management and invites scrutiny.

In plain language: States the specific date by which the company commits to presenting the completed financial statements, giving the receiving party a concrete revised timeline.

Common mistake: Proposing an open-ended or conditional new deadline such as 'as soon as practicable.' A counterparty needs a fixed date to evaluate whether to grant the extension and to schedule their own processes accordingly.

In plain language: Represents that except for the anticipated delay in financial statement presentation, the company is not aware of any other breach of the underlying agreement and remains in compliance with all other obligations.

Common mistake: Omitting this confirmation entirely. Without it, the receiving party may worry that the financial delay is a symptom of a wider compliance problem and may be less willing to grant the extension.

In plain language: Formally asks the receiving party to acknowledge the delay notice and provide written consent to the proposed extended deadline, confirming they will not treat the late presentation as a default during the extension period.

Common mistake: Treating the delivery of the request itself as equivalent to receiving consent. The extension is only effective when the counterparty provides written acknowledgment — do not assume silence is acceptance.

In plain language: Offers the receiving party access to preliminary or management-prepared financial information during the extension period, demonstrating transparency while the audited statements are being finalized.

Common mistake: Making no interim disclosure offer at all. Lenders and investors granted an extension will expect some financial visibility in the interim — a proactive commitment builds goodwill and reduces the likelihood of the extension being refused.

In plain language: Restricts the receiving party from disclosing the reason for the delay or any preliminary financial information shared during the extension period to third parties, protecting the company from reputational or market damage.

Common mistake: Skipping confidentiality provisions when disclosing a sensitive reason such as a material accounting restatement. Without this clause, the receiving party may share the information with co-lenders, other creditors, or market counterparties.

In plain language: Specifies which jurisdiction's law governs the interpretation of the request letter and states how formal notices must be delivered between the parties.

Common mistake: Using a different governing law than the underlying agreement. Inconsistent governing law creates ambiguity about which jurisdiction's courts would interpret the extension arrangement if disputed.

In plain language: Provides signature lines for an authorized officer of the requesting party and a countersignature block for the receiving party to confirm consent, with date fields for each.

Common mistake: Using only one signature line without a countersignature block for the receiving party. Without the counterparty's signed acknowledgment, the extension has not been formally granted and the original deadline remains operative.

A request delay to present financial statement is a formal written communication from a company to a lender, board, investor, or regulator asking for additional time before presenting or filing required financial statements. It identifies the original deadline, explains the specific reason for the delay, proposes a new deadline, and seeks the receiving party's written consent. When properly executed and countersigned, it prevents the delay from being treated as a contractual default or regulatory breach.

Send the request as early as you know the original deadline cannot be met — ideally ten or more business days before the deadline, never after it has passed. Common triggers include an audit running behind schedule, a key finance team member leaving, a material accounting judgment that requires additional time to resolve, or a system migration affecting financial reporting. Proactive notice demonstrates good faith and significantly improves the likelihood of consent.

In most commercial loan agreements, a missed financial reporting deadline constitutes a technical default — even if payments are current. The agreement typically gives the lender the right to accelerate the loan or invoke other remedies. A properly submitted and consented extension request suspends that right for the agreed extension period. Without written consent from the lender, the technical default stands regardless of the reason for the delay.

No. A lender, board, or regulator is not obligated to grant the extension simply because a request was made. However, a well-documented request submitted with lead time, a specific new deadline, a credible reason, and an offer of interim reporting significantly increases the likelihood of consent. In some regulated contexts — such as securities filings — regulators have a formal process for considering extension applications, with defined criteria for approval.

At minimum: the full legal names of both parties, a precise citation of the original obligation and its deadline, a specific and documented reason for the delay, a proposed new deadline stated as a calendar date, a representation that no other obligation is in breach, an offer of interim financial information during the extension period, a confidentiality clause if sensitive reasons are disclosed, and a countersignature block for the receiving party. Missing any of these elements weakens the request and may cause it to be refused or to fail as a legal notice.

Requesting a second extension within the same reporting period is a significant credibility concern for any lender or investor. It signals that the first request underestimated the problem and raises questions about management's control over financial reporting. If a second extension becomes necessary, accompany the request with a detailed root-cause explanation, a concrete remediation plan, and — where possible — a letter from the auditor confirming the new timeline is realistic. Engage legal counsel before submitting a second request.

Yes. The requesting party's authorized officer must sign the request, and the receiving party must countersign to confirm their consent to the extended deadline and agreement not to treat the delay as a default. Without the receiving party's countersignature, the extension arrangement is one-sided and unenforceable. Some agreements specify additional formalities — such as board approval or notarization — for extension consents, so check the governing agreement before finalizing the document.

This template is designed primarily for contractual extension requests between private parties — lenders, investors, boards, and business partners. Regulatory filing extensions (such as SEC Form 12b-25 in the US or equivalent filings with HMRC, ASIC, or SEDAR) are governed by specific statutory forms and procedures that vary by jurisdiction and regulator. Consult the relevant regulatory authority's guidance and consider engaging legal counsel before using this template for a regulatory filing extension.

For commercial loan covenants, lenders typically consider extensions of 15 to 60 days reasonable for audit-related delays, depending on the complexity of the audit and the company's track record. Extensions beyond 60 days attract greater scrutiny and may require additional conditions — such as weekly management reporting or a fee. For shareholder or board reporting, the acceptable range depends on the company's articles of association or shareholder agreement. In all cases, propose the shortest realistic extension and build in a buffer of five to seven days beyond your expected completion date.