Declare or update the beneficial owner

When to use

The company's ownership has changed, or a check shows the register's beneficial-owner entry is out of date. Not for a change of the board or the legal address — use company.change-board-member or company.change-legal-address. Not for a routine check that the entry is still true — that is company.registry-watch. Not for a new company — the initial declaration is part of company.register-sia-lv.

Before you start

• The ownership event is known and documented: sale agreement, gift agreement, inheritance certificate, or resolution.
• The current shareholder list with capital and vote percentages is at hand.
• Each beneficial owner has confirmed their details and is willing to sign (an owner abroad may need

What a run requires3

The trail8 steps

1. S1

   Establish who qualifiesagent

   Apply the 25% test to capital and votes; add anyone who controls the company by other means (agreements, veto rights). A listed company or a fund may be exempt — note it if so.

   Done when a written list of beneficial owners exists with, for each one, the basis of qualification.

   ⛔ A shareholder holding exactly 25.0% and one holding 24.9% through a nominee can both be relevant — do the arithmetic on totals, not on names.

2. S2

   Confirm the listownerneeds approval · owner

   Approval · S2 · owner — the run stops until a named person records the decision

   Present the proposed list against the current register entry, with the difference marked.

   Done when the owner has confirmed the list in writing (a yes in the task is enough).

3. S3

   Collect signaturesagent

   Each beneficial owner signs the UBO declaration; the application is signed with e-paraksts or prepared for the register's accepted signing method.

   Done when every required signature is in the documents module and the file names match the signers.

   ⛔ A signature missing at this stage is the most common cause of rejection — do not file with a placeholder.

4. S4

   Draft the applicationagent

   Fill the register's application for beneficial-owner data with the confirmed list, attach the ownership document and declarations.

   Done when the draft application and its attachments are complete and read back against S1's list.

5. S5

   File with the registeragentneeds approval · ownerirreversible

   Approval · S5 · owner — the run stops until a named person records the decision

   Irreversible · S5 — an agent never closes it alone

   Submit the application through the Enterprise Register portal and pay the state fee from company funds ⚠ verify current fee and payment method, ur.gov.lv.

   Done when the register shows the application as received, with a confirmation number.

6. S6

   Verify acceptanceagent

   Check the register status until the application is accepted; if rejected, read the rejection reason and return to S4.

   Done when the register shows the application as accepted, not merely received.

7. S7

   Read back from the registeragent

   Order or view the register extract and compare the beneficial-owner entry against the S1 list, name by name.

   Done when every name, identity number and qualification basis matches, or a correction is filed.

8. S8

   Record and hand backagent

   Update the internal UBO record and the compliance file; add the next review date to the registry watch; send the owner a three-line summary: who is now declared, when filed, confirmation number.

   Done when the UBO record and the compliance file show the new declaration, the registry watch carries the next review date, and the owner has the three-line summary.

Checks — how we know it worked

• Register extract (read from ur.gov.lv, not from the submitted form) shows exactly the S1 list.
• Every beneficial owner's signed declaration is in the documents module, dated before the filing.
• The ownership document (sale, gift, resolution) is archived and linked to the application.
• The internal UBO record and the register entry agree — checked by reading both, not by memory.

If it goes wrong

What each step leaves behind

1. S1a written list of beneficial owners exists with, for each one, the basis of qualification.
2. S2the owner has confirmed the list in writing (a yes in the task is enough).
3. S3every required signature is in the documents module and the file names match the signers.
4. S4the draft application and its attachments are complete and read back against S1's list.
5. S5the register shows the application as received, with a confirmation number.
6. S6the register shows the application as accepted, not merely received.
7. S7every name, identity number and qualification basis matches, or a correction is filed.
8. S8the UBO record and the compliance file show the new declaration, the registry watch carries the next review date, and the owner has the three-line summary.

Evidence to keep

Ownership event document · S1 list with qualification basis · owner's S2 confirmation · signed UBO declarations · register confirmation number and acceptance date · register extract after acceptance · S7 comparison note.

How this playbook improves

After every 5 runs ask: how many days from ownership event to accepted filing, and where did it wait? Did the register reject anything, and why? Did company.registry-watch catch the change, or did a human have to raise it? A new version changes the step that caused the wait or the rejection, and says so in its change note.