A NACHA file is a standardized electronic record that banks use to process batches of payments all at once

NACHA stands for the National Automated Clearing House Association, the organization that sets the rules for how banks move money between accounts. A NACHA file is the actual document — usually a plain text file with a .ach or .txt extension — that contains payment instructions in a format every bank in the United States recognizes. When your employer deposits your paycheck or a company bills your account automatically, that transaction travels through the banking system inside a NACHA file.

You will most often encounter NACHA files if you run a business, manage payroll, or work in accounting. If you use online banking to send a single payment to one person, you are not creating a NACHA file — your bank handles that behind the scenes. But if you need to send 50 paychecks at once, or receive 100 customer payments in a single batch, a NACHA file is how that happens.

Key Takeaways

  • A NACHA file is a text document that holds multiple payment instructions in a format banks recognize, allowing them to process many transactions at once instead of one at a time.
  • The file contains sender information, receiver information, dollar amounts, and account numbers, all arranged in rows that follow strict formatting rules.
  • Payroll deposits, bill payments, and customer refunds often travel through NACHA files, even though you never see them as a consumer.
  • If you need to create or send a NACHA file, accounting software, payroll platforms, and your bank's business portal can generate them for you.
  • NACHA files are plain text and can be opened in any text editor, but the formatting is rigid — even a misplaced space can cause a bank to reject the entire batch.

How a NACHA file is structured

A NACHA file is organized into sections, each with a specific purpose. The file starts with a header that identifies who is sending the batch, which bank is processing it, and when it was created. Then come the individual transaction records — one row per payment, with the sender's account, the receiver's account, the amount, and a description. The file ends with a trailer that totals up all the transactions so the bank can verify nothing was lost or duplicated.

Every piece of information sits in an exact position. The sender's routing number must start at character 4 and end at character 12. The account number goes in a different fixed spot. If you move a number one space left or right, the bank's computer will not recognize it and will reject the entire batch. This is why NACHA files are almost never created by hand — payroll software, accounting platforms, and banking portals generate them automatically to avoid these errors.

The file itself is plain text, so you can open it in Notepad or any text editor and read it. But what you will see is rows of numbers and letters with no spaces between them, because the format prioritizes machine readability over human readability. A single NACHA file can contain hundreds or thousands of transactions, all processed together in one batch.

Common uses for NACHA files in business

Payroll is the most common use. When a company with 500 employees pays everyone on Friday, it does not send 500 separate bank transfers. Instead, the payroll system generates one NACHA file containing all 500 deposits, and the bank processes them all at once. The same happens with bill payments — a utility company that collects payments from 10,000 customers receives them through NACHA batches, not individual transactions.

Refunds work the same way. If an online retailer processes 200 refunds in a day, those go out in a NACHA file. Loan payments, insurance premiums, and subscription charges often travel through NACHA files too. Any time a business or organization needs to move money to many accounts at once, a NACHA file is usually the tool.

For the person receiving the money, the process is invisible. Your paycheck arrives in your account the same way whether it came through a NACHA file or any other method. But on the sending side, NACHA files save time and reduce errors because one file replaces hundreds of individual transactions.

Where NACHA files come from and how they are sent

You do not create a NACHA file by typing it out. Payroll software like ADP, Gusto, or QuickBooks generates NACHA files automatically when you tell it to process payroll. Accounting software does the same for bill payments. Your bank's business portal often has a tool to upload a NACHA file that you have received from a vendor or partner.

Once the file is created, it is sent to a bank through a find connection — usually through the bank's online portal, sometimes through an encrypted email or a dedicated file transfer service. The bank receives the file, validates that the format is correct and the math adds up, and then processes all the transactions in the batch. If something is wrong — a mismatched total, a malformed account number, a routing number that does not exist — the bank rejects the entire batch and sends back an error report.

Processing usually takes one to two business days. The bank does not move the money when ready; instead, it schedules the transactions to clear on a specific date, which is why payroll deposits often arrive on the same day even though they were all sent in one file.

Why the format is so strict

NACHA files follow rigid rules because they move real money between real accounts, and there is no room for ambiguity. A space in the wrong place could cause a payment to go to the wrong account. A digit out of order could change the amount. The format was designed in the 1970s when computer memory was expensive and processing power was slow, so every character had to count. The rules have stayed the same for decades because changing them would require every bank in the country to update their systems at the same time.

This strictness is also a security feature. Because the format is so specific, a NACHA file that does not match the standard format is obviously corrupted or fraudulent. A bank can reject it when ready without having to examine the content. If someone tries to alter a NACHA file by hand — changing an amount or an account number — the format breaks and the bank catches it.

Storing and backing up NACHA files

If you work with NACHA files, you will want to keep copies for your records. A NACHA file is just a text file, so it takes up very little space — even a file with 1,000 transactions is usually less than 100 kilobytes. You can store it on your computer, on a network drive, or in cloud storage like Google Drive or Dropbox.

Because NACHA files contain account numbers and routing numbers, treat them as sensitive documents. Store them in a folder that is password-protected or encrypted. If you use cloud storage, make sure the folder is not shared publicly. Many businesses keep NACHA files in a dedicated folder on their accounting server, with access limited to the people who need it.

Organize NACHA files by date and purpose — for example, "Payroll_2024_01_12" or "Customer_Refunds_January". This makes it straightforward to find a specific batch if you need to look up a transaction later. Keep files for at least three to seven years, depending on your industry and tax requirements — your accountant can tell you how long to retain them.

What happens if a NACHA file is rejected

Banks reject NACHA files for a few common reasons. The most frequent is a formatting error — a character in the wrong position, a missing field, or a calculation that does not match. The second is a bad account number or routing number — if the receiving bank does not exist or the account is closed, the batch fails. The third is a mismatch in the total — if the header says the batch contains $50,000 but the transactions add up to $49,999, the bank rejects it.

When a batch is rejected, the bank sends back an error report that explains what went wrong. If the error is in the format, you will need to fix the file in your software and resubmit it. If the error is a bad account number, you will need to correct the account information and try again. No money moves until the file is accepted, so a rejection just means a delay, not a loss.

Frequently Asked Questions

Can I open a NACHA file in Excel or Google Sheets?

You can open it, but it will not look right. NACHA files are plain text with fixed-width columns, so a spreadsheet will either show everything in one column or break the formatting. If you need to view or edit a NACHA file, use a text editor like Notepad, or use your payroll or accounting software to view it in a readable format.

Is a NACHA file the same as an ACH file?

Yes. ACH stands for Automated Clearing House, and NACHA is the organization that sets the standards. The file format is called the NACHA format or the ACH format interchangeably. You may see files with a .ach extension or a .txt extension — they are the same thing.

What if I receive a NACHA file from someone else?

If a vendor or partner sends you a NACHA file, you will upload it to your bank through your business portal. Your bank will validate it and process the transactions. You do not need to do anything to the file itself — just make sure it comes from a trusted source before uploading it, since it will contain account information.

Do I need to create NACHA files myself?

Almost never. Your payroll software, accounting software, or bank portal creates them for you. The only time you might manually work with a NACHA file is if you are a developer building a payment system, or if you are troubleshooting a rejected batch with your bank or software provider.

How long does it take for a NACHA batch to process?

Once your bank accepts the file, processing usually takes one to two business days. The bank does not move the money when ready — it schedules the transactions to clear on a specific date. Weekends and holidays add extra time, so a batch submitted on Friday may not clear until Tuesday.