Implementation Guide for Oracle Billing Insight > Payment Processing >

About Payment Auditing

Oracle Billing Insight Payment audits some Oracle Billing Insight Payment jobs to track a variety of transaction failures. Audits are kept for actions taken through the UI, as well as jobs.

Payment Jobs That Are Audited

The following jobs write to the audit tables:

• pmtCheckSubmit. Writes the following audited information:
  • Payments that failed during submission.
  • Encryption exceptions.
• pmtPaymentReminder. Writes payment reminders that were not sent, including:
  • Regular payment reminders that failed to send, for any reason, such as bad email address.
  • Check payment email that failed to send, for any reason, such as encryption error, bad email address.
  • Credit card payment email failed to send, for any reason, such as encryption error or bad email address.
• pmtCreditCardSubmit. Writes credit card payments that failed to submit, for example, because of encryption errors, invalid credit card information (such as invalid account) or network errors.
• pmtIntegrator (AR). Writes check and credit card payments that were not written to the AR file, such as because of encryption errors or file write errors.
• pmtRecurringPayment Job. Check and credit card payments that failed.
• pmtCheckSubmit and pmtCreditCardSubmit. Submits check and credit card payments.

UI Actions That Are Audited

Lists successful and unsuccessful payments along with a reason code.

The UI actions that trigger an audit entry are:

• Create Recurring Payment
• Update Recurring Payment
• Delete Recurring Payment
• Create Schedule Payment
• Create Instant Payment
• Cancel Future Payment (Credit and Debit Card Payments)
• Update Future Payment (Credit and Debit Card Payments)
• Cancel Future Payment (Check Payment)
• Update Future Payment (Check Payment)
• Create Check Account
• Edit Check Account
• Delete Check Account
• Create Credit Card Account
• Edit Credit Card Account
• Delete Credit Card Account
• Create Debit Card Account
• Edit Debit Card Account
• Delete Debit Card Account

Audit Database

The Oracle Billing Insight database supports auditing.

Columns for Audit

The EDX_PMT_TRANSACTION_HISTORY table has the new columns. The history tables have all the columns that the base table (EDX_PMT_TRANSACTION) has, plus the columns listed in Table 66.

New Tables

The following tables are based on the table name with _history at the end. They have all the columns in the base table, plus the new columns listed in Table 66 to support auditing.

• payment_accounts_history
• payment_bill_summeries_history
• payment_reminder_history
• recurring_payments_history

Audit Table Constants

Table 67 lists the tables that have audit information and the names of the corresponding code tables that explain the numeric codes for audit columns. See the tables in your Oracle Billing Insight database for the code descriptions.

Job Name Entries

User job names are combined with a shortened version of the task name to keep database entries manageable. The name of the job given by the user is combined with a shortened version of the task name as follows:

<job name given by the Admin>-<shorten task name>

Table 68 shows the shortened name for each job.