Administration, Core Financials, and Project Accounting

[snolte]

Good morning,

I looked through the prior postings on EFT's and didn't see anything that covered this item - if there is something, I apologize for the oversight.  We are currently changing over our main payment method to EFT's.  I've been able to setup MAS with all the required information and generating the file was no trouble, but I seem to have one error from the bank when the file is submitted.  The error coming back is "Invalid Item Trace Number". 

I've looked in the Help and found the tables which relate to the format of the files that are being created.  Our bank's tables indicate that in Field #15 should be the Originator Reference number, 19 digits.  On the MAS 500 Help (Logical Record Type C) Field #15 is Alphanumberic , 19 digits and Filler... however MAS is only generating 12 digits and it is definitely assigning them in a sequential order.  This should be the unique transaction number and while it appears to be unique it isn't long enough.

Has anyone else encountered this before?

Thanks for any insight.

Sarah Nolte

[MCarlise]

Our specs indicate that field 15 for detail record C is defined as ‘ORIGINATORS CROSS REFERENCE’ .  This field is mapped to tapPendVendPmt.TranNo field (i.e. CheckNo) and its defined as alphanumeric with the total width size of 19.   The first 12 characters are filled with the checkno (right justified with preceeding zeros) and the last 7 are blank. The specs also indicate that the last 7 must be blank because it used by the Credit Union Central of British Columbia.

If you would like to send me your bank name and file layout I can take a closer look.

thank you,

Mari.carlise@sage.com

[koheare]

We also ran into an issue with the Canadian EFT that field 9 was supposed to be 22 zeroes but the output file contained 22 spaces instead.

the code in the core procedure was:

  RIGHT('00000000' + RIGHT(  LTRIM(RTRIM(COALESCE(tapVendAddr.BankRoutingTrnstNo,'')  ))  , 8), 8),
  LEFT(LTRIM(RTRIM(tapVendAddr.BankAcctNo)),12),
  ' ',
  0,
  tapACHOptions.CANOriginShortName,
  LEFT(tapVendor.VendName, 30),
  tapACHOptions.CANOriginLongName,
  @_lCANOriginID,
  RIGHT('000000000000'+ RIGHT(  LTRIM(RTRIM(COALESCE(tapPendVendPmt.TranNo,'')  ))  , 10),12),
  ' ',

  0,
  RIGHT('00000000' + @_lCANRtrnBankRoutingTrnstNo , 8),
  @_lCANRtrnBankAcctNo, 

once we changed the code to:

  RIGHT('00000000' + RIGHT(  LTRIM(RTRIM(COALESCE(tapVendAddr.BankRoutingTrnstNo,'')  ))  , 8), 8),
  LEFT(LTRIM(RTRIM(tapVendAddr.BankAcctNo)),12),
  '0000000000000000000000', -- ' ', _ESS this should be 22 zeros
  0,
  tapACHOptions.CANOriginShortName,
  LEFT(tapVendor.VendName, 30),
  tapACHOptions.CANOriginLongName,
  ' ', -- @_lCANOriginID, _ESS this should be filler for BMO

  RIGHT('000000000000'+ RIGHT(  LTRIM(RTRIM(COALESCE(tapPendVendPmt.TranNo,'')  ))  , 10),12),
--  ' ', _ESS commented out

  0,
  RIGHT('00000000' + @_lCANRtrnBankRoutingTrnstNo , 8),
  @_lCANRtrnBankAcctNo, 

the file was able to be successfully uploaded to the bank.

Hope this helps.

[snolte]

Thanks for the information.  We were able to work directly with Sage to get a fix for the issues we were experiencing, thanks to Mari and the team!

[MCarlise]

Thank you for reporting this. It is corrected in December 2011 Product Update.

Thanks again to all of you!!