EFT Return Codes: What They Mean and How to Handle Them

Learn > Payments > EFT

Electronic Funds Transfers (EFTs) in Canada are processed through the Automated Clearing Settlement System (ACSS) and governed by Payments Canada rules.

When an EFT cannot be completed, the receiving financial institution assigns a standardized return reason code. These codes indicate why a transaction was rejected or returned.

Understanding EFT return codes helps businesses:

  • Identify the cause of failed payments
  • Take corrective action
  • Manage cash flow more effectively
  • Reduce operational risk
  • Stay compliant with Payments Canada requirements

Canadian EFT return codes are defined under Payments Canada Standard 007 and related rules, including Rule H1 (Pre-Authorized Debits).

1. Edit Rejects (File Validation Errors)

Edit rejects occur before funds are processed. These are technical validation failures and must be corrected before resubmission.

CodeReasonDescription
900Edit RejectFile failed validation due to formatting errors, missing mandatory fields, or invalid institution, transit, or account number structure.

Edit rejects are not customer returns. They indicate a file-level issue that prevented processing.

2. Administrative EFT Return Codes

Administrative returns occur after the transaction has been presented to the receiving financial institution.

CodeReasonDescription
R901Non-Sufficient Funds (NSF)The account does not have enough available funds to process the transaction.
R902Account Not Found / Cannot TraceThe account number does not exist or cannot be located.
R903Payment StoppedThe payor placed a stop payment on the transaction.
R904Post-Dated or Stale-DatedThe transaction date is invalid or outside the allowable processing window.
R905Account ClosedThe account has been closed and is no longer active.
R907No Debit AllowedThe account does not permit debit transactions.
R908Funds Not ClearedFunds are on hold and not yet available.
R909Currency / Account MismatchThe transaction currency does not match the account denomination.
R910DeceasedThe account holder is deceased.
R911Account FrozenThe account is legally restricted or frozen.
R912Invalid Account NumberThe account number structure is invalid.
R922Customer-Initiated Return (Credit Only)The customer requested return of a credit item.
R990Institution in DefaultThe financial institution is in default.

3. PAD (Pre-Authorized Debit) Return Codes

Pre-Authorized Debit (PAD) returns relate to authorization disputes and are governed by Payments Canada Rule H1.

PAD return rights differ depending on whether the PAD is:

  • Personal (consumer)
  • Business
  • Funds Transfer
CodeReasonDescription
R915No PAD AgreementNo valid PAD authorization agreement existed.
R916Not in Accordance with Agreement (Personal)The debit did not comply with the personal PAD agreement (e.g., incorrect amount or timing).
R917Authorization Revoked (Personal)The consumer revoked authorization before processing.
R918Required Pre-Notification Not Provided (Personal)Required notice or confirmation was not provided.
R919Not in Accordance with Agreement (Business)The debit did not comply with the business PAD agreement.
R920Authorization Revoked (Business)The business revoked authorization.
R921Required Pre-Notification Not Provided (Business)Required notice or confirmation was not provided.

EFT Return Time Limits in Canada

Return eligibility depends on the type of return and PAD classification.

  • Administrative returns (e.g., NSF, Account Closed): within 2 business days
  • Business PAD disputes: within 10 business days
  • Consumer PAD disputes: within 90 calendar days

After these timeframes expire, recovery may require indemnification or alternative resolution processes.

Important Clarifications

Name Matching

Canadian EFT processing is based on:

  • Institution number
  • Transit number
  • Account number

Payee name mismatches do not typically trigger EFT returns.

Recalls

There is no universal "recall" return code in Canada. Returns must follow standardized Payments Canada return reason codes and defined timing rules.

Internal vs. Official Codes

Some financial institutions or processors may use internal status codes. For compliance and reconciliation purposes, businesses should reference official Payments Canada return reason codes.

Regulatory Framework

Canadian EFT return codes are defined by:

  • Payments Canada Standard 007
  • Payments Canada Rule H1 (Pre-Authorized Debits)
  • ACSS By-Laws and Rules

Businesses processing EFT transactions must align with these national clearing standards.

Learn More about EFT

EFT (Electronic Funds Transfer)

-

EFT stands for Electronic Funds Transfer and is the backbone of the Canadian payment industry. EFT offers a safe and cost-effective way to electronically credit or debit accounts at any Canadian financial institution in Canadian or U.S. dollars.

A Complete Guide to EFT Reversals for Businesses

+

EFT reversals are when a payment is reversed due to issues such as incorrect payment details or customer disputes.

The Ultimate Guide to Bulk EFT Payments

+

Bulk EFT payments refer to processing Canadian bank account transactions in bulk in order to optimize payment operations at scale.

EFT CPA 005 File Guide: Everything You Need to Know

+

The EFT CPA 005 file format is a Canadian formatting standard for generating electronic funds transfer files.

EFT Cut-Off Times: What You Need to Know

+

EFT cut-off times refer to the deadlines set by financial institutions for processing EFT transactions.

EFT API Integration: Simplifying Payment Processes

+

An EFT API integration connects a business’s software infrastructure to an EFT payment gateway, enabling programmatic access to EFT payment processing.

EFT vs Wire Transfer: Key Differences Explained

+

EFT payments and wire transfers are two different types of electronic transactions, each with its own pros and cons.

Why PAD/ACH Payments Have a 3-Day Hold

+

VoPay applies a three-day hold on PAD and ACH payments to allow banks time to confirm funds have cleared. This safeguard helps prevent reversals, reduce payment risks, and ensure compliance with Payments Canada and NACHA regulations.

Speak to a Fintech Specialist Today!

1. Speak To Our Team

Speak to a Fintech Advisor to outline your needs and impact plan.

2. Access Sandbox

Start testing in the VoPay sandbox to explore our advanced API functions.

3. Sign & onboard

Our compliance and onboarding team will guide you through the process.

4. Go live!

Choose a production date and launch your integration with confidence!

Talk with our sales team

We are happy to answer your questions. Fill out the form and we will have one of our team members contact you.