CPA 005 compliance: what makes an EFT 1464 file acceptable

Payments Canada Standard 005, usually called CPA 005, is the rulebook every Canadian bank applies to batch EFT files. It exists so that a payment sent through one institution can be settled at any other Canadian institution without anyone interpreting it by hand. When your bank offers EFT, AFT or batch payments from a file, that file has to follow this standard. Banks apply it strictly, and a file that breaks a rule is rejected rather than corrected.

The EFT 1464 format is position-based: every value has to sit in exactly the right place, and the bank's system reads the file by position rather than by label. One wrong character in the wrong place fails the whole file, which is why files built in a spreadsheet or by editing an old template are so fragile. The rejection notice rarely says what went wrong, so whoever built the file starts over by guesswork. Too often that happens after the payment date has passed and a vendor is already waiting.

Three things have to be right in every file. The first is your identity as originator: the originator ID your bank assigned to you and your business name as registered with the bank, exactly as the bank expects them. The second is the amounts and totals: every payment amount has to be written correctly, and the totals and counts in the file have to agree with the payments it contains, to the cent. The third is dates and account formats: the payment date has to fall inside the window your bank allows, and every vendor's institution, transit and account numbers have to be valid and complete. Each of these is easy to get wrong by hand, and each is enough on its own to fail the file.

Zefty checks the file before it exists, not after the bank rejects it. Bills whose vendor is missing an institution, transit or account number are blocked before they can enter a file. Amounts come straight from the bills in Zoho Books, so nothing is retyped, and totals are calculated from the payments actually in the file, so they always agree. Your originator details are applied to every file the same way, and the payment date you choose is written the way your bank expects. If something is missing, you see it on screen while there is still time to fix it.

Zefty builds each file from the bills in Zoho Books and from the bank details you entered once during setup. Numbering and totals are handled for you, so your bank never sees a duplicate file or a total that does not match. Bills with incomplete vendor banking details are blocked before a file exists. Test mode lets you produce a file marked as a test to validate your setup with your bank before any real payment goes out, with nothing recorded in Zoho Books. The result is the same for all nine supported banks: a file named and formatted the way your bank's portal expects, ready to upload as is.

Compliance does not end when the bank accepts the file. Zefty keeps every file you generate, with its number, total, creation date and payment date, and you can download it again at any time. Each file comes with a readable report that lists every payment in plain language, so an auditor, a bank representative or a colleague can verify what was sent without decoding the raw file. In Zoho Books, each bill paid through a live file carries its vendor payment, and your payment history in Zefty links to it. From any payment in the file you can reach the bill, the accounting entry and the person who generated it.