RFC taxpayer lookup by name or partial data — is this possible via API?
nora_pm opened this thread ·
· 0 replies
rfc-lookupname-searchfuzzy-matchingbatch-api
Question
N
nora_pmAsker
We have a specific use case for RFC taxpayer lookup that's a bit different from standard validation. Our accounts receivable team handles invoicing for a large enterprise and often receives incomplete taxpayer information from clients. They might have a company name and state but not the full RFC, or they have a partial RFC with an uncertain homoclave.
What we need is an RFC taxpayer lookup capability that can search by: partial RFC (first 10 characters), company/taxpayer name, or a combination of name plus state. The goal is to resolve the full 13-character RFC so we can issue CFDIs correctly. Getting the RFC wrong on an invoice means it gets rejected by SAT's CFDI validation and we have to re-issue it — costing time and potentially causing payment delays.
Specific scenarios we deal with daily:
Client sends us "GALO850315" (10 chars) — we need to find the full RFC including homoclave
Client says their company name is "Tecnología Avanzada SA de CV" — we need to find their RFC
Client provides RFC but with a typo in the homoclave — we need fuzzy matching to suggest corrections
New client hasn't provided any RFC — we want to search by name and state before asking them
The volume is moderate — about 80-100 lookups per day. But accuracy is critical because an incorrect RFC on a CFDI has real financial consequences. We'd rather get a "multiple matches found" response that our team can disambiguate manually than a single wrong result.
I've seen some RFC taxpayer lookup APIs on apipull.com but most seem focused on exact RFC validation rather than search/discovery. Does anyone know of a provider that supports fuzzy or partial matching? Is name-based RFC lookup even legally available through SAT or would a provider need their own indexed database?
Our tech stack is PHP (Laravel) with a MySQL database. We'd integrate the RFC taxpayer lookup into our internal invoicing tool. Ideally the API would return a list of candidate matches ranked by confidence score so our team can pick the right one when there's ambiguity.
Also wondering about privacy implications — is there any restriction on searching for someone else's RFC by name? We're always doing this with the client's implicit consent (they want us to invoice them correctly) but I want to make sure we're not in a legal grey area.
Answers
● Thread open · 0 replies · Be the first to answer
We have a specific use case for RFC taxpayer lookup that's a bit different from standard validation. Our accounts receivable team handles invoicing for a large enterprise and often receives incomplete taxpayer information from clients. They might have a company name and state but not the full RFC, or they have a partial RFC with an uncertain homoclave.
What we need is an RFC taxpayer lookup capability that can search by: partial RFC (first 10 characters), company/taxpayer name, or a combination of name plus state. The goal is to resolve the full 13-character RFC so we can issue CFDIs correctly. Getting the RFC wrong on an invoice means it gets rejected by SAT's CFDI validation and we have to re-issue it — costing time and potentially causing payment delays.
Specific scenarios we deal with daily:
The volume is moderate — about 80-100 lookups per day. But accuracy is critical because an incorrect RFC on a CFDI has real financial consequences. We'd rather get a "multiple matches found" response that our team can disambiguate manually than a single wrong result.
I've seen some RFC taxpayer lookup APIs on apipull.com but most seem focused on exact RFC validation rather than search/discovery. Does anyone know of a provider that supports fuzzy or partial matching? Is name-based RFC lookup even legally available through SAT or would a provider need their own indexed database?
Our tech stack is PHP (Laravel) with a MySQL database. We'd integrate the RFC taxpayer lookup into our internal invoicing tool. Ideally the API would return a list of candidate matches ranked by confidence score so our team can pick the right one when there's ambiguity.
Also wondering about privacy implications — is there any restriction on searching for someone else's RFC by name? We're always doing this with the client's implicit consent (they want us to invoice them correctly) but I want to make sure we're not in a legal grey area.