This section only discusses running INV620. Please see the Performing Shipping Maintenance for more information on INV200.The Shipping Maintenance (INV200) screen varies from INV620 in that INV200 is a screen within Personify360 where you can manually generate Pick Lists and packing slips; print labels, invoices, and bad addresses; or mark products as back order. The INV620 process, on the other hand, is a batch job that automatically performs the tasks you manually do from INV200 depending on which parameters you set for INV620.
This section only discusses running INV620. Please see the Performing Shipping Maintenance for more information on INV200.
INV620 checks to see if an Inventoried product is available for shipment. If so, depending on your INV620 parameters, the process generates the product’s packing slip, finalizes shipping, and generates an invoice.
When you create an Inventoried product deferred receipt to be paid by credit card, you request authorization for the credit card payment. Before INV620 can generate a packing slip and finalize shipping, the process must confirm that the credit card authorization for the Inventoried product receipt did not expire. Credit card authorizations are only valid for a pre-determined amount of days set by the credit card company.
By default, Personify authorizes credit cards for eight days; however, if your credit card processors authorize credit cards for a different amount of time, you must configure your Personify application on the Configure and Verify Interfaces (APP014) screen to match your credit card processors. For more information, please see Personify Universal Payment Handler Interface.
In the case that the credit card authorization expires before INV620 confirms the product for shipment, the process issues a new authorization before generating the packing slips. If the authorization does not go through (i.e., the credit card is declined), then, on the basis of the STOP_SHIPPING_ON_REJECT parameter you set, the system decides whether to ship the product or put it on HOLD. The INV620 report groups these declined credit card orders on HOLD in a separate report output. For more information on declined credit cards, please refer to Credit Cards Declined During Shipping.
Some credit cards may be declined when you run INV620. The Pre-Auth Error report lists such transactions. The cause for decline could be because the authorization expired or the credit card itself expired. In these cases, the status of the deferred receipt and credit card payment depends on the value you set for the STOP_SHIPPING_ON_REJECT parameter on the System Parameter Maintenance (APP008) screen.
For more information regarding declined credit cards and setting the ORD STOP_SHIPPING_ON_REJECT application parameter, please refer to Credit Cards Declined During Shipping.
The INV620 process differs from the CCP610 process in that scheduling the process is not necessarily beneficial to your association. How often you run INV620 depends on your business process. For example, since shipping products is a manual process, you do not want to process shipping invoices until you confirm the actual shipment occurred.
The steps to schedule the INV620 process, however, are the same as scheduling the CCP610 process. To schedule INV620, please refer to Scheduling the CCP610 Process, but make sure to enter “INV620” instead of “CCP610” on the Job Submission search screen.