NetSuite EFT Payments: Setup & Configuration Guide

If you're still printing checks for vendor payments in NetSuite, you're spending more time and money than you need to. Electronic Funds Transfer — EFT — lets you pay vendors, reimburse employees, and process payroll directly through bank-to-bank transfers, all generated from within NetSuite. No paper, no postage, no waiting for checks to clear.

TL;DR: NetSuite's EFT feature lets you generate bank files (NACHA/ACH for the US, BACS for the UK) to pay vendors and employees electronically. You enable EFT under Setup > Company > Enable Features, configure bank accounts with routing details, add vendor bank information, create or customize file templates for your bank's format, then use payment batches to select bills, generate the file, and upload it to your bank portal. It replaces manual check runs with faster, cheaper, more auditable electronic payments.

The EFT process in NetSuite isn't complicated once you understand the moving parts. But the setup has enough configuration steps — and enough bank-specific quirks — that getting it wrong means rejected files, delayed payments, and frustrated vendors. This guide walks through the full setup, day-to-day processing, and the issues you'll actually run into.

---

What EFT means in NetSuite

EFT is an umbrella term in NetSuite covering any payment that moves money electronically between bank accounts. That includes ACH payments (the US Automated Clearing House network), direct deposits for employee payroll, BACS transfers in the UK, SEPA payments in Europe, and wire transfers. If money moves from your bank account to someone else's without a physical check, it's an EFT.

In practice, most US-based NetSuite customers use EFT for two things: ACH vendor payments (paying bills without printing checks) and direct deposit (payroll). The mechanics are the same — NetSuite generates a formatted file containing payment instructions, you upload that file to your bank, and the bank executes the transfers.

This is fundamentally different from payment gateway processing where a processor like Stripe or Adyen handles the transaction in real time. EFT is batch-based: you collect payments, generate a file, upload it, and the bank processes everything on its schedule (typically 1-2 business days for ACH).

---

EFT vs. manual check payments

The case for EFT over checks is straightforward.

Speed. Checks take 5-10 business days to reach a vendor, get deposited, and clear. ACH payments settle in 1-2 business days. Same-day ACH is available for an additional fee.

Cost. Printing and mailing a check costs $4-8 per payment when you factor in paper, toner, envelopes, postage, and the labor to stuff and mail them. ACH payments cost $0.20-1.00 per transaction depending on your bank. At 200 vendor payments per month, that's $800-1,600 in savings.

Reconciliation. Checks create reconciliation headaches — outstanding checks that haven't cleared, stale-dated checks, stop payments, lost checks that need reissuing. EFT payments hit the bank predictably, making reconciliation cleaner and reducing the time your accounts payable team spends chasing down discrepancies.

Security. Checks can be lost, stolen, altered, or forged. EFT payments go directly to verified bank accounts through encrypted bank networks. Combined with dual-approval workflows in NetSuite, EFT is significantly more secure than paper checks.

---

How to set up EFT in NetSuite

Enable the EFT feature

Go to Setup > Company > Enable Features > Accounting (some versions show this under the Payments subtab). Check the Electronic Funds Transfer box. This unlocks EFT-related fields on bank accounts, vendor records, and employee records, and makes payment batch processing available.

If you also need to process positive pay files (a fraud prevention measure where you send your bank a list of issued payments), enable that option at the same time.

Configure bank accounts for EFT

Open your bank account record (Setup > Accounting > Bank Accounts or navigate to the account in your Chart of Accounts). On the Electronic Funds Transfer subtab, enter:

• Bank routing number — your bank's ABA routing number (9 digits for US banks)
• Bank account number — your company's account number at the bank
• Company identification — typically your EIN or a company ID assigned by your bank for ACH origination
• EFT file format — select the template that matches your bank's requirements

The company identification field trips people up. Your bank assigns this when you set up ACH origination, and it's not always your EIN. If the bank rejects your first file, this is one of the first things to check.

Set up vendor bank details

Each vendor you want to pay via EFT needs their banking information on file. Open the vendor record and navigate to the Entity Bank Details subtab. Enter:

• Bank name
• Bank routing number (ABA number for US banks)
• Bank account number
• Account type (checking or savings)

This information typically comes from the vendor during onboarding. If you're using a platform like Tipalti for AP automation, vendor bank details are collected and validated through Tipalti's vendor portal and synced to NetSuite automatically — which is much cleaner than chasing vendors for ACH forms via email.

Create or customize EFT file templates

This is where most of the bank-specific configuration happens. NetSuite includes standard EFT file templates for common formats — NACHA (the standard US ACH file format), BACS (UK), and several others. But many banks require a specific variant of NACHA with particular header values, company entry descriptions, or addenda record formats.

Go to Setup > Accounting > EFT File Templates (or search for "EFT" in the global search). You can either:

1. Use a built-in template if your bank accepts standard NACHA format
2. Clone and customize an existing template if your bank needs specific field values
3. Create a custom template using NetSuite's template editor for banks with proprietary file formats

The NACHA file format has a specific structure: a file header, batch headers, entry detail records (one per payment), and corresponding trailers with hash totals. If your bank rejects the file, the issue is almost always in the header records — wrong immediate origin, wrong company identification, or wrong standard entry class code (PPD for payroll, CCD for vendor payments).

Pro tip: Get a sample file from your bank before you start configuring. Comparing the expected format against what NetSuite generates saves hours of back-and-forth troubleshooting.

---

Payment batch processing

Day-to-day EFT processing in NetSuite happens through payment batches. This is the workflow your AP team will follow weekly or biweekly.

Creating a payment batch

Navigate to Transactions > Bank > Payment File Administration (or search for "Payment Batch"). Create a new batch and select:

• Bank account — the account funds will be drawn from
• Payment method — EFT/ACH
• Subsidiary (if multi-subsidiary)

Selecting bills for payment

NetSuite shows you all approved vendor bills eligible for payment. You can filter by due date, vendor, amount, or payment terms. Select the bills you want to include in this batch. The system totals everything so you can verify the batch amount before proceeding.

Most AP teams run batches on a schedule — weekly payment runs are the most common. Some companies run separate batches for different bill categories: recurring vendor payments on one schedule, one-time invoices on another.

Generating the EFT file

Once you've confirmed the batch, NetSuite generates the EFT file using your configured template. The file contains all the payment instructions formatted for your bank — routing numbers, account numbers, amounts, and identification details.

Download the file. It's a plain text file with a specific structure (for NACHA, it's a fixed-width format with 94-character records). You don't need to open or edit it — but if your bank rejects it, being able to read the file helps with troubleshooting.

Uploading to your bank portal

Log into your bank's online portal, navigate to their ACH file upload section, and upload the file. The bank validates the file format, verifies the batch total, and queues the payments for processing. Most banks provide a confirmation screen showing the number of transactions and total amount — verify these match your NetSuite batch before confirming.

Payments typically settle in 1-2 business days after upload. Same-day ACH is available at most banks for an additional per-transaction fee.

---

Employee direct deposit setup

EFT isn't just for vendor payments. Employee direct deposit for payroll uses the same underlying feature.

On the employee record, navigate to the Direct Deposit subtab. Employees can split their deposit across multiple bank accounts — for example, a fixed amount to a savings account with the remainder to checking. Enter bank routing numbers, account numbers, and the allocation for each account.

When payroll runs, NetSuite generates an EFT file containing all employee direct deposit instructions. The file uses PPD (Prearranged Payment and Deposit) entry class codes rather than the CCD codes used for vendor payments, but the upload process to your bank is identical.

If you're running NetSuite SuitePeople for payroll, direct deposit configuration is integrated into the payroll setup wizard. If you use a third-party payroll provider (ADP, Paychex), direct deposit is typically handled on their side rather than through NetSuite's EFT feature.

---

Common EFT issues and troubleshooting

File format rejections

The most common EFT problem is the bank rejecting your file. Causes include:

• Wrong company identification in the file header — this must match exactly what your bank has on file for your ACH origination agreement
• Incorrect standard entry class code — CCD for vendor payments, PPD for payroll. Mixing these up causes rejections
• File structure errors — missing batch trailers, incorrect hash totals, wrong record counts. These usually indicate a template configuration problem
• Character encoding issues — some banks reject files with special characters in vendor names or addenda records

Always test with a small batch first when setting up a new bank or changing templates.

Missing vendor bank details

If a vendor doesn't have bank details on their record, NetSuite excludes them from the EFT batch and processes them as a check (or skips them entirely, depending on your configuration). Run a saved search for vendors with payment method set to EFT but missing bank details — this catches the gap before your AP team wonders why certain bills weren't included in the batch.

Duplicate payment prevention

NetSuite flags potential duplicate vendor bills based on vendor + invoice number + amount, but duplicate EFT payments can still happen if someone processes the same batch twice or re-uploads a file to the bank portal. Build a process check: verify the batch status in NetSuite before uploading, and never re-upload a file without confirming with your bank that the previous upload was rejected (not just delayed).

Bank reconciliation with EFT

EFT payments should make reconciliation easier, but only if you're matching bank transactions against NetSuite payment records systematically. NetSuite's bank feed integration can auto-match EFT payments when the amounts and dates align. For bulk ACH files, the bank may show a single debit for the entire batch rather than individual transactions — configure your reconciliation process to handle both scenarios.

---

EFT security best practices

Electronic payments carry risk. A compromised EFT file or a fraudulently modified vendor bank account can redirect funds to the wrong place. Protect yourself with:

• Dual approval workflows — Require two authorized users to approve payment batches before the EFT file is generated. NetSuite's SuiteFlow can enforce this based on batch amount
• Vendor bank detail change alerts — Set up workflow alerts that notify your AP manager whenever vendor bank details are modified. This catches both errors and potential fraud (business email compromise attacks often involve changing vendor bank details)
• File integrity — Some banks support encrypted file uploads or require digital signatures on EFT files. Use these when available
• Audit trails — NetSuite logs who created each payment batch, who approved it, and when the file was generated. Review these logs regularly
• Positive pay integration — Send your bank a file listing all authorized payments so they can reject any payment that doesn't match. NetSuite supports positive pay file generation alongside EFT

---

Third-party EFT solutions

NetSuite's native EFT handles standard domestic ACH payments well. But if you need more — international payments, automated vendor onboarding, or tighter bank integrations — third-party solutions fill the gaps.

Tipalti automates the entire payables workflow including EFT. It handles vendor bank detail collection and validation, supports payments in 196 countries via local payment methods, and generates payment files or executes payments directly through its payment network. For companies paying hundreds of vendors across multiple countries, Tipalti replaces NetSuite's native EFT with a more robust system.

HSBC and bank-specific connectors provide direct integration between NetSuite and your bank, bypassing the manual file upload step. Instead of generating a file and logging into your bank portal, payments transmit directly through a secure API connection. These are available for major banks and are worth evaluating if your payment volume justifies the setup effort.

Bill.com offers payment execution as part of its AP automation platform, handling both ACH and check payments (Bill.com prints and mails the checks for you if a vendor doesn't accept electronic payment). The NetSuite integration syncs payment status back to vendor bill records automatically.

---

Frequently asked questions

Frequently Asked Questions

How do I set up EFT payments in NetSuite?expand_more

What is the difference between EFT and ACH in NetSuite?expand_more

Can NetSuite generate ACH files for vendor payments?expand_more

How do I troubleshoot EFT file rejections in NetSuite?expand_more

Does NetSuite support direct deposit for payroll?expand_more