Anyone able to use EFT with RBC succesfuly after its integration in SAGE50 ? Duplicate transaction rejected

For the past 2 weeks we've been having trouble with EFT payroll transactions, after it was integrated into SAGE50 (following last update).

We are getting rejected transactions every time an EFT file is uploaded to our bank, after much investigation we found through careful examinatio of the EFT files what was going on.

For employees that have more than one transaction (for example: someone leaving and getting leave pay), EFT generates transactions with duplicate payment numbers when using RBC's Standard (STD152) Debit File Format  ( https://www.rbcroyalbank.com/ach/file-451773.pdf ), field #7, columns 41-42. RBC payroll support helped us find this problem. SAGE50 tech support then suggested using the CPA Standard 005.

After testing the result EFT file, it turned out to be invalid. Guided by RBC, it was determined there were extra blank lines.Even removing them the file was still invalid and rehected by RBC. The long waiting time and the multiple resources involved on our side to wait on the phone, wait for call backs, investigate, test and keep track of all this is absurd.

Is anyone else having these problems? Using SAGE50 latest version, its payroll EFT feature and RBC should not be that uncommon in Canada, has anyone had resolution for this? What other options or solutions are possible other than waiting forever on the phone? A timely software fix seems unlikely at this point, and it will be the third week we have to prepare several payments manually and deal with employees communications, clarifications, cancelling/updating transactions manually etc.

Parents
  • This morning SAGE support wrote to apologize for not calling us in more than 12 hours sinc our last call, suggesting our routing numbers for employees were bad and to verify them (really? for all employees?).

    After some brainstorming one of our accountants suggested:

    1) Using the original file format for RBC (STD152)
    2) Generating 2 EFT files: one with the first transaction for each employee (and only the first one), and another with remaining transactions.

    We tested this with RBC and it worked. This also means paying an extra $10 (each EFT batch processed costs $10), but at least it minimizes any manual editing of files and payroll will happen on time unlike last two weeks.

    SAGE support also offered 2 month extension on our support contract - quite insulting given we did all the research and came up with this workaround.
  • in reply to F.R.

    We want to pay our employees by direc deposit, we create the file in Sage 50 and export to the bank, but we don't know with format use in the RBC bank, they have five formats, we used RBC standard, but was aborted because we have 5 validation error in 5 records and 5 lines, additonally the bank said that import record length is incorrect, we are trying with two employees and the bank said that there are 9 records in the sage file. Anyone can help me. Thanks.

Reply
  • in reply to F.R.

    We want to pay our employees by direc deposit, we create the file in Sage 50 and export to the bank, but we don't know with format use in the RBC bank, they have five formats, we used RBC standard, but was aborted because we have 5 validation error in 5 records and 5 lines, additonally the bank said that import record length is incorrect, we are trying with two employees and the bank said that there are 9 records in the sage file. Anyone can help me. Thanks.

Children
No Data