Payables & Cash Management

Get Involved. Join the Conversation.

Topic

    Logan Wacker
    Adding Addenda Detail to ISO 20022 CGI Payment Format
    Topic posted March 12, 2018 by Logan WackerSilver Trophy: 7,500+ Points, last edited January 30, 2019, tagged Cash Management, Payables 
    307 Views, 12 Comments
    Title:
    Adding Addenda Detail to ISO 20022 CGI Payment Format
    Summary:
    SaaS doesn't provide the ability to map addenda details to payment file - extremely limiting treasury payment processing issue
    Content:

    Most Global Banking Partners expect to receive free form additional payment information -- known as addenda -- in the <Ustrd> xml tag under the <RmtInf> tag within an ISO 20022 xml message. The delivered data model doesn't provide the ability to add this tag and allow for the mapping of the Memo field from the ad hoc payments UI to the payment file. Passing additional payment information to beneficiaries to support the identification of payments is a core treasury process regardless of client industry. This has caused one client to not use the the ad hoc payment's functionality and will continue to be an issue in the future. 

     

    Has anyone else ran into this previously? 

    Comment

     

    • Becky Alvarez

      You know that our system is just Cash Management and for full Treasury Capabilities we do integrate with Reval.  We do also allow you to customize the payment formats but don't know if that is going to help you if the memo field is ad hoc.

    • Logan Wacker

      Hi Becky:

      I understand the payment formats are customizable, and we do routinely enhance them to align ISO payment file layouts to bank specifications. The issue is the xml tag that most banks identify as the addenda field doesn't exist in the data model, and MOS agreed that I cannot add the desired field to the model, to in turn build the desired payment file. It was sited as a limitation of SaaS.

      Reval does offer additional treasury functionality, but adding addenda to payment file is core treasury functionality. This gap makes it unusable to where the client wishes to return to bank portals. Additionally this memo field travels with the payment through CM, to IBY, and can be accessed from the GL, but I cannot print any delivered payment report and see this memo field as a work around.

      Thanks.

      Logan

    • Madhu Bolli

      Becky/Logan,

                        We are also on the same boat of existed process add addenda records in the payment file to Bank. Do we have any solution or workaround to solve this problem. Our cloud payment implementation is blocked due to this issue.

        Do we have any existed enhancement or bug for this issue.  

    • Becky Alvarez

      I just passed this by development to express your concerns.  They mentioned that we have the different fields i.e. the remittance message, invoice flex fields that can be used to capture any additional information from the invoice.

      They also would be happy to review and make suggestions if any of you would like to provide exact details of what you/your customer want to send in the ISO file and in which tag you need to send it in.

      • Logan Wacker

        Hi Becky:

        If you're using this format for Cash Management payments then you need the ability to pass free form text in the unstructured or structured XML tags that serve as additional info fields. Ideally, the memo field on the eft or bank transfer page could be mapped to this field. As we know this memo field isn't contained within the raw XML passed from Oracle and mapped through the xsl to generate the iso 20022 xml payment file. The addition of addenda is standard functionality in other erp's like PeopleSoft

        • Becky Alvarez

          Here is the feedback I received from the developers.  Let me know if this helps.

          The memo details of the bank transfer are populated in the invoice description and the template can be customized to pass this in the unstructured remittance. Here are the specific changes the customer can include in their template to pass the memo details. You can let us know if any more details are needed.

           

          <RmtInf>

          <xsl:for-each select="DocumentPayable">

          <Ustrd>

          <xsl:value-of select="DocumentDescription"/>

          </Ustrd>

          </xsl:for-each>

          </RmtInf>

      • Madhu Bolli

        Thank You Becky.

        Pls. find the details below. It would be appreciate if you can give any workaround or point to other source to implement this requirement.


        1. Required Payment File Structure for some suppliers are:
        "The EDI 820 component is embedded into the ACH CTX structure.  You can think of this structure as a “file within a file”. ACH CTX and EDI 820 each have their own file structure and rules.  So, the EDI 820 structure includes in EFT/ACH Payment file"

        2. Addenda Record Structure:
        Each record within the ACH addenda is 94 bytes.  The breakdown of those 94 bytes is as follows:

        Position 1 = Addenda Record Indicator. 
        Position  2 & 3 = CTX Indicator
        Positions 4 to 83 = EDI File information
        Positions 84 to 87 = Addenda Sequence Number
        Positions 88 to 94 = Trace Number


        3. Each "Addenda Record" must contain all below headers with values delimiting each header with '\':
        ISA/GS/ST/BPR/TRN/DTM/ENT/DED/SE/GE/IEA


        4. As the addenda record length will be more than 79 ('EDI File Information') characters, we have to chunk it and add the chunk# ('Addenda Sequence Number') at the end of each record(Position 84 to 87).

        • Becky Alvarez

          Madhu,

          According to the developers, you just need to ensure that the addenda structure required by your bank is entered correctly in the memo details. As long as the memo details are populated with the right addenda text, the same can then be extracted and passed in the payment file.

          • Madhu Bolli

            Thank You Becky.

            1. Could you point us where we see the 'Memo' filed. I didn't find it in 'Outbound Payment Instructions' XML file.

            2. The addenda records need the payment and invoice information (which generates when Build Payment executed).  I think in 'Memo' field we can provide only the 'HardCoded'/'Constant' strings. Adding to this, the addenda record should be in a specific format and needs the total no. of addednda records in its trailer record and a bit complex.

            3. Some of the custom data is in custom lookups(in EBS) and using extension hook, we included it in 'XML' file. In the Cloud Outbound Instruction XML file, do we have any placeholder to read from lookups/'similar like lookups'

        • Glen Ryen

          Hi Madhu,

          Were you ever able to solve for this CTX ACH requirement?  I don't think a BIPublisher eText template could handle the 'file within a file' structure of an ASC X12 820 transaction set embedded in multiple NACHA addenda ('7') records.  I saw an enhancement request for it within EBS, though that ER doesn't appear to ever have been implemented (due to BIP limitations).  A custom XSLT layout template could produce the desired output, but that would have to be pretty complex.  Did you happen to find a better approach?  Or did you move your client over to CGI ISO 2002 XML instead of NACHA?

          Thanks in advance,

          Glen

    • Becky Alvarez

      It shown above in the post I made on April 30th in response to Logan's comment.

    • Madhu Bolli

      Thank You Becky.

      1. Found from your reply -  snippet of your statement is "The memo details of the bank transfer are populated in the invoice description" .. Could you point me where can I find this Memo field to enter the details (at Invoice screens or Payment screens). I would like to check if the Memo is able to get dynamic data for addenda records.