CRO B1 Signatures: Wet Ink, ROS and Remote Directors

Electronic filing and electronic signing are different questions

B1 is delivered electronically, but that does not mean every way of putting a name on a PDF is acceptable. CRO's peak-filing instructions distinguish ROS digital signing from a signature page that is printed, signed and uploaded. The upload is electronic delivery of the signed page; it does not change how that page was executed.

Ask the presenter which route applies before asking anyone to sign. Also identify whether the request concerns the annual return itself, a certification of filed accounts or approval of the original financial statements. Those documents can look similar in an email bundle but serve different purposes.

Use the comparison below to frame that conversation. It is not an instruction to switch signing routes on an unfinished live submission or to treat one method as a universal answer for all CRO forms.

• CRO: B1 signature-page and ROS routes

Do not substitute a saved signature or a general e-signature PDF

For the ordinary signature-page route, obtain signatures on the actual page produced for the filing. A scanned signature clipped from a previous return is not the same as scanning the newly signed page. Do not assemble a supposedly signed document by copying handwriting between files.

An earlier CRO forum record specifically discusses copied signature images and a request to consider DocuSign. It records the Registrar's position at that meeting, including the wet-signature requirement on certain forms. It is historical context, not a new 2026 announcement or a general ruling that electronic signatures are unlawful.

The practical basis for this guide is the CRO's current original-signature and supported-route instructions. Do not infer acceptance from a commercial platform's audit trail or from the fact that the same tool worked for a customer contract. If a presenter proposes another method, obtain a clear explanation of its acceptance for the exact document before relying on it.

• CRO: forum discussion of wet signatures and DocuSign
• CRO: original signatures and common B1 errors

Confirm who signs, not just how the signature is applied

Section 134 prevents a requirement involving a director and secretary from being fulfilled by the same person acting in both capacities. In the ordinary officer-signing arrangement, identify two different people and the capacity in which each acts. Two signatures from one founder do not become two signatories because the labels differ.

A corporate secretary needs an appropriate human signatory acting for that appointed entity. CRO's dual-capacity guidance addresses the case where a sole director is also a director of the secretarial company: that does not allow the individual to satisfy both required capacities on the same form.

Check the actual officer record before circulating the page. An accountant preparing the figures, an employee helping with administration or a shareholder without the relevant appointment is not automatically the right officer signatory. Resolve an incorrect or outdated appointment separately instead of changing the name on the signature page informally.

• Companies Act: Section 134, different signing capacities
• CRO: sole directors and corporate-secretary signing

ROS signing is a specific certificate workflow

CRO's ROS help page explains that the certificate must match the expected signatory and the relevant ROS account. It distinguishes the company's director-signing setup from an agent's setup. Having access to ROS for some tax work is not, on its own, confirmation that the certificate needed for this CRO submission is ready.

Have the presenter check the intended signer, certificate status, account and current CORE instructions early. A name mismatch, an expired or replaced certificate, or an incorrectly issued sub-user certificate is a technical problem to resolve through the authorised administrator, not a reason to borrow somebody else's credentials.

Do not email a ROS certificate, password or one-time code to an unfamiliar helper. Agree an authorised support method and protect access to the company's accounts. This guide does not ask you to install software, loosen browser security or change live credentials to complete a filing.

• CRO: ROS certificate, account and signatory checks

A filing-agent engagement is not automatic EFA authority

Section 35 makes company authorisation and notification to the Registrar part of the EFA framework. Paying a provider to prepare B1 is not the same as establishing every authority required for the provider to sign it electronically on the company's behalf.

CRO describes the agent's J1a process and the company's B77 notification, and says only one EFA can hold concurrent authority for a company. Ask whether an existing authority is in place, who it names and which route the presenter proposes for this return. Do not leave an authority handover until the final filing day.

An authorised EFA route can change who electronically signs B1, but it does not make the contents true by itself. The company must provide accurate information and the required supporting documents. Confirm separately which documents the officers still need to approve or certify.

• Companies Act: Section 35, authority before the agent acts
• CRO: Electronic Filing Agents, J1a and B77

Typed names on filed accounts do not replace signed originals

Section 347 distinguishes original documents from the copies annexed to the annual return. It provides for original signatures and dates to appear in typeset form on the filing copy, together with the required director-and-secretary certificate that it is a true copy. That is not permission to invent approval of unsigned draft accounts.

Keep the properly approved original documents and the filing copy linked by version and period. The person preparing the accounts should explain which documents are ready, who signed them and what copy is being attached. A filename containing final is not evidence that approval has actually happened.

CRO's B1 error guidance says an EFA cannot certify the financial statements in that capacity. Where an EFA signs the return and accounts are required, arrange the separate officer certification through the proper route. Do not treat the EFA's electronic signature as a replacement for that certification.

• Companies Act: Section 347, typeset filing copies and certification
• CRO: financial-statement certification and EFA limits

A practical example with a director signing from abroad

Ravi is the sole director of a fictional Irish LTD and is working in Berlin. A separate company secretary is available in Ireland. The accountant has finished the relevant accounts, but nobody has yet agreed the B1 signing method. The wrong shortcut would be to paste Ravi's signature from an old file and assume the accountant can sign the other officer box.

Instead, the presenter first confirms the officer details, approved accounts version, required certification and available filing route. Ravi confirms when he can review and sign the actual documents and obtain a readable scan. The secretary confirms the correct signatory and availability. If EFA signing is proposed, its authority and the remaining accounts certificate are checked before anyone assumes the process is entirely paperless.

The presenter also explains how documents will circulate where signatories are in separate places. Do not assume that separate counterpart sheets or a digitally assembled combined page will be accepted. Agree the required sequence and format for the particular submission. Overseas location calls for planning; it is not an exemption from the signing requirements.

Work back from the complete filing deadline

Section 343 generally requires delivery within 56 days after the annual return date, or after an earlier date to which the return is made up. Accounts-age requirements can also affect the deadline. Have the presenter confirm the actual company dates rather than starting a fresh clock when the signatures arrive.

For example, a company with an ARD of 30 September 2026 may have the familiar 25 November 2026 deadline where the applicable accounts-date conditions are satisfied. That is not the deadline for every company, and an earlier effective return date changes the calculation. Set an internal signing deadline comfortably before the confirmed filing deadline.

CRO says the B1 is not submitted until the payment stage is completed. Sending a signed scan to an adviser is therefore not proof of delivery to CRO. Obtain the submission reference and confirmation, and arrange who will watch for queries. A signature or upload problem should be escalated promptly, not treated as extra time to file.

• Companies Act: Section 343, annual-return delivery period
• CRO: completion, payment and peak-filing timetable
• CRO: effective dates and accounts-related deadlines

Pre-signing checklist for the director and secretary

Give the presenter one agreed contact list and identify any travel, printing, scanning or certificate constraints at the start. Use a secure document channel; do not put passports, PPSNs, certificates or passwords into a general website enquiry. Keep drafts visibly separate from the version released for signature.

• Confirm the company, return date, period and actual filing deadline.
• Check the officer appointments and distinct required signatories.
• Agree signature-page or supported ROS signing before circulation.
• Confirm EFA authority where applicable and any separate accounts certificate.
• Review the final accounts and B1 particulars before signing.
• Use the correct generated page, genuine signatures and readable complete scans.
• Ask whether a change requires a newly generated page and fresh sign-off.
• Retain the final documents, submission reference and filing confirmation.

What to confirm before ordering annual-return support

StartCompany.ie's annual-return service covers the listed B1 preparation and filing support, including attaching financial statements where required. Tell us the company number, recorded dates, signatory locations and whether accounts are ready. Mention an existing EFA or a rejected submission before ordering.

A routine B1 order does not automatically include preparing accounts, setting up ROS certificates, replacing an officer, resolving a disputed signature or obtaining a court extension. Confirm any additional work, the signing route, secure document handover and total payable for the agreed scope.

For a new company's first annual return, Section 349 removes the requirement to annex the statutory financial statements and other Section 347(1) documents. It does not make the first B1 optional or remove its signing process. If a formation package includes first-return support, check whether that particular return falls within the purchased scope rather than assuming every future B1 is covered.

• Companies Act: Section 349, first-return accounts exception