Skip to main content

On-boarding Module 3 - Transaction data

Collection of transaction data to ensure overview and traceability to products and suppliers.

Bjarke Guldager avatar
Written by Bjarke Guldager
Updated over 2 months ago

Need help?

Contact us at support@prduct.com or via the chat icon in the bottom right corner.

3.1 – Define data points

You need to define the data points included in your transaction data. Consider what information you currently have available on your orders and which should be transferred into prduct.com.

3.2 – Create custom data points

There may be data points you want that are not in the system. These can be created as needed, but if you already know them, we recommend doing this before step 3.3.

3.3 – Set up integration with order system

Integration with your order system depends heavily on the specific system and the desired level of integration. Expect 1–2 months including setup and testing.

3.4 – Set up invoice data model

To handle invoices, a data model must be configured. This should at minimum include the points listed on the right.

3.5 – Set up batch data model

To handle batches, a data model must be configured. This should at minimum include the following attributes.

3.6 – Set up invoice alerts

If you need to ensure that specific information is present on incoming invoices, we recommend using alerts — a way to automatically flag missing information.

3.7 – Set up DDS alerts

We recommend setting up DDS alerts so you automatically receive notifications on batches and invoices if information required for DDS is missing.

3.8 – Set up integration with EU TRACES

You must have your business registered on EU TRACES. The integration is then activated in prduct.com.

In connection with this, you need to determine whether you are an operator or distributor, as this affects the level of integration with EU TRACES.

Need help?

Contact us at support@prduct.com or via the chat icon in the bottom right corner.

Did this answer your question?