Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Nostro break feed files

Updated on March 4, 2022

One of the sources of investigations is the Nostro Account Reconciliation system. During the reconciliation cycle, SWIFT statements are matched with ledger statements and debits are matched with credits. Inevitably, however, a small percentage of the debits and credits do not have a contra entry to match against. These exceptions are typically called breaks and at the end of the reconciliation cycle, these breaks are exported to Smart Investigate for Payments in the form of a file for loading and investigating. Smart Investigate for Payments comes with three predefined file listeners for receiving nostro feeds.

Follow the steps below to set up the nostro interface. See the Integrationarticles on the Community for additional interface information.

  1. Create the directory structure. Smart Investigate for Payments requires a separate directory for each file type. The directory structure should be set up as follows:
    • NostroInbound
    • NewBreak
    • ResolveBreak
    • ValDiff
    Note: The path to NostroInbound you use may be different depending upon the Web server being used (WebSphere or WebLogic). You can use any directory in the Web server as long as you reference the path in the Source Location field in step 2.
  2. Configure aConnect FileListener instance for:
    • NostroNewBreakFileListener
    • NostroResolveBreakListener
    • NostroValDiffListener

    Enter the following information for your system. You can get the location and node name from your server.

    • Node name — node on which Process Commander runs.
    • Source Location — directory where the appropriate input file (New Breaks, Resolved Breaks, and Value Diffs) will be located.
    • Password: — The password as specified for the NostroFileService operator.

    This image is a sample of NostroNewBreakFileListener.

  3. Click Test Connectivity to verify that the system can access the directory you specified. Once you have verified connectivity, these file listeners will start when you restart your application.
Pega Smart Investigate for Payments Implementation Guide

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us