Audit

Audit events in payment investigations are critical for regulatory compliance, operational oversight, and issue resolution. In Pega Smart Investigate™ for Payments (SIP), audit trails captured key actions and decisions but required custom configuration to meet specific regulatory requirements.

SIAA enhances audit features with a configurable framework that automatically captures a wide range of events. The system distinguishes between system-generated events and user actions to provide clear visibility into the investigation life cycle. This framework supports detailed reporting and alignment with regulatory standards, which reduces the need for custom development.

You use the following process to configure audit events:

1. Identify regulatory requirements for your regions of operation.
2. Document internal audit policies that must be enforced.
3. Determine which legacy custom audit configurations need to be recreated.
4. Configure audit settings as needed to capture:
   • Message processing events (receipt, parsing, and routing).
   • Case Life Cycle transitions and status changes.
   • User actions and decisions with appropriate detail.
   • System-automated actions and their outcomes.
5. Set up audit reporting and monitoring to provide:
   • Regular compliance reports for oversight teams.
   • Real-time alerts for critical audit events.
   • Searchable audit history for investigations and inquiries.

Field-level auditing tracks changes to specific data elements in an investigation Case. In SIP, this feature was limited to key fields and required custom configuration.

Smart Investigate Agentic Automation introduces enhanced field-level auditing that tracks changes to any Case property with minimal configuration. This feature is valuable for sensitive data elements such as payment amounts, account numbers, and resolution decisions. The system maintains a complete history of field changes, including previous value, new value, timestamp, and operator, which reduces the need for custom development.

You use the following process to configure field-level auditing:

1. Identify critical fields that require detailed audit tracking:
   • Financial data (amounts, account numbers, transaction references).
   • Case decisions and rationales.
   • Customer communications and agreements.
   • Regulatory reporting information.
2. Enable auditing for the identified critical fields.
3. Set appropriate audit retention periods for different field types.
4. Configure field-level security to complement audit controls.
5. Implement reporting to use field-level audit data:
   • Create reports showing field change history for specific case types.
   • Set up alerts for changes to sensitive fields.
   • Develop audit dashboards for compliance and management teams.
6. Review and test field-level auditing during implementation to confirm that compliance and operational needs are met.