Skip to main content

Celonis Product Documentation

Installing the object-centric Duplicate Invoice Checker

The object-centric version of the Duplicate Invoice Checker for Accounts Payable works with objects and events created for object-centric process mining. Before you set up the object-centric version of the Duplicate Invoice Checker, you’ll need to enable and configure the Accounts Payable process, load the object-centric data model with your data, and validate the standard Accounts Payable perspective. You’ll also need to activate AI Annotations for the team. See Prerequisites for the object-centric Duplicate Invoice Checker.

You can download the Duplicate Invoice Checker from the Celonis Marketplace. The app uses a dedicated perspective perspective_DuplicateInvoiceChecker_DuplicateInvoiceCheckerApp, which uses the objects and events that you’ve built from your source system data for Accounts Payable and stored in the OCPM Data Pool.

Algorithm and default search patterns for the object-centric Duplicate Invoice Checker has more details about the app’s architecture and behaviors.

Here’s how to install the object-centric Duplicate Invoice Checker:

  1. Open the Celonis Marketplace from the Celonis navigation menu, and search for all or part of the app’s name. You’ll probably see an original case-centric version of the app as well as the object-centric version. Only the object-centric version is suitable for object-centric process mining.

  2. Select the Duplicate Invoice Checker (object-centric) app to see its information page, and select Get it now to install the app. If you see Request Access instead, click this to request the app, and check the other prerequisite steps in Prerequisites for the object-centric Duplicate Invoice Checker.

  3. In Celonis, choose a Studio space to install the app in. You can use an existing Studio space or create a new one. (You can move the app after installation.) Click Confirm to proceed with the installation.

  4. In the newly installed package, go to Package Settings > Variables and locate the “accounts_payable” Data Model variable. Select the Assign Data Model button, then search or browse for the perspective_DuplicateInvoiceChecker_DuplicateInvoiceCheckerApp perspective and click to select it. Click Save to set the Data Model variable.


    Don’t pick the version of the perspective with the prefix test: This is the version for the development environment, which won’t work - you need to use the production perspective without the prefix.

  5. Go to the data pool that you’re using for objects and events, and schedule and run the data job auto_generated_dic_combine_vendor_credit_debit_account_items. We create this data job automatically when we enable AI Annotations and the Duplicate Invoice Checker Signal in your team. It contains a transformation that unifies the debit and credit items into the VendorAccountItem object (in the table o_DuplicateInvoiceChecker_VendorAccountItem). Here’s how to schedule and run it:

    1. In the data pool that you’re using for objects and events, find the schedule that you’re using to run the data job ocpm-data-job. If you haven’t set up a schedule yet, follow the instructions in  Scheduling data jobs for object-centric process mining to create one.

    2. At the end of the schedule page, select Add Data Job and select the job auto_generated_dic_combine_vendor_credit_debit_account_items. By default, it’s added to the end of the schedule. It needs to run any time after the data job ocpm-data-job.

    3. Run all the data jobs in your schedule, and check that they completed successfully.

    4. Go to the Data Models area in this data pool, and select the perspective_DuplicateInvoiceChecker_DuplicateInvoiceCheckerApp perspective. Go to its Data Loads tab, and check that the data model load completed successfully. If it hasn't, click Load Data Model.

    When you’ve successfully run the data jobs and loaded the perspective, the AI Annotation will be able to use the VendorAccountItem objects.

  6. Set the Knowledge Model key for your local app installation, as the value of the Knowledge Model Key variable in the app’s Knowledge Model. Setting the Knowledge Model Key variable for the object-centric Duplicate Invoice Checker explains how.


    Typically you'd go to an app's views at this point in the install to check if your data is showing correctly. However, the Duplicate Invoice Checker won’t show any results in the Action View until you’ve set up and run the AI Annotation, so don’t expect the components to be working at this stage. There’s also no Settings view - you set the app’s operating parameters in the AI Annotation configuration interface. And you don't need to validate the KPIs in the Knowledge Model.

  7. Configure and run the AI Annotation for the app to define custom patterns and filters. Configuring the AI Annotation for the object-centric Duplicate Invoice Checker has the instructions.

  8. If you want to customize the app’s views to change their look, fit your business process, or include custom attributes or relationships that you added to the Celonis object types used in the Accounts Payable process, edit them in Studio. Editing views for the object-centric Duplicate Invoice Checker explains the process. You’ll need Analyst permissions for Studio and the views to modify them.

  9. Publish a version of the app, then check that the Action View shows your data correctly. There's a Publish Package button at the top of all the screens in your Studio space.