Saint Lucia KYB, Without the Back-and-Forth: A Broker-Ready Entity Checklist

KYB (Know Your Business) is where many broker and prop firm onboarding timelines quietly slip—especially with offshore entities where ownership and authority need to be crystal clear. If you’re using a Saint Lucia entity (or onboarding one as a counterparty), the fastest path is not “more documents,” but the right set of documents, packaged in a way that answers the reviewer’s questions upfront.

Below is a broker-ready KYB checklist focused on four friction points that trigger most follow-ups: UBOs, directors, proof-of-address, and corporate resolutions. Treat this as general guidance—requirements vary by bank, PSP, liquidity provider, platform vendor, and regulator, and they can change.

1) Start with a “KYB cover pack” (what reviewers want in 60 seconds)

Before you upload individual files, create a simple cover pack that lets a compliance analyst understand the entity at a glance. This reduces ping-pong emails because it pre-answers: Who owns it? Who controls it? Who can sign? What’s the business model?

Include a 1–2 page PDF summary with:

• Entity legal name, registration number, incorporation date
• Registered address and principal place of business (if different)
• Business activity (e.g., brokerage, prop firm, technology services) and key counterparties (high level)
• Ownership chart (even if simple)
• List of directors and authorized signatories
• A table of enclosed documents (filename + date)

Packaging tip: name files consistently (e.g., 01_Certificate_of_Incorporation.pdf, 06_UBO_Passport_John_Doe.pdf). Reviewers move faster when the pack reads like an index, not a folder dump.

2) UBOs: prove beneficial ownership (and make the structure easy to audit)

UBO review is where Saint Lucia entities can slow down—not because they’re “problematic,” but because ownership can be layered (holding companies, nominees, trusts, multiple jurisdictions). Your goal is to make beneficial ownership auditable.

Provide for each UBO (typically anyone meeting the reviewer’s threshold):

• Government-issued photo ID (passport is usually the cleanest)
• Proof of residential address (see the POA section for formatting)
• Source of wealth/source of funds evidence if requested (common for higher-risk profiles)

Also provide at the entity level:

• A clear ownership declaration (signed) stating UBO names, % ownership, and control basis
• An ownership chart showing every layer from the Saint Lucia entity up to the natural persons
• If a corporate shareholder exists: corporate documents for that shareholder (registry extract, directors, shareholders/beneficial owners) until you reach natural persons

Common follow-up triggers to avoid:

• Ownership chart doesn’t match shareholder documents
• Missing “control” explanation when ownership is indirect (e.g., voting rights, shareholder agreements)
• UBO address document is not readable, not dated, or doesn’t match the name format on ID

3) Directors & controllers: verify the people who run the company

Brokers and prop firms often focus on UBOs and forget that directors and controllers are a separate KYB track. Many providers require verification for all directors and sometimes key officers (e.g., CEO, compliance lead, operations lead), even if they are not owners.

For each director (and any required controller):

• ID document (passport/national ID)
• Proof of address
• Basic role confirmation (appointment evidence or registry extract listing directors)

Operationally, you want to remove ambiguity around authority:

• If one director will sign everything, make sure the signing authority is explicitly documented (see resolutions below).
• If there are multiple directors, clarify whether the company requires joint signatures or any one director can sign.

Practical example: If your bank mandate requires two signatures but your KYB submission includes only one director’s ID, expect a delay. Align the “who can sign” story across your corporate documents, resolutions, and any mandates.

4) Proof-of-address (POA): make it pass on the first review

POA rejections are rarely about the jurisdiction—they’re about formatting, recency, and mismatches. Treat POA like a quality-control exercise.

For individuals (UBOs/directors):

• Use a recognizable document type (commonly utility bill, bank statement, government letter)
• Ensure it shows full name, full residential address, and a recent date (many reviewers expect a recent window)
• Provide the full document (not cropped), readable, and in color if possible

For the entity address:

• Provide evidence for the registered office and, if different, the operating address
• If you use a registered agent address, be prepared to evidence the operating location (e.g., lease, service agreement, or other proof depending on counterparty expectations)

Mismatch traps that cause repeat requests:

• “St.” vs “Street” differences across documents that look like different addresses
• Name order differences (e.g., middle names) without a consistent format
• POA in a different person’s name (even if same household) unless the reviewer explicitly accepts it

5) Corporate resolutions: document authority, banking, and onboarding intent

Corporate resolutions are the fastest way to eliminate “authority” questions—especially when onboarding with banks, PSPs, liquidity providers, or platform vendors. A resolution tells the reviewer: the board approved this relationship and these people can act.

A broker-ready board resolution (or written resolution) typically covers:

• Approval to open and operate accounts (bank/PSP) and/or enter service agreements (LP, platform, CRM)
• Appointment of authorized signatories (names + titles)
• Signing rules (sole signatory vs two directors jointly)
• Authority to provide KYB/KYC documents and sign onboarding forms
• (If relevant) authority to appoint delegates (e.g., compliance officer, operations manager)

Attach supporting evidence where possible:

• Director appointment evidence / registry extract listing directors
• Specimen signatures if requested by the counterparty

Practical example: If you’re onboarding a liquidity provider and the contract is signed by an operations manager, the resolution should explicitly authorize that person (or authorize a director to delegate). Otherwise, the reviewer may insist on director signatures.

6) A broker-ready submission checklist (copy/paste for your ops team)

Use this as a working checklist for Saint Lucia broker entities. Adjust based on your counterparty’s KYB list and your risk profile.

Entity documents

• Certificate of Incorporation
• Registry extract / company search (showing status, registered address, directors)
• Constitutional documents (e.g., memorandum/articles or equivalent)
• Shareholder register (or equivalent evidence of shareholders)
• Business description (products, client base, countries served—high level)

UBO pack (each UBO)

• Passport/ID
• Proof of address
• Ownership declaration (signed) and ownership chart
• Source of funds/wealth evidence (if requested)

Director/controller pack (each person)

• Passport/ID
• Proof of address
• Evidence of role (registry extract/appointment)

Authority & governance

• Board resolution / written resolution covering onboarding, signing authority, and account operation
• Authorized signatory list (if separate)
• Delegation letter (if non-directors sign operational documents)

Submission hygiene

• One indexed PDF “KYB cover pack” + separate source PDFs
• Consistent naming, dates visible, no cropped pages
• A single point of contact for follow-ups (ops/compliance email)

The Bottom Line

KYB for Saint Lucia entities moves faster when you treat it like an audit trail: clear beneficial ownership, verified directors, clean proof-of-address, and explicit signing authority via resolutions. Most delays come from mismatches and missing authority—not from the jurisdiction itself. Build a repeatable KYB pack once, then reuse it across banks, PSPs, LPs, and vendors with minimal edits.

If you want to streamline KYB workflows inside your onboarding and backoffice stack, talk to Brokeret at /get-started.