Homeโ€บArticlesโ€บGuideโ€บUS Everyday Formatters
GUIDE

US Everyday Formatters: Addresses, Phone Numbers & Currency

A guide to formatting US addresses, phone numbers, currency, ZIP codes, and EINs correctly โ€” with the standard formats forms and systems expect.

Updated 2026-07-04

Overview

Formatting American addresses, phone numbers, and currency correctly seems like it should be trivial, but it's exactly the kind of detail that causes real problems when it's wrong โ€” a misformatted ZIP code with a dropped leading zero fails delivery-address validation, an EIN entered without its hyphen gets rejected by a business form, and a phone number typed in three different formats across a customer database makes deduplication and lookup unreliable. This guide covers the standard US formats for these everyday but frequently mishandled data types.

None of these formats are complicated once you know them, but they're specific enough that getting them wrong is easy, especially when data comes from multiple sources (a spreadsheet, a form, a scraped list) that each format things slightly differently before you consolidate them. The problems these formatting mistakes cause also tend to surface at inconvenient times โ€” a rejected form submission during a business registration deadline, a piece of mail delayed during a critical filing window, or a customer record that duplicates silently in a database because two entries used different phone number punctuation.

The fix in every case below is the same idea applied to a different data type: standardize on one format at the point of entry, rather than trying to clean up inconsistent formats after they've already spread across a spreadsheet, a database, or a mailing list.

Step 1: Format a US Mailing Address Correctly

The US Address Formatter applies USPS standard formatting โ€” recipient name on the first line, street address on the second, and city, two-letter state abbreviation, and ZIP code on the final line, conventionally in uppercase with minimal punctuation for optimal machine scanning. This matters most for bulk mailings and mail merges, where USPS automated sorting equipment reads addresses optically, and inconsistent formatting across a mailing list increases the chance of a piece being misrouted or delayed. For domestic US mail, omit the country name entirely โ€” it's only needed when mailing internationally.

Step 2: Get the ZIP Code and ZIP+4 Right

The ZIP Code Formatter validates and formats the base 5-digit ZIP code and the optional ZIP+4 extension, which narrows delivery down to a specific block or building for faster automated sorting. The single most common ZIP code error is a dropped leading zero โ€” ZIP codes across the northeastern US and Puerto Rico start with 0, and if a spreadsheet or database stores the ZIP as a number rather than text, that leading zero silently disappears, turning a valid ZIP code into an invalid one that no longer matches any real location.

Step 3: Standardize US Phone Number Formatting

The US Phone Formatter converts a raw string of digits into the standard (555) 123-4567 display format, which matters for both readability and for passing form validation that expects a specific pattern. Databases that accumulate phone numbers from multiple entry points โ€” a web form, a CSV import, a manually typed customer record โ€” often end up with the same number stored in several visually different formats, which breaks simple deduplication and exact-match lookups until everything is normalized to one consistent format.

If you're integrating with an SMS or telephony API rather than displaying a number to a person, check whether that specific system requires E.164 format instead (a plus sign, country code, and digits with no other punctuation) โ€” that's a different standard than the domestic display format this formatter produces, and using the wrong one will cause API calls to fail even though the underlying phone number is correct.

Step 4: Format US Currency Amounts Consistently

The US Currency Formatter applies the standard US convention โ€” a dollar sign directly before the number with no space, commas as thousands separators, and a period as the decimal point (for example, $1,234.56). The most common error isn't the dollar sign or decimal placement but comma consistency in larger numbers, and occasionally confusion with the European convention that swaps the roles of the comma and period entirely. For negative amounts, decide up front whether your context calls for a minus sign (more common in general software and writing) or parentheses (the traditional accounting and financial-statement convention), since mixing the two within the same document reads as inconsistent.

Step 5: Format an EIN Correctly

The EIN Formatter applies the standard XX-XXXXXXX format to a nine-digit federal Employer Identification Number, placing a hyphen after the second digit. Many business registration forms, payroll systems, and financial software validate EIN input against this exact pattern and will reject an EIN typed as a plain nine-digit string with no hyphen, or with the hyphen misplaced, even though the underlying nine digits are correct โ€” getting the punctuation right the first time avoids a rejected form submission over what's ultimately a cosmetic formatting detail. See the EIN glossary entry for more on what the number itself represents and how it's assigned.

Key Terms

  • USPS Standard Address Format โ€” the recipient name, street address, and city/state/ZIP line format that US Postal Service automated sorting equipment is optimized to read
  • ZIP+4 โ€” the optional four-digit extension to a standard US ZIP code that narrows delivery to a specific block, building, or high-volume recipient
  • E.164 โ€” an international phone number formatting standard (a plus sign, country code, then digits with no other punctuation) commonly required by SMS and telephony APIs, distinct from standard US domestic display formatting
  • EIN โ€” Employer Identification Number, a nine-digit federal tax ID issued by the IRS to businesses in the format XX-XXXXXXX

Frequently Asked Questions

USPS standard formatting places the recipient name on line one, street address on line two, and city, two-letter state abbreviation, and ZIP code on the final line, all in uppercase with no punctuation for machine-readable optical scanning. The [US Address Formatter](/us-address-formatter/) applies this standard automatically, which matters most for mail merges and bulk mailings where inconsistent formatting can cause USPS automated sorting to misread an address and delay delivery.
No โ€” for mail sent within the United States, including "USA" or "United States" on the address is unnecessary and can occasionally confuse international sorting systems if the mail is briefly routed through one; USPS guidance is to omit the country line entirely for domestic mail and only include it when mailing internationally to the US from abroad.
The base 5-digit ZIP code identifies a general delivery area, while the additional 4-digit extension (ZIP+4) narrows delivery down to a specific block, building, or even a single high-volume mail recipient, which speeds up USPS automated sorting. The [ZIP Code Formatter](/zip-code-formatter/) validates and formats both forms โ€” use ZIP+4 when you have it, since it's optional for senders but preferred by USPS automation.
Raw ten-digit strings are valid for storage, but display formatting โ€” (555) 123-4567 versus 555-123-4567 versus 555.123.4567 โ€” affects both readability and how forms validate the input, since some systems expect a specific pattern and reject numbers that don't match it exactly. The [US Phone Formatter](/us-phone-formatter/) standardizes the display format, which matters for consistency across a customer database that might otherwise have the same number stored in three different visual formats.
US currency convention places the dollar sign directly before the number with no space, uses a comma as the thousands separator, and a period for the decimal point (e.g. $1,234.56) โ€” the most common formatting error is inconsistent comma placement in numbers over a thousand, or confusing the US convention with the European convention that swaps the comma and period. The [US Currency Formatter](/us-currency-formatter/) applies the standard format consistently, including correct handling of negative amounts, which are conventionally shown in parentheses in accounting contexts rather than with a minus sign.
An EIN (Employer Identification Number) is a nine-digit federal tax ID issued by the IRS to businesses, formatted as XX-XXXXXXX with a hyphen after the second digit. The [EIN Formatter](/ein-formatter/) applies this standard format, which matters because many business forms and financial software validate EIN input against this exact pattern and will reject a nine-digit string with no hyphen or a hyphen in the wrong position.
EIN prefixes (the first two digits) are assigned by IRS campus and historically indicated which service center issued the number, though this system has been phased toward centralized assignment over time. There's no publicly meaningful business information encoded in the prefix the way there sometimes is in other identifier formats, so formatting correctly matters more for passing validation checks than for interpreting anything about the business from the number itself.
Most US systems accept the standard (555) 123-4567 or 555-123-4567 formats for both voice and SMS use, but international or programmatic systems (like SMS APIs) often require E.164 format instead โ€” a plus sign, country code, and digits with no other punctuation (+15551234567). The [US Phone Formatter](/us-phone-formatter/) is built for the standard domestic display format; if you're integrating with an API that specifically requires E.164, check that system's documentation for the exact expected format.
The main formatting issue is leading zeros โ€” ZIP codes in the northeastern US, including much of New England and Puerto Rico, start with 0, and if the ZIP code is stored or entered as a number rather than a text string, the leading zero can be silently dropped (00501 becomes 501), which then fails to match the real ZIP code. The [ZIP Code Formatter](/zip-code-formatter/) preserves the leading zero and validates the correct 5-digit or ZIP+4 length.
The conventional order is name, street address (including apartment/suite number), city, state, ZIP code, which matches USPS mail-sorting logic and is what most US-based form validation and address-autocomplete systems expect. Deviating from this order โ€” putting ZIP code before city, for example โ€” can cause address-verification APIs to fail even when all the individual pieces of information are correct.
Both conventions exist depending on context โ€” general writing and most software commonly uses a minus sign (-$50.00), while formal accounting and financial statements traditionally use parentheses ($50.00) to indicate a negative or debit amount, since a minus sign can be easy to miss at a glance in a dense table of numbers. The [US Currency Formatter](/us-currency-formatter/) can apply either convention depending on which context you're formatting for.

Related Articles

GUIDE

Everyday ID Checks: Phone, ZIP & Vehicle Registration Validators

GUIDE

More Everyday Conversions: Currency History, GPA & Odd Units

COMPARISON

Life Path vs Destiny vs Birthday Number (Numerology Numbers Compared)

GUIDE

Stud to Siding: Framing a House by the Numbers

GUIDE

Data Format Validators: IPs, MAC Addresses, ISBNs & More