PVI Documentation > Reference Manual Menu
There are 3 data files which are produced each morning by PaymentVision, recapping the previous day’s transactions. The “Import Daily Files” program reads those files from the “import” folder on your TCS host, converts the data into report data, and writes reports out to another folder for use by your accounting staff.
This program does not retrieve the daily data files from PaymentVision. Rather, retrieving the files, decrypting them if necessary, and placing them into the import folder is a manual process. The “Import Daily Files” program takes over from that point, reading the files, producing the output report files, and moving the PaymentVision files to an archive folder.
The data files which come from PaymentVision have a naming convention which looks like this:
AAAAAAAAAAAAAAA_BBBBBBB_YYYYMMDD.txt
which can be parsed as follows:
“AAAAAAAAAAAAAAA” is the name of the type of file. It will always be one of these:
- “PaymentVisionTransactionCCPosting” – File contains yesterday’s credit card transactions.
- “TransactionPosting” – File contains yesterday’s ACH transactions.
- “ReturnCorrection” – File contains previous days’ returned (i.e for NSF) ACH transactions.
“BBBBBBB” is the primary PaymentVision merchant account code.
“YYYYMMDD” is the date that the transaction file was created.
The “Import Daily Files” function is a bit outdated, having been mostly replaced by the ability to manually create transaction batches through the PaymentVision Admin Web Portal and to import those batches into TCS through the PayAPI data communications interface. Prior to the introduction of batch import functionality, the reports produced by this function were used as source documents for posting transactions to TCS. The great majority of our interface users have replaced this data flow by importing batches. However, for some of our TCS users, the “ReturnCorrection” file is the main conduit by which those agencies are notified of NSFs, so “Import Daily Files” is still an important function.
There are 2 front-ends, PV.IMPORT.FILES.MANUAL which is called by the menu, and PV.IMPORT.FILES.AUTO which can be called by the TCS dayend or a background processor without a user interface.
These reports are in external report format but, by default, they will be directed to the report folder as files. If hard-copy printed reports are desired by a TCS user, we can re-direct the output to the printer as a minor program modification.
File name: PVConfirmedPayments_YYYYMMDD where the date is from the PaymentVision import file name.
A report of all payments confirmed by today’s imported files (ACH and Credit Card Posting Files), sorted by TCS Logon, PaymentVision’s EventDate, and then by Payer name.
PaymentVision – Confirmed Payments – YYYYMMDD
28
AUG 2009 11:14:43
Logon
Date Payer
Dnum Type Amount Fee
XXXXXXXXXXXX
MM/DD/YY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 99999999 XXX 999999.99 9999.99
File name: PVPaymentExceptions_YYYYMMDD where the date is from the PaymentVision import file name.
A report of all payment exceptions noted. There are 3 kinds of exceptions:
- Transactions pending in the PV-PYMT file, but not confirmed on this import. These are the first section of the report, sorted by TCS Logon, PaymentVision’s EventDate, and then by Payer name.
- Transactions confirmed by PaymentVision, but we don’t have them in the PV-PYMT file. These are the second section of the report, sorted by EventDate and Payer Name
- Transactions present in both places (PaymentVision file and PV-PYMT file), but a data discrepancy was noted.
PaymentVision – Payment Exceptions – YYYYMMDD
28
AUG 2009 11:14:43
Transactions
Still Pending In TCS:
Logon
Date Payer
Dnum Type Amount Fee Tracking Nbr
XXXXXXXXXXXX
MM/DD/YY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 99999999 XXX 999999.99 9999.99
XXXXXXXXXXXXXXX
Confirmations
from PV, not in TCS:
Date Payer
Type Amount Fee Tracking Nbr
Customer Reference
MM/DD/YY
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXX 999999.99 9999.99 XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Confirmation
matches, but data discrepancy:
Logon
Date Payer
Dnum Type Amount Fee PV Data
Discrepancy
XXXXXXXXXXXX
MM/DD/YY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 99999999 XXX 999999.99 9999.99
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
File name: PVACHReturns_YYYYMMDD where the date is from the PaymentVision import file name.
A report of all returned ACH transactions in today’s imported ACH Return files, sorted by TCS Logon, PaymentVision’s EventDate, and then by payer name.
PaymentVision – Returned ACH Payments – YYYYMMDD
28
AUG 2009 11:14:43
Logon
Date Payer
Dnum Amount Return
Reason
XXXXXXXXXXXX
MM/DD/YY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 99999999 999999.99 R99
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
If a NSF is noted for an account on an ACH future payment plan, the TCS database is updated as follows:
- The future payment plan is cancelled.
- Notes are written detailing the cancelled future payments.
- The status code of the account may be changed, depending upon configuration.
- The account is added back to the tickler file with a next work date of tomorrow.
Copyright 2012, Cubs Consulting, Inc.