RB D16 - Local transaction date not in MMDD format or invalid

The batch Local Transaction Date is a four-digit field. The date format is MMDD and must be numeric. The Shipping Date is recognized as the transaction date for CPS/Direct Marketing merchants. The system validates that the Local Transaction Date field corresponds to the following format:

MM = month entry must be two digits, 01-12.
DD = day entry must be two digits, 01-31.
Leap year = a valid calendar day 0229 for MMDD is acceptable.

Possible Causes	Solutions
A transaction has an incorrect or invalid local transaction date.	Delete the transaction that caused the RB. Offline the corrected transaction and re-transmit. If the Delete feature is not available, delete the batch, offline corrected transactions, and re-transmit.
VT13PA3 w/ the PS2K offline prompts flagged on (792=Y1) has a transaction that was offlined into the terminal. The Original Trans Date was not entered in the format of MMDDYY into the terminal.	Void the transaction that caused the RB and offline the transaction back into the terminal. When the Original Trans Date prompt displays, make sure the merchant uses the MMDDYY format. Check totals and transmit the batch again.
POS-partner - a future shipping date is attached to one of the transactions.	Correct the shipping date to a past or present date and re-transmit.