Proof of address: what a utility bill does and does not prove
A proof-of-address document shows that an address was printed on a document, often with a name, at a date. Give it the weight of corroborating evidence, not verification, and set rules for name, recency and document type that fit each market.
Charles Archibong, Co-founder
· 5 min read
Key takeaways
- A proof-of-address document is corroboration: an address, a name and a date on paper, not proof of residence.
- In some markets the bill names the meter or the landlord, so a strict name rule fails honest applicants.
- Recency matters: set a maximum document age per document type.
- The document gains weight when independent evidence, such as the government record or a map pin, agrees with it.
A proof-of-address document deserves the weight of corroborating evidence, not verification. A utility bill proves that someone printed an address on a document, often alongside a name, at some date. It does not prove the applicant lives there, that the document is unaltered, or that the name on it belongs to the person in front of you.
That still makes it useful. Its value depends on four things you can control: which documents you accept, whether you require the applicant's name on it, how recent it must be, and whether other evidence agrees with it. Set those deliberately, per market, and treat the document as one input into an address decision rather than the decision.
What does a proof-of-address document actually show?
Claim | Does the document support it? |
|---|---|
This address exists and receives bills or statements | Usually yes |
An account was registered to this address at this date | Yes, if the document is genuine |
The applicant's name is associated with the address | Only if the name is printed and matches |
The applicant lives there now | No; at most they did when it was issued |
The document has not been edited | No; the document cannot vouch for itself |
The applicant is the person the document names | No; that needs an identity check |
The last two rows matter most. A downloaded statement is easy to edit, and a real bill belonging to a relative or landlord is easy to borrow. Neither is detectable from the address on the page.
Whether you must collect proof of address at all, and which documents count, depends on your regulator and your risk assessment. Requirements differ by jurisdiction; this article is general information, not legal advice.
Why does a strict name rule fail in some markets?
The textbook check is "the applicant's name must appear on the document". It works where every household holds utilities and bank accounts in its own name. It fails where they do not.
In some markets a bill names the meter or the landlord rather than the person who lives there. Tenants in a shared building may sit behind one meter registered to the landlord, a prepaid electricity receipt may identify a meter rather than a customer, and adult children often live in homes whose accounts are in a parent's name. A strict name rule in those settings fails honest applicants while doing little against a determined fraudster who can open an account in their own name at an address they do not live at.
A better approach sets the name rule by document type and country:
Document | Where names are reliable | Where they are not |
|---|---|---|
Bank statement | Require the name | Require the name |
Tenancy agreement | Require the name | Require the name |
Utility bill | Require the name | Record the name if present, but do not fail on it |
Government-issued letter | Require the name | Require the name |
"Record but do not fail" keeps the information: a rule can still send a missing name to review when other signals are weak.
How recent should the document be?
A three-year-old bill shows where someone lived three years ago. Set a maximum age, and consider setting it by document type. A monthly bill or statement can reasonably be required to be recent; a tenancy agreement covers a period, so its start date matters less than whether it is still running.
Two practical cautions. First, date extraction from real-world bills is imperfect, so decide what happens when no date can be read (reject, or route to review) rather than letting the default decide for you. Second, tell the applicant the age limit before they upload; learning the rule from a rejection costs the applicant a second attempt, and some will not make one.
When does the document earn more weight?
Corroboration is the point. A proof-of-address document becomes strong evidence when something independent agrees with it:
The government record. If the identity check returned an address from the government record and it names the same area, two sources agree.
The applicant's location. A pin the applicant drops on a map, especially with a device location fix taken as they confirm, that lands in the same locality as the bill.
Your own history. An address the customer has used consistently for deliveries or previous verifications.
Compare at the level of the locality (town, district or area) rather than the exact string. Free-text addresses are written in endless ways, and a strict string comparison produces mismatches out of formatting alone.
A worked example
A consumer lender in Accra and one in Lagos both collect proof of address.
Applicant A uploads a bank statement dated five weeks ago, with her name and an address in East Legon. Her identity check returned a government record address in the same area. Two sources agree, the name matches, the document is recent. Treat the address as corroborated.
Applicant B uploads a prepaid electricity statement from Surulere with a meter number and no name. It is recent. The government record gives an address in Ikeja. His map pin lands in Surulere. The document and the pin agree with each other but not with the older government record, which is common after a move. Route to a light review rather than decline, and consider asking for a second document.
Applicant C uploads a bill in someone else's name, eight months old, in a different city from both his government record and his pin. Nothing agrees. Ask for a different document, and decline if none arrives.
How Myaza Trust handles proof of address
A workflow's Proof of Address step collects a utility bill, bank statement, tenancy agreement or government-issued document, reads the address, checks the document's age and applies your name rule, which you set to Required, Optional or Not needed per workflow, with per-country and per-document exceptions. The result is a soft one: it never changes the verification's own pass or fail status, and your decision rules route on verification.poaStatus, verification.poaNameMatch and verification.poaDocumentAgeDays. See the workflows documentation for the step.
Address Intelligence adds the corroboration: the applicant's map pin is compared at locality level with the government record's address and the proof-of-address document. Both can run inside a full Identity Verification flow, or on their own in an address-only workflow for customers verified elsewhere.
Rules to set before you launch
List the documents you accept, per country.
Set the name rule per document type and country, not globally.
Set a maximum document age, and decide what happens when no date is readable.
Tell the applicant the rules on the upload screen.
Route on agreement between sources, not on the document alone.
Keep proof of address out of the identity decision; it answers where, not who.
Sources
Charles Archibong
Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
