Change a board member in the commercial register

When to use

The shareholders want to appoint, replace or remove a member of the board (valde) of a Latvian company and the change must reach the commercial register. Not for changing the registered legal address — use company.change-legal-address. Not for merely watching what the register already shows — use company.registry-watch. Not for hiring an employee — use people.hire-employee; a board member is a corporate-governance change, not a payroll one.

Before you start

• The owners have decided the new composition in principle; this playbook does not run the meeting itself
• You have a current UR extract of the company (board as registered today, legal address, registration number).
• You know whether the new member holds a Latvian e-paraksts or must sign on paper / at a notary.
• ⚠ verify current application form, state fee and processing term on ur.gov.lv before drafting — these change.

What a run requires4

The trail10 steps

1. S1

   Pull the current register dataagent

   Fetch the UR extract for the company; note every board member, their authority limits, and the registration date of the last change.

   Done when the current board as registered is written down with the extract's date.

2. S2

   Decide the compositionownerneeds approval · owner

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

   Present the change: who joins, who leaves, effective date, and what documents the owners must sign.

   Done when the owner has confirmed the new composition and the effective date in writing.

3. S3

   Draft the documentsagent

   Prepare the shareholders' decision/minutes naming the new board, the new member's written consent, and the UR application with the new member's ID data exactly as in the passport.

   Done when every document exists as a draft and names, codes and addresses match the ID documents.

   ⛔ A personal code or name one letter off from the passport is the most common cause of refusal.

4. S4

   Verify the new member's details and signing capabilityagent

   Check the ID document, confirm the consent text is understood, and confirm how they will sign (e-paraksts, paper, notary).

   Done when the signing route for each signer is named in the file.

5. S5

   Sign the documentsownerneeds approval · owner

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

   The owners and the new member sign the decision and consent — with e-paraksts where possible (see documents.sign-with-eparaksts), otherwise on paper / before a notary.

   Done when every signature exists as a file or wet-ink scan, dated on or before the filing date.

6. S6

   Assemble the filing packageagent

   Attach the decision, consent, application, proof of the state fee payment, and any required notarisation. Re-read the application against the UR extract from S1.

   Done when the package is complete and a second read finds no mismatch.

7. S7

   File and payownerneeds approval · ownerirreversible

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

   Irreversible · S7 — an agent never closes it alone

   Submit the application to the Register of Enterprises via ur.gov.lv (or on paper) and pay the state fee.

   Done when UR has issued a submission number and the fee receipt exists.

   ⛔ The agent never files with the state or pays without this approval step.

8. S8

   Track until registrationagent

   Watch the application status; if UR raises defects, fix and refile within the stated correction term (⚠ verify correction deadline in the UR refusal notice).

   Done when the UR extract shows the new board with a new registration date.

9. S9

   Update downstream recordsagent

   Update the company file, board signatory lists, and templates; list who must be told — bank, accountant, major counterparties — and add each as a task (bc tasks add).

   Done when the task list exists and internal records name the new board.

10. S10

    Hand backagent

    Send the owner a three-line summary: what changed, the UR registration date, what notifications remain open.

    Done when the owner confirms receipt.

Checks — how we know it worked

• The UR extract (fetched fresh, not the filed copy) shows the new board and the old member is gone.
• The shareholders' decision covers every member change made — the extract and the decision match one-to-one.
• Bank signatory records no longer list the removed member.
• The submission number, fee receipt and registration date are all in the company file.

If it goes wrong

What each step leaves behind

1. S1the current board as registered is written down with the extract's date.
2. S2the owner has confirmed the new composition and the effective date in writing.
3. S3every document exists as a draft and names, codes and addresses match the ID documents.
4. S4the signing route for each signer is named in the file.
5. S5every signature exists as a file or wet-ink scan, dated on or before the filing date.
6. S6the package is complete and a second read finds no mismatch.
7. S7UR has issued a submission number and the fee receipt exists.
8. S8the UR extract shows the new board with a new registration date.
9. S9the task list exists and internal records name the new board.
10. S10the owner confirms receipt.

Evidence to keep

UR extract before and after (with dates) · shareholders' decision and consent (signed) · submission number · fee receipt · UR refusal and correction, if any · the owner's S2 decision · the S9 notification task list.

How this playbook improves

After every 10 runs ask: days from decision to registration, and which step waited longest? How many UR refusals, and for what defect? Was any downstream record still naming a removed member a month later? A new version fixes the step behind the longest wait or the refusal cause, and says so in its change note.