Due Date Filter

Overview

The Due Date filter is a specialized Accounts Payable filter that selects cases based on when payment was made relative to the invoice due date. This process-specific filter helps identify late payments, early payments, or on-time payments by comparing the payment activity timestamp against the due date attribute, enabling focused analysis of payment timeliness patterns.

Common Uses

  • Identify late payments for supplier relationship analysis
  • Find early payments that may miss discount opportunities
  • Analyze on-time payment rates by vendor or department
  • Measure payment timeliness KPIs
  • Investigate factors contributing to payment delays
  • Monitor payment performance against targets

Settings

Search Type: Determines how payments are compared to due dates:

  • Activity Time Greater Than (Late - Full DateTime): Finds cases where payment occurred AFTER the due date and time
  • Activity Date Greater Than (Late - Date Only): Finds cases where payment occurred on a date AFTER the due date (ignores time component)
  • Activity Time Less Than (Early - Full DateTime): Finds cases where payment occurred BEFORE the due date and time
  • Activity Date Less Than (Early - Date Only): Finds cases where payment occurred on a date BEFORE the due date
  • Activity Time Same Day (On-Time): Finds cases where payment occurred on the same date as the due date

Remove Selected Cases: When enabled, inverts the filter to exclude matching cases instead of including them.

Note: This filter uses the standard Accounts Payable activity "PayInvoice" and attribute "DueDate" automatically.

Examples

Example 1: Finding Late Payments

Scenario: You want to identify all invoices that were paid after their due date for supplier relationship management.

Settings:

  • Search Type: Activity Date Greater Than (Late - Date Only)
  • Remove Selected Cases: Unchecked

Result:

Cases where the payment date is after the due date are included. Invoice #1001 with Due Date 2024-01-15 and Payment Date 2024-01-20 is included (5 days late). Invoice #1002 with Due Date 2024-01-15 and Payment Date 2024-01-10 is excluded (early).

Insights: Late payments damage supplier relationships, may incur penalties, and indicate process bottlenecks. Analyzing late payment patterns helps identify root causes like approval delays, cash flow issues, or processing backlogs.

Example 2: Identifying Early Payments

Scenario: You want to find payments made significantly early, which might indicate cash management inefficiencies (paying too early loses interest income).

Settings:

  • Search Type: Activity Date Less Than (Early - Date Only)
  • Remove Selected Cases: Unchecked

Result:

Cases where payment occurred before the due date are included. This might reveal opportunities to better time payments - paying at the optimal point to maximize cash flow while still meeting obligations.

Insights: Paying too early ties up working capital unnecessarily. Analyzing early payments helps identify where payment timing could be optimized without risking late fees.

Example 3: On-Time Payment Analysis

Scenario: You want to analyze your on-time payment rate by finding cases paid exactly on the due date.

Settings:

  • Search Type: Activity Time Same Day (On-Time)
  • Remove Selected Cases: Unchecked

Result:

Cases where payment occurred on the same day as the due date are included. This shows your "just in time" payments - maximizing cash flow while meeting deadlines.

Insights: High rates of same-day payment may indicate good cash management or may suggest cutting it too close with risk of slipping late. Balance against early and late payments for a complete picture.

Example 4: Excluding Late Payments

Scenario: You want to analyze your successful payment processes by focusing only on payments that were NOT late.

Settings:

  • Search Type: Activity Date Greater Than (Late - Date Only)
  • Remove Selected Cases: Checked

Result:

Late payments are excluded. The remaining cases (early and on-time payments) represent successful process execution. Analyze these to understand what makes timely payments possible.

Insights: By removing problematic cases, you can identify best practices from your successful payments that could be applied to improve late payment rates.

Example 5: Precise Time-Based Analysis

Scenario: Your company defines "late" as any payment after the exact due date and time (not just date). You need this precision for contractual compliance.

Settings:

  • Search Type: Activity Time Greater Than (Late - Full DateTime)
  • Remove Selected Cases: Unchecked

Result:

Cases are evaluated against the full datetime. A payment at 2024-01-15 09:00 is on-time if the due datetime is 2024-01-15 17:00, but late if the due datetime is 2024-01-15 08:00.

Insights: Full datetime comparison is important when contracts specify exact payment times or when operating across time zones where date-only comparison might miscategorize payments.

Required Data Structure

This filter is designed for Accounts Payable processes and requires:

  • Activity: "PayInvoice" - The activity representing payment execution
  • Attribute: "DueDate" - A datetime attribute on cases containing the payment due date

If your data uses different naming, you may need to use the general Deadline filter with custom activity and attribute names.

Output

This filter operates at the case level comparing payment timing:

  • Compares the PayInvoice activity timestamp against the DueDate attribute
  • Supports both date-only and full datetime comparisons
  • Can identify late, early, or on-time payments
  • When "Remove Selected Cases" is unchecked: Returns matching cases
  • When "Remove Selected Cases" is checked: Returns non-matching cases
  • Preserves all case and event attributes for included cases

Use the Due Date filter to analyze payment timeliness in Accounts Payable processes, enabling root cause analysis of late payments and optimization of payment timing strategies.

This documentation is part of the mindzie Studio process mining platform.