Address Verification

Address Verification in KYC and KYB: Which Address Is the Provider Actually Checking?

An address mismatch is only a mismatch if the two records are supposed to describe the same address.

That sounds obvious. In merchant onboarding, it often is not.

A company can have:

•a registered office in London;

•an operating office in Berlin;

•a director living in Paris.

All three addresses can be genuine.

If an onboarding system compares the director's Paris residence with the company's London registered office and returns “address mismatch,” the problem may not be that either address is wrong. The problem may be that two different verification subjects have been compared as though they represented the same fact.

Current FATF customer-due-diligence standards make this distinction particularly clear for legal persons: the information relevant to identifying a company includes the address of its registered office and, if different, its principal place of business. FATF's standards are international standards that countries implement through their own legal and regulatory frameworks, so they should not be treated as a universal merchant document checklist.

The practical rule for merchants is therefore:

Before trying to make two addresses match, determine whose address is being verified, what type of address it is, and why the provider needs it.

That usually resolves more confusion than uploading another proof-of-address document.

Address verification starts with the subject, not the document

When a PSP, acquirer, bank or verification provider asks for an address, the first question should be:

Whose address?

Possible subjects include:

The merchant legal entity

The company being onboarded.

An operating business

The physical or principal location from which business activity takes place.

A director

A natural person associated with management or representation.

A beneficial owner or UBO

A natural person whose identity may need to be established under the applicable KYC/KYB framework.

An authorized representative

The individual submitting information or acting for the merchant.

Once the subject is clear, ask the second question:

Which address type?

That distinction is the basis of accurate address verification.

Registered address versus operating address

These are among the most commonly confused merchant addresses.

Registered office

The registered office is the company's formally registered legal address under the applicable corporate framework.

It can be used for official notices and corporate records.

It does not necessarily tell a payment provider where the merchant's employees, warehouse, management team or day-to-day commercial operations are located.

The distinction is not merely theoretical. In the United Kingdom, for example, Companies House explicitly states that a company's registered office does not need to be the place where the company carries on its day-to-day business. Current UK guidance also permits use of an eligible service provider's address, such as an accountant or solicitor, as the registered office where the relevant requirements are satisfied.

That is a jurisdiction-specific example, not a rule for every country.

But it demonstrates the larger verification principle:

registered office ≠ operating location by definition.

Operating address or principal place of business

An operating address generally describes where relevant business activity actually takes place.

Depending on the company, that could be:

•Headquarters

•Commercial office

•warehouse

•store

•service location

•principal management location

•another place where material operations occur

Terminology varies across jurisdictions and providers.

FATF's current Recommendation 10 framework expressly recognizes that a legal person's registered office and principal place of business may be different addresses.

So if:

Registered office: London

and:

Principal operating office: Berlin

the correct first response is not:

“One of these addresses must be wrong.”

It is:

“Which address does this particular field intend to capture?”

Residential address answers a different question

Now introduce the director living in Paris.

The company's address does not establish where that person lives.

If KYC is being performed on a relevant director, beneficial owner or representative, the provider may need personal information appropriate to that individual under the applicable jurisdictional and provider requirements.

A residential address is therefore attached to a natural person, not automatically to the merchant entity.

This produces an important distinction:

KYB address question

Where is this legal entity registered or operating?

KYC address question

What is the relevant address of this natural person?

A merchant application can legitimately contain:

Company registered address: London

Company operating address: Berlin

Director residential address: Paris

without those three values inherently contradicting one another.

The precise personal-address information and verification required depends on the applicable legal, regulatory and provider framework. FATF establishes risk-based identification and verification principles rather than one universal proof-of-address document package.

Correspondence and service addresses create another layer

Some systems also maintain a:

•correspondence address;

•service address;

•mailing address;

•administrative address.

These may exist primarily to establish where communications should be sent rather than where a person lives or where a business operates.

Again, the exact legal meaning is jurisdiction-specific.

The United Kingdom provides a useful illustration: Companies House distinguishes directors' service addresses from their usual residential addresses and permits the service address to differ from both the home address and the company's registered office.

That means:

service address

cannot automatically be interpreted as:

residential address.

And:

correspondence address

should not automatically replace:

registered office.

The role of the field determines what should match it.

The real address-verification problem

Most address problems can be reduced to one of four questions:

•Does the address belong to the correct subject?

A company's evidence has been submitted for an individual, or vice versa.

•Is it the correct address type?

A registered office has been entered where principal place of business was requested.

•Is the stated value supported?

The merchant declares one address while the relevant evidence or authoritative source supports another.

•If two values differ, is there a legitimate reason?

The merchant recently moved.

A corporate registry has not yet reflected a change.

The company uses an accountant's office as its registered office.

A director has a separate service and residential address.

These questions are more useful than asking simply:

“Do all the addresses match?”

Address difference versus false information

A difference is observable.

False information is a conclusion.

They should not be treated as synonyms.

Suppose a company provides:

Registered office: 10 Example Street, London

while its website says:

European Operations: 25 Example Strasse, Berlin

That could indicate:

•A legitimate registered-office/operating-office distinction

•incomplete onboarding information

•an outdated address

•a different group company

•an actual inconsistency

The difference itself does not tell the reviewer which explanation is correct.

The appropriate verification task is:

Determine what each address represents and whether the evidence supports that role.

This distinction prevents legitimate corporate structures from producing unnecessary compliance escalation while still preserving the need to investigate genuinely inconsistent information.

The Address Verification Diagnostic

For every disputed address, run the same eight checks.

•Subject

Who or what is the address attached to?

Examples:

•Merchant legal entity

•director

•UBO

•authorized representative

•operating business location

•Address type

What kind of address is being requested?

Examples:

•Registered office

•principal place of business

•operating location

•residential address

•correspondence/service address

•Stated value

What address did the merchant actually provide?

Do not begin comparison until the source field is identified.

•Evidence source

What supports the value?

Potential sources can include, depending on the check:

•Corporate registry

•official corporate record

•provider-accepted documentary evidence

•reliable electronic verification

•other independent information

FATF's customer-due-diligence framework uses the concept of reliable, independent source documents, data or information for verification rather than requiring one universal evidence format.

•Registry/application match

Does the declared value agree with the relevant authoritative or documentary source?

The important word is:

relevant.

A director's residential evidence should not be expected to match the merchant's registered-office entry merely because both contain an address.

•Legitimate reason for difference

If the values differ, is the difference explainable?

Possibilities include:

•Different address roles

•recent move

•pending registry update

•group-company structure

•use of an authorized registered-office provider

•different correspondence location

•Unresolved discrepancy

After the role and available evidence are understood, does an actual contradiction remain?

For example:

The merchant states that its current registered office is Address A.

The current applicable corporate registry shows Address B.

The merchant provides no explanation for the difference.

That is an unresolved discrepancy.

•Action required

The action should correspond to the actual problem.

It might be:

•Correct the application

•provide evidence

•explain the address relationship

•update an official record where required

•provide current information through the provider's approved process

•escalate for review where the difference cannot be reconciled

The answer should not automatically be:

upload another utility bill.

Address Verification Diagnostic

Subject

Address type

Stated value

Evidence source

What should match?

Legitimate difference?

Unresolved issue

Action

Merchant entity

Registered office

Registry/corporate evidence

Relevant registered-office record

Possibly, if record changed or context differs

Merchant entity

Operating/principal business address

Business evidence / relevant source

Evidence of operating location

Can differ from registered office

Director

Residential

Provider-accepted KYC evidence/source

Director's relevant personal-address record

Can differ from company

Director

Service/correspondence

Relevant official/business source

Service-address record

Can differ from residence

UBO

Residential where required

Provider-accepted verification evidence

Relevant person's address

Can differ from all company addresses

This is a diagnostic framework.

It is not a universal legal requirement or provider document list.

Proof of address comes after the address type

Merchants often start with:

“What counts as proof of address?”

That is one step too early.

First establish:

What address are we proving?

A corporate registry may be highly relevant when establishing a registered office.

It may be irrelevant to proving a director's residence.

A personal document may help verify an individual's address.

It does not prove that the merchant actually operates from that location.

An operating-location check may require evidence different from either.

The correct hierarchy is:

Subject

→ Address type

→ Declared address

→ Verification objective

→ Acceptable evidence

not:

document

→ hope it proves the right address.

There is no universal “three-month proof of address” rule

One of the most persistent onboarding shortcuts is the claim:

“Proof of address must always be less than three months old.”

That should not be stated as a universal KYC or KYB requirement.

CDD implementation varies by jurisdiction, regulated context, provider and risk assessment. In the UK, for example, the FCA explains that AML law and its rules do not prescribe every detail of how firms must perform customer due diligence, allowing firms to design risk-based processes appropriate to their circumstances.

A particular provider can absolutely impose a document-age rule for a particular verification workflow.

That makes it:

a provider-specific requirement in that context

—not:

a universal law of KYC.

Merchants should therefore check the current requirement for the actual provider and verification subject instead of relying on a document-age rule copied from another onboarding process.

Provider requirements can be more specific than the general framework

International standards, national law and provider procedures operate at different levels.

A merchant might encounter an address request because of:

•Applicable law or regulation

•customer-due-diligence obligations

•acquirer or banking requirements

•provider policy

•risk-based enhanced review

•a discrepancy that requires resolution

Those sources should not be conflated.

FATF's standards themselves emphasize a risk-based approach and are designed to be implemented by countries through measures adapted to their particular circumstances.

A PSP can therefore request evidence under its own compliant workflow without that exact document being named in international standards.

The merchant question should be:

“What fact is this provider trying to establish under this check?”

Why international merchants encounter more address friction

International businesses can generate several simultaneously valid locations:

•Incorporation jurisdiction

•registered office

•headquarters

•operating offices

•warehouse locations

•director residences

•UBO residences

•group-company addresses

•settlement-related locations

Different countries also use different:

•Address formats

•alphabets

•transliterations

•postal conventions

•registry structures

•administrative subdivisions

So address normalization itself can introduce apparent discrepancies.

For example:

Straße

might appear transliterated as:

Strasse

or a bank, registry and onboarding form may represent an apartment/unit field differently.

The relevant question remains whether the records identify the same underlying address for the same subject—not whether every character string is identical.

Exact text matching is a poor substitute for address verification

Imagine these values:

10 Rue Exemple, Apt. 4

and:

10 Rue Exemple, Appartement 4

A system might flag the strings as different.

A human or a properly designed normalization process may recognize that they refer to the same location.

Conversely:

10 Example Street

and:

100 Example Street

may look superficially similar but represent different locations.

This is why address verification needs both:

normalization

and:

semantic role awareness.

The objective is not merely to compare strings.

It is to establish the relevant address with sufficient confidence under the applicable process.

Registered address and website address need context too

A merchant website may display a company address for customer transparency.

That does not automatically establish which address type it represents.

That is a website-standard requirement.

It should not automatically be interpreted as:

“whatever address appears in the website footer is sufficient proof of the merchant's operating location.”

Website disclosure and KYB verification answer related but different questions.

“address”

can sit in a wider merchant profile containing information about:

•the business;

•its locations;

•its registered details;

•relevant people;

•other underwriting information.

A merchant should therefore use the live onboarding workflow and current instructions to identify which address is requested in a particular field rather than assume that one company address should be copied everywhere.

Older provider documentation should not become a universal rule

That information should not be converted into a statement such as:

“KYC proof of address must always be less than 90 days old.”

For a current application, merchants should follow the live request shown for their specific verification case.

Common address mismatches and what they actually mean

Registered office differs from operating office

Possible interpretation

Completely legitimate.

Question

Has the merchant correctly labeled both locations?

Action

Provide the correct address in each relevant field and support each where required.

Director residence differs from merchant address

Possible interpretation

Expected.

Question

Was the system comparing a natural person's address with a company address?

Action

Separate the KYC subject from the KYB subject.

Registered office differs from corporate registry

Possible interpretation

Potentially outdated or inaccurate information.

Questions

•Did the company recently move?

•Is an update pending?

•Did the application use an old address?

•Is the registry record current?

Action

Resolve the discrepancy with current supporting information or update the relevant record where appropriate.

Operating address differs from the website

Possible interpretation

Could be legitimate or could indicate outdated business information.

Questions

•What address does the website claim to show?

•Headquarters?

•returns address?

•registered office?

•customer-service address?

Action

Clarify the role before treating the difference as contradictory.

Individual recently moved

Possible interpretation

A timing mismatch.

Question

Which source reflects the current residential address?

Action

Follow the provider's current process for updated information and evidence.

International transliteration differs

Possible interpretation

Formatting or transliteration issue rather than a different address.

Action

Preserve the authoritative spelling where required and explain the transliteration where the system does not normalize it automatically.

A virtual or shared address is not automatically an operating address

Businesses may legitimately use:

•accountants;

•solicitors;

•company formation agents;

•serviced offices;

•shared offices;

for certain address purposes where permitted.

As one current jurisdiction-specific example, UK Companies House permits an appropriate service-provider address to serve as a registered office.

But that does not automatically establish:

“this is where the merchant conducts its operations.”

If a provider asks for the principal place of business, supplying a registered-office service address without explaining the distinction can create another verification round.

The useful response is to label the locations correctly rather than force the service address into a field describing something else.

An address mismatch can be legitimate and still require evidence

“Legitimate difference” does not mean:

“no verification is needed.”

Suppose the merchant says:

Registered office: London

Operating office: Berlin

That structure may be entirely reasonable.

The provider may still need to establish that:

•the London address is in fact the registered office;

•the Berlin address is genuinely associated with the merchant's operations;

•the correct entity is being described;

•neither value was entered accidentally.

The editorial position should therefore not be:

ignore address mismatches.

It is:

Investigate them according to the role each address is supposed to play.

A mismatch should produce a targeted request

Poor request:

“Address verification failed. Upload proof of address.”

Better request:

“The registered-office address declared in your application differs from the current corporate record. Please confirm whether the company recently changed its registered office and provide the requested evidence for the current registered address.”

Or:

“The address supplied for the director appears to be the merchant's business address. We need the director's relevant residential address for this verification step.”

The better request tells the merchant:

•Whose address is affected

•which address type is affected

•what discrepancy exists

•what needs to be established

That reduces unnecessary document exchanges without weakening the underlying verification.

Address verification should follow an evidence hierarchy

A useful model is:

Level 1 — Declared information

What the merchant or individual entered.

Level 2 — Documentary evidence

Evidence submitted under the provider's permitted process.

Level 3 — Independent information

A registry, reliable electronic source or other authoritative source where applicable.

Level 4 — Discrepancy resolution

If the sources disagree:

why?

FATF's current framework calls for customer identity verification using reliable, independent documents, data or information and expressly recognizes the registered office and, if different, principal place of business for legal persons.

A successful process therefore does not merely ask:

“Was a PDF uploaded?”

It asks:

“Did the available evidence establish the address we actually intended to verify?”

How merchants can prevent avoidable address-verification delays

Before onboarding, create an address register.

Not a folder of utility bills.

A register.

For each relevant party, record:

Subject

Address type

Current address

Effective date

Evidence/source

Notes

Merchant Co

Registered office

Corporate registry

Merchant Co

Principal operating address

Different from registered office

Director A

Residential

Provider-requested source

Confidential

Director A

Service/correspondence

Corporate record

Different from residence

UBO B

Residential if required

Provider-requested source

Confidential

Then compare that register against:

•Merchant application

•corporate registry

•website

•bank/payout information

•ownership documentation

•provider onboarding fields

The purpose is not to make every row identical.

It is to make every row correctly labeled and internally explainable.

Five questions to ask before uploading proof of address

•Who is the subject?

Company or person?

•What address type did the provider request?

Registered, operating, residential or correspondence?

•What source currently supports it?

Registry, documentary evidence or another accepted verification source?

•If another record differs, should it?

A company office and a director's home should not be expected to coincide.

•If it should match but does not, why?

Resolve that explanation before sending an unrelated additional document.

These five questions eliminate much of the preventable confusion around address verification.

What merchants should not do

Do not respond to an address discrepancy by:

•Altering documents

•substituting an address merely because it matches another field

•calling an operating address a registered office when it is not

•using another entity's address without explaining the relationship

•hiding a director's relevant current information where legitimately required

•presenting obsolete information as current

•sending sensitive personal documents through insecure channels

The objective is not to create artificial consistency.

It is to make the actual structure verifiable.

Which address is actually blocking activation?

Address verification should also be treated as a dependency problem.

If onboarding has stopped because:

the merchant's registered office cannot be reconciled with the corporate record,

then uploading more information about a director's home address will not unblock the critical path.

Likewise, if:

a relevant individual's residential verification remains unresolved,

correcting the business website's office address may not solve that problem.

Ask:

Which subject, address type and unresolved discrepancy is preventing this verification stage from completing?

That turns a vague compliance delay into a specific operational dependency.

The London–Berlin–Paris merchant revisited

Return to the original example:

Merchant registered office

London

Merchant operating office

Berlin

Director residential address

Paris

What should match?

Not all three.

Instead ask:

London

Does this match the merchant's current registered-office evidence for the correct legal entity?

Berlin

Does this accurately represent the operating or principal business location being requested?

Paris

Does this correspond to the relevant director's residential information where that check is required?

If each answers a different question correctly, the existence of three addresses is not itself a verification failure.

If a source that should confirm one of those specific facts says something else, that is the discrepancy to resolve.

And that is the central lesson of address verification in KYC and KYB:

Do not ask whether every address matches. Ask whether each address matches the fact it is supposed to represent.

The fastest legitimate way to resolve an address discrepancy is therefore not to make the data look uniform.

It is to identify:

the subject

→ the address type

→ the verification purpose

→ the relevant evidence

→ the actual discrepancy

and correct only what is genuinely inconsistent.

That preserves the verification control while eliminating a large category of avoidable onboarding confusion.

This article provides general information and does not constitute legal, regulatory, compliance, tax, accounting, or financial advice. KYC and KYB requirements vary by jurisdiction, regulated activity, provider, financial institution, merchant structure, and risk profile. Merchants should verify current requirements with qualified advisers, relevant authorities, and their payment providers or acquirers.

🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂

A. Brief interpretation

This article owns one deceptively simple question: when an onboarding system says two addresses do not match, were those addresses ever supposed to be the same? The verification subject can be either the legal entity or a relevant natural person; the objective is to establish the correct address for that subject and purpose, not to force every address associated with a merchant into one value. The uploaded brief correctly makes address role the organizing principle.

The strongest authoritative anchor is FATF's current Recommendations, amended in June 2026. For legal persons, its customer-due-diligence framework explicitly distinguishes the registered-office address from a principal place of business when different.

C. Original article asset

The Address Verification Diagnostic should be the principal practical asset rather than a generic proof-of-address checklist.

Its visual flow should be:

ADDRESS MISMATCH DETECTED

↓

•WHO IS THE SUBJECT?

Legal entity / Director / UBO / Representative

↓

•WHICH ADDRESS TYPE?

Registered / Operating / Residential / Correspondence

↓

•WHAT VALUE WAS DECLARED?

↓

•WHAT SOURCE SUPPORTS IT?

Registry / Document / Reliable electronic source / Other approved evidence

↓

•ARE THE TWO VALUES SUPPOSED TO MATCH?

NO → Label both correctly → No inherent discrepancy

YES ↓

•IS THERE A LEGITIMATE EXPLANATION?

Recent move / pending registry update / service address / transliteration / group relationship

↓

•CAN THE DIFFERENCE BE VERIFIED?

YES → Resolve and document

NO → Escalate unresolved discrepancy

The critical design idea is that the flow asks “should these values match?” before “why don't they match?”

D. SEO & EDITORIAL NOTES — NOT PART OF THE ARTICLE

H1: Address Verification in KYC and KYB: Which Address Is the Provider Actually Checking?

Meta description: Learn how KYC and KYB address verification distinguishes registered, operating, residential and correspondence addresses—and how merchants should resolve genuine address mismatches.

URL slug: /address-verification-kyc-kyb/

Secondary keywords: KYC address verification, KYB address verification, proof of address KYC, business address verification, merchant address verification, registered address KYB, residential address KYC.

Related entities: registered office, principal place of business, operating address, residential address, correspondence address, service address, customer due diligence, legal entity, director, UBO, company registry, proof of address.

Excerpt: Address verification fails unnecessarily when merchants and providers compare addresses that represent different things. Registered offices, operating locations and personal residential addresses can legitimately differ. The first question is not whether the values match, but which subject and address type the provider is trying to verify.

Internal linking

Link to KYB Explained from the registered-office/principal-place-of-business discussion and to KYC Explained when the verification subject changes from the company to a director, UBO or representative.

Link to Corporate Structure Verification when different addresses belong to different group entities. That is particularly important because a group-company mismatch is fundamentally different from a simple address-format mismatch.

Avoid deep discussion of Bank Account Verification here. An address appearing on banking evidence may become relevant to a discrepancy, but account ownership and payout eligibility belong to the dedicated bank-account article.

Structured data

Use Article or BlogPosting, BreadcrumbList, and ImageObject.

A generic FAQ is not needed. The Address Verification Diagnostic has greater information value and better differentiates this article from conventional “acceptable proof of address documents” pages.

Supporting visual

Title: Which Address Should Match?

Four parallel lanes:

LEGAL ENTITY

Registered office

Principal/operating address

DIRECTOR / UBO

Residential address

Service/correspondence address

Then beneath them:

MATCH WITH THE EVIDENCE FOR THAT ADDRESS ROLE

—not—

MATCH EVERY ADDRESS TO EVERY OTHER ADDRESS

Recommended alt text: “Address Verification Diagnostic for KYC and KYB showing how registered office, operating address, residential address and correspondence address belong to different verification subjects and should be checked against the appropriate evidence.”

E. Source and verification plan

The strongest general source is the FATF Recommendations as amended June 2026. FATF states that its Recommendations are international standards implemented by countries according to their own legal and operational circumstances.

For this article specifically, the current Interpretive Note to Recommendation 10 is highly valuable because it expressly identifies the registered office and, if different, the principal place of business as separate information for legal persons. FATF also anchors identity verification in reliable, independent source documents, data or information rather than prescribing one global utility-bill model.

The UK Companies House material is useful only as a jurisdiction-specific illustration of why different addresses can legitimately coexist. Current guidance permits an appropriate service-provider address as the registered office, and Companies House material says that registered office need not be the company's day-to-day place of business. Its guidance also distinguishes directors' service and residential addresses.

For provider-policy differentiation, the FCA's current AML guidance is useful because it states that UK AML law and FCA rules do not dictate every procedural detail of CDD, reinforcing why a provider's proof requirements should not automatically be described as universal law.

Jurisdiction-specific claims to verify before adding them

Any localized version should separately verify current rules covering:

•Registered-office requirements

•principal-place-of-business definitions

•residential-address collection

•service/correspondence addresses

•accepted proof documents

•document-age limits

•electronic verification

•certified copies

•translations

•registry-update requirements

•virtual/shared office treatment

•address privacy rules

Do not transfer the UK examples into Germany, France, the EU generally, the US or another jurisdiction without checking that jurisdiction's current primary sources.

•Which address fields currently exist in the Business Profile

•Exact meaning of “business address”

•Whether registered and operating addresses are captured separately

•Which individuals currently undergo residential-address verification

•Current accepted evidence by verification subject

•Current electronic-verification options

•country-specific evidence differences

•translation/certification policy

•how recent moves are handled

•how registry discrepancies are handled

•treatment of service, virtual or shared office addresses

•current document-age rules

F. Human review recommendation

Author: Merchant onboarding/KYB specialist who routinely works with multinational legal entities.

Primary reviewer: KYC/KYB or AML compliance specialist.

Operations reviewer: Merchant onboarding operations lead who can validate whether the diagnostic reflects real address-discrepancy workflows.

Regional reviewer: Add a jurisdiction-specific compliance or legal specialist whenever the article introduces concrete address-document requirements, registered-office rules or document-age limits for a particular country.

Last-reviewed date: Publish prominently because both provider procedures and jurisdiction-specific verification requirements can change.

The article's final differentiation test should remain:

A merchant should read this article when it has several apparently conflicting addresses and needs to determine whether the addresses actually contradict each other—or simply represent different people, entities, locations and verification purposes.