Billing Change
Last updated
Last updated
COPYRIGHT © 2024 NAVIGA
This option allows billing changes to be imported in order to update a subscriber’s renewal delivery method, rate code, auto renew credit card, or auto renew bank draft information. For example, this tool can be useful in cases where a renewal delivery method (such as eBill) is tracked by another system. The import format is user-defined, and must be set up in advance using File Map (“SubTranImprt” usage). See Appendix B for a list of data elements that can be included.
Select Billing Change from the Import menu to display the Billing Change Import screen.
Select Add and complete the following fields.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (transactions imported into Circulation) or edit mode (no transactions imported—the file is simply read and any errors displayed). We recommend running this option in edit mode first to confirm that there will be no errors during the import.
TRAN TYPE
predefined
Enter the transaction type to be exported. Currently, “Billing Change” is the only choice.
SOURCE, SUBSOURCE REASON
setup
If the import is being run in commit mode, enter the source, subsource (if applicable) and reason code for the billing change transaction.
TRAN DATE
date
If the import is being run in commit mode, enter the transaction date for the billing changes. If a transaction date is contained in the file, the file’s transaction date will override this date.
FILE FORMAT
setup
Enter the ID of the subscriber transaction import format that should be used. This must be defined in advance in File Map.
FILE NAME
open (30)
Enter the import file name. This file must be in the /dti/exchange/cm directory. The file name may default from the file format.
Select Continue to do the import. This will create unprocessed billing change transactions for the subscribers in the file. When the import is complete a processing report will be displayed, listing how many records were exported and any errors that occurred.
