INTERFACING

Irrespective of which part of the Coprocess Intercompany Netting solution you choose, interfacing unlocks value and integrates the Coprocess platform into your enterprise. Coprocess will help specify (and possibly build) interfaces for getting data into Coprocess and the system has multiple standard formats to extract data out. If a standard format does not exist we will follow your specification to build one. Both import and export can be automated via the API. 

Connectivity

We do this in 2 ways:

1. API

The Coprocess.Netting API allows external applications to automatically trigger actions within the netting in a secure way without any manual intervention. It is part of our continued effort to streamline straight-through-processing. For example, it would now be possible for a developer to implement an automated bulk import of invoices from a specific secure folder location within your corporate network, or even directly from an ERP system such as SAP. The API supports bulk importing and exporting of invoices and will support data querying and report generation.

How it works:

NetAPI provides a secure RESTful set of web services over https for interacting with Coprocess.Netting. It is installed alongside NetWeb and relies on the same proven enterprise-standard secure authentication and authorisation mechanisms. All resources are named using a base URI and Swagger documentation is provided. The default data format is JSON with UTF-8 but xml can be requested also. Any errors are returned as part of the response. The API currently supports various netting functions including import and export of bulk data via the existing import/export formats defined in Coprocess.Netting. Additional services will be added in future releases including support for general data queries.

• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10

Interested?

Contact your Account Manager for pricing, test database setup and to book time with our technical team.

2. File based upload and download

• We have over 40 interfaces already built and tested and working in production including all the major players be they banks, TMS or ERP.
• If we do not currently support an interface we wil build it for you using the interface builder in our application.

ERPs

For import and export of invoice level data it is best to use interfaces. This is true for 3 reasons:

• the volume of invoices
• remove the problems of re-keying
• easier synchronization between ERP and Netting

The key interface for Coprocess is therefore with the ERP system or systems and the extract of AP and / or AR data directly out of the ERP and into the netting.

Coprocess can achieve this easily and simply in one of three ways:

• The client extracts the data out of the ERP using the standard Coprocess interface (simple CSV file, one invoice per line)
• The client is using an existing interface that we already support (we have interfaces today with most of the common ERP systems including SAP, ORACLE, Baan, JD Edwards, Microsoft Dynamics, Peoplesoft, Navision, BPCS, Movex, Scala, Jeeves, Pulse etc)
• The client gives Coprocess the specification of existing extracts that they support and Coprocess build this interface.
  NB. We have an interface builder within the application so we are able to build and add interfaces without upgrading or changing the software.

NB. The most common ERP system used by our clients is SAP. We have over 40 corporates using SAP in different ways and that has given us great experience in integrating SAP with Coprocess.Netting for seamless and smooth exporting and importing of files.

In addition Coprocess supports interfaces to book back into the ERP system the invoices that have been settled in the netting. This booking file can be delivered by email with the netting statements on final day if required.

Treasury Management System (TMS)

Coprocess supports interfaces with most commonly found TMS's both for import and export of data:

• Importing treasury transactions such as forward contracts, spot deals, loans and deposits
• Exporting the net payments from the netting system for settlement in the TMS (either the physical payments are made from the TMS or the client is settling on the in-house bank (which is a part of the TMS) or a mixture of the 2. Coprocess can support all 3 methods.
• Import of rates from TMS
• Export of deals

Coprocess has existing interfaces with the following Treasury Systems:

Cashflow, Globe$, Fides, KTP, Integrity, IT2, PeopleSoft, Quantum, SAP (IHC), Trema, Twin, CRM

Banks

In order to simplify and avoid double work and the risk of errors when making payments it is very useful to be able to interface with a Bank payment system. The Coprocess system can work with many bank systems for transactions such as payments, direct debits, Advice to Receive (ATR's) and rate feeds.

Coprocess supports the following standard payment interfaces:

BACS, ETEBAC5, ISABEL, Multicash, Paymul, SWIFT MT101 and 210, XML (ISO 20022)

In addition Coprocess supports the following proprietary payment interfaces:

Bank of America Cashpro, CitiDirect, Deutsche Bank DB-Direct, JPMorgan, Nordea, PostFinance (Switzerland), RBS Access Direct and Access Online, SEB C&I Online, Telepay (Norway), UBS, PNC Pinacle, Svenska Handlesbanken, to name just a few.

In addition we can deliver the payments securely to the bank over SFTP.

FX dealing platforms

Many clients take rate feeds from providers such as 360T, FXAll, Bloomberg and others. Some also transact Final Day FX transactions on the trading platform. Coprocess allows the import of rates in simple .csv formats and import/export of amounts for FX dealing.

Hedging and other platforms

Some clients interface Coprocess to their chosen hedging provider, to keep track of and execute, hedges in Coprocess. Systems such as Hedge Trackers LLC for example.