ACH/EFT Payments Explained: The Canadian Standard

Electronic Funds Transfer (EFT) is the backbone of Canadian financial infrastructure. Payroll runs on it. Government benefit payments run on it. Mortgage payments and utility bills run on it. For businesses, EFT is one of the most cost-effective ways to move money — often costing cents per transaction versus dollars in credit card fees. Yet many businesses do not fully understand how EFT works, how long it takes, or how to implement it effectively.

ACH vs EFT: Understanding the Terminology

The terms ACH and EFT are often used interchangeably, but they refer to slightly different things:

• ACH (Automated Clearing House): This is the specific US payment network operated by NACHA (National Automated Clearing House Association). It processes batch electronic payments between US banks. In the US, ACH is the system; in Canada, we have an equivalent but distinct system.
• EFT (Electronic Funds Transfer): This is the generic Canadian term for bank-to-bank electronic payments processed through the Automated Clearing Settlement System (ACSS), which is governed by Payments Canada. What Canadians call "EFT" is functionally equivalent to what Americans call "ACH."

In Canadian business contexts, EFT is the correct term. Many payment processors and software platforms use "ACH" interchangeably to accommodate US-centric terminology, but the underlying Canadian infrastructure is ACSS. When integrating with a payment processor like TIB Finance for Canadian EFT, you will typically encounter both terms.

How EFT Works in Canada

Every EFT transaction in Canada moves through the following stages:

1. File creation: The originating business (or their processor) creates a batch file containing transaction details — account numbers, routing numbers (transit + institution numbers), amounts, and transaction codes.
2. Submission to processor: The file is submitted to the payment processor (e.g., TIB Finance), which validates the file format and transaction data.
3. Submission to ACSS: The processor submits the validated file to the ACSS through their clearing bank, typically by a daily cut-off time (often 6:00 PM ET).
4. Overnight clearing: ACSS processes the batch overnight, calculating net positions between all participating financial institutions.
5. Settlement: The Bank of Canada settles the net positions between participating institutions in the early morning.
6. Posting: Individual financial institutions post the transactions to customer accounts, typically by 9:00 AM on the settlement date.

Payments Canada's Role

Payments Canada is the national organization responsible for Canada's payment clearing and settlement infrastructure. They operate:

• ACSS (Automated Clearing Settlement System): The primary batch payment system for EFT, cheques, and pre-authorized debits. Processes approximately 32 million transactions daily.
• Lynx: Canada's high-value real-time gross settlement system for large-value transactions between financial institutions.
• RTR (Real-Time Rail): Canada's real-time payment system (currently in development/rollout), which will enable near-instant EFT payments 24/7.

The rules governing EFT transactions — including pre-authorized debits, return timeframes, and dispute processes — are set by Payments Canada in their Rule Set. Businesses that collect payments via EFT must comply with these rules, particularly Rule H1 for pre-authorized debits. See our dedicated guide on pre-authorized debits (PAD) compliance for details.

Processing Timeline: T+2 Explained

Standard EFT transactions in Canada settle on a T+2 basis — meaning if you submit a file on Monday (day T), the funds appear in the recipient's account on Wednesday (T+2 business days). Here is a typical timeline:

Note that bank holidays and weekends do not count as business days. A file submitted on Friday before cut-off will typically settle by Tuesday (skipping Saturday and Sunday). Statutory holidays further delay this timeline.

Direct Deposit vs Pre-Authorized Debit

EFT transactions come in two fundamental types, and understanding the distinction matters for your implementation:

EFT Credit (Direct Deposit)

An EFT credit pushes money from your account to a recipient's account. You are the originator and sender of funds. Examples:

• Payroll disbursements to employee bank accounts
• Vendor payment transfers
• Customer refunds
• Insurance claim payouts
• Government benefit payments

EFT Debit (Pre-Authorized Debit / PAD)

An EFT debit pulls money from a payer's account into your account. The payer must authorize this in advance with a signed PAD agreement. Examples:

• Monthly subscription billing
• Recurring invoice collection
• Mortgage and loan payments
• Utility bill collection
• Membership dues

Pre-authorized debits carry specific compliance requirements under Payments Canada Rule H1, including written consent requirements, advance notice periods, and cancellation rights. These are covered in detail in our PAD compliance guide.

Types of EFT Transactions

The ACSS processes several categories of EFT transactions, each coded differently:

• Personal PAD (PPD): Pre-authorized debit from a personal bank account. Common for subscription services, rent, and personal loan repayments.
• Business PAD (BPD): Pre-authorized debit from a business bank account. Used for B2B recurring invoices and supplier payments.
• Direct Deposit: Credit to an individual's account. Used for payroll and government payments.
• Funds Transfer: Credits between business accounts.

Cost Comparison: EFT vs Credit Cards

The cost advantage of EFT over credit cards becomes dramatic for large or recurring transactions:

For a business collecting 200 recurring monthly payments of $500 each ($100,000/month):

• Credit card cost: $100,000 × 1.5% = $1,500/month
• EFT cost: 200 × $0.50 = $100/month
• Monthly savings: $1,400 | Annual savings: $16,800

This comparison is why subscription businesses, SaaS companies, and any business with regular recurring billing from the same customers should strongly consider EFT over credit cards. The tradeoff is the 2-day settlement delay and the requirement for advance customer consent.

NSF and Return Codes

EFT debits can be returned (rejected) by the receiving bank. Common return codes include:

• 900 — NSF (Non-Sufficient Funds): The payer's account did not have sufficient funds. The most common return.
• 901 — Account Not Found: The account number provided does not match any account at the receiving institution.
• 902 — Account Closed: The account has been closed.
• 905 — Payment Stopped: The payer instructed their bank to stop the payment.
• 907 — Authorization Revoked: The payer has revoked their PAD authorization.

Your processor will provide return files, typically within 3–5 business days of the original debit date. NSF returns result in the debit being reversed from your account, so it is important to have a return handling process in your billing workflow. Most processors charge a return fee ($5–$25) per returned item.

Implementing EFT for Your Business

To start accepting EFT payments through TIB Finance:

1. Open a merchant account: Apply through TIB Finance's onboarding portal. EFT processing is available alongside credit card and INTERAC payment acceptance.
2. Obtain PAD agreements: For pre-authorized debits, you must collect written consent from each payer. TIB Finance provides compliant PAD agreement templates and an electronic consent collection service.
3. Integrate the API or upload files: Choose between API-based integration (recommended for automated billing systems) or manual file upload through the merchant portal.
4. Test in sandbox: Use our test environment to simulate EFT credits and debits, including return scenarios, before going live.
5. Set up return handling: Configure your system to handle NSF and other return codes automatically, including customer notification and retry logic.

For businesses considering whether EFT or INTERAC e-Transfer is the better fit, see our comparison guide on ACH vs INTERAC payment methods.