Skip to main content

Reconciliation Engine v1.3.0

Release Date September 05, 2024

This release resolves an issue with uploading big camt files via API, performance improvements and provides an important infrastructure upgrade.

Highlights in this release:

Deprecation Notice

Currently, given a corresponding configuration, the reconciliation engine supports uploading a camt file to a blueprint. This method is now deprecated and will be removed in a future release. Improved functionality is provided by uploading to a source definition as outlined below.

About this update

This update has been rolled out automatically to all customers with the corresponding licensing option.

Remove 10 MB upload limit for camt files​

Within the reconciliation engine, a blueprint is a specification of what to expect in a certain file and how that file must be processed. For example, you need specific information to be extracted from

  • a camt.053 file to match settlement payouts, and
  • a camt.054 file to generate payment records for direct debit payments received on your bank account.

For this purpose we configure dedicated blueprints for each of those use cases. A possible scenario is to provide a camt file and execute such a blueprint. A camt file may be provided via a defined source:

  • PostFinance MFTPF
  • You SFTP server
  • API Upload

A source is mapped to a blueprint and files provided for that source will automatically be processed according to the blueprint definition.

Due to technical constraints, uploading a file larger than 10 MBs by specifying a blueprint directly is not possible. For this reason the operation has been split into two steps

  1. Request file upload credentials for a defined source configuration. The credentials received in the response will be valid for 5 minutes.
  2. Upload your file to a dedicated S3 storage directory using those credentials

Example:

GET https://api.raisenow.io/reconciliation/sources/{{source_uuid}}/file-upload-credentials Response body

{
  "inputs": {
    "X-Amz-Security-Token": "ItOJb....",
    "key": "8d98f....",
    "X-Amz-Credential": "ASIA...",
    "X-Amz-Algorithm": "AWS4-HMAC-SHA256",
    "X-Amz-Date": "20240903T114424Z",
    "Policy": "eyJleH...",
    "X-Amz-Signature": "b32...."

  },
  "attributes": {
    "action": "https://rnw-prod-reconciliation-two.s3.eu-central-1.amazonaws.com",
    "method": "POST",
    "enctype": "multipart/form-data"
  },
  "expires_at": 1725364164
}

You now need to use the response values to POST the file.

POST https://rnw-prod-reconciliation-two.s3.eu-central-1.amazonaws.com/ form-data:

key: "{{returned-key}}/{{your-file-name}}"
X-Amz-Credential: "{{X-Amz-Credential}}"
X-Amz-Security-Token: "{{X-Amz-Security-Token}}"
X-Amz-Date: "{{X-Amz-Date}}"
X-Amz-Signature: "{{X-Amz-Signature}}"
X-Amz-Algorithm: "{{X-Amz-Algorithm}}"
X-Amz-Meta-Name: "{{your-file-name}}"
Policy: "{{Policy}}"
Content-Type: "{{your-file-extension}}"
file: "{{your-file-path}}"

You should receive an HTTP 204 on a successful request.

New infrastructure, refactoring and other improvements​

The reconciliation engine has a new home. In the course of our ongoing efforts to modernize the underlying infrastructure on which RaiseNow services are run, we have moved reconciliation to a new container engine and upgraded to software and libraries used to the latest LTS versions. In addition, various improvements were made to improve debugging options and performance.