![]() The table below outlines what submissions routing and triggers could be used for this use case in order to automate data feeds and snapshot creation: The run will be automatically initiated when the two-sided process has both the internal file and the Data Prep snapshot. This will automate the creation of snapshots, which will then be pushed into the two-sided process. Typically either a Timing (that uses all data received up to a specified time) or a Completion trigger (that creates a snapshot of your data once all your counterparty files have been received) would be used here. The Data Prep process will also require a trigger or triggers to automate this part of the flow. Each counterparty file will require its own data source or submission routing to the relevant input within the Data Prep process and the internal file will need a separate data source or submission routing pointing to the internal side of the generic two-sided reconciliation. The rest of the configuration steps will be as is standard for a two-sided process.Īutomating such a reconciliation using SFTP will require that the counterparty files are pointed at the Data Prep process, while the internal files are fed into the two-sided process directly. Once that has been set-up, a two sided process can then be created, with your internal file as one Data Input and the Data Prep process acting as the other. ![]() See the Data Prep Quick Start Guide for how to configure this. The different counterparty files will be fed to a Data Prep process, that will apply mappings and any normalisation required to produce a single combined output data set. This scenario will require a single Data Prep process to consolidate and normalise your multi-counterparty data and a two-sided generic process, where this is reconciled against your internal data. ![]() Typically the counterparty data is captured in different file formats with different layouts. Multiple external datasets vs multiple internal source systemsĪ common use case for Data Prep is where a single internal file capturing trades/positions needs to be reconciled against files coming in from multiple counterparties.Multi-counterparty trade or position reconciliations.Create Counterparty #Ĭreates an ACH counterparty for a specific customer.The most common use cases that we have seen with our Data Prep Early Adopter customers are the following: This adds another layer of security, because the API Token alone cannot make payments to counterparties which are not created and approved by the customer. The counterparty resource also allows you to make (automated) payments without creating a Customer Token or selecting sensitive scopes for the API Token,īy using ACH payment to linked Counterparty and API Token with only payments-write-counterparty selected. When using the recommended scopes for API Token you would first need to Create a Customer Token (along with two-factor authentication) in order to create the counterparty resource. Which allows making payments to counterparty resource only. When creating an API Token Unit recommends not to select the payments-write and counterparties-write, however we do recommend selecting payments-write-counterparty scope, Instead of the customer typing the routing number and account number repeatedly. ![]() When a customer is expected to send funds to same counterparty on multiple occasions you may create a counterparty resource and re-use it by creating an ACH payment to linked Counterparty, The counterparty resource represents the other party that participates in a financial transaction. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |