Beneficial Ownership Certification Form
A Beneficial Ownership Certification Form for collecting legal entity ownership, control person details, and certification in one place. Use it to support customer due diligence with clear consent, required fields, and an audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Banking · Credit Unions · Fintech · Commercial Lending · Regulated Financial Services
Overview
This Beneficial Ownership Certification Form collects the information a legal entity customer must provide to certify ownership and control for due diligence. It is built around the core workflow: acknowledge the purpose, consent to collect PII, identify the entity, list beneficial owners who own 25% or more, name one control person, and capture a signed certification with reviewer notes.
Use this template when you need a repeatable intake for customer onboarding, periodic refreshes, or ownership-change reviews. The structure supports conditional logic, so the beneficial owners table only appears when there are qualifying owners, and the no-25%-owner statement can be used when no individual meets that threshold. That keeps the form shorter and easier to complete while still producing a clear audit trail.
Do not use this template as a general business registration form or for collecting more data than your policy requires. If you do not need a field, remove it. Avoid asking for full identifiers when last-4 or another minimized field is sufficient, and do not collect sensitive details without a clear disclosure and consent step. This template is most useful when your process depends on accurate certification, reviewer follow-up, and a record that can be retained with the customer file.
Standards & compliance context
- The consent-to-collect-PII field supports GDPR Article 5 data minimization by making the collection purpose explicit and limiting unnecessary data capture.
- The form’s structured fields and validation help create an audit trail that supports customer due diligence recordkeeping and internal review.
- If the form is used in a workplace or customer-facing context, ensure the layout and labels meet WCAG 2.1 AA accessibility expectations.
- When collecting identification or date of birth, use the minimum-necessary principle and avoid collecting more than your policy requires.
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
Form Purpose and Consent
This section sets the reason for collection, captures consent to collect PII, and tells the respondent what kind of submission they are making.
- I understand this form is used for beneficial ownership certification under 31 CFR 1010.230.
- I consent to the collection and use of the personal information provided in this form for customer due diligence and compliance review.
- Submission type
- Legal entity name
- Legal entity type
- If other, specify entity type
Legal Entity Information
This section identifies the customer entity and gives reviewers the basic facts needed to match the certification to the correct file.
-
Tax identification number ending
Enter only the last 4 digits if your institution requires it. Do not enter a full tax ID unless specifically required by policy.
- State or country of formation
- Business address
- Date of formation
-
Brief business purpose
Optional. Provide a short description if needed for compliance review.
Beneficial Owners
This section captures the individuals who own 25% or more and supports conditional logic when no qualifying owner exists.
- Does any individual own 25% or more of the legal entity?
- Individuals owning 25% or more
- Beneficial owner details
- No individual owns 25% or more
Control Person
This section identifies the one person who controls the entity, which is essential when ownership alone does not tell the full story.
- Control person full name
- Title or role
- Date of birth
-
Residential address
Collect only if required by your institution’s policy.
- Identification type
-
Identification number ending
Enter only the last 4 characters if needed for verification. Do not enter full ID numbers unless required.
Certification and Review
This section creates the signed attestation and internal review record that turns the intake into a usable compliance document.
- Certifier name
- Certifier title or authority
-
Certification statement
I certify that the information provided is true, complete, and accurate to the best of my knowledge and that I am authorized to submit this certification on behalf of the legal entity.
- Signature
- Date signed
- Compliance reviewer notes
How to use this template
- 1. Set the submission type, entity type options, and required fields so the form matches your onboarding or refresh workflow without collecting unnecessary PII.
- 2. Add conditional logic so the beneficial owners table appears only when the filer indicates there are one or more 25% owners, and show the no-25%-owner statement when needed.
- 3. Configure validation for dates, tax ID last-4, identification last-4, and address fields so the certifier cannot submit incomplete or malformed data.
- 4. Assign the form to the authorized certifier and route submissions to the compliance or onboarding reviewer who will check the certification statement and reviewer notes.
- 5. Review the submission against your due diligence policy, resolve missing or inconsistent fields, and store the completed form in the customer record with an audit trail.
Best practices
- Mark only the fields you truly need as required, and keep optional fields clearly labeled so the form does not over-collect PII.
- Use a date picker for formation date, date of birth, and certification date instead of free text to reduce validation errors.
- Show the beneficial owners table only when the respondent indicates there are qualifying owners, and keep the no-25%-owner statement mutually exclusive.
- Ask for last-4 identifiers where possible rather than full numbers, and explain why each sensitive field is collected.
- Include a clear statement about what happens after submission, including review, follow-up, and record retention.
- Use reviewer notes for exceptions, missing documentation, or clarifications instead of forcing the certifier to guess.
- Keep the certification language aligned with your internal policy so the signer understands what they are attesting to.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this Beneficial Ownership Certification Form?
Use this template when your organization needs a legal entity customer to certify beneficial ownership information for onboarding or periodic review. It is a fit for banks, credit unions, fintechs, lenders, and other regulated businesses that need a structured customer due diligence record. It is not meant for general employee onboarding or consumer intake.
What information does this form collect?
This form collects the entity’s identifying details, the beneficial owners who own 25% or more, one control person, and the certification that the information is accurate. It also includes consent language for collecting PII and a reviewer notes field for internal follow-up. The structure is designed to keep only the fields needed for due diligence.
How often should this form be completed?
Most organizations use it at onboarding and again when ownership or control changes, or during periodic refresh reviews. If your policy requires annual or event-driven recertification, this template can be reused without changing the core field set. The right cadence depends on your risk program and internal review schedule.
Who should fill out and sign the certification?
The form should be completed and signed by an authorized representative of the legal entity, such as an officer, manager, or other certifier with knowledge of the ownership structure. In some workflows, a compliance or onboarding reviewer may also add internal notes after submission. The signer should be able to attest to the accuracy of the information provided.
How does this template handle privacy and PII?
The template includes a consent-to-collect-PII field and uses targeted fields such as last-4 identifiers instead of full numbers where possible. That supports data minimization and reduces unnecessary exposure of sensitive information. If you collect date of birth, address, or identification details, make sure the disclosure explains why each field is needed.
What are the most common mistakes when using this form?
Common mistakes include marking every field required, asking for full identifiers when last-4 is enough, and skipping the no-25%-owner statement when no one meets the threshold. Another issue is failing to use conditional logic for the beneficial owners table, which can make the form too long and confusing. The form should also clearly state what happens after submission.
Can this form be customized for different entity types?
Yes. The entity type and other entity type fields are designed for customization, so you can adapt the form for corporations, LLCs, partnerships, trusts, or other structures. You can also adjust the beneficial owners table, reviewer notes, and certification language to match your internal policy. Keep the minimum-necessary principle in mind when adding fields.
Can this template connect to onboarding or compliance systems?
Yes. It can be routed into CRM, onboarding, case management, or document storage workflows through integrations or export steps. The certification date, reviewer notes, and submission type fields make it easier to trigger downstream review or record retention. If you use automation, preserve the audit trail and access controls around PII.
How is this better than collecting ownership details by email?
A structured form creates consistent field validation, clearer consent, and a better audit trail than ad hoc email threads. It also reduces back-and-forth by prompting for the exact ownership, control, and certification details needed up front. That makes review faster and lowers the chance of missing or inconsistent information.
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...
-
Disconnected cloud apps create friction and waste time. Learn why unified work platforms improve productivity and retention.
-
See how MangoApps employee dashboards unify communications, tasks, and company updates in one personalized workspace — no developer required.
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
Slow decisions cost time and money. Learn how knowledge sharing eliminates analysis paralysis, speeds up decisions, and boosts team productivity.
Ready to use this template?
Get started with MangoApps and use Beneficial Ownership Certification Form with your team — pricing built for small business.
