> Continuous Process Improvement > Credit Management & Collections > HighRadius > Data Template

Your Credit Management & Collections Data Template

HighRadius

Credit Management & Collections Attributes (22) Credit Management & Collections Activities (15) Extraction Guides (2)

Your Credit Management & Collections Data Template

This template provides a structured guide to collecting the necessary data for analyzing your credit management and collections process. It outlines essential attributes to capture, key activities to track, and provides practical guidance on how to extract this information from your HighRadius system. Using this template will help you prepare your data efficiently for process mining.

Recommended attributes to collect
Key activities to track for process visibility
HighRadius-specific extraction guidance

New to event logs? Learn how to create a process mining event log.

Download Template

Credit Management & Collections Attributes

These are the recommended data fields to include in your event log for comprehensive analysis of your credit management and collections process.

3 Required 7 Recommended 12 Optional

	Name	Description
	Activity Name ActivityName	The name of the specific business event that occurred at a point in time for an invoice.
Description The Activity Name describes a step in the credit and collections process, such as 'Invoice Generated', 'Overdue Reminder Sent', or 'Payment Received'. This sequence of activities forms the process flow for each case. Analyzing this attribute allows for the discovery and visualization of the actual process map. It helps identify bottlenecks, deviations from the standard procedure, and rework loops. The frequency and order of activities like 'Collection Call Logged' or 'Dispute Registered' are key to understanding process efficiency. Why it matters This attribute defines the steps in the process, enabling the reconstruction and analysis of the process flow for each invoice. Where to get This is typically derived from event logs, status changes, or specific action records within the HighRadius platform's various modules. Examples Invoice Sent to CustomerDunning Procedure InitiatedPayment ReceivedDispute Resolved
	Event Time EventTime	The timestamp indicating when the activity occurred, including date and time.
Description Event Time provides the precise date and time for each activity in the process. This chronological data is the backbone of process mining, allowing for the correct ordering of events and the calculation of durations between them. This attribute is used to calculate all time-based KPIs, such as cycle times for dispute resolution, credit approval, and payment posting. It is also used to analyze process performance over time, identify activities that cause delays, and measure adherence to service level agreements. Why it matters It provides the chronological context for all activities, which is essential for calculating cycle times, discovering bottlenecks, and understanding process dynamics. Where to get Every transactional record or event log in HighRadius should have a corresponding timestamp field, often named 'Creation Date' or 'Timestamp'. Examples 2023-03-15T10:00:00Z2023-04-01T14:35:10Z2023-05-20T09:12:45Z
	Invoice Number InvoiceNumber	The unique identifier for each invoice, serving as the primary case identifier for the credit-to-cash process.
Description The Invoice Number is the central key that links all activities related to a single accounts receivable transaction. It allows for tracking the entire lifecycle from invoice generation, through various credit management and collection activities, to final settlement or write-off. In process mining analysis, this attribute is essential for grouping all related events into a single case. This enables the visualization of end-to-end process flows, the calculation of case durations like Days Sales Outstanding (DSO), and the analysis of different paths an invoice might take, such as dispute resolution or dunning procedures. Why it matters It is the fundamental identifier that connects all process steps, making it possible to analyze the complete journey of an invoice from creation to closure. Where to get This is a primary field in HighRadius, typically found in the core invoice or receivables data objects. Examples INV-2023-001239876543210SI-55482
	Collector Name CollectorName	The name of the user or agent responsible for performing a collection activity.
Description This attribute identifies the collections agent, credit analyst, or other user who executed a manual activity, such as 'Collection Call Logged' or 'Dispute Resolved'. In analysis, this allows for performance comparisons between different collectors or teams. It helps in understanding workload distribution, evaluating the effectiveness of individual strategies (e.g., Collection Call Success Rate per collector), and identifying coaching opportunities. It is also key for resource management and capacity planning. Why it matters It links process activities to specific individuals, enabling analysis of team performance, workload, and the effectiveness of manual interventions. Where to get This information is typically stored in activity logs or user action records within the HighRadius Collections module. Examples John SmithJane DoeEmily Jones
	Customer ID CustomerId	The unique identifier for the customer associated with the invoice.
Description The Customer ID links an invoice to the specific customer entity. This allows for aggregating and analyzing process data from a customer-centric view. This attribute is essential for analyzing payment behaviors of different customers or customer segments. It helps answer questions like: Which customers are frequently late? Which customers raise the most disputes? It supports dashboards like Payment Terms Adherence and allows for segmenting KPIs by customer. Why it matters It enables customer-level analysis of payment behavior, dispute frequency, and overall process interaction, helping to tailor collection strategies. Where to get This is a standard field on the invoice header or customer account data within HighRadius. Examples CUST-001ACME-CORPGLOBEX-US
	Dispute Reason DisputeReason	The reason code or description provided when an invoice is disputed by a customer.
Description When a customer raises a dispute, they typically provide a reason, such as 'Incorrect Pricing', 'Damaged Goods', or 'Duplicate Invoice'. This attribute captures that reason. Analyzing Dispute Reason is key to the 'Invoice Dispute Resolution Time' dashboard. It helps identify the root causes of disputes, allowing the business to address systemic issues in pricing, shipping, or billing. Reducing disputes at the source can significantly accelerate cash flow. Why it matters It provides insight into the root causes of payment delays, enabling targeted process improvements to prevent future disputes. Where to get This information is captured in the dispute management or deductions module of HighRadius when a dispute is logged. Examples Incorrect QuantityPrice DiscrepancyDamaged GoodsDuplicate Billing
	Due Date DueDate	The calculated date by which the invoice payment is due.
Description The Due Date is the specific calendar date that an invoice must be paid by to avoid being considered overdue. It is typically calculated from the invoice date and the payment terms. This attribute is fundamental for all overdue analysis. It is the primary input for calculating 'Days Overdue', triggering dunning procedures, and measuring the 'Payment Terms Adherence Rate' KPI. It directly supports dashboards related to invoice aging and dunning effectiveness. Why it matters It is the critical date that determines if an invoice is on-time or overdue, triggering all subsequent collection activities and KPIs. Where to get This is a standard field on the invoice record in HighRadius. It may be populated from the source ERP or calculated within HighRadius. Examples 2023-04-142023-05-312023-06-20
	Invoice Amount InvoiceAmount	The total monetary value of the invoice.
Description This attribute represents the total amount due on the invoice. It is a critical financial metric for understanding the value associated with each case. In process mining, Invoice Amount is used to prioritize collection efforts, for example, by focusing on high-value overdue invoices. It is fundamental for financial KPIs like Days Sales Outstanding (DSO) and is used in the Invoice Write-Off Analysis dashboard to quantify the financial impact of bad debt. Why it matters It provides the financial context for each case, enabling value-based analysis, prioritization of work, and quantification of financial impacts like write-offs. Where to get This is a standard field on the invoice header data within HighRadius. Examples 5000.001250.7525000.50
	Payment Status PaymentStatus	The current financial status of the invoice, such as Open, Paid, Overdue, or Disputed.
Description Payment Status provides a snapshot of where an invoice is in its lifecycle. It indicates whether it is still awaiting payment, has been fully or partially paid, is past its due date, or is under investigation due to a dispute. This attribute is central to the 'Invoice Payment Status & Aging' dashboard. It allows for quick segmentation of the accounts receivable portfolio to understand the overall financial health and prioritize collection efforts on overdue or disputed items. Why it matters It categorizes invoices into actionable groups, providing immediate visibility into the state of receivables and helping to prioritize collection activities. Where to get This is a core status field on the invoice or accounts receivable record within HighRadius. Examples OpenPaidOverdueDisputedWritten Off
	Payment Terms PaymentTerms	The agreed-upon terms that define when a customer is expected to pay an invoice.
Description Payment Terms specify the conditions of payment, such as 'Net 30', 'Net 60', or 'Due on Receipt'. This attribute is the basis for calculating the invoice due date. This is a key attribute for the 'Payment Terms Adherence' dashboard and KPI. Analyzing it helps identify whether standard terms are being applied consistently and which payment terms are associated with higher rates of late payments. This insight can inform credit policy and customer negotiations. Why it matters It sets the baseline for expected payment timelines, making it crucial for calculating due dates and measuring customer adherence to payment agreements. Where to get This is typically found on the invoice header or customer master data within HighRadius or the source ERP. Examples Net 30Net 60Due on Receipt
	Business Unit BusinessUnit	The internal business unit or division responsible for the sale or invoice.
Description The Business Unit attribute assigns the invoice to a specific part of the organization, such as 'Retail', 'Wholesale', or 'Services'. This allows for performance analysis to be broken down by different business segments. Management can compare KPIs like DSO, dispute rates, and write-offs across business units to identify areas of excellence or those needing improvement. It helps in holding different parts of the organization accountable for their receivables performance. Why it matters It allows for performance benchmarking across different parts of the organization, helping to identify which divisions have the most effective credit-to-cash processes. Where to get This is organizational data, typically found on the invoice or derived from the associated sales order or customer account in HighRadius or the ERP. Examples BU-North AmericaServices DivisionManufacturing
	Country Country	The country of the customer associated with the invoice.
Description This attribute specifies the country where the customer is located. It allows for geographical segmentation of the credit and collections process. Analyzing data by country can reveal regional differences in payment behavior, the effectiveness of collection strategies, and common dispute reasons. This information is vital for tailoring regional policies and for high-level management reporting in global organizations. Why it matters It enables geographical analysis, which can uncover regional trends in payment behavior and help tailor collection strategies accordingly. Where to get This information is part of the customer master data, which is typically available in HighRadius or synchronized from a source ERP. Examples USAGermanyBrazil
	Currency Currency	The currency code for the invoice amount.
Description This attribute specifies the currency of the invoice, such as USD, EUR, or JPY. It provides essential context for any monetary values like Invoice Amount. In any multi-national company, this field is non-negotiable for accurate financial analysis. It ensures that monetary values are interpreted correctly and allows for proper currency conversion when aggregating data for global reporting. Why it matters It is essential for the correct interpretation of all monetary values, preventing inaccurate financial calculations and reporting in multi-currency environments. Where to get This is a standard field on the invoice record, usually located alongside the Invoice Amount. Examples USDEURGBP
	Days Overdue DaysOverdue	The number of days an invoice is past its due date. It is zero if the invoice is not yet due or has been paid on time.
Description Days Overdue is a calculated metric that measures the difference between the current date (for open invoices) or the payment date (for paid invoices) and the invoice's due date. It is a key indicator of payment delinquency. This attribute is the foundation of the 'Invoice Payment Status & Aging' dashboard, where it is used to group receivables into aging buckets (e.g., 1-30 days, 31-60 days). It is also a component of the Days Sales Outstanding (DSO) calculation and helps prioritize collection efforts on the most overdue accounts. Why it matters This metric directly quantifies payment delays, making it essential for aging analysis, prioritization of collections, and calculating DSO. Where to get This is not a stored field. It is calculated during data transformation using the Due Date and either the Payment Date or the current date. Examples 1545092
	Dunning Level DunningLevel	The stage or level of the automated dunning process that has been reached for an overdue invoice.
Description The Dunning Level indicates the intensity of the collection effort, often corresponding to a sequence of automated reminders or notices sent to the customer. For example, Level 1 might be a gentle reminder, while Level 3 is a final notice. This attribute is essential for the 'Dunning Strategy Effectiveness' dashboard. By analyzing which dunning levels most often lead to payment, companies can optimize their dunning workflows, ensuring they are effective without being overly aggressive and damaging customer relationships. Why it matters It tracks the escalation of collection activities, allowing for analysis of which dunning strategies are most effective at prompting payment. Where to get This is a status field managed by the automated collections or dunning workflow engine within HighRadius. Examples 123 - Final NoticeLegal Collections
	End Time EndTime	The timestamp indicating when an activity was completed.
Description The End Time marks the conclusion of an activity. While many activities in collections are instantaneous events where Start Time equals End Time, some activities like 'Dispute Resolution' can have a distinct duration. This attribute, when available, is used with Start Time to calculate the Processing Time for individual activities. This helps in identifying which specific steps, not just the gaps between them, are consuming the most time and resources. Why it matters It enables the precise measurement of individual activity durations, offering a more detailed view of where time is spent within the process. Where to get Consult HighRadius documentation. This may be available for certain logged activities that have a start and end state. Examples 2023-03-15T10:45:00Z2023-04-01T15:00:10Z2023-05-20T11:15:00Z
	Is Automated IsAutomated	A boolean flag that indicates whether an activity was performed automatically by the system or manually by a user.
Description This calculated attribute distinguishes between system-generated events (e.g., 'Overdue Reminder Sent' by an automated dunning run) and human-driven actions (e.g., 'Collection Call Logged'). This flag is crucial for calculating the 'Automated Collection Activity Rate' KPI. It helps measure the level of automation in the collections process, identify opportunities for further automation, and analyze the relative effectiveness of automated versus manual touches. Why it matters It helps measure the degree of automation in the process, enabling analysis of the efficiency and effectiveness of automated systems versus manual efforts. Where to get This is derived during data transformation. It requires creating a mapping that flags certain Activity Names as automated based on business knowledge. Examples truefalse
	Last Data Update LastDataUpdate	The timestamp when the data for this record was last refreshed from the source system.
Description This attribute indicates the recency of the data. It records the date and time of the last data extraction or update from HighRadius. For analysis, this field provides context on the freshness of the insights. It is crucial for dashboards and reports to display how current the information is, ensuring that business decisions are based on up-to-date data. Why it matters It provides transparency about the timeliness of the data, which is critical for building trust in the analysis and making informed decisions. Where to get This timestamp is generated and added to each record by the data ingestion pipeline during the extraction process. Examples 2023-06-10T02:00:00Z2023-06-11T02:00:00Z2023-06-12T02:00:00Z
	Processing Time ProcessingTime	The duration of a single activity, calculated as the difference between its End Time and Start Time.
Description Processing Time measures the time spent actively working on a specific task. For many collections activities, this will be zero as they are instantaneous events. However, for tasks with a defined start and end, it provides valuable insight. This metric helps pinpoint which specific activities, rather than the waiting time between them, are consuming the most time. For example, it could measure the time a dispute case is actively being worked on. This allows for more targeted improvements to how individual tasks are performed. Why it matters It isolates the duration of value-adding work from waiting time, helping to identify inefficiencies within specific process steps. Where to get This is calculated as 'EndTime' - 'StartTime' during the data transformation process. It can only be calculated when both fields are available and meaningful. Examples 8640036000
	Promise To Pay Date PromiseToPayDate	The date on which a customer has promised to make a payment for an overdue invoice.
Description When a collector contacts a customer, they may secure a 'Promise to Pay', which is a commitment from the customer to pay by a certain date. This attribute records that promised date. Analyzing this data is important for evaluating the reliability of customer promises and the effectiveness of collectors in securing firm commitments. It can be used to track the 'kept promise' rate, which is a key performance indicator for a collections team. Why it matters It captures a key outcome of collection activities and is used to measure the effectiveness of follow-ups and the reliability of customer commitments. Where to get This date is recorded when a 'Promise to Pay' activity is logged in the HighRadius Collections module. Examples 2023-06-152023-07-012023-06-25
	Source System SourceSystem	The system from which the data originates.
Description This attribute identifies the source system where the event data was generated. For this process view, the value will typically be 'HighRadius'. In environments with multiple systems, this field is crucial for understanding data lineage and tracing information back to its origin. It helps differentiate processes that may span across different platforms, such as an ERP and a specialized collections tool. Why it matters It clarifies the origin of the data, which is important for data governance, validation, and understanding the technological landscape of the process. Where to get This is typically a static value added during the data extraction and transformation process to label the dataset. Examples HighRadiusHighRadius-CollectionsHighRadius-CashApp
	Write-Off Reason WriteOffReason	The reason code or explanation for why an invoice was written off as bad debt.
Description When an invoice is deemed uncollectible, it is written off. This attribute captures the reason for the write-off, such as 'Customer Bankruptcy', 'Unresolved Dispute', or 'Small Balance Write-Off'. This is a critical attribute for the 'Invoice Write-Off Analysis' dashboard. It helps in root cause analysis of financial losses, providing insights that can be used to refine credit policies, improve dispute handling, or adjust collection strategies to minimize future write-offs. Why it matters It explains the reasons for revenue loss, providing crucial feedback to improve credit risk assessment and collection policies. Where to get This information is recorded when an 'Invoice Written Off' activity is processed, typically within the financial or collections module of HighRadius. Examples BankruptcyStatute of Limitations ExpiredCost of Collection Exceeds Debt

Required Recommended Optional

Credit Management & Collections Activities

These are the key process steps and milestones to capture in your event log for accurate discovery and analysis of your credit management and collections process.

7 Recommended 8 Optional

	Activity	Description
	Dispute Registered	This activity marks the point when a customer raises a dispute or deduction against an invoice, which is then formally logged in HighRadius. This pauses the standard collections process for the disputed amount.
Why it matters This is the start event for measuring the Average Dispute Resolution Time. Identifying when and why disputes are raised is key to addressing root causes like billing errors or shipping issues. Where to get This event is captured when a user creates a dispute case linked to an invoice in the HighRadius Deductions Cloud. This action creates a timestamped dispute record. Capture Captured from the creation timestamp of the dispute case record associated with the invoice. Event type explicit
	Dispute Resolved	Represents the conclusion of the dispute management process, where the issue has been investigated and a resolution has been reached. The invoice can now proceed to payment or write-off.
Why it matters This is the end event for measuring the Average Dispute Resolution Time. Long cycles here can significantly delay cash collection and indicate process inefficiencies. Where to get This is captured when the status of the dispute case is changed to 'Resolved', 'Closed', or a similar terminal state. The timestamp of this status change is used for the activity. Capture Inferred from the timestamp when the dispute case status is updated to a final 'Resolved' state. Event type inferred
	Invoice Generated	This is the starting point for an invoice's lifecycle in the collections process. It signifies that an invoice has been created in the ERP system and imported into HighRadius for receivables management.
Why it matters This activity serves as the primary start event for the invoice-to-cash process analysis. All cycle times, such as Days Sales Outstanding (DSO), are typically measured from this point. Where to get This is an explicit event captured from the creation date of the invoice record within HighRadius, which is usually synced from the source ERP system like SAP or Oracle. Capture Captured from the creation timestamp of the invoice record in the receivables data. Event type explicit
	Invoice Settled	This activity signifies the successful end of the invoice lifecycle, where the invoice is fully paid and closed. It is the desired final state for the process.
Why it matters This serves as the primary 'happy path' end event for the process. Analyzing paths to this outcome helps identify best practices and successful collection strategies. Where to get This is typically not an explicit event but is inferred from the invoice status changing to 'Closed' or 'Cleared' and the balance becoming zero. The timestamp of the final payment posting often serves as the event time. Capture Inferred from the invoice status changing to 'Closed' or when the invoice balance field becomes zero. Event type inferred
	Invoice Written Off	Represents an alternative end to the invoice lifecycle where the debt is deemed uncollectible and is written off as bad debt. This is an undesirable outcome.
Why it matters Tracking write-offs is critical for calculating the Invoice Write-Off Rate and analyzing the root causes of financial loss. It helps identify failures in credit assessment or collection efforts. Where to get This event is captured when a specific transaction to write off the invoice balance is posted or when the invoice status is changed to 'Written-Off'. Capture Inferred from a status change to 'Written-Off' or from a specific write-off transaction type being posted against the invoice. Event type inferred
	Payment Due Date Passed	A calculated event that occurs when the current date surpasses the invoice's payment due date. This activity does not represent a user or system action but is a critical state change that triggers the collections process.
Why it matters This activity is the primary trigger for all subsequent dunning and collections activities. It separates on-time invoices from overdue ones, enabling analysis of collection strategy effectiveness. Where to get This event is not stored directly but is calculated by comparing the invoice due date field with the timestamp of other events. It is derived during the process mining data transformation. Capture Calculated by comparing the invoice due_date with the current date or event timestamp (Timestamp > Due Date). Event type calculated
	Payment Received	This activity marks the receipt of payment from a customer, often recorded from a bank statement or lockbox file. This signifies that funds have been received but not yet applied to the specific invoice.
Why it matters This is a critical milestone that often stops the collections clock. It's the starting point for measuring the Payment Receipt to Posting Lag KPI, highlighting delays in cash application. Where to get This is captured from payment records in HighRadius's Cash Application Cloud. Each payment batch or transaction from a bank file will have a receipt date. Capture Captured from the timestamp of the payment record when it is imported or entered into the cash application module. Event type explicit
	Collection Call Logged	Represents a manual collection call made by a collections agent to the customer regarding an overdue invoice. Agents log the details and outcome of the call directly in HighRadius.
Why it matters This activity is crucial for assessing the Collection Call Success Rate and Collection Activity Efficiency. It helps distinguish between automated and manual collection efforts. Where to get This is an explicit event created when a collector uses the 'Log Call' or 'Add Activity' function on the invoice or customer account in the HighRadius interface. The entry includes a timestamp. Capture Captured from the activity log table where collectors record manual actions. Event type explicit
	Credit Limit Approved	Represents the successful completion of the credit review process, where a credit limit is officially granted to the customer. This event is captured when a credit manager approves the request within the HighRadius platform.
Why it matters This is a key milestone that unblocks the sales process. Tracking this activity is essential for calculating the total credit approval cycle time KPI. Where to get This event is typically captured from a status change on the credit limit request, moving to 'Approved'. It may also be an explicit event in the system's audit log. Capture Inferred from a status change on the credit request to 'Approved' or from the approval timestamp field. Event type inferred
	Credit Limit Requested	This activity marks the initiation of a credit assessment for a customer. It is typically triggered before a sales order is finalized and is captured when a request for a new or updated credit limit is entered into the system.
Why it matters Analyzing the time from request to approval helps identify bottlenecks in customer onboarding and sales cycles. It is a critical starting point for measuring the efficiency of the credit management team. Where to get This event is likely inferred from a status change on the customer's credit profile or from the creation date of a credit limit request record in HighRadius's Credit Management module. Capture Inferred from the creation timestamp of a credit limit request object or a status change to 'Pending Approval'. Event type inferred
	Dunning Procedure Initiated	This activity signifies the start of a formal dunning process or a specific level within that process for an overdue invoice. It represents a more systematic step than a single reminder.
Why it matters Tracking the initiation of dunning procedures helps in analyzing the effectiveness of different collection strategies and dunning levels at prompting payment. Where to get This event is typically inferred from a change in the 'Dunning Level' or 'Collection Strategy' field associated with the invoice record in HighRadius. Capture Inferred from a change in the invoice's dunning level attribute, captured via change logs or timestamped history. Event type inferred
	Invoice Sent to Customer	This activity marks the point at which the invoice has been delivered to the customer, typically via email or a customer portal. HighRadius can automate and log this communication event.
Why it matters Tracking this helps ensure that customers are receiving invoices promptly. Delays between invoice generation and sending can directly impact payment times and DSO. Where to get This is often logged explicitly in the correspondence or activity history associated with the invoice in the Collections Cloud module. It may also be inferred from the status of an automated correspondence job. Capture Logged in the communication history for the invoice when an email or portal delivery is executed. Event type explicit
	Overdue Reminder Sent	Represents an automated or manual reminder sent to a customer regarding an overdue invoice. HighRadius automates this as part of its dunning strategies, creating a log of the communication.
Why it matters This activity is fundamental to measuring the Dunning Effectiveness Rate. It allows for analysis of how many reminders are needed before a payment is received. Where to get This is an explicit event recorded in the activity or correspondence log for the invoice within the HighRadius Collections Cloud. Each reminder sent will have a corresponding entry and timestamp. Capture Captured from the timestamped communication log associated with the invoice. Event type explicit
	Payment Posted	Represents the completion of the cash application process, where a received payment has been successfully matched and applied to a specific invoice, clearing the open balance.
Why it matters This activity concludes the payment processing cycle. The time between 'Payment Received' and 'Payment Posted' reveals the efficiency of the cash application process. Where to get This event is captured from the posting date or clearing date field on the invoice record. This timestamp is recorded when the cash application is finalized. Capture Captured from the 'posting date' or 'clearing date' timestamp on the invoice's accounting line item. Event type explicit
	Promise to Pay Created	This activity occurs when a customer makes a commitment to pay an invoice on a future date, and the collections agent records this promise in the system. This is a positive intermediate outcome.
Why it matters Tracking promises to pay helps in forecasting cash flow and evaluating collector effectiveness. It also allows for analysis of broken promises, where payment is not received by the promised date. Where to get This is an explicit event logged in HighRadius when an agent creates a 'Promise to Pay' record linked to an invoice. This record has its own creation timestamp. Capture Captured from the creation timestamp of the 'Promise to Pay' object in HighRadius. Event type explicit

Recommended Optional

Extraction Guides

How to get your data from HighRadius

Steps

Access the Reporting and Analytics Module: Log in to your HighRadius instance with a user that has the necessary permissions to create and run custom reports. Navigate to the Reporting and Analytics section from the main dashboard or application menu.
Create a New Custom Report: Initiate the process to build a new report. Select a base object that serves as the primary anchor for your data, such as the Invoices or Open A/R object. Give the report a descriptive name, for example, ProcessMind_Credit_Collections_Log.
Define Core Invoice Attributes: Add the primary fields for the invoice to your report layout. This includes InvoiceNumber, CustomerId, InvoiceAmount, PaymentTerms, DueDate, and PaymentStatus. These will form the base columns for every event.
Add Data from Related Objects (Events): This is the most critical step. You will need to join or union data from various HighRadius objects to capture all 15 required activities. Use the report builder's functionality to add related data sources. For each activity, you will create a set of columns representing the event details.
Structure the Report for Event Log Format: Configure the report to produce one row per event. This typically involves unioning different data blocks rather than joining them as columns. For each unioned block, you will map the relevant date field to a common EventTime column and hardcode the corresponding ActivityName.
Configure the 'Payment Due Date Passed' Event: This event is conditional. Create a specific data block in your report for invoices where the DueDate is in the past and the PaymentStatus is still 'Open' or 'Overdue'. For these records, set the ActivityName to 'Payment Due Date Passed' and use the DueDate itself as the EventTime.
Add Collector and Dispute Information: Ensure you include data from the Collections and Disputes modules. Join to objects like CollectorNotes or ActivityHistory to get CollectorName. Join to the Disputes object to retrieve DisputeReason when applicable.
Set Report Filters: Apply filters to define the scope of the extraction. Set a specific date range for the EventTime, such as the last 6 months, to keep the dataset manageable. You may also need to filter by specific Company Codes or business units depending on your organizational structure.
Run and Preview the Report: Execute the report to preview the data. Verify that the structure matches the required event log format, with one row per activity and columns for InvoiceNumber, ActivityName, EventTime, and other attributes.
Export the Report Data: Once you are satisfied with the preview, export the full report. Select CSV as the export format, as it is easily ingested by process mining tools. Ensure the export settings use UTF-8 encoding to prevent character issues.
Final Data Review: Open the exported CSV file in a spreadsheet application. Perform a final check to ensure all 15 activities are present, timestamps are correctly formatted, and key attributes are populated as expected before uploading to ProcessMind.

Configuration

Report Type: A custom report combining data from multiple modules. This may be called a 'Joined Report' or require multiple data 'Blocks' that are unioned together, depending on the specific HighRadius version.
Primary Data Object: Start with the Invoices or Accounts Receivable object as the base of the report.
Secondary Data Objects: You will need to link to additional objects such as CreditRequests, CustomerCommunications, DunningHistory, CollectorActivityLog, PromiseToPay, DisputeCase, and CashApplication.
Date Range Filter: Apply a filter on the primary event timestamp field. It is recommended to extract data for a period of 3 to 6 months to balance detail with performance. For example, EventTime within the last 180 days.
Status Filters: Consider filtering out irrelevant invoice statuses, such as 'Cancelled' or 'Draft', unless they are part of the process you wish to analyze.
Permissions: The user account running the report must have read access to all relevant modules, including Credit, Collections, Disputes, and Cash Application, to ensure a complete dataset is extracted.

a Sample Query config

/*
 This is a configuration model for a HighRadius custom report. 
 It is not an executable SQL script but a blueprint for building the report in the UI.
 The report should be configured to UNION the following data blocks to create a single event log.
*/

// Report Name: ProcessMind_Credit_Collections_Log
// Report Output Format: CSV

// === BLOCK 1: Credit Limit Requested ===
{
  "ActivityName": "Credit Limit Requested",
  "Source Object": "CreditRequests",
  "Join Condition": "CreditRequests.CustomerId = Invoices.CustomerId",
  "Columns": {
    "InvoiceNumber": null, // May not be available at this stage
    "ActivityName": "Credit Limit Requested",
    "EventTime": "CreditRequests.RequestTimestamp",
    "CollectorName": "CreditRequests.CreditAnalystName",
    "CustomerId": "CreditRequests.CustomerId",
    "InvoiceAmount": null,
    "PaymentTerms": null,
    "DueDate": null,
    "PaymentStatus": null,
    "DisputeReason": null
  }
}

// === BLOCK 2: Credit Limit Approved ===
{
  "ActivityName": "Credit Limit Approved",
  "Source Object": "CreditRequests",
  "Join Condition": "CreditRequests.CustomerId = Invoices.CustomerId",
  "Columns": {
    "InvoiceNumber": null, // May not be available at this stage
    "ActivityName": "Credit Limit Approved",
    "EventTime": "CreditRequests.ApprovalTimestamp",
    "CollectorName": "CreditRequests.CreditAnalystName",
    "CustomerId": "CreditRequests.CustomerId",
    "InvoiceAmount": null,
    "PaymentTerms": null,
    "DueDate": null,
    "PaymentStatus": null,
    "DisputeReason": null
  }
}

// === BLOCK 3: Invoice Generated ===
{
  "ActivityName": "Invoice Generated",
  "Source Object": "Invoices",
  "Columns": {
    "InvoiceNumber": "Invoices.InvoiceNumber",
    "ActivityName": "Invoice Generated",
    "EventTime": "Invoices.CreationTimestamp",
    "CollectorName": null,
    "CustomerId": "Invoices.CustomerId",
    "InvoiceAmount": "Invoices.InvoiceAmount",
    "PaymentTerms": "Invoices.PaymentTerms",
    "DueDate": "Invoices.DueDate",
    "PaymentStatus": "Invoices.PaymentStatus",
    "DisputeReason": null
  }
}

// === BLOCK 4: Invoice Sent to Customer ===
{
  "ActivityName": "Invoice Sent to Customer",
  "Source Object": "CustomerCommunications",
  "Filter": "CustomerCommunications.Type = 'Invoice Delivery'",
  "Columns": {
    "InvoiceNumber": "CustomerCommunications.InvoiceNumber",
    "ActivityName": "Invoice Sent to Customer",
    "EventTime": "CustomerCommunications.SentTimestamp",
    "CollectorName": null,
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 5: Payment Due Date Passed ===
{
  "ActivityName": "Payment Due Date Passed",
  "Source Object": "Invoices",
  "Filter": "Invoices.DueDate < CURRENT_DATE AND Invoices.PaymentStatus = 'Open'",
  "Columns": {
    "InvoiceNumber": "Invoices.InvoiceNumber",
    "ActivityName": "Payment Due Date Passed",
    "EventTime": "Invoices.DueDate",
    "CollectorName": "Invoices.AssignedCollector",
    "CustomerId": "Invoices.CustomerId",
    "InvoiceAmount": "Invoices.InvoiceAmount",
    "PaymentTerms": "Invoices.PaymentTerms",
    "DueDate": "Invoices.DueDate",
    "PaymentStatus": "Invoices.PaymentStatus",
    "DisputeReason": null
  }
}

// === BLOCK 6: Overdue Reminder Sent ===
{
  "ActivityName": "Overdue Reminder Sent",
  "Source Object": "DunningHistory",
  "Filter": "DunningHistory.Action = 'Reminder'",
  "Columns": {
    "InvoiceNumber": "DunningHistory.InvoiceNumber",
    "ActivityName": "Overdue Reminder Sent",
    "EventTime": "DunningHistory.ExecutionTimestamp",
    "CollectorName": null, // Often automated
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 7: Dunning Procedure Initiated ===
{
  "ActivityName": "Dunning Procedure Initiated",
  "Source Object": "DunningHistory",
  "Filter": "DunningHistory.Action = 'Dunning Level 1'",
  "Columns": {
    "InvoiceNumber": "DunningHistory.InvoiceNumber",
    "ActivityName": "Dunning Procedure Initiated",
    "EventTime": "DunningHistory.ExecutionTimestamp",
    "CollectorName": null, // Often automated
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 8: Collection Call Logged ===
{
  "ActivityName": "Collection Call Logged",
  "Source Object": "CollectorActivityLog",
  "Filter": "CollectorActivityLog.Type = 'Call'",
  "Columns": {
    "InvoiceNumber": "CollectorActivityLog.InvoiceNumber",
    "ActivityName": "Collection Call Logged",
    "EventTime": "CollectorActivityLog.ActivityTimestamp",
    "CollectorName": "CollectorActivityLog.CollectorName",
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 9: Promise to Pay Created ===
{
  "ActivityName": "Promise to Pay Created",
  "Source Object": "PromiseToPay",
  "Columns": {
    "InvoiceNumber": "PromiseToPay.InvoiceNumber",
    "ActivityName": "Promise to Pay Created",
    "EventTime": "PromiseToPay.CreationTimestamp",
    "CollectorName": "PromiseToPay.CreatedByCollector",
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 10: Dispute Registered ===
{
  "ActivityName": "Dispute Registered",
  "Source Object": "DisputeCase",
  "Columns": {
    "InvoiceNumber": "DisputeCase.InvoiceNumber",
    "ActivityName": "Dispute Registered",
    "EventTime": "DisputeCase.CreationTimestamp",
    "CollectorName": "DisputeCase.AssignedAnalyst",
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "Disputed",
    "DisputeReason": "DisputeCase.ReasonCode"
  }
}

// === BLOCK 11: Dispute Resolved ===
{
  "ActivityName": "Dispute Resolved",
  "Source Object": "DisputeCase",
  "Filter": "DisputeCase.Status = 'Closed' OR DisputeCase.Status = 'Resolved'",
  "Columns": {
    "InvoiceNumber": "DisputeCase.InvoiceNumber",
    "ActivityName": "Dispute Resolved",
    "EventTime": "DisputeCase.ResolutionTimestamp",
    "CollectorName": "DisputeCase.AssignedAnalyst",
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": "DisputeCase.ReasonCode"
  }
}

// === BLOCK 12: Payment Received ===
{
  "ActivityName": "Payment Received",
  "Source Object": "CashApplication.Payments",
  "Columns": {
    "InvoiceNumber": null, // Often matched later
    "ActivityName": "Payment Received",
    "EventTime": "CashApplication.Payments.PaymentDate",
    "CollectorName": null,
    "CustomerId": "CashApplication.Payments.CustomerId",
    "InvoiceAmount": null,
    "PaymentTerms": null,
    "DueDate": null,
    "PaymentStatus": null,
    "DisputeReason": null
  }
}

// === BLOCK 13: Payment Posted ===
{
  "ActivityName": "Payment Posted",
  "Source Object": "CashApplication.AppliedPayments",
  "Columns": {
    "InvoiceNumber": "CashApplication.AppliedPayments.InvoiceNumber",
    "ActivityName": "Payment Posted",
    "EventTime": "CashApplication.AppliedPayments.ApplicationTimestamp",
    "CollectorName": null,
    "CustomerId": "[From joined Invoice]",
    "InvoiceAmount": "[From joined Invoice]",
    "PaymentTerms": "[From joined Invoice]",
    "DueDate": "[From joined Invoice]",
    "PaymentStatus": "[From joined Invoice]",
    "DisputeReason": null
  }
}

// === BLOCK 14: Invoice Settled ===
{
  "ActivityName": "Invoice Settled",
  "Source Object": "Invoices",
  "Filter": "Invoices.Status = 'Closed' AND Invoices.ClosureReason = 'Paid'",
  "Columns": {
    "InvoiceNumber": "Invoices.InvoiceNumber",
    "ActivityName": "Invoice Settled",
    "EventTime": "Invoices.ClosureTimestamp",
    "CollectorName": null,
    "CustomerId": "Invoices.CustomerId",
    "InvoiceAmount": "Invoices.InvoiceAmount",
    "PaymentTerms": "Invoices.PaymentTerms",
    "DueDate": "Invoices.DueDate",
    "PaymentStatus": "Paid",
    "DisputeReason": null
  }
}

// === BLOCK 15: Invoice Written Off ===
{
  "ActivityName": "Invoice Written Off",
  "Source Object": "Invoices",
  "Filter": "Invoices.Status = 'Closed' AND Invoices.ClosureReason = 'Write-Off'",
  "Columns": {
    "InvoiceNumber": "Invoices.InvoiceNumber",
    "ActivityName": "Invoice Written Off",
    "EventTime": "Invoices.ClosureTimestamp",
    "CollectorName": "Invoices.AssignedCollector",
    "CustomerId": "Invoices.CustomerId",
    "InvoiceAmount": "Invoices.InvoiceAmount",
    "PaymentTerms": "Invoices.PaymentTerms",
    "DueDate": "Invoices.DueDate",
    "PaymentStatus": "Written Off",
    "DisputeReason": null
  }
}

Steps

Prerequisites: Ensure you have Python 3.6+ installed along with the pandas and requests libraries. You can install them using pip: pip install pandas requests. You must also obtain API credentials (Client ID and Client Secret) from your HighRadius administrator with read access to the necessary data objects like invoices, collections, disputes, and payments.
Script Initialization: Create a new Python script file, for example, extract_hr_data.py. Begin by importing the necessary libraries (requests, pandas, datetime) and defining placeholder constants for your HighRadius API base URL, client credentials, and the desired date range for the extraction.
Implement Authentication: Write a function to handle authentication. This function will take your Client ID and Secret, make a POST request to the HighRadius authentication endpoint (e.g., /auth/v1/token), and retrieve a bearer token. This token will be used in the header of all subsequent data requests.
Fetch Primary Invoice Data: Develop a function to query the main invoice endpoint (e.g., /invoices/v1/search). This function should handle pagination to ensure all records within your specified date range are retrieved. It should iteratively call the API, collecting invoice data until no more pages are available. Store this primary invoice data in a list of dictionaries.
Fetch Related Object Data: For each core data entity like Disputes, Collection Notes, and Payments, create separate data retrieval functions. These functions will query their respective endpoints (e.g., /disputes/v1/search, /collections/v1/notes, /cashapp/v1/payments) and should be designed to fetch all relevant data for the specified time period efficiently. It is often best to fetch these datasets in bulk rather than querying one invoice at a time.
Structure the Event Log: Initialize an empty list that will hold all your event log rows. The script will iterate through the fetched data and transform each relevant action or status change into a standardized dictionary representing a single event row. Each dictionary should contain keys for InvoiceNumber, ActivityName, EventTime, and all other required attributes.
Generate Invoice Lifecycle Events: Iterate through your primary list of invoices. For each invoice, create events for 'Invoice Generated', 'Invoice Sent to Customer', 'Invoice Settled', and 'Invoice Written Off' based on its creation date, correspondence logs, close date, and status fields. Store these as event dictionaries.
Calculate 'Payment Due Date Passed': Within the same invoice loop, add logic to create a 'Payment Due Date Passed' event. This is a calculated event. The logic should check if the invoice's due date has passed, the invoice is not yet paid, and a 'Payment Due Date Passed' event has not already been generated for it. The EventTime for this activity should be the due date itself.
Generate Collections & Dispute Events: Process the data fetched from the collections and disputes endpoints. For each note, promise to pay, dunning action, or dispute record, create corresponding event log rows ('Overdue Reminder Sent', 'Collection Call Logged', 'Promise to Pay Created', 'Dispute Registered', 'Dispute Resolved'). Map the relevant details like CollectorName and DisputeReason to the event record.
Generate Payment Events: Process the payment data from the cash application module. Create 'Payment Received' events based on the payment creation or bank statement date, and 'Payment Posted' events based on the date the payment was successfully applied to the invoice.
Consolidate and Format Data: After processing all data sources and generating events, convert the list of event dictionaries into a pandas DataFrame. This allows for easy sorting and final data type conversions. Ensure the EventTime column is in a consistent timestamp format (YYYY-MM-DD HH:MI:SS).
Export to CSV: Use the pandas to_csv function to export the final DataFrame to a CSV file. Name the file clearly, for example, highradius_event_log.csv. Set the parameter index=False to avoid writing the DataFrame index as a column. This file is now ready for upload to ProcessMind.

Configuration

API Credentials: A dedicated API user with a Client ID and Client Secret is required. The user must have read permissions for all relevant API endpoints, including invoices, customers, collections activities, disputes, and cash application.
Date Range: The Python script includes START_DATE and END_DATE variables. It is critical to set a specific and reasonable date range, such as 3-6 months, to limit the data volume and prevent excessively long script execution times. Filter based on an indexed date field like invoice creation date or modification date.
Endpoint URLs: The specific API endpoint paths (e.g., /invoices/v1/search) are placeholders. You must confirm the correct endpoint URLs from your organization's HighRadius API documentation.
Pagination Parameters: The script must correctly handle the API's pagination mechanism. This typically involves using limit and offset parameters or a cursor-based approach. A page size of 100-500 is generally a good starting point.
Environment: The script should be run in a stable environment with sufficient memory to handle the dataframes, especially for large extracts. Running it on a server is preferable to a local machine for production-scale extractions.
Custom Fields: If your process relies on custom fields within HighRadius, the script will need to be modified to query for and include these fields in the output.

a Sample Query python

import requests
import pandas as pd
from datetime import datetime, time

class=class="hl-string">"hl-comment"># --- Configuration Settings ---
HIGH RADIUS_BASE_URL = class="hl-string">"https://[your-highradius-instance].highradius.com/api"
CLIENT_ID = class="hl-string">"[Your_Client_ID]"
CLIENT_SECRET = class="hl-string">"[Your_Client_Secret]"
START_DATE = class="hl-string">"2023-01-01"
END_DATE = class="hl-string">"2023-06-30"

class=class="hl-string">"hl-comment"># --- Helper Functions ---
def get_auth_token():
    class="hl-string">"""Authenticates with HighRadius and returns a bearer token."""
    auth_url = fclass="hl-string">"{HIGH RADIUS_BASE_URL}/auth/v1/token"
    payload = {
        class="hl-string">'grant_type': class="hl-string">'client_credentials',
        class="hl-string">'client_id': CLIENT_ID,
        class="hl-string">'client_secret': CLIENT_SECRET
    }
    response = requests.post(auth_url, data=payload)
    response.raise_for_status() class=class="hl-string">"hl-comment"># Raises an exception for bad status codes
    return response.json()[class="hl-string">'access_token']

def fetch_paginated_data(endpoint, params, headers):
    class="hl-string">"""Fetches all pages of data from a given HighRadius endpoint."""
    all_data = []
    page = 0
    limit = 200 class=class="hl-string">"hl-comment"># Records per page
    while True:
        params[class="hl-string">'offset'] = page * limit
        params[class="hl-string">'limit'] = limit
        response = requests.get(fclass="hl-string">"{HIGH RADIUS_BASE_URL}{endpoint}", headers=headers, params=params)
        response.raise_for_status()
        data = response.json()
        records = data.get(class="hl-string">'data', []) class=class="hl-string">"hl-comment"># Adjust based on actual API response structure
        if not records:
            break
        all_data.extend(records)
        page += 1
    return all_data

class=class="hl-string">"hl-comment"># --- Main Extraction Logic ---
def main():
    class="hl-string">"""Main function to extract, transform, and save the event log."""
    print(class="hl-string">"Starting HighRadius data extraction...")
    auth_token = get_auth_token()
    headers = {class="hl-string">'Authorization': fclass="hl-string">'Bearer {auth_token}'}
    events = []

    class=class="hl-string">"hl-comment"># 1. Fetch all relevant invoices in the date range
    print(class="hl-string">"Fetching invoice data...")
    invoice_params = {class="hl-string">'creationDate_gte': START_DATE, class="hl-string">'creationDate_lte': END_DATE}
    invoices = fetch_paginated_data(class="hl-string">"/invoices/v1/search", invoice_params, headers)

    class=class="hl-string">"hl-comment"># Fetch related data in bulk to reduce API calls
    invoice_ids = [inv[class="hl-string">'invoiceNumber'] for inv in invoices]
    print(fclass="hl-string">"Fetching related data for {len(invoice_ids)} invoices...")

    notes = fetch_paginated_data(class="hl-string">"/collections/v1/notes", {class="hl-string">'invoiceNumber_in': class="hl-string">','.join(invoice_ids)}, headers)
    disputes = fetch_paginated_data(class="hl-string">"/disputes/v1/search", {class="hl-string">'invoiceNumber_in': class="hl-string">','.join(invoice_ids)}, headers)
    payments = fetch_paginated_data(class="hl-string">"/cashapp/v1/applications", {class="hl-string">'invoiceNumber_in': class="hl-string">','.join(invoice_ids)}, headers)
    credit_requests = fetch_paginated_data(class="hl-string">"/credit/v1/requests", {class="hl-string">'requestDate_gte': START_DATE, class="hl-string">'requestDate_lte': END_DATE}, headers)

    class=class="hl-string">"hl-comment"># Create dictionaries for quick lookups
    notes_by_invoice = {k: [n for n in notes if n[class="hl-string">'invoiceNumber'] == k] for k in invoice_ids}
    disputes_by_invoice = {k: [d for d in disputes if d[class="hl-string">'invoiceNumber'] == k] for k in invoice_ids}
    payments_by_invoice = {k: [p for p in payments if p[class="hl-string">'invoiceNumber'] == k] for k in invoice_ids}
    
    class=class="hl-string">"hl-comment"># Process each invoice to create events
    print(class="hl-string">"Transforming data into event log...")
    for invoice in invoices:
        common_attrs = {
            class="hl-string">'InvoiceNumber': invoice.get(class="hl-string">'invoiceNumber'),
            class="hl-string">'CustomerId': invoice.get(class="hl-string">'customer', {}).get(class="hl-string">'id'),
            class="hl-string">'InvoiceAmount': invoice.get(class="hl-string">'invoiceAmount'),
            class="hl-string">'PaymentTerms': invoice.get(class="hl-string">'paymentTerms'),
            class="hl-string">'DueDate': invoice.get(class="hl-string">'dueDate'),
            class="hl-string">'PaymentStatus': invoice.get(class="hl-string">'paymentStatus'),
            class="hl-string">'CollectorName': invoice.get(class="hl-string">'collector', {}).get(class="hl-string">'name'),
            class="hl-string">'DisputeReason': None
        }

        class=class="hl-string">"hl-comment"># Invoice Generated
        events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Invoice Generated', class="hl-string">'EventTime': invoice.get(class="hl-string">'creationDate')})
        
        class=class="hl-string">"hl-comment"># Invoice Sent to Customer (example from correspondence log)
        if invoice.get(class="hl-string">'sentDate'):
            events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Invoice Sent to Customer', class="hl-string">'EventTime': invoice.get(class="hl-string">'sentDate')})

        class=class="hl-string">"hl-comment"># Payment Due Date Passed (calculated)
        due_date_obj = datetime.strptime(invoice.get(class="hl-string">'dueDate'), class="hl-string">'%Y-%m-%dT%H:%M:%S.%fZ').date()
        if due_date_obj < datetime.today().date() and invoice.get(class="hl-string">'paymentStatus') not in [class="hl-string">'PAID', class="hl-string">'CLOSED']:
            event_time_at_due_date = datetime.combine(due_date_obj, time(23, 59, 59)).isoformat()
            events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Due Date Passed', class="hl-string">'EventTime': event_time_at_due_date})

        class=class="hl-string">"hl-comment"># Invoice Settled / Written Off
        if invoice.get(class="hl-string">'closeDate'):
            if invoice.get(class="hl-string">'paymentStatus') == class="hl-string">'PAID':
                events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Invoice Settled', class="hl-string">'EventTime': invoice.get(class="hl-string">'closeDate')})
            elif invoice.get(class="hl-string">'statusReason') == class="hl-string">'WRITTEN_OFF':
                events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Invoice Written Off', class="hl-string">'EventTime': invoice.get(class="hl-string">'closeDate')})

        class=class="hl-string">"hl-comment"># Process related notes for this invoice
        for note in notes_by_invoice.get(invoice[class="hl-string">'invoiceNumber'], []):
            activity_map = {
                class="hl-string">'REMINDER_SENT': class="hl-string">'Overdue Reminder Sent',
                class="hl-string">'DUNNING_STARTED': class="hl-string">'Dunning Procedure Initiated',
                class="hl-string">'COLLECTION_CALL': class="hl-string">'Collection Call Logged',
                class="hl-string">'PROMISE_TO_PAY': class="hl-string">'Promise to Pay Created'
            }
            activity_name = activity_map.get(note.get(class="hl-string">'noteType'))
            if activity_name:
                events.append({**common_attrs, class="hl-string">'ActivityName': activity_name, class="hl-string">'EventTime': note.get(class="hl-string">'creationDate'), class="hl-string">'CollectorName': note.get(class="hl-string">'createdBy')})

        class=class="hl-string">"hl-comment"># Process related disputes for this invoice
        for dispute in disputes_by_invoice.get(invoice[class="hl-string">'invoiceNumber'], []):
            events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Dispute Registered', class="hl-string">'EventTime': dispute.get(class="hl-string">'creationDate'), class="hl-string">'DisputeReason': dispute.get(class="hl-string">'reasonCode')})
            if dispute.get(class="hl-string">'resolutionDate'):
                events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Dispute Resolved', class="hl-string">'EventTime': dispute.get(class="hl-string">'resolutionDate'), class="hl-string">'DisputeReason': dispute.get(class="hl-string">'reasonCode')})
        
        class=class="hl-string">"hl-comment"># Process related payments for this invoice
        for payment in payments_by_invoice.get(invoice[class="hl-string">'invoiceNumber'], []):
            if payment.get(class="hl-string">'paymentReceivedDate'):
                events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Received', class="hl-string">'EventTime': payment.get(class="hl-string">'paymentReceivedDate')})
            if payment.get(class="hl-string">'applicationDate'):
                events.append({**common_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Posted', class="hl-string">'EventTime': payment.get(class="hl-string">'applicationDate')})

    class=class="hl-string">"hl-comment"># Process credit requests (linked by customer ID)
    for request in credit_requests:
        class=class="hl-string">"hl-comment"># Note: Linking to a specific invoice is often not possible. Here we create a case-level event.
        class=class="hl-string">"hl-comment"># A more advanced logic could try to link based on customer and time proximity to an invoice.
        credit_attrs = {**common_attrs, class="hl-string">'InvoiceNumber': fclass="hl-string">"CREDIT-{request.get('customerId')}", class="hl-string">'CustomerId': request.get(class="hl-string">'customerId')}
        events.append({**credit_attrs, class="hl-string">'ActivityName': class="hl-string">'Credit Limit Requested', class="hl-string">'EventTime': request.get(class="hl-string">'requestDate')})
        if request.get(class="hl-string">'status') == class="hl-string">'APPROVED' and request.get(class="hl-string">'approvalDate'):
            events.append({**credit_attrs, class="hl-string">'ActivityName': class="hl-string">'Credit Limit Approved', class="hl-string">'EventTime': request.get(class="hl-string">'approvalDate')})

    class=class="hl-string">"hl-comment"># Finalize DataFrame
    if not events:
        print(class="hl-string">"No events found for the specified criteria.")
        return

    df = pd.DataFrame(events)
    df[class="hl-string">'EventTime'] = pd.to_datetime(df[class="hl-string">'EventTime'], errors=class="hl-string">'coerce')
    df.dropna(subset=[class="hl-string">'InvoiceNumber', class="hl-string">'ActivityName', class="hl-string">'EventTime'], inplace=True)
    df.sort_values(by=[class="hl-string">'InvoiceNumber', class="hl-string">'EventTime'], inplace=True)
    
    class=class="hl-string">"hl-comment"># Save to CSV
    output_file = class="hl-string">'highradius_event_log.csv'
    df.to_csv(output_file, index=False, date_format=class="hl-string">'%Y-%m-%d %H:%M:%S')
    print(fclass="hl-string">"Extraction complete. Event log saved to {output_file}")

if __name__ == class="hl-string">'__main__':
    main()

Your Credit Management & Collections Data Template

Your Credit Management & Collections Data Template

Credit Management & Collections Attributes

Credit Management & Collections Activities

Extraction Guides

HighRadius Reporting and Analytics Module Export

Steps

Configuration

a Sample Query config

Python Script Extraction via HighRadius REST APIs

Steps

Configuration

a Sample Query python

Ready to Get Started?

Start Optimizing Your Credit Management & Collections

Your Credit Management & Collections Data Template

Your Credit Management & Collections Data Template

Credit Management & Collections Attributes

Credit Management & Collections Activities

Extraction Guides

HighRadius Reporting and Analytics Module Export

Steps

Configuration

a Sample Query config

Python Script Extraction via HighRadius REST APIs

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Start Optimizing Your Credit Management & Collections