Skip to main content

Statement Matching: Create the extension

info

This page covers the statement matching extension, which reconciles supplier statement lines against your Unit4 ERP transactions. If you are setting up the invoice flow instead, see creating the extension.

warning

Please note that if you are using our hosted solution, this step may already have been done for you. Please get in touch with support if you are unsure.

Statement matching is set up as its own Rossum queue and webhook extension, separate from the invoice extension covered on the create the extension page. You can run both side by side under the same license, each pointed at its own queue.

Sign up with Rossum​

To continue you will need access to a Rossum document processing queue dedicated to statements. If you are using our hosted solution this will be provided. If you are not using this, you will need to sign up for your own processing queue at Rossum and follow their documentation to create a queue.

Add a webhook extension​

info

Some of the information you will need to configure the extension will come from ERP Apps following the authorisation step, and some from your Unit4 ERP following configuration of permissions there. So ensure those steps are complete before proceeding.

To add the extension, log into Rossum and navigate to "Extensions" -> "My Extensions" then hit "Create Extension".

Fill in the form fields as follows:

  • Name: Something meaningful to you. This can be anything.
  • Description: Something meaningful to you. This can be anything.
  • Triggered events: Ensure you select Document Content - Updated, Document Content - Initialize, Document Content - Started and Document Content - Export and no other events.
  • Queues: Select the statement queue to which this should be applied. (Note this can be applied to multiple queues under the same license, all queues must be licensed to work)
  • Extension Type: Choose "Webhook"
  • URL: Enter the statement matching URL provided to you after you purchased the system. This is a different URL to the one used for the invoice extension.
  • Shared Secret: This should be the API Key provided to you after you purchased the system (may be referred to as a license key).
  • Logging ability: "Log payload of the extension" should usually be set to off to ensure no unexpected PII is recorded in Rossum's data stores. However during initial setup with example data or when troubleshooting, you may find it useful to temporarily turn this option on.

Now we need to configure some advanced settings in order to tailor the solution to your particular needs and to allow access to your Unit4 ERP solution. To continue with this, click "Show Advanced".

In the Access to Rossum's API from extension dropdown, choose a user with adequate permissions to mark a document as exported.

Configuration box​

In the configuration text box, copy the following and then edit to match your setup.

clientId should be your Unit4 ERP client ID. (Note this is optional, please see the getting started documentation for some notes on multi client setups)

statementDocumentType and erpVersion are the only required settings — statementDocumentType should be the document type that the statement match report will be written back to (must be a valid document type attached to the supplier).

{
    "clientId": "PUK",
    "erpVersion": "erp7",
    "statementDocumentType": "STATREP"
}

This minimal configuration will use our default matching behaviour. It is likely that you will want to tailor the matching rules (matchCodes / matchSequences) and other options further, please see our statement extension configuration page.

Secrets box​

In the secrets text box you should now paste your connection details. Options are available for ERPCR and ERP7 solutions, either in cloud or on premise, please see the information on our secrets page for more details — the same secrets configuration is used for both the invoice and statement extensions.

When you save the secrets the box will show as blank again, however the data will be saved. To overwrite a secret, simply input the corrected data and save it.

Queue schema​

Your statement queue will also need the required schema fields configuring — see the statement queue schema page.

Finalise Setup​

Once all details are entered and correct, hit "Create". (You may be able to save your progress before this point)

You're now ready to go!

To understand how matching behaves once documents start flowing through, see the statement matching user guide.