Optional cookies require your permission.Privacy & cookies

Your first major client wants a company file. What should it contain?

A buyer holding the first invoice wants a company file before paying. Answer the supplier-diligence questions that matter: the registered company, the person authorized to sign, and the Bitcoin or bank payment instructions that were approved.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (3)
Labeled folders and binders stand in rows on open shelves.
In this essay6 sections
  1. Read the request before assembling the folder.
  2. Connect the registered name, the brand, and the person signing.
  3. Select the disclosure instead of exporting the business.
  4. Make the receiving instructions part of the transaction record.
  5. Keep the file current without resending everything.
  6. The Bitcoin Lawyer take

Read the request before assembling the folder.

The first large customer sends a supplier questionnaire, asks for company documents, and puts the initial invoice on hold. The founder responds with everything available: a certificate, an old bank statement, a passport scan, and a screenshot of a Bitcoin wallet. The customer still cannot confirm which company signed the contract. More documents have not answered the question.

Consider a hypothetical UK consultancy trading under the brand Field Office. Its registered name is Field Office Research Limited. A Singapore customer is buying a research project and requests a company file before onboarding the supplier. The example concerns this specific commercial transaction; it does not assume that every customer can demand the same information or that every requested document must be provided.

Break the request into purposes. The customer may need to identify the legal supplier, confirm the signatory’s authority, satisfy an internal ownership check, validate tax information, or verify payment instructions. Ask which record is intended to answer each question. A form labeled company verification may combine several distinct reviews with different recipients and access requirements.

Check the request itself through an established customer contact. A new email asking for sensitive documents or changed payment details should not gain authority merely because it uses the customer’s logo. Record who requested the information, the destination for submission, the relevant transaction, and the deadline. Use the agreed procurement channel where one exists.

Identify who inside the consultancy owns the response. The founder may approve disclosure, the company administrator may supply registry records, the accountant may confirm financial information and another person may verify receiving instructions. Give the customer one coordinated response without pretending that one employee can certify every legal, tax, and financial fact.

Finally, distinguish a required record from a preferred format. If the customer asks for a document that the supplier’s jurisdiction does not issue, explain the available equivalent and its limits. Do not create a certificate with an authoritative title because a questionnaire contains a compulsory upload field. Resolve the mismatch with the recipient before submitting misleading evidence.

Connect the registered name, the brand, and the person signing.

Start the file with a short identity sheet. State the registered entity name, registration number, incorporation jurisdiction, relevant address, trading name, and the contract being reviewed. Link each identifier to its source. This page should make the relationships understandable without asking the customer to infer them from logos on invoices.

For the UK example, Companies House provides access to company information and filed documents, and offers specified certified copies and certificates. Choose the record that addresses the customer’s purpose. A search result, a certificate of incorporation, and a certified document are different outputs. Check what the document actually establishes rather than describing every registry download as proof of good standing.

Existence is not the same as solvency, licensing, or authority to enter this contract. A registry record may help identify a director, but the proposed signatory could be another employee acting under an internal authority. Obtain the appropriate company evidence and professional review where needed. Do not use a formation certificate as a universal answer to questions it does not address.

Reconcile the contract, proposal, and invoice. If the proposal used the brand alone, the signed agreement named the registered company and the invoice contains an old company name, record the inconsistency. Determine the appropriate correction with the people responsible for the agreement. Quietly replacing files can destroy evidence of what the customer actually received.

Check addresses carefully. A registered office, operating location, and billing contact can legitimately differ, but the file should explain their roles accurately. Do not present a service address as staffed premises or invent a local office to make a supplier form look more familiar. If the customer requires a physical operating address, answer that question directly.

The resulting identity chain should be readable in one sentence: this registered company uses this brand, entered this contract through this authorized person, and issued this invoice. Any uncertainty in that sentence is a task to resolve. It should not be hidden by increasing the number of attachments.

Select the disclosure instead of exporting the business.

Build an index before transmitting documents. For each item, record its purpose, intended recipient, source, verification date, redactions, and refresh trigger. The index is useful internally even if the customer does not need every administrative field. It creates a record of why sensitive information left the company.

Ownership information deserves particular attention. Identify exactly what the customer asks for and why, then confirm the applicable disclosure, and data-handling requirements. The appropriate response might be a current ownership statement, specified registry information or supporting identification through a secure channel. It should not default to every owner’s complete personal file.

Separate company records from personal and customer records. A bank statement may contain unrelated transactions and counterparties. A customer contract may contain confidential pricing or personal information. If a limited extract or redacted document can answer the request, obtain the recipient’s agreement and retain the original securely. Redaction should not remove the information needed to understand or authenticate the relevant fact.

Use the same discipline with Bitcoin evidence. A transaction reference or a controlled confirmation of receiving instructions may answer a payment question. A wallet export could reveal unrelated business activity. A seed phrase, private key, or unrestricted account credential is not a diligence document. No procurement process needs the ability to spend the supplier’s funds to identify the supplier.

Apply access controls suited to the material. Limit recipients, use the agreed transfer method, record when access was granted and remove temporary access when appropriate. This is a proposed operating process, not a claim that a particular portal meets every legal requirement. The actual confidentiality and data-protection obligations need review for the parties and information involved.

Preserve a copy of exactly what was sent. File names such as final-final-company-pack do not establish a reliable version. Use a dated index and document identifiers, with any replacement clearly linked to the earlier version. If the customer later asks why an ownership statement changed, the company should be able to answer from its records rather than memory.

Supplier-diligence index for the hypothetical consultancy
RecordPurposeRecipient and handlingRefresh trigger
Registry evidenceIdentify registered companyProcurement; source and retrieval date recordedName or registration change
Signatory evidenceExplain authority for this contractDesignated reviewer; limited relevant extractSignatory or authority changes
Ownership responseAnswer stated ownership requestApproved secure channel; scoped disclosureOwnership or control changes
Invoice and receiving instructionsConnect contract to paymentAccounts payable; independent change verificationAccount or payment method changes
Disclosure logRecord what was sent and acceptedInternal owner; preserve exact versionsEvery submission and correction

Make the receiving instructions part of the transaction record.

The customer has identified the company and now needs to pay it. Compare the contract counterparty, invoice issuer, and receiving account holder. If the names differ, do not assume the difference is harmless because the businesses share an owner. Identify any collection or agency arrangement and have the appropriate people confirm how it should be documented and communicated.

For an ordinary bank payment, use the approved account details, and an independent verification process for changes. Record who authorized the instructions and when they became effective. If the account is held by another entity, the customer may need a clear explanation and supporting authority before paying. Editing the invoice header alone does not establish that authority.

For an optional Bitcoin payment, identify the invoice reference, price currency, payment asset, receiving network where relevant, quote terms, and process for checking payment status. The instructions should come from the authorized checkout or agreed process. A screenshot of an address forwarded through an unverified chat is a poor substitute for a controlled customer payment flow.

Separate the company’s receiving evidence from a claim of completed payment. An issued invoice is a request. Detection, confirmation, accounting reconciliation, and delivery are later stages. BTCPay’s invoice documentation distinguishes payment states; the supplier’s actual integration must be checked separately. The company file should explain the process accurately without claiming a pilot or unavailable payment method is already in general use.

Suppose the customer asks to pay from an exchange account. Record the supported method and explain the information needed if the payment arrives late or cannot be matched. Avoid asking for account passwords or promising an automatic refund to a transaction’s sending address. The support process should verify the actual payment and use the agreed contract and refund procedure.

Before releasing the file, test the full chain with someone who did not prepare it. Can that person identify the supplier, the authorized signatory, the invoice, and the approved receiving process? Can they distinguish a proposed instruction from a completed payment? This short review catches inconsistencies that each specialist may miss while checking only their own document.

Keep the file current without resending everything.

A useful supplier file has a maintenance owner. Set refresh triggers such as a name change, new director, ownership change, revised payment instructions, or a new customer request with a different purpose. A calendar reminder can help, but it should not replace event-driven updates when a material fact changes.

The UK company’s underlying record duties continue independently of this customer pack. GOV.UK guidance for a limited company distinguishes records about the company itself from its financial and accounting records, and it states how long those records must be kept. The supplier pack is a selected disclosure from the records the company holds, not the entire statutory or financial archive. Keeping the two separate makes it easier to provide appropriate evidence without losing control of the original record.

Track the customer’s response. Uploaded, received, reviewed, and accepted are different states. A portal receipt establishes submission, not approval of the supplier or release of the invoice. Record unresolved questions and who must answer them. If the customer has accepted a document only for this transaction, do not treat that as universal acceptance by every future counterparty.

When a correction is required, explain it plainly. Identify the affected document, what changed, and whether the correction alters payment instructions or the contracting arrangement. Preserve the prior version. If the issue concerns a substantive contract or ownership question, route it to the relevant professional rather than allowing an administrator to improvise a legal explanation.

Use the final index as a reusable starting point, with care. Another customer may have a different purpose, jurisdiction, or secure submission process. Reuse verified facts and current documents, then reconsider the disclosure scope. The goal is a controlled response that can be adapted efficiently, not a permanent bundle of sensitive information sent whenever someone asks about the company.

For Field Office, success means the customer can identify the actual supplier and its receiving process, and the consultancy can explain what it disclosed and why. It does not mean the customer has certified the company’s solvency or every aspect of its compliance. A well-prepared file answers the relevant questions while leaving unrelated claims out of the conversation.

The whole picture

The Bitcoin Lawyer take

Build the file around the check the buyer is actually running. Connect the registered company, the trading name, the authorized signer, and the Bitcoin or bank payment instructions, then send only the records that establish those facts.

A thick folder is not supplier diligence. Keep the version you submitted, and replace it when an officer, an address, or a payment instruction changes. Where authority or ownership is unclear, resolve that before asking the customer to pay.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “Your first major client wants a company file. What should it contain?” https://www.bitcoinlawyer.com/journal/your-first-major-client-wants-a-company-file-what-should-it-contain