A message saying that your Irish company's annual return has been sent back needs attention now, not when the next annual reminder arrives. The important question is what the CRO has actually issued: a correction notice, an outright rejection or an identity-validation problem. Those situations are not interchangeable.
This guide helps directors and company secretaries organise a returned Form B1, work with their presenter and avoid repeating an error. It is not a substitute for the company's notice or advice on a disputed deadline. Keep the actual submission reference and company record in front of you while deciding what to do.
Start with the notice, not the word returned
Save the complete message, attachments, date, reference and reason given. If an accountant or filing agent presented the B1, ask them to share the notice and current status rather than summarising it as a small admin issue. Identify who is managing the response and who will check that the final submission is complete.
Make a short issue list in plain language. For example: the officer details disagree with the register, an accounts date differs from the B1, or a certification is missing. Separate each issue so one correction does not distract from another. Ask the presenter or CRO for clarification if the message does not identify a usable next step; do not keep sending the same files unchanged.
Understand the 14-day correction rule and its limits
Section 898 of the Companies Act 2014 allows the Registrar to issue a notice identifying non-compliance. If the required replacement is not received within 14 days after service of that notice, the original document is treated as not delivered. The provision is not an automatic extra fortnight for every failed filing. Read the notice to establish whether this process applies to your return.
Have the presenter confirm the deadline against the actual notice, including when it was served. Do not count from the day the director happened to open a forwarded email. Plan to finish before the last day, allowing time for officer signatures, revised documents and a second review. A reminder in a calendar is useful, but it is not evidence that a compliant replacement reached the CRO.
Some failures do not receive a correction window
The CRO says that an unsigned B1 signature page or overall certificate, or one carrying only one signature, is automatically rejected without the Section 898 amendment period. It also describes rejection without that period when required financial statements have not been uploaded before the signature page is received. Do not assume an error of this kind can be fixed under a general grace period.
Ask whether a fresh submission is needed and how its delivery date affects the company's deadline. Paying a fee or starting a form is not proof of a complete filing. If the ordinary deadline has passed, obtain advice promptly on the consequences and available options rather than asking the presenter to describe an incomplete submission as on time.
Use this triage table to assign the next action
The table is a working checklist, not a decision by the Registrar. Match it to the wording of your notice. Where several people are involved, record a responsible person and a target completion time for every action instead of forwarding the message to a group and assuming someone will fix it.
| Problem shown | Who to involve | Check before proceeding |
|---|---|---|
| Correction notice | Presenter and company officers | The notice, deadline and every listed defect |
| Rejected signature or missing attachment | Presenter and relevant signatories | Whether a fresh complete submission is required |
| Director identity mismatch | Affected director and presenter | The official details behind the mismatch |
| Accounts or exemption issue | Accountant and directors | The correct approved documents and eligibility |
| Officer record mismatch | Company secretary or adviser | Whether a separate officer filing is outstanding |
| Deadline already missed | Company adviser promptly | Late-filing position and any lawful relief route |
Resolve an identity mismatch without guessing
The CRO's B1 identity guidance describes a submission being held where a director's name, birth date or PPSN/IPN/RBO information does not match official records. For a PPSN, check the Department of Social Protection details; for an IPN, check the details supplied in the VIF application and the number issued. Use the feedback facility described by the CRO to identify the affected director.
Have that director confirm the relevant information through the proper secure channel. Repeatedly changing spellings, dates or numbers until something passes is not a sensible correction method. Do not put a PPSN, identity document or login credential into a general contact message. If the underlying record needs clarification, use the official route indicated in the CRO guidance, and keep the presenter informed about progress.
Match the B1 dates and officer details to the records
CRO common-error guidance identifies mismatched financial-year dates, a return made up beyond the ARD and signatories not recorded as current officers. Compare the actual B1, financial statements and CRO officer record side by side. If the company has changed a director or secretary, check the separate notification rather than treating a B1 as a replacement for it.
Write down the verified value and its supporting record before editing. Ask the accountant to resolve an accounts-period discrepancy; do not rewrite an approved financial statement merely to match a mistaken form field. A clear change log helps the officers review what they are certifying and allows the presenter to explain exactly what was corrected.
Check the financial-statement pack and certification separately
Section 347 sets out the documents to accompany an annual return, subject to applicable exemptions, and the director-and-secretary certification of true copies. Do not assume that uploading an accounts PDF alone covers every requirement. The accountant should identify the correct filing pack and any applicable exemption, while the presenter checks that the correct version is attached.
Use a final, agreed version with its required names, dates and statements. Check that every page opens, the period is correct and no pages are missing. Do not copy an exemption clause from another company's accounts without checking entitlement. CRO guidance distinguishes an Electronic Filing Agent signing an authorised B1 from the separate officer certification of the financial statements. Confirm which signing route is being used.
Resubmit the corrected return, not an old signature page
For a sent-back B1, CRO guidance describes resubmitting the form, re-uploading the financial statements and producing a new signature page for signing and upload. The usual officer route requires the director and secretary to be different signatories. Follow the actual CORE instructions for the submission and any authorised agent route, rather than reusing a page generated before the corrections.
Give the signatories enough time to review the final particulars. Keep obsolete versions clearly separate so the presenter does not accidentally attach an earlier accounts file or signature page. After resubmission, preserve the reference and delivery evidence, and check for further messages. Monitor the presenter's email as well as the company's own correspondence until the issue is resolved.
A fictional example: two corrections, not just one
Suppose a consultancy receives a notice identifying an accounts-period mismatch and an officer-record problem. The director asks the accountant to verify the correct accounting period, while the secretary checks the appointment records and earlier CRO notification. The presenter keeps one issue list, confirms the notice deadline and waits for both problems to be properly resolved before generating the corrected submission.
Changing the date field alone would leave the second defect untouched. Equally, changing the officer record does not establish that the accounts attachment is correct. The useful approach is coordinated review of the whole filing. This example illustrates organisation only; it does not establish that either defect in a real company qualifies for a particular correction period or guarantee acceptance.
If the deadline is missed, do not assume an automatic waiver
Section 343 provides the usual 56-day delivery period after the annual return date, or an earlier effective date if the return is made up earlier. It also provides for a court order extending time for a particular return. That is a separate legal process, not something created by buying filing support, correcting a typo or contacting the CRO helpdesk.
Take the notice, submission history and company calendar to an adviser promptly. Ask what must happen next and whether a court application is appropriate before making assumptions about timing. Do not delay a necessary decision while waiting for a hoped-for waiver. A service enquiry does not stop a statutory clock, and a court's decision cannot be promised.
Use the current audit-exemption rule when assessing consequences
Older summaries sometimes describe every late return as automatically causing two years without audit exemption. The CRO's dedicated guidance states that the repeat-lateness rule effective from 16 July 2025 applies where returns are late more than once in a five-year period, with loss for the following two years. Other eligibility and transition questions still need review.
Ask the accountant to assess the company's actual filing history and entitlement, rather than relying on a blanket statement in an old checklist. A first late filing is not harmless: fees and other compliance consequences may still arise. Equally, an exemption should not be abandoned without checking the applicable facts. Record the advice and keep supporting evidence with the annual-return file.
Final checklist before you close the correction task
Do not mark the job complete simply because a PDF has been sent to the presenter. Review the evidence and agree who checks the outcome. Keep the notice and corrected documents together, with a brief explanation of the change, so a future accountant or secretary can understand what happened.
- The submission status and notice have been reviewed, with the applicable response deadline confirmed.
- Every stated defect has an owner and a documented correction.
- Officer particulars, accounting dates and identity information have been checked against reliable records.
- The approved attachment pack and correct signing or certification route have been used.
- The complete corrected or fresh submission has delivery evidence and an identifiable reference.
- Someone is monitoring the final status and any further CRO correspondence.
- Any separate accounts, officer filing or late-deadline matter has its own agreed next action.
Arrange the right annual-return support with StartCompany.ie
StartCompany.ie provides annual-return preparation and filing support and works with authorised partners to provide its services. If a return has already been sent back, explain that at the start. Share the company number, reason for return, relevant dates and whether an accountant has prepared the required statements. Ask the team to confirm availability and scope before relying on a completion date.
Check the annual-return product page for the current total payable. Accounts preparation, audit work, separate officer changes and court applications should not be assumed to be part of a routine B1 filing. Where your case needs different work, agree it first. Buying the service does not itself resubmit the return, extend a deadline or guarantee CRO acceptance.
StartCompany.ie service
Annual Returns
Official information and next steps
Primary sources checked on 9 October 2026. This general correction checklist does not determine your company's deadline or audit-exemption entitlement. Follow the actual notice, current CORE instructions and advice for the specific filing. For audit consequences, use the dedicated current CRO audit-exemption guidance rather than older blanket wording on other pages.