RFC Translation: Mexico's Tax ID (Registro Federal de Contribuyentes)

RFC stands for Registro Federal de Contribuyentes, the Federal Taxpayer Registry. It is Mexico's tax identification code, assigned and administered by the SAT (Servicio de Administracion Tributaria), the federal tax authority that sits under the Secretaria de Hacienda y Credito Publico. The closest U.S. analogy is the IRS, and the RFC plays a role broadly similar to a U.S. taxpayer identification number.

The single most important thing to understand is that the RFC is not a standalone document and it is not an identity document. It is a registration key, a 'clave', that appears printed on other fiscal paperwork. You do not get handed 'an RFC' the way you get a birth certificate; you get a tax document that displays your RFC inside it.

The SAT issues the RFC only to people and entities engaged in economic activity, such as earning income, invoicing, or running a business. That is a narrower group than the population at large, which is one of the cleanest ways to tell the RFC apart from the CURP that everyone in Mexico holds.

Because it is a fiscal registration key rather than civil or relationship evidence, the RFC has no standalone weight for immigration purposes. It matters only as one field on a larger document that may need translating. Throughout this guide we treat it that way: a code to be reproduced precisely, surrounded by labels and fields that get translated into English.

If the document carrying the RFC is, say, a Mexican birth certificate or another civil record rather than a tax form, the certified Spanish civil-document translation we produce reproduces every printed code exactly while rendering the labels in English.

For an individual ('persona fisica'), the RFC is 13 characters. The first four are letters drawn from the name: the first letter and first internal vowel of the paternal surname (apellido paterno), the first letter of the maternal surname (apellido materno), and the first letter of the given name. The next six characters are the date of birth as digits in YYMMDD format, zero-padded. The last three are the homoclave.

For a company ('persona moral'), the RFC is 12 characters. The first three characters are letters derived from the company's legal name (the denominacion or razon social) following SAT's derivation rules: typically the initials of the first three significant words, but with articles, prepositions and conjunctions skipped, and additional letters drawn from inside a word when the name has fewer than three significant words. Those letters are followed by the six-digit incorporation date in YYMMDD format and, again, a three-character homoclave.

The homoclave is the part people most often misunderstand. It is a three-character alphanumeric segment assigned exclusively by the SAT to make each RFC unique and prevent two people or companies from ending up with an identical key. It is computer-generated, it carries no translatable meaning, and it must be transcribed exactly as printed.

Two structural details deserve flags. First, the embedded date uses a two-digit year, so the century is ambiguous: a '99' could mean 1899 or 1999. A translator never expands or reinterprets the date inside the code, and relies instead on other dated fields on the document for the real birth or incorporation date. Second, the letters can look 'wrong': when the first four name letters would spell an offensive or inconvenient word, SAT replaces the offending letter (typically the last of the four) with an 'X'; it skips particles like 'de', 'la' and 'y'; and it pads short names with filler 'X' characters. None of that is an error to be corrected.

SAT illustrates the layout with a schematic placeholder rather than a real key: an individual's slots are shown as four name letters, then the six-digit YYMMDD date, then a three-character homoclave (the pattern AAAA + YYMMDD + a three-character homoclave). We describe the slots this way only to show the structure, never as anyone's actual RFC.

The RFC and the CURP are the two Mexican codes most likely to be mixed up, because both are built from a person's name and date of birth and therefore look superficially alike. They are separate identifiers issued by different authorities for different purposes, and a translation must label each one correctly.

The CURP (Clave Unica de Registro de Poblacion) is an 18-character population and identity registry code issued by RENAPO. Every resident has one. The RFC is shorter (13 characters for an individual, 12 for a company), is issued by the SAT, and exists only for tax purposes. An individual's RFC overlaps in logic with the opening characters of the CURP, but it is a distinct, shorter code, and it does not 'contain' the full CURP.

In practice you may see both codes on the same document, for example on a Cedula de Identificacion Fiscal. The translator's job is to keep them apart: label the 18-character string as the CURP and the 13- or 12-character string as the RFC, and never let one be presented as the other.

If you specifically need to understand the CURP, our dedicated walkthrough covers its structure, issuer and translation handling in detail.

Names are also where these codes most often appear to 'disagree' with each other, because Mexican paternal and maternal surnames feed each code differently. When a name on one document does not visibly line up with another, our name-discrepancy walkthrough explains how a certified translation documents the variation without altering any code.

The most common modern carrier of the RFC is the Constancia de Situacion Fiscal (CSF), a SAT-issued Certificate of Tax Status. It lists the RFC alongside the holder's name or razon social, the tax address (domicilio fiscal), the tax regime (regimen fiscal) and the SAT registration date. Employers and counterparties request it constantly, so it surfaces often in financial paperwork.

Closely related is the Cedula de Identificacion Fiscal (CIF), a SAT card or certificate that displays the RFC together with a QR code used for online validation. Near that QR you may also see an 'IDCIF', the CIF's own numeric identifier, which must be transcribed but never confused with the RFC itself.

The RFC also appears on facturas, the electronic tax invoices known as CFDI, which carry both the issuer's and the recipient's RFC. The variant most relevant to immigration is the CFDI de nomina, the payroll or income receipt that shows an employee's RFC, since that is the kind of income evidence that can travel into a filing.

Watch out for generic placeholder RFCs on invoices. 'XAXX010101000' is labeled PUBLICO EN GENERAL (the domestic public or an unidentified customer) and 'XEXX010101000' is the generic code for foreign clients without Mexican tax residency. These are placeholders, not a specific taxpayer's key, and should never be read as the client's personal RFC. Where the label appears, 'PUBLICO EN GENERAL' is rendered 'GENERAL PUBLIC' with a note that it is a generic code.

Because many of these tax documents accompany civil records in a green-card file, the same translation order often also covers items like a certified Spanish birth certificate translation alongside the income paperwork.

Let's be precise about relevance, because it is easy to overstate. The RFC is secondary, supporting material only. It is never primary civil or relationship evidence, and it does not establish identity, civil status, or a family relationship. It is simply a field that happens to sit on a Mexican financial or tax document a sponsor or applicant might submit.

The realistic place the RFC appears is on income or employment evidence, most plausibly documents offered in support of a Form I-864 Affidavit of Support under Section 213A of the INA, or other proof of income. Even there, the limits matter: the I-864 income determination rests on U.S. federal tax returns and U.S. income documentation. A Mexican document bearing an RFC is at most supplementary corroboration of foreign income or employment, never a substitute for the required U.S. tax records.

USCIS has no policy that names the RFC specifically, so no one should claim that USCIS 'recognizes' or 'requires' it. We describe its role by inference from how Mexican income documents function under the I-864 rules, not as any official statement about the code.

What is firmly established is the translation obligation. Under 8 CFR 103.2(b)(3), any document containing a foreign language submitted to USCIS must be accompanied by a full English translation that the translator certifies as complete and accurate, together with the translator's certification of competence. So whenever a Spanish document carrying an RFC is filed, it needs a certified English translation, regardless of how minor the RFC field is.

RFC-bearing income evidence most often rides along with a green-card application, so the practical takeaway is to translate the whole document properly and let the RFC be one accurately reproduced field among many.

Our certified translations are produced specifically for green-card and adjustment-of-status filings, with the certification language USCIS expects.

The governing rule is simple: transcribe the code, translate the labels. The RFC string, including its homoclave, is reproduced character-for-character exactly as printed. The label around it is what changes language, so 'Clave del RFC' becomes 'RFC code' or 'RFC key' while the value stays untouched. The code is never translated, normalized, expanded, or 'corrected'.

That discipline extends to all the apparent oddities. An 'X' where a name letter is expected, a missing 'de la' particle, filler letters in a short name, a two-digit year with an ambiguous century: every one of these is intentional SAT behavior, and a translation that 'fixes' them is wrong. The surrounding document fields, not the code, are where the actual date and full name are read.

The Spanish labels around the RFC do get clear English equivalents. 'Domicilio fiscal' becomes 'Tax address', 'Regimen fiscal' becomes 'Tax regime', 'Constancia de Situacion Fiscal' becomes 'Certificate of Tax Status' and 'Cedula de Identificacion Fiscal' becomes 'Tax Identification Card'. A particular false friend to avoid: 'persona moral' is a legal entity or juridical person, not a 'moral person', and 'razon social' is the corporate or legal business name.

Machine elements and officialdom must be accounted for, because USCIS expects everything on the page to be rendered. The QR code on a CSF or CIF is noted as a placeholder such as '[QR code]' rather than encoded, any seal or stamp text is translated into English, and the 'HACIENDA / Secretaria de Hacienda y Credito Publico' and 'SAT / Servicio de Administracion Tributaria' mastheads are translated or glossed with their acronyms retained.

Done correctly, the result reads as a faithful English mirror of the Mexican document: every label in English, every code, including the RFC and its homoclave, reproduced exactly, and nothing invented or omitted. If you want this handled by a Spanish-English specialist, you can start a certified RFC document translation and have your Registro Federal de Contribuyentes paperwork delivered in 24 hours.