Announcements
08/01/2011
SuiteLink® Requirement Modification

The Postal Service® is modifying the current CASS™ Cycle N requirement that to qualify for an automation price, mailers must show on the mailpiece the suite number returned by SuiteLink® processing used to determine the correct ZIP +4™ code.

Announcements
02/01/2011
NCOALink® Pricing Changes

Effective April 17, 2011, most of the NCOALink® licensing fees will change.

Announcements
06/30/2010
Licensing Announcement: NCOALink® Release Number 930

The NCOALink® data fulfillment received this week was labeled with the incorrect release number. The correct release number is 930, not 929.

Announcements
05/20/2010
NCOALink® Release Number 925

Regarding NCOALink® release number 925, there will be no additional moves out of ZIP™ codes that begin with ‘00’ and ‘33.’ This release is scheduled to be mailed the week of May 24.

Announcements
03/30/2010
CASS™ Cycle N Partnership in Tomorrow Minutes

The Partnership in Tomorrow Meeting was hosted by the National Customer Support Center in Memphis, TN with attendees and webinar participants from various industry representatives. These minutes are a record of discussions held during the meeting

Announcements
11/06/2009
NCOALink® Data Release #897

The NCOALink® data contained in data release #897 will include fewer records due to the expired records rolling off of the database.

Announcements
10/29/2009
CASS™ and MASS™ Cycle N Deferment Letter

The implementation date for CASS/MASS Cycle N is being deferred to August 1, 2011.

Announcements
05/20/2009
NCOALink® Reporting and Technical Changes Required

The following changes were established during the NCOALink® Developer meetingheld in December 2008.  These requirements should be implemented by all users byOctober 1, 2009.

Announcements
02/16/2009
ACS™ Announcement: OneCode ACS® Fulfillment

Information regarding OneCode ACS data content regarding the Intelligent Mail (IM) barcode

Announcements
04/25/2008
Licensing Announcement: DPV®/DSF2® Header Files

DPV and DSF2 Products currently have a very limited header file called month.dat which only contains the product month.