Nigerian Corporate Documents for a U.S. Transaction: Treat Legalisation as a Deal Workstream
When a Nigerian founder is signing into a U.S. company, purchasing a target, opening a business relationship, or appointing someone to act for the company, the most expensive document problem is often the one discovered at the end. The commercial point may already be agreed. The signatory may already be ready. Yet the U.S. recipient may still need evidence from Nigeria in a form it can rely on. That is why document legalisation belongs on the transaction plan early, alongside the ownership, signing, and closing materials.
Nigeria is not a party to the Apostille Convention.[1] A Nigerian document intended for use abroad therefore follows the consular legalisation route rather than the apostille route.[1] The Ministry of Foreign Affairs is the country-side authority identified in the published materials.[2] Those are not merely labels. They tell a founder what not to assume: a document does not become an apostille simply because it is being used in a transaction that also involves the United States.
The right starting point is not a generic document checklist. It is the U.S. recipient’s actual request. A buyer may need proof that a person can sign. A bank may ask for a corporate record. A lawyer may need a document that supports a transaction file. Each request should be obtained in writing and identified by purpose. That gives the Nigerian side a precise target and prevents a team from legalising documents that do not match the recipient’s instructions.
The Difference Between a Corporate Record and a Usable Record
A corporate document can be genuine and still be unusable for the immediate purpose if the recipient cannot accept its form. A careful founder should keep those ideas separate. The first question is what document exists. The second is why the U.S. recipient needs it. The third is what that recipient expects before it will rely on it. Nigeria’s non-membership in the Apostille Convention answers the country-status question; it does not answer the recipient’s individual requirement.[1]
That distinction changes how a cross-border transaction should be managed. Instead of asking only, “Which Nigerian documents do we have?”, the team should ask, “Which document does this U.S. counterparty need, and for what decision?” A document supporting signing authority may have a different purpose from a document supporting company identity. One counterparty’s request may not satisfy another’s. Separate purposes should produce separate confirmations.
The Ministry of Foreign Affairs is the named point of reference for the Nigerian side of the legalisation question.[2] That makes it appropriate to confirm the country-side requirement against the particular document once the U.S. recipient’s written instruction is known. The Ministry’s role in this guide should not be exaggerated into a promise about a particular result. Its relevance is that the published Ministry material identifies it as the country-side point of reference for the document-authentication workstream.
Make the U.S. Recipient State Its Requirements First
The recipient should be asked to identify the document by name, explain why it is needed, and state any current requirements for format, translation, delivery, and timing. A short written request is more useful than an informal suggestion passed through a deal team. It gives the founder a record against which to assess the Nigerian document and allows the country-side inquiry to be framed correctly.
This is especially important where the transaction has several participants. A purchaser, a lender, a service provider, and a lawyer may all be looking at different issues. A founder should not assume that a document requested by one of them satisfies the others. The safer practice is to list the recipient, the document, its business purpose, the requested date, and the response received. That turns document collection into a controlled part of the transaction rather than an exchange of last-minute files.
The recipient also controls its own acceptance decision. The fact that Nigeria uses consular legalisation does not tell the recipient which document it will accept or when it wants it. Asking that recipient directly avoids a false sense of completion. It also helps the founder decide which questions belong to the Nigerian side and which questions belong to the U.S. counterparty.
Legalisation Should Not Be Left Until Signing Week
It is tempting to delay the document question while commercial terms are still under discussion. That can be a mistake. The documents that later matter most are often tied to authority, identity, ownership, or the power to take a particular corporate action. Waiting until the final week can leave the team trying to solve a country-side authentication question at the same time as it is managing negotiations and signature logistics.
A better approach is to create a document workstream as soon as a U.S. recipient identifies the records it expects. The workstream does not need to presume a fixed outcome. It needs only to identify the document, record the recipient’s written request, and direct the country-side question to the appropriate authority. For Nigeria, the project should begin with the premise that consular legalisation is the relevant route, because Nigeria is not an Apostille Convention party.[1]
This also gives the founder a clear basis for communicating with advisers. Rather than asking for a broad answer about “Nigerian paperwork,” the question can identify the actual document and the actual recipient. That is the difference between a general discussion and a request that can be answered in a way that supports a live transaction.
Keep the Record Clear Enough to Reuse
A useful working file has a modest purpose: it lets the team see what has been requested, what has been confirmed, and what remains open. It should preserve the source of each instruction. The U.S. recipient’s instruction should be retained as the recipient-side record. The Ministry of Foreign Affairs inquiry should be retained as the country-side record. The founder’s own decisions should be kept separately from both.
This arrangement is valuable when the transaction changes. A new counterparty, a changed document purpose, or a revised signing plan can create a new document question. The earlier confirmation may still be relevant, but it should not be stretched beyond the purpose for which it was obtained. Keeping the records separate makes it easier to see whether the same question is being asked again or whether a new requirement has emerged.
It also keeps language disciplined. A founder can accurately say that Nigeria is outside the Apostille Convention and that consular legalisation is the applicable route for Nigerian documents used abroad.[1] The founder should not add an unsupported statement about a fee, a turnaround, a translation rule, or an automatic acceptance result. Those points belong to the parties who can confirm the specific document and transaction.
Keep Responsibility With the Party That Can Answer
A founder does not need to solve every document question alone. The commercial counterparty is the right party to explain what it needs for its decision. The Ministry is the country-side point of reference for the legalisation question. Advisers can help the founder make sure that the document described by one party is the same document being considered by the other. This allocation of responsibility is important because it keeps the transaction team from creating a rule that neither the recipient nor the country-side authority has actually stated.
It also makes escalation easier. If the recipient changes its request, the founder can return to the Nigerian workstream with a revised, written description of the document and its purpose. If the country-side answer introduces a question for the recipient, the founder can take that question back with the same record. This does not determine a document outcome. It is a controlled exchange in which each participant is asked to address the point within its own responsibility.
A Practical Closing Rule
The closing rule is simple: do not let an apostille label enter the transaction file for a Nigerian document merely because the broader deal is international. Start with the U.S. recipient’s written requirement. Identify the document’s purpose. Confirm the country-side legalisation question with the Ministry of Foreign Affairs. Keep the evidence of each answer with the transaction materials.
That approach does not make document work glamorous, but it makes it controllable. It gives the Nigerian founder a clear division of responsibility. The recipient defines what it needs. The Nigerian authority is the reference point for the country-side authentication question. The founder and advisers make sure the two are not confused. In cross-border deals, that clarity is more valuable than a generic promise that paperwork will be handled later.
Related guides
References
[1]: https://www.hcch.net/en/instruments/conventions/status-table/?cid=41 — HCCH Apostille Convention status table [2]: https://www.foreignaffairs.gov.ng/services/document-authentication/ — Nigerian Ministry of Foreign Affairs document-authentication service