Skip to main content

Paid Early Report

The Paid Early Report Action Flow optimizes working capital by identifying and reporting invoices settled ahead of their due dates. By highlighting these early payments—often caused by a lack of invoice prioritization—this tool helps organizations prevent unnecessary cash-in-hand loss and improve liquidity KPIs through automated, aggregated data insights.

This Action Flow automates the monitoring of payment timing across your organization. It follows a multi-stage logic to transform raw AP data into executive summaries:

  • Data extraction: Queries the data model for specific invoice details and aggregate measures (volume and total value).

  • Organization and sorting: Maps data to specific Company Codes, orders results by invoice value, and isolates the top 5 high-impact early payments.

  • Smart routing: Uses a router to direct specific Company Code insights (e.g., Code 1000 or 2000) to the appropriate regional managers.

  • Automated delivery: Formats and distributes the findings via email to ensure timely intervention.

PaidEarlyReport_ProcessDiagram.png

Before configuring this Action Flow, you need access to a data model that includes accounts payable information.

See: Modeling your data.

For this Action Flow, only the modules listed below require configuration:

1. Set Initial Variables

You can define the running variables for your process, allowing you to define the time frame, currency, early payment buffers, and any application links you want to refer to in the final email.

To define the running variables, click the Clock icon on the Action Flow Editor:

PaidEarlyReport_SetInitial.png

In this module you can define the sets that will be used for aggregating your Invoices or KPIs.

To configure the map loop and company codes, click the icon on the Action Flow Editor.

PaidEarlyrReport_Map.png

In the image, you can see two different outputs. In the first iteration, this module will output ‘1000’,’2000’. This output means the KPIs will be calculated for invoices belonging to these Company Codes.

In the second iteration, they will be calculated for invoices belonging to Company Code ‘3000’.

You can add as many rules as you want, including having Outputs with more than one Company Code (e.g. if your country is composed of Company Codes A and B, you can add a rule like “Pattern = 3, Output = ‘A’,’B’ “ .) You will also need to increase the maximum number of iterations in module 2.Loop for each new rule you add.

To get the Invoice details, you have to set up the Get Rows module.

Note

You don't have to change any fields or filters.

In this module, you can set up the filters that will be applied when displaying the data in the email.

To configure your router, click the connections on the Action Flow Editor.

PaidEarlyReport_Router.png

In our example, we will be passing information regarding the iteration that contained Company Code 1000 (and ‘2000’ since the list also contained a second Company Code) for the next module of the AF.

You can add as many routing paths as you would like. In the case you want the same recipient to receive the information about two different lists of Company Codes (defined in module3.Map Loop and Company Codes) you will need to set up 2 routes, one for each list.

PaidEarlyReport_FilterExample.png

You need to set your desired Company Code value in the first condition, e.g.

Condition 1: “30.Output contains 1000”

Conditions 2 and 3 do not require changes.

In this module, you need to configure the email connection and to define the recipient(s) of the email.

To configure your email settings, click the Email icon on the Action Flow Editor:

PaidEarlyReport_Email.png

Change the following settings:

  • Connection: Connect to your mail account and grant Celonis permission to read and write emails.

  • To: Define the recipient you want to send the emails to, e.g. johndoe@domain.com

Related topics