Frequently Asked Questions

The payment request transaction can be excluded from intercept processing even when intercept is to be processed for the payment request. When for a record on the Disbursement Request (DISRQ) with values of Transaction Code, Transaction Department, Transaction ID, Department, Object, Appropriation, TIN, and TIN Type matches any combination of Transaction Code, Transaction Department, Transaction ID, Department, Object, Appropriation, TIN, TIN Type, Vendor/Customer, and BSA on the Intercept Disbursement Exception (INTDBEX) table, then the DISRQ record is not eligible for intercept. DISRQ records that meet one of the above exclusion criterion will not be considered for the subsequent intercept logic steps.

A single check can be generated for a specific payment request. The vendor line of the payment request transaction has a Single Payment flag. When checked on the vendor line of a Payment Request or Accounting Based Spending transaction, either manually or inferred from the Vendor/Customer table, all accounting lines under that vendor line lead to a single payment instrument.

The Disbursement Parameter table has an EFT to Hard Copy flag. When selected, the Automated Disbursement process will generate a check or warrants for Disbursement Requests selected as EFT disbursements.

The Remittance Advices will be generated for EFT payments to those Vendors for whom the Remittance Advice Required flag on the Vendor Customer or Vendor Address tables is set to Yes (checked). The Remittance Advices are generated by the Disbursement Printing job. Please refer to the "Disbursement Printing Process” topic in this user guide for additional details on how to generate a Remittance Advice for EFT disbursements.