Subscribe

UiPath Process Mining

The UiPath Process Mining Guide

Purchase-to-Pay Due Dates

Introduction

In UiPath Process Mining, a due date is defined as an activity that needs to occur before a specified date. Due dates are used to get information regarding cases meeting or not meeting deadlines and the related costs.

A due date checks the difference between the Actual date of an event and the Expected date of the event. By default, the actual date is defined as value of the event end attribute. To create a proper due date, you must define the Expected date for the due date. Optionally, you can define the Due date amount, which is often referring to a penalty or a discount, and a Time bin, which is a description of whether the due date was met on time or not. For example, 1 day late or 3 days late.

Default Due dates

In the SAP Purchase-to-Pay Connector default due dates are defined for the Purchase-to-Pay process. For each Due date an expression for the actual date and for the expected date is defined in the Events_preprocessing table. See illustration below.

In the SAP Purchase-To-Pay Connector the following default due dates are defined for the Purchase-to-Pay process.

Due date

Description

Actual date

Expected date

Requested goods receipt deadline

The goods should be delivered on/before the goods receipt deadline. If the goods are delivered after the goods receipt due date, the goods delivery is considered overdue.

Event end of activity Post goods receipt

Requested delivery date

Payment complete deadline

The invoice should be paid on/before the payment due date. If the invoice is paid after the payment due date, the accounts receivables are considered to be overdue.
Note: discount periods can be taken into account.

Event end of activity Create outgoing payment

Payment due date

Updated 11 days ago



Purchase-to-Pay Due Dates


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.