authoritative-guide

Last updated June 25, 2026

Latvia Personal Code for Foreigners: Residence Permit, eID and Address

Personal code dependency map

A Latvian personal code shows up across many records, but that does not mean it solves every residence or admin problem by itself. This page explains how the code connects to residence-permit steps, PMLP records, eID use, declared address, banking, tax, and health files, while making clear what the identifier does not replace. Readers looking for a practical explanation of where the code matters, when they receive it, and how it fits into a wider relocation file should get a clearer map before dealing with separate institutions.

Latvia's personal code, formally the personal identity number, is one of the first administrative identifiers foreigners need to understand after moving to Latvia. It appears in employment, tax, residence permits, e-services, banking, healthcare, declared address records, education, signatures, rental files, and official correspondence. Because it appears everywhere, newcomers often assume the personal code is the same as a residence permit, the same as an eID card, or proof that every public and private service must accept them. That is not accurate. The personal code is an administrative identifier. The residence permit is the legal basis to reside. The residence permit card or foreigner's eID card is a physical identity or status document. The declared address is a separate population-register record. Banks and employers run their own checks.

The official source to start with is the Office of Citizenship and Migration Affairs, commonly known by the Latvian abbreviation PMLP and in English as OCMA. PMLP guidance explains that a residence permit is the document giving a foreigner the right to reside in Latvia temporarily or permanently, and that a permit is needed if the person wants to reside in Latvia for more than 90 days within half a year counted from the first day of entry. PMLP guidance also explains that a personal identity number is allocated to a foreigner upon receipt of a temporary residence permit or permanent residence permit. Use the current PMLP/OCMA site navigation for the latest direct page because official URLs can change.

That last point is the operational anchor: foreigners should not treat the personal code as a free-standing shortcut around immigration. If your basis for Latvia is a residence permit, the code is connected with the residence-permit process. If you need to work, pay taxes, open a bank account, use e-services, access health care, or declare residence, the personal code matters, but it does not replace the underlying permission and evidence.

This article is general information. It is not legal, immigration, tax, banking, employment, healthcare, or data-protection advice. Latvian procedures, e-services, document requirements, and institutional practice can change. Use current PMLP, Latvija.lv, State Revenue Service, NVA, bank, employer, and health-system guidance for your case.

Direct answer

A Latvian personal code is the core personal identifier used by Latvian public systems and many private institutions. For most non-EU newcomers, the practical route starts with the PMLP residence-permit process, then the residence permit card or foreigner eID, then consistent use of the code across address, employer, bank, tax, health and e-service records. PMLP states that a personal identity number is allocated to a foreigner upon receipt of a temporary or permanent residence permit. The personal code can be needed for employment, tax, banking, declared residence, healthcare, e-services, official correspondence, and contracts. But it is not the same as the residence permit, not the same as an address declaration, and not proof that a bank, employer, municipality, or health institution must complete every service without additional documents.

If you are moving to Latvia, start with your legal basis to stay. If you will reside for more than 90 days within half a year, PMLP's residence-permit guidance is central. Once the residence permit and personal code exist, keep the code consistent across employer, bank, tax, address, health, and e-service records. If any institution says your personal code is missing, invalid, private, or mismatched, ask which exact record is missing and which authority owns it.

Quick route checklist

Related Latvia guides: , , , and .

Official sources to use first

Use official sources because the same identifier is used across many systems.

• PMLP/OCMA residence permit guidance from the current official site navigation.
• PMLP/OCMA guidance on obtaining a personal identity number and declaring residence.
• PMLP/OCMA residence declaration and e-service guidance.
• PMLP/OCMA guidance on residence-permit types and foreigner's eID cards.
• PMLP/OCMA guidance on changing a personal identity number.

Use each official source for its own layer. PMLP handles residence permits, identity-number allocation, eID-related documents, and declared residence services. Banks handle customer due diligence. Employers handle employment files and payroll. Tax authorities handle tax records. Health institutions handle health-insurance and family-doctor contexts. A personal code is the connector, not the entire workflow.

Vocabulary that prevents mistakes

"Personal code" is the everyday English phrase many foreigners use for Latvia's personal identity number. It is used to identify an individual in public and private records.

"Personal identity number" is the formal phrase used in PMLP English materials. When an institution asks for the personal identity number, it usually means the personal code.

"PMLP" or "OCMA" is the Office of Citizenship and Migration Affairs. It is the canonical authority for residence permits and many identity-register issues.

"Residence permit" is the legal status document giving a foreigner the right to reside in Latvia temporarily or permanently. PMLP states that it is necessary for stays exceeding 90 days within half a year, subject to the applicable legal basis.

"Residence permit card" is the physical card format for the permit. It is not just a number. It may include or be connected to identity and status data.

"Foreigner's eID card" is a separate card concept. PMLP compares the foreigner's eID card, residence permit card, and Latvian citizen/non-citizen eID card. Do not assume every foreigner with a personal code has the same card or rights.

"Declared place of residence" is the address record used for legal relations with the state and local government. PMLP guidance explains declaration or designation of residence and additional address functions. It is not the same as simply telling a landlord where you live.

"Additional address" is not the declared place of residence. PMLP's e-service description says a person with a valid declared or indicated place of residence can specify one additional address, but also states that the indicated additional address is not the declared place of residence.

"Register of Natural Persons" is the register updated by the declaration or designation e-service. PMLP states that data specified in the e-service is updated in that register immediately at service execution.

What the personal code does

The personal code lets Latvian systems identify the correct person. It supports employment records, tax records, bank onboarding, residence declarations, health-related records, contracts, e-services, and official correspondence. Without it, institutions may be unable to create or match records.

It reduces ambiguity. Foreign names can be spelled differently, transliterated, abbreviated, or entered in different order. A stable personal identity number helps prevent confusion between people with similar names and helps link records correctly.

It supports electronic services. Many Latvian e-services require authentication through bank tools, eID, secure electronic signature, eParaksts, or official electronic address. The personal code is often part of the identity layer behind these services.

It supports employment and tax administration. Employers need correct personal identifiers for payroll, taxes, social contributions, and employment records. A mismatch can delay onboarding or create reporting errors.

It supports banking and AML files. A bank may ask for personal code, passport, residence permit, address, source of funds, tax residency, and account purpose. The personal code helps identify the customer, but it does not replace due diligence.

It supports declared residence and public-contact records. Once a person has the right status and access, address declaration or designation can update register data.

What the personal code does not do

It does not itself grant the right to reside. The right to stay comes from the residence permit or other legal status. A number is not permission.

It does not automatically prove the permit is valid. A bank or employer may still ask for the card, passport, approval, or validity dates.

It does not prove address. A declared residence record, lease, owner consent, or other address evidence may be needed separately.

It does not prove health insurance. Health coverage or access can depend on employment, contribution, state insurance, EU coordination, private insurance, or another route.

It does not guarantee a bank account. Banks still conduct KYC and AML checks and may require source-of-funds and tax-residency evidence.

It does not prove tax residency. A person can have a Latvian personal code and still have cross-border tax questions. Tax residency depends on law and facts.

It does not eliminate data-protection concerns. The personal code is sensitive identifier data. Use it where needed, not casually.

How foreigners receive the code

For many foreign residents, the personal identity number is connected with the residence-permit process. PMLP guidance states that the personal identity number is allocated to the foreigner upon receipt of the temporary residence permit or permanent residence permit.

That means the first question is not "how do I get a number?" but "what is my legal basis to reside and which PMLP route applies?" Employment, study, family, business, EU Blue Card, startup, long-term residence, or other grounds can involve different documents and timing.

If the person has no information in the Population Register and no identity number, PMLP also has guidance on establishing legal status and granting an identity number. That is a specific legal-status process, not a general shortcut for convenience.

If you lived in Latvia before, do not assume you need a new number. Ask PMLP or a qualified adviser how the existing record should be used or updated.

If an institution says your code is "wrong," check whether the issue is old code format, data entry, name mismatch, date of birth, card validity, or a record that has not been updated.

If your personal identity number changes under the special change process, PMLP warns that documents and tools specifying the number must be changed, including driver licence, personalised card, student card, e-signature, bank authorisation tool, and similar records. That shows how deeply the number connects across systems.

Residence permit versus foreigner's eID card

PMLP materials compare Latvian citizen/non-citizen eID cards, residence permit cards, and foreigner's eID cards. Foreigners should not assume these documents have the same purpose.

The residence permit card is tied to the right to stay for a certain period or permanently. It is the immigration-status document for the relevant foreigner.

The foreigner's eID card can be relevant for identification and electronic services, but it does not necessarily equal a residence permit. The exact card depends on the person's status and purpose.

An employer may need the residence permit card to check work and stay conditions. A bank may need identity and residence information. An e-service may require electronic authentication. These are different needs.

If someone says "you need eID," ask whether they mean residence permit card, foreigner's eID card, electronic signature, bank authentication, or access to a specific e-service.

If you are staying in Latvia rarely or for a short period, a foreigner's eID route may be relevant, but it should not be confused with long-term residence permission.

Declared residence and additional address

PMLP's declaration e-service allows eligible people to declare their place of residence in Latvia or indicate residence address abroad, and to specify one additional address. The service description says the data is updated in the Register of Natural Persons immediately at the time of service execution.

The duty to declare or designate residence applies to specified categories, including citizens and non-citizens of Latvia, EU/EEA/Swiss citizens and family members who have received registration or permanent residence certificates in Latvia, and third-country nationals or stateless persons who have received a residence permit issued in Latvia.

This means the address layer usually follows status. A third-country national generally needs the residence permit before the declaration duty and e-service route apply in the same way.

The declared residence is used for legal relations with the state and local government. It is not only a mailing preference. It affects official reachability and administrative records.

An additional address is useful if you can be reached somewhere else, but PMLP states that the additional address is not the declared place of residence. Do not use additional address as if it replaced the declaration.

If you move, update the address. A bank, employer, municipality, tax office, and health provider may each also need separate updates.

Banking and the personal code

Latvian banks usually need a personal identifier to create or match a customer record. But the bank account is not granted by personal code alone.

Prepare passport, residence permit or relevant card, personal code, address evidence, employment or study documents, tax-residency declaration, source-of-funds evidence, and expected account activity.

If you do not yet have the code, ask the bank whether it offers any limited non-resident or pre-onboarding route. Do not assume all banks have the same policy.

If the bank asks for a code but your PMLP process is pending, provide the bank with clear status evidence and ask whether onboarding can wait or proceed later.

If a bank refuses, ask whether the issue is missing personal code, residence permit, declared address, source of funds, sanctions risk, tax residency, or product policy.

If the account receives foreign salary, business income, crypto proceeds, or large savings transfers, prepare evidence. The personal code identifies you; it does not explain money.

Employment and tax

Employers need accurate personal data. The personal code can be necessary for employment contracts, payroll, tax, social insurance, workplace records, and official reporting.

If the residence permit is tied to employment, the employer should understand both immigration and payroll layers. A personal code is not proof that the employment basis is correct.

If the code is pending, ask the employer what can be done before issuance and what must wait. Some onboarding steps can proceed with passport and permit application evidence; others require the code.

If payroll uses the wrong code or name spelling, correct it early. Errors can affect tax and social contribution records.

Remote workers should be cautious. Having a personal code and Latvian address does not automatically make foreign payroll compliant. Tax residency, social security, employment law, and work authorization require separate analysis.

Self-employed people and company owners should check tax registration and business-account requirements. The personal code is only one identifier.

Healthcare and family doctor context

Health access can depend on status, employment, insurance, EU coordination, or state-funded eligibility. A personal code can be needed for records, but it does not create coverage by itself.

If a clinic or family doctor asks for personal code, they may need it to identify you in the system. They may also ask for residence permit, insurance, employment, or other eligibility documents.

If you are an EU citizen, EHIC, S1, employment, or registration status may affect health coverage. If you are a third-country national, private insurance or residence-permit category may matter.

Do not assume that because a bank or employer accepted your personal code, the health system will treat you as covered. These are separate systems.

Keep health-insurance documents, employment evidence, residence permit, personal code, address, and clinic records together.

Privacy and safe use

The personal code is sensitive. Do not publish it on social media, rental groups, or open chats. Do not send it to unknown agents.

Legitimate institutions may need it: employer, bank, PMLP, tax authority, health provider, university, municipality, or e-service. Ask why if a private person requests it.

When sending documents, use secure channels where possible. Redact unrelated information if the institution allows it, but do not alter official documents for official use.

Keep a log of where you sent passport, permit card, personal code, and bank statements. If identity misuse happens, the log helps.

If your personal code changes, update all linked institutions. PMLP's change guidance shows that many cards and tools can need replacement.

New-arrival profiles

Employee: start with residence permit and employer documents. Once the personal code is issued, update payroll, bank, tax, and address records. Keep employer and PMLP records consistent.

Student: use university and residence-permit documents. Ask which systems require personal code: dormitory, bank, scholarship, health insurance, or e-services.

Family member: personal code may follow residence permit or family status. Keep relationship evidence, sponsor documents, address, and health-insurance records.

EU/EEA/Swiss citizen: check registration certificate and residence declaration rules. Do not assume third-country procedures apply.

Remote worker: get tax and immigration advice. Personal code and declared address can trigger additional obligations.

Company founder: distinguish personal code, company registration number, tax records, bank beneficial-owner checks, and residence permit basis.

Leaving Latvia: ask PMLP and relevant institutions what happens to permit card, declared address, bank, tax, and health records. Do not rely on forum answers for card return or deregistration duties.

Common mistakes

Mistake one: treating personal code as residence permission.

Mistake two: treating residence permit card as proof of address.

Mistake three: assuming a foreigner's eID card and residence permit card are identical.

Mistake four: not updating declared residence after moving.

Mistake five: sending personal code to unverified landlords or agents.

Mistake six: assuming bank refusal is only about the personal code when the issue is source of funds or AML.

Mistake seven: using old name spellings across employer, bank, and PMLP records.

Mistake eight: not keeping a record of the code after leaving Latvia.

Troubleshooting

If an institution cannot find your code, check spelling, date of birth, old documents, and whether the record has been activated or updated.

If the code is pending, ask PMLP or the relevant institution what proof of pending residence permit can be used temporarily.

If address declaration fails online, check authentication method, eID, bank authentication, eParaksts, eligibility, and whether you already have valid declared or indicated residence.

If bank onboarding fails, ask for the exact missing item. Do not assume another bank will use the same checklist.

If employer payroll is blocked, ask whether the missing item is personal code, residence permit, work authorization, tax registration, or bank account.

If a document shows an old code or wrong code, ask PMLP or the issuing institution how to correct it.

First-month action plan

Before arrival, identify residence basis and PMLP document list. Gather passport, employment or study evidence, financial means, insurance if required, address evidence, and civil-status documents if relevant.

On arrival, complete the residence-permit process or card collection route as instructed. Record dates and reference numbers.

After receiving personal code, update employer, bank, tax, health, university, and address records as needed.

Declare or update residence through the correct route once eligible. Keep proof.

Set up e-services carefully. Understand whether you need bank authentication, eID, eParaksts, or e-address.

Audit records after the first month: name, code, address, employer, bank, health insurance, and permit validity.

Final checklist

Use PMLP as the source for residence and identity-number questions. Confirm whether your stay requires a residence permit. Treat personal code as an identifier, not a permit. Keep residence permit card, foreigner's eID, declared address, bank account, tax, and health insurance separate. Update records after moving or changing status. Protect the code as sensitive data. Ask institutions which exact record is missing when something is blocked.

Decision tree: which layer is actually missing?

If an employer says the personal code is missing, ask whether the blocker is payroll reporting, work authorization, employment contract, tax registration, bank account, or identity verification. The personal code may be one missing field, but the employment file can also need residence permit and work-basis evidence.

If a bank says the personal code is missing, ask whether the bank can begin review with passport and residence-permit evidence or whether the product requires the code before onboarding. Also ask whether the real blocker is source of funds, sanctions screening, address proof, tax residency, or account type.

If a health provider says the code is missing, ask whether they need identity matching, insurance eligibility, family-doctor registration, state-funded coverage confirmation, or private-insurance billing. The code identifies you; coverage still needs a basis.

If an e-service fails, ask whether the problem is authentication, eID, eParaksts, internet-bank login, e-address access, declared residence eligibility, or missing register data. The personal code can exist while authentication is not working.

If a municipality or public body cannot find you, check whether your name, code, declared address, and status are updated in the relevant register. A spelling mismatch can look like missing status.

If a landlord asks for the personal code, ask why. It may be needed for a contract, utility setup, or verification, but it is sensitive data. Do not provide it to informal rental leads without a legitimate reason.

Institution-by-institution questions

Questions for PMLP: Has my residence-permit process reached the point where a personal identity number is allocated? Which document proves the number? Which card should I receive? What should I do if the number or personal data is wrong? How do I update address or status? What happens if I leave Latvia?

Questions for the employer: Which payroll or tax process requires the code? Can onboarding begin with passport and permit evidence while the code is pending? What happens to payroll if the code arrives after start date? Which name spelling will be used?

Questions for the bank: Which account type am I applying for? Is the personal code mandatory before opening? Do you require residence permit card, declared address, source-of-funds evidence, or tax-residency forms? Can I update the code later if first onboarding uses another identifier?

Questions for health providers: Is the code needed for identification only, or for eligibility? What insurance evidence is required? Does employment status matter? Can private insurance be billed if state eligibility is not active?

Questions for the municipality or address process: Am I eligible to declare residence now? Is my current accommodation a valid place of residence? Do I need owner consent or another lawful basis? Can I specify an additional address?

Questions for universities: Is the code needed for enrolment, dormitory, scholarship, student card, health insurance, or e-services? Can a passport number be used temporarily?

Profile-specific operating models

Third-country employee: focus on residence permit first. The personal code follows status. Employer payroll, bank account, tax, declared address, and health records should be updated after the code is issued. The employee should keep the contract, employer letters, permit card, personal code, and address records consistent.

EU/EEA/Swiss citizen: check registration certificate and residence declaration rules. The process can differ from third-country permits. Do not assume the personal code route is identical to a non-EU worker's route.

Student: ask the university which records require the personal code and which can be handled with passport until permit or registration is complete. Keep dormitory, scholarship, health-insurance, and address records together.

Family member: document sponsor status, relationship, address, financial support, insurance, and each family member's identity. One spouse's personal code does not replace the other's record.

Remote worker: personal code and declared address may support living in Latvia, but tax residency, social-security coverage, employer compliance, and work authorization require separate analysis.

Company founder: separate personal code from company registration number, VAT or tax records, bank beneficial-owner checks, and residence permit basis. Banks may ask for both personal and company documents.

Person leaving Latvia: before departure, ask how to update declared address, employer, bank, tax, health, and residence-permit records. Personal code may remain in records, but rights and obligations can change.

Personal code and declared address: common sequencing

Many newcomers expect to declare address before all status documents are complete. PMLP's e-service guidance identifies who has the duty and right to declare or designate residence, including third-country nationals who have received a Latvian residence permit. That wording matters. Address declaration often depends on status being established.

If you cannot declare yet, gather address evidence anyway: lease, host confirmation, employer accommodation, university housing, or owner consent where relevant. These documents may support the residence-permit application or later declaration.

If you can declare, make sure the address is real and reachable. Declared residence is used in legal relations with the state and local government. It should not be a convenient fiction.

If you have an additional address, remember that PMLP says it is not the declared place of residence. It is useful for reachability but does not replace the primary declared record.

If you move, update records promptly. Address mismatches can affect official mail, banking, health records, and employer files.

If the online declaration route fails, check authentication methods and eligibility before assuming the address is invalid.

Personal code and e-services

Latvian e-services can depend on authentication tools, not only the personal code. PMLP's declaration e-service refers to internet-bank authentication, eID card, secure electronic signature, and eParaksts or eParaksts Mobile.

If you have a code but cannot access an e-service, the issue may be lack of authentication method. Ask whether you need a residence permit card with eID function, foreigner's eID card, bank authentication, eParaksts, or official e-address.

If you use bank authentication, the bank account and e-service access become linked in practice. A bank onboarding delay can therefore affect public-service access.

If you use eParaksts or eID, check certificates, PINs, card reader, mobile setup, and expiry. Technical access is a separate operational layer.

Do not share authentication credentials with relocation agents or employers. A personal code plus eID access can expose sensitive public-service records.

If an e-service updates the Register of Natural Persons immediately, as PMLP states for declaration or designation of residence, review the result carefully. Immediate updates also mean mistakes should be corrected quickly.

Data matching and transliteration issues

Foreign names can create data problems. Latvian records, passports, bank systems, employer payroll, and health records may handle diacritics, multiple surnames, patronymics, hyphens, and transliteration differently.

Use the official spelling from your passport and residence documents. If the Latvian record uses a specific transliteration, keep a note explaining it.

If a bank says the code does not match, the issue may be name order or date of birth rather than the code itself.

If an employer enters your name incorrectly, payroll and tax records can later mismatch. Correct early.

If you change name after marriage or legal change, update PMLP, employer, bank, health, and education records. Keep the certificate and translation.

If old documents show an old personal code or old name, keep them. Future institutions may ask why records differ.

Privacy risk matrix

Low-risk sharing: providing the code to PMLP, employer payroll, bank, tax authority, health provider, university, or official e-service for a clear purpose.

Medium-risk sharing: providing the code to a landlord, telecom provider, utility company, private insurer, or service provider. It may be legitimate, but ask why and use official channels.

High-risk sharing: sending the code in public chats, rental groups, job boards, informal relocation groups, or to unknown agents.

Very high-risk sharing: sending code with passport, residence permit, bank statement, and address to an unverified person. This creates identity-misuse risk.

If a private party demands the code before any contract or verified relationship, slow down. Ask for the legal or business reason and whether another identifier can be used initially.

If you suspect misuse, contact the relevant institution and preserve evidence of where the code was shared.

Document governance routine

Create a master identity file. Include passport, residence permit card, personal code evidence, address declaration, eID or authentication notes, employer contract, bank records, health insurance, and tax documents.

Create a personal data sheet. Include official name, date of birth, nationality, passport number, Latvian personal code, residence permit number, declared address, additional address if any, employer, bank, and emergency contacts.

Update the sheet after every move, job change, card renewal, name change, or bank change.

Use consistent filenames. 2026-latvia-residence-permit-card.pdf is better than image7.jpg.

Store backups securely. The personal code is sensitive, but losing the only copy of a record also creates problems.

Track who received your personal code. For each disclosure, note date, institution, purpose, and document sent.

When a card expires or is replaced, keep old scans. Do not rely only on current documents if you may need residence history later.

Advanced troubleshooting cases

Case one: bank says personal code is private and cannot be used. The likely issue is not privacy itself but the bank's onboarding route or document policy. Ask what identifier or document it requires.

Case two: employer cannot report payroll. Ask whether the missing item is personal code, residence permit validity, work permission, tax account, or bank details. Solve the exact layer.

Case three: address declaration online fails. Check whether you are eligible, whether you have the right authentication, whether your permit is active, and whether you are using declaration or additional address function.

Case four: health provider cannot find you. Check code, name spelling, insurance route, employer status, and whether the provider has access to the right system.

Case five: you received a new code. Update all cards, tools, bank authorisation, student cards, employer records, and e-signature tools as PMLP's change guidance indicates.

Case six: you leave Latvia and later return. Bring old code and documents. Do not create duplicate identities.

Important warning for newcomers

Do not treat the personal code as a shortcut around residence status. The code is not a permit, an address declaration, bank approval, tax residency, employment authorization, health insurance, or e-service access by itself. It is the identifier that helps those systems find the right person once the relevant legal or institutional condition is met.

If you are stuck in a loop, separate the problem by record owner. PMLP owns residence-permit and identity-number records. Banks own onboarding and AML checks. Employers own payroll and work-file checks. Health providers and insurers own health-system records. The fastest next step is usually to ask which exact layer is missing, not to resend the same number repeatedly.

Practical case studies

Case one: a third-country employee receives a residence permit card and personal code, then sends only the code to the bank. The bank still refuses to open the account because it needs source-of-funds documents, tax-residency declaration, and address evidence. The problem is not that the personal code failed. The problem is that banking has its own compliance file.

Case two: a student has a personal code but cannot complete an e-service. The issue is authentication. They need a supported bank authentication method, eID, eParaksts, or another accepted access route. The code exists, but digital access is not configured.

Case three: a family member moves apartments after receiving the permit. The personal code remains the same, but declared residence, bank address, employer address, and health-provider address need updates. The move is an administrative event, not only a housing event.

Case four: an employer enters the worker's name with a shortened version and the bank uses passport spelling. Payroll records later mismatch. The fix is data consistency: official passport spelling, personal code, and residence permit data should align.

Case five: a person leaves Latvia and later returns. They assume the old code is invalid and try to start again. The better route is to disclose the old records and ask PMLP how to update status. Duplicate identity records create avoidable friction.

Case six: a remote worker obtains residence and personal code but continues foreign payroll without advice. The personal code helps identify them in Latvia, but it does not decide tax residency, social security, or employer obligations.

Monthly self-audit for the first year

Month one: confirm personal code, permit card, employer records, bank onboarding, health insurance, and address records. Correct spelling errors immediately.

Month two: verify that e-service access works. If not, identify whether the missing piece is bank authentication, eID, eParaksts, card PIN, or official e-address.

Month three: review declared residence. If you are still at a temporary address, plan the move or update. If you already moved, confirm the register and private institutions were updated.

Month four: audit bank and tax records. Make sure the personal code, tax-residency declaration, source-of-funds evidence, and address match reality.

Month five: review health records. Confirm whether your coverage or private insurance is active and whether the personal code appears correctly in medical records.

Month six: check permit, passport, employment contract, lease, and insurance expiry dates. Calendar renewal milestones.

Month nine: collect updated documents for any upcoming renewal, bank refresh, or employer audit.

Month twelve: archive the first-year document file. Keep old address records, first permit card scan, bank statements, employment records, and insurance documents.

Risk control for personal code misuse

If someone requests the code without a clear reason, ask for the legal or contractual purpose. A legitimate institution should explain why it needs the identifier.

If a landlord asks before viewing or contract, be cautious. Rental scams can collect identity documents from foreigners.

If an employer requests the code before a formal offer, ask whether it is needed for a contract draft or payroll. Avoid sending full identity bundles too early.

If a bank or insurer requests documents through email, verify the address. Use secure upload portals where possible.

If you accidentally sent the code to a suspicious party, preserve messages, warn affected institutions if necessary, and monitor accounts.

If a document containing the code is lost, consider which institutions could be affected: bank, employer, e-services, health provider, or tax authority.

If your number is changed officially, treat it as a full migration project. Update cards, bank tools, e-signature, student records, employer records, tax, health, and subscriptions.

FAQ

Is a Latvian personal code the same as a residence permit?

No. The personal code identifies the person in Latvian records. The residence permit is the legal basis to reside, and the card or eID document is evidence or access infrastructure tied to that status.

Can I open a bank account with only a personal code?

Usually no. A bank may use the personal code for identification, but it can still require passport, residence-permit evidence, declared address, tax residency, source-of-funds information, account purpose, and expected transaction activity.

Does a declared address create the personal code?

Not by itself. Address declaration is a separate register layer. PMLP materials connect personal identity number allocation for foreigners with temporary or permanent residence permit receipt, while declared residence records and additional address records serve different administrative purposes.

What should I do if an institution says my code does not work?

Ask which layer is failing: spelling, personal code, residence-permit validity, declared address, eID/authentication, bank KYC, employer payroll, tax registration, or health record. Then contact the institution that owns that layer.

Final self-audit before using the code

Before giving the personal code to any institution, confirm the purpose. Is it for payroll, bank onboarding, declared residence, tax, health records, university records, contract drafting, or e-service access? If the purpose is unclear, ask.

Confirm the supporting document. A personal code is stronger when paired with the right evidence: residence permit card for status, passport for identity, address declaration for residence, contract for employment, policy for insurance, and bank statements for funds.

Confirm the record owner. If data is wrong at PMLP, fix it with PMLP. If the bank typed the code incorrectly, fix it with the bank. If the employer used the wrong name, fix payroll. Do not ask the wrong institution to correct a record it does not control.

Confirm the update path. If you move, change job, change passport, change name, receive a new card, or leave Latvia, decide which institutions must be updated. The personal code may remain stable while the facts around it change.

Confirm the privacy level. The code is not a password, but it is sensitive. Share it deliberately, not casually. Keep copies of documents sent and the reason for sending them.

One-page maintenance log

Keep a one-page log with the personal code, permit card issue and expiry dates, declared address, additional address if any, employer, bank, insurer, university, and e-service access method. Add a column for "last updated." Review it after every move, renewal, job change, or bank KYC request. This prevents the common problem where one institution has current data while another still uses the first temporary address or an old passport spelling.

When a record changes, update the log the same day and save the confirmation. Keep older confirmations archived. Review access permissions regularly. Remove obsolete shared copies and outdated screenshots. Recheck quarterly.

Bottom line

Latvia's personal code is the administrative key that lets institutions identify you, but it does not replace the legal right to reside, the residence permit card, declared address, bank due diligence, tax analysis, or health-insurance eligibility. Foreigners should start with PMLP residence status, then keep the personal code consistent across address, employer, bank, tax, healthcare, and e-service records. Most newcomer problems become easier once each layer is treated separately.

PMLP verification workflow before you rely on the code

The practical risk is not the personal code alone. It is whether the same identity, permit and address data is visible across PMLP, e-services, a bank, an employer, an insurer or a university. Before using the code in another application, build a compact evidence file from the PMLP page that applies to your situation.

Use PMLP/OCMA pages as the source of record for the personal identity number and residence permit relationship. Use EU or general mobility pages only for broader context, not to decide whether a Latvian record has been created or corrected.

Trust

• About
• Contact
• Editorial Policy