UC Davis
Purchasing Card
FAQFormsGlossaryPoliciesContact Us  

Credit Card Payment Lookup Report

The Basics
The Credit Card Payment Lookup (252) in DaFIS Decision Support provides information on payments made with the Purchasing Card.

This query can be run using a variety of criteria, including a date range; the organization/account to which the charges were applied; the name of the cardholder; the department that issued the card; or a specific merchant. For example, you could run this query to find all transactions from a particular cardholder; or you could get a list of all credit card transactions for your entire organization.

The results of your query will include information regarding the name of the cardholder; the last 4 digits of the credit card number; the transaction ID number; the type of document; the merchant's name and location; the account charged; and the transaction date, amount, and tax amount. You may note that some of the amounts will have a "CR" next to them - indicating a credit. This means that the transactions have been moved to a different account using the Feed Payment Distribution (FPD) document in DaFIS TP.

If you want more detail about a transaction, you can click on the Transaction ID number to access the Credit Card Payment Detail (250) report for that particular transaction. Here, you will get additional information about the transaction, including the object code, the date the transaction posted to the ledger, and the reference number of the transaction. This reference number can be used in the Tracking Number field in the DaFIS Document Lookup screen to return an incomplete (I status) FPD document number.

Scheduling the Query
If you wish to automatically receive regular updates on Purchasing Card activity, you may want to schedule the Credit Card Payment Lookup (252). When you schedule a query, you will receive an e-mail at regular intervals with transaction activity. Click the Schedule This Query button on the right side of the query input screen and complete the required fields, including e-mail address and desired notification frequency.