Beneficial Ownership Certification Form
Use this Beneficial Ownership Certification Form to collect legal entity details, identify owners with 25% or more ownership, and name one control person for CDD review.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Banking · Fintech · Credit Unions · Commercial Lending · Insurance
Overview
This Beneficial Ownership Certification Form collects the legal entity details, beneficial owner information, control person details, and certification language needed to support customer due diligence workflows. It is built for situations where you need a structured record of who owns the entity, who controls it, and who is attesting to the accuracy of the submission.
Use this template when onboarding a business customer, refreshing an existing file, or documenting a change in ownership or control. The form is especially useful when your team needs a consistent way to gather names, dates of birth, residential addresses, ownership percentages, and the certifier’s signature in one place. It helps reduce back-and-forth by separating entity data from owner data and by making the certification step explicit.
Do not use this form as a general business intake or marketing lead form. It is not meant to collect broad profile information, and it should not ask for extra PII that you will not use. If your policy does not require beneficial ownership certification for a given customer type, or if you only need a minimal contact record, a lighter template is a better fit. The form works best when paired with validation, conditional logic, and a clear explanation of what happens after submission.
Standards & compliance context
- This template supports customer due diligence workflows aligned to beneficial ownership collection requirements under 31 CFR 1010.230.
- The form should follow GDPR data minimization by collecting only the fields needed for verification, review, and recordkeeping.
- If the form is used in a regulated onboarding flow, preserve the certification date, signature, and review outcome in an audit trail.
- Any consent or disclosure language should be clear enough for the certifier to understand what PII is being collected and why.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Legal Entity Information
This section identifies the customer entity so the ownership record is tied to the correct legal name and business profile.
-
Legal Entity Name
Enter the full legal name of the customer entity.
-
Entity Type
Select the legal form of the customer entity.
-
Tax ID Last 4 Digits
Optional. Collect only if needed for internal matching. Do not enter the full tax ID.
-
Primary Business Address
Provide the principal business address.
Beneficial Owners
This section captures the people who meet your ownership threshold and the details needed to verify each qualifying owner.
-
Beneficial Owner Details
Add each individual who owns 25% or more of the entity.
- Owner Full Name
-
Date of Birth
Collect only if required by your customer identification program.
-
Residential Address
Optional. Collect only if needed for verification or regulatory requirements.
-
Ownership Percentage
Enter the percentage owned by this individual.
-
Ownership Type
Select how the ownership interest is held.
Control Person
This section records the individual who controls the entity even when that person does not hold the ownership threshold.
- Control Person Full Name
-
Title or Role
Example: CEO, Managing Member, General Partner, President.
-
Date of Birth
Collect only if required by your compliance program.
-
Residential Address
Optional. Collect only if needed for verification or regulatory requirements.
-
Is this control person also a beneficial owner?
Select yes if the control person is already listed as a beneficial owner.
Certification and Consent
This section creates the attestation, consent, and audit trail that make the submission usable for compliance review.
-
PII Collection Disclosure Acknowledgement
I understand this form collects personal information for compliance purposes, will be used only for beneficial ownership certification and related due diligence, and may be retained in an audit trail according to policy.
-
Certification Statement
I certify that the information provided is true, complete, and accurate to the best of my knowledge.
-
Certifier Name
Name of the person completing and certifying this form.
-
Certifier Title
Title or authority of the person certifying on behalf of the entity.
-
Certification Date
Date the certification was completed.
-
Signature
Provide an electronic signature to confirm the certification.
How to use this template
- 1. Add your entity-specific instructions, required vs optional markers, and a short note explaining what happens after submission.
- 2. Configure the legal entity section to collect only the fields you actually use, with a tax ID field limited to the last four digits if full identification is not needed.
- 3. Set up repeating beneficial owner rows and conditional logic so you can capture each qualifying owner without showing unnecessary fields for entities with fewer owners.
- 4. Assign the form to the compliance, onboarding, or KYC reviewer who will validate the submission, check the certification, and request follow-up if information is missing.
- 5. Review the submission for completeness, store the certification in your audit trail, and route any exceptions or ownership changes into the appropriate case workflow.
Best practices
- Mark required fields clearly and keep optional fields truly optional so the form does not feel like a blanket data grab.
- Use a date picker for dates, a numeric input for ownership percentage, and structured address fields instead of a single free-text box.
- Apply progressive disclosure so additional owner rows or follow-up prompts appear only when the entity structure requires them.
- Explain the consent and certification language in plain terms before the signature field so the certifier knows what they are attesting to.
- Collect only the PII you need for your due diligence process and avoid adding unrelated identifiers that increase privacy risk.
- Include a clear post-submit message that says who reviews the form, whether follow-up may be requested, and how long the record is retained.
- Validate ownership percentages and control-person fields before submission so incomplete or inconsistent certifications do not enter the audit trail.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use a Beneficial Ownership Certification Form?
Use this form when onboarding or reviewing a legal entity customer that must disclose beneficial owners and a control person for customer due diligence. It is typically completed by an authorized certifier for the entity, not by every individual owner separately. If your process only needs a lighter intake, this template may collect more than you need.
What information does this template collect?
This template collects legal entity information, beneficial owner identity details, ownership percentage, ownership type, control person details, and a certification with consent. The fields are structured to support review and recordkeeping without turning the form into a general onboarding packet. It is focused on what is needed to identify ownership and control.
How often should this form be completed?
Complete it at onboarding and again whenever ownership or control changes, or when your policy requires periodic refresh. Many organizations also rerun it during enhanced due diligence or account review if the prior certification is stale. The form works best when paired with a clear review cadence and change-trigger rules.
Who should fill out and sign the certification?
The certification should be completed by someone authorized to speak for the legal entity, such as an officer, manager, or other designated representative. That person should be able to attest that the information is accurate and complete to the best of their knowledge. The signature field creates an audit trail for who certified the submission and when.
Does this form need to collect every owner?
No. The template is designed to capture beneficial owners who meet your threshold, plus one control person, rather than every stakeholder in the cap table. Use conditional logic or additional rows only if your policy requires more than the minimum set. Avoid collecting extra PII that you will not use.
What are the most common mistakes when using this form?
Common mistakes include making every field required, using free text for dates or ownership percentages, and failing to explain what happens after submission. Another frequent issue is collecting more PII than necessary, such as unrelated identifiers, which can create privacy and retention problems. Clear validation and concise instructions reduce rework.
Can this template be customized for different entity types?
Yes. You can add conditional logic for LLCs, corporations, partnerships, trusts, or nonprofit entities if your workflow needs different ownership prompts. You can also adjust the ownership threshold, add document upload fields, or route submissions to compliance review. Keep the core fields aligned to the data you actually use.
How does this fit into existing compliance systems?
This form can feed a case management, CRM, or KYC workflow through integrations or manual review. The key is to preserve the submission record, certification date, and any review outcome in an audit trail. If you connect it to downstream systems, map each field to a clear owner in your process.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
Employee app solutions that close communication gaps, keep frontline teams informed, and help prevent costly corporate crises.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
Discover 7 common intranet platform failures that exclude frontline workers—and the specific capabilities that close the gap for deskless teams.
Ready to use this template?
Get started with MangoApps and use Beneficial Ownership Certification Form with your team — pricing built for small business.
