A mailing list is created including destination addresses for mailpieces to be submitted to a carrier service for delivery. A unique mailpiece identifier associated with mailpieces on the mailing list is generated by the carrier or other trusted third party. The unique mailpiece identifier is printed on the mailpiece with which it is associated. The mailpieces with the printed unique identifier are submitted to the carrier service. The carrier service obtains the printed unique identifier from the mailpiece. The obtained unique identifier from each said mailpiece is utilized to verify that data associated with the mailpiece has been processed by the carrier or trusted third party. When the unique number has been obtained from the mailpieces, the carrier service, if desired, may note this fact in the carrier records to prevent reuse of the unique identifier. The carrier service as part of issuing the unique identification may: charge the mailer's account of other fund depository for the carrier service charges associated with the mailpiece; and/or, assign a destination delivery code; and/or, provide address hygiene for the mailpiece; and/or change of address processing. When the unique identifier is obtained from the mailpiece, a delivery point destination code may be printed on the mailpiece, based on the corrected address. As an alternative, the destination delivery code may be provided to the mailer with the unique mailpiece identifier to be printed on the mailpiece by the mailer. Various cryptographic techniques may be employed to authenticate the mailer and the carrier service and to protect the transmitted information between the parties. The payment for the carrier services can be implemented prior in time to the entry of the mailpieces to the carrier service mailstream. Unauthorized mailpieces may be out sorted early in the carrier service processing procedure.

 
Web www.patentalert.com

> Cross-system update method and system

~ 00373