Release 25.0.0 – Notes – Version 6

The PostalOne! 25.0.0 Release will be deployed November 7, 2010 to introduce software upgrades to the system. Version 6 has been changed from Version 5 previously posted on RIBBS®.  Changes are noted in Appendix A.  
These Release Notes provide the contents of this release and its effect on the following areas.
Chapter 1	Mailers (External)	3
1.1	Full-Service Changes	3
1.1.1	Full-Service ACS™ Billing	3
1.1.1.1	Full-Service	3
1.1.1.2	Non Full-Service	3
1.1.1.3	Invoices	3
1.1.1.4	Delinquent Accounts	3
1.1.1.5	Foreign Addresses	4
1.1.2	Full-Service eDoc Verification and Assessment	4
1.2	Enterprise Administration (eAdmin)	5
1.2.1	Business Service Administrator	5
1.2.1.1	Reaccepting the Online Agreement	5
1.3	Accounts	6
1.3.1	Balance & Fees	6
1.3.2	Manage Permits	6
1.4	Mail & Transport	7
1.4.1	CAPS	7
1.4.2	Electronic Data Exchange	7
1.4.2.1	Mail.dat	7
1.4.2.2	Mail.XML	11
1.4.2.3	Wizard Web Service Decommissioned	13
1.4.3	Postal Wizard	13
1.4.3.1	PS Form 3700 International Mail Postage Statement	13
1.4.3.2	PS Form 3602 Standard Mail Postage Statement	14
1.4.3.3	Domestic Postage Statements	14
1.4.4	Periodicals Authorization	14
1.4.5	Dashboard	15
1.4.5.1	Postage Statements	15
1.4.5.2	Qualification Report	17
1.4.5.3	Reconciliation Report	17
1.4.5.4	Summary ZIP Destination Report	17
1.4.5.5	Periodicals Advertising Percentage Worksheet	17
1.4.5.6	Periodicals Edition Weight Worksheet	18
1.4.5.7	Postage Register	18
1.4.5.8	Original Container Information Report	18
1.4.5.9	Mailing Dates	18
1.5	Track & Report	19
1.5.1	Mailing Reports	19
1.5.1.1	View Transactions Report	19
1.5.1.2	Mailing Summary Report	19
1.5.1.3	Mail Quality Report	19
1.5.1.4	Consolidated Payment Request (CPP Publishers Only)	19
1.5.1.5	Issue Level Postage Statements	20
1.6	Manage Electronic Verification Activity (eVS)	20
1.6.1	Duplicate Manifest Processing	21
1.6.2	Duplicate Package Adjustment	21
1.6.3	Postage Extract	21
1.6.4	eVS Defect Fixes	21
1.7	Manage Electronic Return Activity (PRS)	22
1.7.1	Duplicate Manifest Processing	22
1.7.2	Duplicate Package Adjustment	22
1.7.3	Error Warning Report	22
1.7.4	Postage Extract	22
1.8	eMIR System	23
1.9	Test Environment for Mailers	23
Appendix A – Changes to Version 5	24

Chapter 1	
Mailers (External) 
PostalOne! Release 25.0.0 will be deployed to introduce software upgrades to the system.  The upgrades include, but are not limited to, improvements to MicroStrategy Mail Quality Reports, Mail.dat and Mail.XML enhancements, and assessments for noncompliance with Full-Service requirements.  Critical issues identified from previous releases will be corrected in this release.    
The following items will be included in PostalOne! Release 25.0.0 and are of interest to external users of the PostalOne! system.
1.1	Full-Service Changes
1.1.1	Full-Service ACS™ Billing
PostalOne! release 25.0.0 will provide capabilities to invoice Full-Service mailers who incur charges for ACS.  Details of this process is communicated in the June 2010 version of the Guide to Intelligent Mail for Letters and Flats.
1.1.1.1	Full-Service  
Full-Service (FS) offers the benefit of ACS at no cost on First-Class Mail, Periodicals, Standard Mail, and Bound Printed Matter (BPM) flats. Terms of this benefit vary by class of mail.  For Periodicals letters and flats, the Full-Service mailer receives notices of Change of Address (COA) or undeliverable as addressed (Nixie) notices at no additional cost for 60 days from the first notice. For Standard Mail letters and flats and BPM flats, the no-added cost service lasts 95 days from the first notice. 
After these specified periods have passed, Full-Service mailers will be charged for additional COA and Nixie notices based on the prices specified in the USPS Price List, Notice 123, under “Address Correction Service”. USPS will identify Mail Owners by the Customer Registration Identification number (CRID) from the associated electronic documentation (eDoc). 
1.1.1.2	Non Full-Service
Mailpieces with a Full-Service Service Type Identifier (STID) that cannot be matched to eDoc,will not be fulfilled.
1.1.1.3	Invoices
Mail Owners will be invoiced for Full-Service ACS charges.
•	Mail Owner is determined based on MID / CRID from the eDoc
o	Identified by MID – invoice will be sent according to ACS OneCode profile if available
o	Identified by CRID, Permit, or MID with no OneCode profile – invoice will be sent to CRID the MID is linked to in the Mailer ID system (no data distribution profile will be used)
Invoices will normally be mailed on the 24th of each month, though if the balance owed is less than $50, invoices will be mailed on March 24th and September 24th of each year. Payment must be submitted with a copy of the invoice within 30 days of invoice date.
1.1.1.4	Delinquent Accounts
If payment is not received within 30 days, the account will become delinquent. Full-Service ACS feedback will be suspended on delinquent accounts, and unpaid balances will be subject to a 10% annual interest rate. Since ACS/Nixie information is provisioned by CRID in the PostalOne! system, a delinquent account could affect multiple Mailer IDs.  If multiple Mailer IDs are linked to a delinquent CRID account, ACS feedback is suspended for ALL of those Mailer IDs. The 10% interest applies, but the account will not be deactivated immediately.  If an account is delinquent for more than 45 days, ACS records will be discarded.
1.1.1.5	Foreign Addresses
Full-Service COA will include Foreign Address Information as part of the COA Delivery and response Mail.XML messages.                                         
1.1.2	Full-Service eDoc Verification and Assessment 
In the November 2010 PostalOne! release, the Postal Service will introduce a process for evaluation of eDoc for Full-Service mailings.  The new process will use a census approach where every container, handling unit and piece will be evaluated to identify eDoc verification errors in container and handling unit records.  Enhancements to the MicroStrategy Mail Data Quality reports will include detailed information on Full-Service jobs. The report will contain affected piece counts and the postage amounts for the impacted pieces.   In addition, there will be a new PostalOne! report called the “Full-Service Error Report.”  This report will provide the eDoc submitter with the functionality to request reconciliation of the identified errors.  The new functionality will provide Mailers with an opportunity to advantage of the reconciliation process and use the feedback to correct Full-Service verification errors. 
On January 2, 2011 the errors identified in the MicroStrategy Mail Data Quality reports will result in the loss of the Full-Service discount for all Full-Service pieces contained in the containers or handling units.  For logical containers and handling units, due to lack of visibility of pieces tied to physical containers, the loss of discount will be assessed for all Full-Service pieces in the logical containers and handling units when an error occurs.   In the January release, the PostalOne! Full-Service Error Report will provide the eDoc submitter with the functionality to make payment for the assessment as well as request reconciliation of the identified errors.
All errors will be reported to the associated eDoc submitter CRID (SEG Mailer Facility ID). 
The errors for loss of Full Service discount verified by the system will include:
•	Mailer ID: Verify that the Mailer ID parsed from the barcode provided in the eDoc is a valid Mailer ID in the MID system 
•	Service Type ID: Verify that the Service Type Identifier parsed from the barcode provided in the eDoc is valid for the Mail Class and indicates Full-Service 
•	By/For: Verify that the Mail Owner and Mail Preparer provided in the eDoc by MID or CRID map to a valid CRID from the Customer Registration system 
•	FAST Customer Supplier Agreement (CSA): Verify that the eDoc contains valid elements for all of the required fields for the CSA. 
•	Barcode Uniqueness: Verify that Intelligent Mail barcodes (pieces), Intelligent Mail tray barcodes, and Intelligent Mail container barcodes provided in the eDoc are unique within and across mailing jobs (as designated by the Mailer Facility ID) based on the Postage Statement Mailing Date provided in the eDoc.  

Full-Service eDoc verification errors will be reported in the MicroStrategy Mail Data Quality reports through the Business Customer Gateway generally within 48 hours after the finalization of postage statements. The Mail Data Quality reports will continue to aggregate errors by the job based on finalization of postage statements until the job is completed. Mail Owners are encouraged to monitor the Mail Data Quality reports through the duration of the mailing cycle. See the User Access to Electronic Mailing Information and Reports Guide on RIBBS (http://ribbs.usps.gov/) at (http://ribbs.usps.gov/intelligentmail_guides/documents/tech_guides/user_access/user_access.htm) for detailed instructions on accessing the Mail Data Quality Reports.  A new Full-Service eDoc Verification Error Invoice report will provide detailed information on Full-Service jobs. The report will contain affected piece counts and additional postage amounts that will correlate with the PostalOne! Full-Service Error report.  
The PostalOne! system will create the Full-Service Error report 30 days after the job is completed in PostalOne! or 30 days after the date the last postage statement was finalized, whichever comes first. The PostalOne! system considers a job complete when the total pieces for finalized postage statements matches the total pieces in the qualification report. The Full-Service Error report will provide information to identify the specific job found with errors and the additional postage charges.   The report will provide functionality to allow the eDoc submitter to make payment for the assessment or request reconciliation of the identified errors.  The reconciliation request will be sent to Remediation Team/Help Desk for review:  The Help Desk will review/investigate the reconciliation request and notify mailer of review results.  
While the discount removal will not be activated in this release, Mailers are encouraged to take advantage of the reconciliation process and use the feedback to correct Full-Service verification errors prior to the implementation of the Full-Service Discount Removal on January 2, 2011. Mailings completed prior to January 2, 2011 will not be subject to loss of the Full-Service discount.
A new, Business Service Administrator Verification Assessment Evaluator (VAE), service type will be added to the Business Customer Gateway. The VAE BSA will
•	Receive email notifications or online popup messages alerting them of a Full-Service eDoc Verification Error report
•	Gain access to the PostalOne! Full-Service Error Report
•	Make payments through the report for additional postage charges
The Business Service Administrator Verification Assessment Evaluator (VAE) may delegate the VAE service to other BSAs and approve users for the VAE service.  All BSAs and users will receive email notifications or on-line pop-up notices while accessing the PostalOne! system. 
•	An email notification for the Full-Service eDoc verification errors will be sent if an established threshold is exceeded:
–	If the total amount of disqualified postage is greater than $150  and 
–	The number of compliant pieces is greater than 70%
•	The email notification is sent to the mailer’s appropriate Verification Assessment Evaluator (VAE) 
–	The VAE is assigned by mailers for each CRID (business location)
Details of the Full-Service eDoc verification process are documented in section 5.1.4 of the Guide to Intelligent Mail for Letters and Flats.

1.2	Enterprise Administration (eAdmin)
1.2.1	Business Service Administrator
1.2.1.1	Reaccepting the Online Agreement
On November 1, 2010, new Enterprise Administration functionality will be implemented to enable the USPS to update the online agreement and existing external Business Services Administrators (BSA) to reaccept the new agreement.
The grace period to reaccept the new agreement is configured for November 1 through December 15th.  At the start of the period, the new BSA agreement will be replaced with the existing one. During this period, BSAs and associated users may still access the service and location combinations, but the new online agreement must be reaccepted during the grace period. The BSA can defer reacceptance until the final day of the grace period. A ‘New BSA Agreement’ link will be enabled and pop-up reminders will display throughout the grace period. At the end of the grace period and where the BSA did not reaccept, the BSA and all affiliated users’ access at that service and location combination will be disabled.
1.3	Accounts
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
1.3.1	Balance & Fees
Mailers will see an opening and closing balance on the review page and the confirmation/receipt page that the system produces once a postage statement is at the confirmation page.  The system will provide balances for all permits that maintain a balance (Permit Imprint, Additional Postage accounts, Business Reply permits, Periodicals and Postage Due). 
The system will provide a graphical display of fees due.  The display will be in a calendar format on the Balance and Fees page.  It will display 3 months worth of data at a time.  The display will include the current month plus the next 2 months followed by a data grid.  The data grid will include the Permit type and number, office where the permit is held, the fee type and the fee expiration date.
The Balance and Fees screen will provide the Nonprofit Authorization number for the permits when applicable.  The Nonprofit Authorization Number will be displayed on the following screens:  Permit Entry, Account Verification and Confirmation.
Users will be able to generate and print a fee renewal letter (invoice).

1.3.2	Manage Permits
The Manage Permits screen will provide the Nonprofit Authorization number for the permits when applicable.  
The following changes are being made within Manage Permits for BSAs/External Users (SRS 367 part 3.1):
•	Text revisions will be made on several screens to use terminology more consistent with other USPS systems and provide better instructions to users.  Graphical improvements will also be made to improve user experience, which includes a new navigation menu similar to other PostalOne! Mailer pages of the Business Customer Gateway. Other changes include removal of irrelevant display fields on screens, and additional sorting capabilities on tabs displayed within Manage Permits.
•	The PostalOne! system will as a back end process update name and address information on permit account records if there is a CRID match between permit records and information stored in Business Customer Gateway profiles.
•	Permit Validation will be improved for BSA users by enhancements to the address checking performed during validation attempts and by storing failure reasons currently displayed to the user but not visible to the PostalOne! Help Desk.
For Periodicals permits (type Periodicals or Pending Periodicals), the system shall display a new column indicating if the Post Office location for the permit is the original entry office (OE) or the additional entry office (AE). [49962, SRS 352, part 3.9]
The Postal One! system will display “Additional Postage” for ADD-POS accounts wherever the name of the permit type is written out. The system shall display “AP” as the permit type for permit imprint accounts. This will distinguish Permit Imprint accounts from additional postage accounts.
The system will provide mailers an email notification when the account balance falls below a threshold that the Business Service Administrator (BSA) sets.  The system will generate a generic email message that informs the user that the balance has fallen below the prescribed level.  Only one threshold can be set for all accounts linked to the user.  The low balance alert will not contain any sensitive information. 57911
Users will be able to receive an email notification when existing fees (not CAPS accounts) in the system are about to expire (30 days in advance of the expiration date). 57926
The maximum number of available Permit Type GH (Ghost) will be increased to 99999. 56577

1.4	Mail & Transport
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
1.4.1	CAPS
For Mail.dat postage statements and for Mail.XML postage statements with spoiled or shorted pieces, the CAPS system shall display the shorted and spoiled pieces in the transaction details. [59308 CR SRS 352, SRS 378 part 3.6]

1.4.2	Electronic Data Exchange
Users participating in electronic data exchange with the US Postal Service should reference the Postal Service Mail.dat Technical Specification, Postal Service Mail.XML Technical Specification for Postage Payment and Reporting (eDoc), Postal Service Mail.XML Technical Specification for Appointment Scheduling (FAST), and Postal Service Mail.XML Technical Specification for Profiles and Full Service Feedback.
The following changes affect mailers participating in electronic data exchange using either Mail.XML® messaging or Mail.dat® files: 
Mailers can no longer cancel files by submitting Mail.dat files or Mail.XML messages if the job has been frozen for dashboard processing by a postal employee. Previously, a defect allowed such jobs to be cancelled. 50327
The PostalOne! Desktop Application will allow users to set the number of tries to reconnect and the amount of time between tries if network failures prevent validation from completing. Files will not fail validation until all retries have been used. Previously, validation failed jobs without attempting to reconnect if network issues prevented connection. 50635, 52294
1.4.2.1	Mail.dat
The changes in the following sections apply to customers participating in electronic data exchange using Mail.dat as a means of electronic submission.
1.4.2.1.1	Mail.dat Client Application
As a reminder, with this release it is required that mailers download the new Mail.dat client application. The latest Mail.dat application is available for download from the Electronic Data Exchange page, accessed from the Business Customer Gateway.
When a Mail.dat job was rejected due to a validation failure, users were sometimes unable to view the validation errors on the Job Validation / Upload Details screen.  The problem was intermittent and only affected users when they had a Job ID that was used by another mailer with a different provider code.  The PostalOne! system has been updated to properly retrieve submission history information for the job, so that the validation errors are always displayed.  61349
The standard error output by the Java API for XML Web Services (JAX-WS) library will now only include error messages. Previously, informational messages were also included which affected the internal error handling processes of some mailers. 59376
1.4.2.1.2	Mail.dat Processing
a.	General
The SASP system will no longer accept Mail.dat 08-2 files marked as Full-Service in the SEG SASP Preparation Option field. 59285
For Standard Mail Postage Statements with Parcels or Not Flat-Machinable, the system will map CQT file rate categories PK, PM, NK to price level SCF; the system will map CQT file rate categories P5, P7 and N5 to price level NDC; and the system will map CQT file rate categories N6, P6 and P8 to price level mixed NDC. [54421 SRS 352, part 3.22]
Updates and inserts of CQT and PQT records will be allowed until the CSM file Container Status is set to Ready-to-Pay. Validations on these files will be re-run for the update job.  All relevant reports and Postage Statements will be regenerated after the update job has been uploaded. [47642, 47562, 59313, SRS 352 part 3.6]
For Mail.dat jobs that generate a single billable postage statement, the verification data will appear on that statement and not in a separate Master Statement. [39273, SRS 352 part 3.12]. 
On the Mail.dat ASCII format status receipt, the extra space after an error message will be eliminated. The extra line at the end of the file will be eliminated. [60111]
For Mail.dat jobs, the postage statement time will be removed as a postage statement generation key field. Postage statement time is the CSM Container Ship time in the Mail.dat version 08-2 file or the CSM Postage Statement Time in the Mail.dat version 09-1 file. Postage Statement Mailing Date is still a factor for determining the number of postage statements. Previously, for non-Periodicals mailing classes postage statement generation erroneously split single statements into multiple statements if the mailing time was different, even if all other postage statement generation key fields were identical. 48096
Postage statement generation will include all statements in a mailing, even if Carrier Sequencing Date is not included. Previously, statement generation did not include child statements if this date was blank, even when the date was not required for the prices claimed. 58688 
When there is only one billable postage statement (for MLOCR or list mail) the PostalOne! system will no longer generate a master statement for one billable postage statement (MLOCR or otherwise). The billable statement will include all detailed information and postage verification features. 56487
The PostalOne! system will no longer use the Full Service Participation Indicator field in the SEG file as a postage statement generation variable for Non Periodical postage statements. 60009

•	Priority Mail
The system will be discontinuing support of Priority Mail in Mail.dat effective with the deployment of Release 26.0 (January, 2011).  There are currently issues recorded related to Priority Mail and Mail.dat, however because of the discontinued support of Priority Mail in Mail.dat the Postal Service will not expend resources to resolve those issues in this release (Release 25.0).  Users may continue to submit Priority Mail files until January, 2011 as some functionality does remain in Mail.dat and will work correctly
•	Periodicals
For Periodicals Mail.dat jobs, the performance for job upload and postage statement generation will be enhanced. [54114, SRS 372]
For a Periodicals with piece data provided in a PDR file, the MPA file field USPS Publication number will be allowed to identify the mail owner for the purpose of Full-Service data distribution. [38249, SRS 352 part 3.4]
For a Periodicals incidental enclosure that is not a loose addressed supplement, the Mail.dat validation shall allow the incidental enclosure to be defined in a different CPT from the main book. The MCR Host Statement Component ID is optional and if provided will refer to the main book. The CPT Periodical Ad% Treatment may be S. The CPT Component - Rate Type may be Z. The MPU ID will be the same as the main book. For a Periodicals incidental enclosure the Periodicals postage statement generation the system shall include the incidental enclosure editorial weight in the main book editorial weight and the incidental enclosure advertising weight in the main book advertising weight. [59326]
The PostalOne! system was incorrectly calculating Periodicals container charges. In the case that a pallet, sack, or tray, at the carrier route, 5-digit carrier routes, or 5-digit/scheme presort level has a mixture of In-County pieces and Outside County pieces, the system will be updated to ensure that the postage statement is generated correctly and that there is no container charge for this container . Previously, the system incorrectly generated a container charge for this container. 60988.
Validation will verify that Periodicals non-incidental enclosures are accepted if the MPU/Component Relationship MCR) Host Component ID references the correct files. Host Component ID must reference either its own MCR Component ID or a MCR Component ID within the same MCR Mail Piece Unit ID. Previously, a defect failed Periodicals with Rate Type “R” and non-incidental enclosures with the error message “If the MPU class does not equal the CPT class and the CPT rate type is R, then the MCR Host Statement CPT ID must be the same as the CPT ID or it must be null.” 49775
•	Error Messages
For Mail.dat jobs with non-carrier route automation mail, the error message validating the SEG Automation Coding Date field (incorrectly stating 90 days, but correctly validating 180 days) will be corrected to read: For SEG File Processing, the SEG Automation Coding Date cannot be earlier than 180 calendar days before the CSM Postage Statement Mailing Date for non-carrier route automation mail. 
For Mail.dat jobs with carrier route mail, the error message validating the SEG Automation Coding Date field will read: For SEG File Processing, the SEG Automation Coding Date cannot be earlier than 90 calendar days before the CSM Postage Statement Mailing Date for carrier route mail. [SRS 352 part 3.27]
To assist in troubleshooting, error messaging for Mail.dat validation will be updated to generate an error message documenting the specific data fields provided in the Mail.dat file submission when the statement does not map to any prices for the mail class. Previously, error messages did not include enough information to determine the specific data fields causing the failure to generate postage statements. 49987
The error message “A First Class/Priority Mail Postage Statement did not map to any valid Rates and generated 0 lines” will include the relevant CQT Rate Category of the failed postage statement. Previously, rate information was not included in the error message. 50881
•	Copalletization
Copalletized jobs with different presentation categories will be accepted when submitted through Mail.dat files. For those cases where MLOCR mail is copalletized with other mail, validation now allows consolidation jobs to claim HDR Mail.dat Presentation Category “P” (Conventional Presort), even if the job includes one or more original MLOCR jobs with HDR Mail.dat Presentation Category “M” (MLOCR).  51028
For consolidation of bundles on pallets, at the origin site Mail.dat files, the PostalOne! system shall accept any of the CSM file field Container Type values V, S, 1, 2, 3, 4, or 5 as a container that may be set to CSM file field Included in Other Documentation 'O'. These must be set to a virtual sack in the consolidated Mail.dat file. Sacks submitted from the consolidator must be presented as origin sacks in a separate Mail.dat job and do not show trace back to the origin site. [54113, 61263, SRS 370, REQ 2]
The PostalOne! system will allow linkage of an origin container of type V, S, 1, 2, 3, 4, 5 to a consolidator container of type V in the .oci file.  Currently, the PostalOne! system validates that container type is the same value when linking origin containers to consolidator containers in the .oci file.  61264.
The PostalOne! system will convert container types of S, 1, 2, 3, 4, 5 to container type of V prior to releasing the data to SASP.  This applies to the origin CSM data, as well as the consolidator’s OCI data.  61265
When an origin job is linked to multiple consolidator jobs, the PostalOne! system will correctly link the origin job handling units (trays) to the consolidator jobs.  The system currently links all of the handling units from the origin job, causing creation of handling units that do not belong to the consolidator job, and have not been created in SASP. 63261
b.	Validations
For pending Periodicals Mail.dat jobs, the file validator will validate that the MPA Postage Payment Method is T when the mail class is Periodicals Pending. [38377, SRS 352 part 3.11]
For Mail.dat files with sibling containers, the file validator will allow the sibling container to have a CSM Unique Container ID. [28883, SRS 352 part 3.13]
For MLOCR Mail.dat files (HDR Mail.dat Presentation Category is M), the system will allow all pieces to be Single Piece price (CQT Rate Category is S). The CSM Container Level may be Single Piece (AJ – Mail.dat 08-2 and 09-1) or Single Piece First Class (AN – Mail.dat 09-1 only). For metered or precanceled stamps, the Qualification report will display the single piece prices. [54215, SRS 352, part 3.18]
For Mail.dat files with Transportation updates (CSM Container Status is T), the file validator will allow updates to the CSM Stop Designator or the CSM Truck or Dispatch Number. The system will allow, but ignore updates to other fields not identified as transportation-relevant. [52446, SRS 352 part 3.20]
For a Mail.dat job, the maximum number of MPA CAPS Reference IDs (version 08-2) or MPA Customer Reference IDs (version 09-1) will be changed from 30 to 999. This field is a key field for postage statement generation. [30122, SRS 352 part 3.2]
For all Mail.dat [version 09-1] jobs including MLOCR, the CSM file field Container Ready-to-Pay Transaction ID will be optional for all container statuses. [49027, SRS 352 part 3.7]
When sending an update job, the ‘record name’ Record Status field may not be set to the value O for original within any Mail.dat record, when the values in the record with ‘record name’ are changed. In this case the appropriate value for the ‘record name’ Record Status will be U for update. 52063
The PostalOne! system will validate for all update/change job submissions that a mixed Full-Service with non Full-Service job (SEG Full-Service Participation Indicator set to “M”) contains at least one Full-Service record (CQT Service Level Indicator set to “F”). All records in a Full-Service job must be Full-Service and no records in a basic job can be Full-Service. Mixed service jobs that contain no Full-Service records now fail validation. 54526
For Mail.dat jobs with an IMR file, the system will validate that the Piece Count field in the IMR file is between the CSM Number of Copies and CSM Number of pieces, inclusive, for each container in an update job.  This validation is already run for original job submissions.  49758
The PostalOne! system was allowing the incorrect format for numeric values to be submitted in Mail.dat jobs for alphanumeric fields that are defined in the Postal Service Mail.dat Technical Specification as numeric only. The Mail.dat validations for the MPA CRID of Preparer and the MPA CRID of Mail Owner fields have been updated to enforce the specification rules for numeric values in alphanumeric formatted fields: left-justified and no leading zeroes. 61112
The PostalOne! system will validate that for each CQT Database ID the CQT Number of Pieces must equal the PQT Number of Pieces and the CQT Number of Copies must equal the PQT Number of Copies. [SRS 352, part 3.6]  
A new validation will be added to prevent a mailer from submitting a PDR and an IMR file within the same job.  Currently, the PostalOne! system accepts mailing with both files present, which creates invalid piece barcodes after postage statement finalization.  54074  

1.4.2.2	Mail.XML
The changes in the following sections apply to customers participating in electronic data exchange using Mail.XML as a means of electronic submission: 
1.4.2.2.1	Mail.XML Processing
c.	General
The PostalOne! system now truncates any error messages too long to fit in the logging database. Previously, very large Mail.XML MailPieceCreateRequest messages received corrupted responses if errors resulted from the submission that were larger than the database supports. 61437

•	Support for USPS Publication Number to identify By/For
The Publication Number will be allowed for the identification of By/For by the SASP system for the Full-Service mailing. The SASP system will be modified to identify the customer (By/For) through Publication numbers, besides Permit numbers, CRIDs (Customer registration IDs), and MIDs (Mailer IDs), when provided in the Mail.XML electronic documentation and will return the Full-Service data feedback back to the PostalOne! system.  [SRS 378, part 3.8]
•	Allow Single Piece Rate for MLOCR Co-mailing
The PostalOne! System will allow support for MLCOR mailers to submit MLOCR Mixed option mailings that contain ‘Single Piece’ rate category for Permit Types of permit imprint, pre-cancelled stamps, and metered. This change is necessary to streamline the hard copy postage statement and give the Postal Service more visibility into mail pieces that are claimed at the Single-Piece rates for MLOCR mailers.
•	Government Periodicals to Allow In-County Prices
The PostalOne! system will be updated to allow for In-county prices to be applied to Government Periodicals (OMAS accounts) when the InOutCountyIndicator is “I” and the PermitNumber (Pending Periodicals) or PublicationNumber (Periodicals) represents a government periodicals account.  [SRS 378, part 3.11]
•	Leading Zero
The PostalOne! system was previously failing Mail.XML jobs that were submitted with ZIP codes that began with leading zeros .  The system will be updated to accept jobs that include ZIP codes beginning with leading zeros.   57640
1.4.2.2.2	Mail.XML Messages
d.	eDocumentation
•	Support for DDU Periodicals Prices in Postage Statement
The PostalOne! system will be modified to support PeriodicalStatementCreateRequest and ConsolidatedPeriodicalStatementCreateRequest messages with PeriodicalPrice of “1” for the DDU pieces claimed on line A17.  This change will allow the PostalOne! system to calculate the PS Form 3541 accurately.  [SRS 378, part 3.5]
The PostalOne! system will validate that DiscountQty field within the PeriodicalLineItemData block within the CreatePeriodicalStatement block of the PeriodicalStatementCreateRequest message is greater than 0 and is less than or equal to the number of In-County DDU Pieces when the PeriodicalPrice field within the PeriodicalLineItemData block within the CreatePeriodicalStatement block of the PeriodicalStatementCreateRequest message is1. [59814]
The PostalOne! system will validate that the Zone field within the PeriodicalLineItemData block within the CreatePeriodicalStatement block of the PeriodicalStatementCreateRequest message is DDU when the PeriodicalPrice field within the PeriodicalLineItemData block within the CreatePeriodicalStatement block of the PeriodicalStatementCreateRequest message is 1. [59815]
e.	Validations
•	Support for Transportation Update through Container Update Request Message
The PostalOne! system will add two new fields: ‘Stop Designator’ and ‘Truck or Dispatch Number’ fields to support transportation-related updates. With the implementation of this change, the PostalOne! system will not fail the transaction if non-transportation related fields are updated. The system will instead validate and ignore non-USPS transportation fields in Mail.XML. [SRS 378, part 3.7]
SASP will accept Transportation Updates submitted via the ContainerUpdateRequest message in order to update certain Qualification Report information after Mail.XML electronic documentation finalization.Mail.dat Postage Statements.
•	Automation Address Match Date Validation
The ‘AutomationAddressMatchDate’ element within PeriodicalStatementDataType and PostageStatementDataType blocks will be validated. The system will only allow the AutomationAddressMatchDate to be within 180 days of the mailing date for non-carrier route mail and within 90 days of the mailing date for the carrier route mail.  [59807, 59808, SRS 378, part 3.18] 
•	Barcode Range Validation
Validation will accept Mail.XML jobs where the barcode range lower and upper SerialID6 are the same. Previously, the upper SerialID had to be greater than the lower SerialID in the Serialization block. 58728

1.4.2.2.3	Mail.XML Full-Service
f.	Messages
•	FullServiceNixieDetailResponse Push Message
All of the following fields: SubmittingParty, SubmittingSoftware, UserLicenseCode, JobID, MailingGroupID, and CustomerGroupID will be changed to OPTIONAL.
The ‘BillReasonCode’ and ‘FreeCharge’ fields will be added to this message to support future ACS surcharge notification for non-compliant Full-Service ACS pieces.
•	FullServiceNixieDetail Request and response pull Messages
The following fields will be changed to OPTIONAL in FullServiceNixieDetailDelivery and FullServiceNixieDetailQueryRequest messages: SubmittingParty, SubmittingSoftware, UserLicenseCode, JobID, MailingGroupID, and CustomerGroupID. 
The two new fields ‘BillReasonCode’ and ‘FreeCharge’ will be added to the FullServiceNixieDetailDelivery message.
•	FullServiceAddressCorrections Messages
The following fields will be changed to OPTIONAL in the FullServiceAddressCorrectionQueryRequest, FullServiceAddressCorrectionQuery Response, and FullServiceAddressCorrectionDelivery messages: SubmittingParty, SubmittingSoftware, UserLicenseCode, JobID, MailingGroupID, and CustomerGroupID.
The two new fields ‘BillReasonCode’ and ‘FreeCharge’ will be added to the FullServiceAddressCorrectionDelivery and response message.
g.	Data Distribution
•	Full-Service Data Availability Changes
The PostalOne! system will make data available for ACS, Nixie, Start-The-Clock, By/For, and eDOC data based on the record creation date of the PostalOne! system instead of the SASP creation date. Also, internal help desk functionality will be updated to support troubleshooting requirements for Mail.XML transactions through the health monitoring system. 
•	Full-Service Data Block Size Changes
Upon customer request, the PostalOne! system will be increasing the size of the Mail.XML data blocks returned to the customers to reduce the number of messages in a transaction. The details of the changed block size are made available in the Postal Service Mail.XML Technical Specification for profiles and Full Service Feedback.
1.4.2.3	Wizard Web Service Decommissioned
Wizard Web Service (WWS) was replaced by Mail.XML. The WWS Service Layer will be turned off in Release 25.0.0. WWS transmissions will not be accepted upon implementation of Release 25.0.0.

1.4.3	Postal Wizard
The changes in the following sections apply to customers participating in electronic data exchange using the Postal Wizard as a means of electronic submission: 
1.4.3.1	PS Form 3700 International Mail Postage Statement

Receipts for PS Form 3700 Part A (First-Class Mail International Permit Imprint) postage statements will display the cost center and acceptance facility information. Previously, if a mailer submitted the postage statement, the receipt would not display the correct cost center and not show acceptance facility at all after finalization. 54362
Mailers will now be able to submit International Postage Statements (PS Form 3700) Parts B through I (including extra services) using the Postal Wizard. International postage statements submitted by postal employees or using the Postal Wizard (mailers) are visible on the Dashboard for all searches where status is set to INC (Incomplete), UPD (USPS Processing Due), or ALL (All statement statuses).
An external user will not be able to cancel or save incomplete for 3700 in the 'View forms I have submitted' link. The Mailer user will be able to cancel a submitted 3700 in the Mailer Dashboard and Pending Postage Statements report. (58052, 58056, 58059).

International postage statements no longer display an “Affixed Account” label next to mailer information when entering a postage statement. 63383
1.4.3.2	PS Form 3602 Standard Mail Postage Statement
Users will be able to submit postage statements that include Detached Address Labels (DAL) information. Previously, postage statements with DAL items submitted by mailers did not have DAL items if adjusted by a postal employee, and PS Form 3602 (Standard Mail) postage statement entry pages lacked the DAL option. 48038, 50464
1.4.3.3	Domestic Postage Statements
The system will allow users to select a permit number to populate the mail owner block, Name and Address of the Individual or Organization for Which Mailing is Prepared (if other than the permit holder) except for the PS Form 3541 Periodicals Postage Statement which contains no “Owner block”.
Data entry of containers will be modified to display the entry of container information horizontally to reduce scrolling by users. 57910
The confirmation page will now have a link with a printable page.
Performance enhancements will be made to postage statements during entry from Postal Wizard or BMEU pages, and during finalization. 56746
An external user will be able to save an incomplete domestic statement and go back to it later to complete it under a new link in 'Saved Forms' on the Mailer 'Postal Wizard' screen. The name of the new link shall be 'View incomplete forms I have started'. (SCRs 58052, 58056, 58059)
Printed postage statements no longer display the release number at the top of the page. Previously, an obsolete release number was listed. 63069

1.4.4	Periodicals Authorization 
The Periodicals data will be associated to a Periodicals authorization that is updated by the Pricing and Classification Service Center (PCSC) and attached to the applicable finance number for the Original Entry Office and the finance numbers for the additional entry offices. The postal clerks at these Post Office locations shall be able to display but not change this data. This data includes the Original Entry Office city, state, ZIP code, Publication title or News Agent, Publisher Name, Publisher or News Agent Address (Address Management System compliant), ISSN, Frequency description, Number of Issues Annually, Contact Name, Contact Address (Address Management System compliant), Contact phone number and extension, Contact Email, Advertising Permitted (General, No Advertising, Publisher’s own), DMM Authorizing Section, Organization if Publication of Institution and Societies, DMM Rates allowed (Regular, Science of Agriculture, Nonprofit, or Classroom), Government Publication Indicator, Authorized Date, Effective Date, Preferred Price Effective Date, Review Date, Application Date, Remarks, Additional Entry Offices, USPS Publication Number, News Agent Indicator, Specialist ID, and record of Authorization letters sent. Some of this data may be missing for legacy records. [SRS 353]
For paper postage statements with Periodicals (PE) permits, the system will verify that the permit number is a valid USPS Publication Number has a valid original entry office or additional entry office for use at the finance number. If the number is not valid, the clerk will not be able to enter the postage statement using that permit. The number will be validated against the new Periodical Authorizations data that is maintained by the Pricing Classification Service Center (PCSC). [SRS 353]
When finalizing electronic statements with Periodicals (PE) permits, the system will verify that the permit number is a valid USPS Publication Number and has a valid original entry office or additional entry office for use at the finance number.  If the number is not valid, the clerk will not be able to finalize the postage statement.  The number will be validated against the new Periodical Authorizations data that is maintained by the PCSC. [SRS 353]

1.4.5	Dashboard
Mailers will be able to view all statements with preparer permits linked to them, regardless of whether the permit has been cancelled since the original job submission or not. Previously, if a permit used by a mail preparer was cancelled, the job did not appear on the Dashboard for the preparer. 50854
Mailers will be able to use the location search criteria when creating a Dashboard search. Previously, statements submitted by mailers or postal employees through Web pages did not appear when searched by location. 50880
For all classes of mail, if a mailer creates postage statements by Mail.dat, by Mail.XML, by Postal Wizard, or by the postal clerk, and provides a Customer Reference ID in the MPA file, the system will add the Customer reference ID to the Job/Publication name on the dashboard for this postage statement in the composite field between square brackets []. [SRS 391, Part 3.4]
1.4.5.1	Postage Statements
The postage statements for finalized mailings submitted with Mail.dat files will display a certification and USPS section that includes all applicable disclaimers, including the fact that no further signatures or round stamps are required. 49440
For Periodicals Combined Mail, the system will generate and display the verification statement for the Mail.dat job as soon as the update status postage statement is processed. Currently, the system requires the postal clerk to click on a billable statement within the combined mailing to generate the verification statement. [50088, SRS 352 part 3.10]
For CPP mailings with enclosures, both the consolidated statement and the enclosure statement will be set to FPP (Finalized Pending Payment) upon finalization by a postal employee. Additionally, mailers will be able to select enclosure statements when scheduling payment requests. Previously, enclosure statements were charged immediately to the account, instead of being paid with the rest of the mailing on the scheduled payment date. 50277 50278
For Mail.dat jobs with Periodicals or pending Periodicals sent with CSM file field Container Status with value Ready-to-Pay, the publisher will have the ability to change the following fields in the PS Form 3541 Periodicals Postage Statement up until the postage statement is finalized (in FIN status). The fields available for change are the Issue Date, the Volume Number, the Issue Number, the “from” Mailing Date, the “to” Mailing Date, the Customer Reference ID, and the Issue Frequency. The fields will be available for update on the Postage Statement screen accessible from the dashboard. If the statement is in process by another user USPS or mailer - then there is a message that the statement is not available for update until the record is released. [59318, SRS 391, Part 3.1]
For a Mail.dat copalletized job or a Mail.XML copalletized job with mailing class Periodicals, First-Class Mail or Standard Mail, there will be a copalletization indicator on the postage statement header for the postage statement screen, the xls download, the csv download, and the pdf download. [59327 Mail.dat, 59423 Mail.XML]
For a Mail.dat submission of the PS Form 3541, the pdf download will display the number for Total Addressed Pieces. Prior to this release the pdf download displayed zero Total Addressed Pieces. [58658]
For Mail.dat file submission of combined First-Class Mail or of combined Standard Mail when the master postage statement is reversed all the billable postage statements will be reversed. Prior to this release sometimes some billable postage statements were not reversed. This resulted in request for data repair to complete the reversal. [58995]
Cost center will display accurately on the master postage statements for combined mailings. Previously, a defect displayed the incorrect cost center for some mailings. 57226 
Postal employees will be able to release the freeze on Finalized Pending Payment (FPP) statements if necessary to allow a mailer to cancel the statement. Previously, frozen FPP statements could not be released. 54540
For Mail.dat, Mail.XML, and Postal Wizard submitted postage statements, submission date will remain unchanged after finalization. Prior to this release, mailer-submitted postage statement submission dates did not save when a postal employee finalized the statement. 56965
Users will be able to update or cancel combined statements with REW (Rework) status. Previously, if a postal employee set a master statement to REW status, the associated child statements would not change status, stopping any further updates to the mailing. 54238
The PostalOne! system was incorrectly calculating postage affixed when jobs with the same MPU Mail Piece Unit ID were associated to different segments.  The system will be updated to use the SEG Segment ID together with the MPU Mail Piece Unit ID to determine the unique MPU records, and will calculate postage correctly.    60914
When the MPA CRID of Preparer is provided in a Mail.dat job the PostalOne! system will display the CRID and contact information associated to that CRID in the Mailing Agent block of the postage statement.  The preparer permit number, telephone number, email address, or customer number will no longer be displayed in this case.  If the MPA CRID of Preparer is not provided, then the existing logic will be used to display the preparer permit number, telephone number, address, and email address from the PostalOne! permit tables.  58268
Finalized postage statements now appear as finalized on the Dashboard if finalization results in a transaction number. Previously, errors during finalization allowed some statements to be billed and receive transaction numbers, but did not update the status of the statement. 52001 54100
The downloadable Portable Document Format (.pdf) version of Periodicals postage statements now correctly reports total postage and total addressed pieces. Previously, pdf generation did not include the classroom or nonprofit discount in total calculations and total addressed pieces always displayed as zero (0), even though all other versions of the postage statement displayed the correct information. 57890 58658
The downloadable postage statements for Standard Mail and Package Services statements now match online statements by displaying weights in pounds to four digits after the decimal. Previously, these statements did not match the online versions of the statement. 59054
Issue-level Periodicals postage statements now display the correct advertising percentage. Previously, a defect displayed the incorrect advertising percentage on issue-level statements. 59211
Limited Circulation Discounts are now included in total postage calculations for issue-level Periodicals postage statements. Previously, this discount was missing. 59923
The PostalOne! system will use the postage statement number for a non-consolidated child postage statement to update the Total Postage and Total Adjusted Postage fields, to ensure that the postage amounts from sections D and E are added to the correct postage statement.   Previously, the postage amount from sections D and E were added to the first available non-consolidated child statement, since the process was unclear of the correct statement that the postage amount should be added to.  56843
For a Standard Mail Mail.dat job submitted with pieces that have a price of Single Piece the PostalOne! system will create both the Standard Mail postage statement(s) for the presorted piece prices and the First-Class Mail postage statement(s) for the Single Piece prices. If appropriate, the First Class postage statements will be combined to master statements and the Standard Mail postage statements will be combined to master statements. All postage statements for the job will appear in the same mailing group.  Previously, the system was incorrectly combining the Standard Mail and First Class Mail statements into the same combined statement and causing a timestamp error preventing postage statement finalization.  57428

1.4.5.2	Qualification Report 
Qualification Reports received a few minor changes. The report now highlights rows as necessary, though previously some lines did not display highlighting if ADC for MADC tray exceeds 89, ADC/5DG/5DGS/3DG/3DGS for Tray ZIP Destination is less than 90, AADC/5DG/5DGS for Tray ZIP Destination is less than 150, 3DG/3DGS claimed at the 3DG/3DGS price for Tray ZIP Destination is less than 150 or 3DG claimed at the 3DG price for ADC Flat Tray exceeds 89. Printing the Qualification Report no longer cuts off the sides of the report.  49522 51772
Entry point information for Standard Mail will receive minor cosmetic changes on several electronic documentation pages. The Qualification Report will no longer separate information by entry point for mailings that are not part of the MultiLine Optical Character Reader (MLOCR) mailings; for MLOCR (and OnePass) mailings, rate categories will be separated by entry point. 49741  
The Container Search feature available from the Qualification Report will no longer require users to enter all leading zeroes padding a container number. Previously, a defect required users to enter all zeroes preceding the actual container ID. Bundles displayed on the report now represent the actual number of bundles; prior to this release, bundle counts were doubled for some sites. 51789 57183
1.4.5.3	Reconciliation Report
For Mail.dat jobs, the system will add to the reconciliation report pieces categorized as Spoiled/Damaged - Postage Adjustment Transaction or Spoiled/Damaged Piece Detail Transaction. [54211, SRS 352 part 3.19]
The Reconciliation Report received several minor fixes. Printing the report no longer cuts off the sides of the report. Additionally, for postage statements submitted using Mail.dat files, shortage pieces now count towards the total number of pieces, allowing statements with shortage pieces to be reconciled if all other pieces are accounted for.  54123 51767
1.4.5.4	Summary ZIP Destination Report
For Mail.dat jobs and Mail.XML jobs, the PostalOne! System will generate a Summary ZIP Destination report that breaks out nonprofit permits and regular permits on separate detail lines. When the system generates the Summary Destination ZIP Destination report for a Mail.dat file, the pay types will be Metered (M), Stamped (S), and Permit (P), Metered Nonprofit (MN), Stamped Nonprofit (SN), and Permit Nonprofit (PN) for the Details and for the Grand Total Summary Section. [SRS 352 and SRS 378, part 3.14]
For Standard Mail, the Summary ZIP Destination Report will separate rate categories by entry point. 49741
1.4.5.5	Periodicals Advertising Percentage Worksheet 
For Periodicals Mail.dat jobs, the Advertising Percentage Worksheet will display a new column for the CPT file field Component - Periodical Ad Percentage: Status. [39219, SRS 352 part 3.8]
For Periodicals Mail.dat jobs, the system will remove the Ad Percent Complete check box in the Advertising Percentage Worksheet. The Ad Percent may not be changed once a Consolidated Payment Request (CPP) postage statement in Finalized Pending Payment (FPP) status is added to a CPP Consolidated Payment Request or once a non-CPP postage statement reaches finalized status (FIN). [SRS 352, part 3.16]
For Periodicals Mail.dat jobs, the Advertising Percentage Worksheet – MPU View for 09-1 Mail.dat files will display the Mailing Group Information in the header. [39219, SRS 352 part 3.10] 
1.4.5.6	Periodicals Edition Weight Worksheet 
For Periodicals Mail.dat jobs, the Edition Weight Worksheet – MPU View for 09-1 Mail.dat files will display the Mailing Group Information in the header. [39219, SRS 352 part 3.10]
1.4.5.7	Postage Register 
For Periodicals Mail.dat jobs,  the Periodicals register will display the piece and pound postage at each combination of entry point and version (MPU ID), the total piece and pound postage, the total Outside-County bundle postage, the total Outside-County container postage, and the total postage. [SRS 352, part 3.24 and SRS 372 REQ 1 and 2]
For Standard Mail, all pages will only show entry points where the mail will be deposited per the Register; currently, all ZIP Codes display. Additionally, rather than displaying the type of facility and ZIP Code, entry points will display the full name of the facility.  These pages will be available only for mailings submitted electronically using Mail.dat files or Mail.XML messaging. 49741 
1.4.5.8	Original Container Information Report
The PostalOne! system will correct an issue where consolidators and their postal clerk are unable to view the Original Container Information Report for a Mail.dat copal job.  For tray-based copalletization, mailers will need to identify the consolidator in the Mail.dat file by updating the MPA Permit ZIP+4 to the ZIP corresponding to the consolidator finance number and the MPA CRID of Preparer to the consolidator CRID.  If there are multiple MPA records, all records should have a single value for the MPA Permit ZIP+4 and MPA CRID of Preparer.  There will be no validation of the MPA Permit Number at the consolidator since trays are paid at the origin.  52350
For copalletized Mail.dat and Mail.XML jobs from consolidators, the Original Container Information Report will display the ZIP Code location but not the city and state. [SRS 352, part 3.15] [SRS 378, part 3.13]
1.4.5.9	Mailing Dates
With this release, the PostalOne! system will implement several changes to more consistently display and process the various dates linked to postage statement processing. This affects both the display of such dates on pages such as the postage entry form, review page, receipt page and reports, as well as the processing and adjustment of dates. Previously, date functionality was inconsistent and confusing. The following defines how the system will use each of the various dates associated with postage statements:
•	Open Date – Date when a mailing group is opened. This is the date when Mail.dat or Mail.XML files are first submitted in any container status. 
•	Submit Date - Date the postage statement is submitted to the PostalOne! system with USPS Processing Due (UPD) status. 
•	Mailer Mailing Date - Date that mailer said they will bring the mail to the Post Office. For electronic submissions, this date is provided by the mailer. For paper postage statements entered at a BMEU, this is the date the BMEU clerk entered as the mailing date. It might or might not be the ACTUAL mailing date. 
•	Certification Date - Date that the mail actually entered the mail stream (date of actual mailing). This date is entered by the BMEU during finalization of the postage statement. 
•	Transaction Date - Date when postage statement is finalized, the permit is charged (if applicable), and the transaction is created. This automatically-generated date is the same as the transaction time stamp.  (58834)
The PostalOne! system will record a new date for Earliest Submit Date.  The Earliest Submit Date is the date that the system can receive a new Mail.dat file that contains a Postage Statement Mailing Date that is applicable to the new price change.  A system administrator or a database script will be able to update the Earliest Submit Date during a normal maintenance window.  61385 
The PostalOne! system will record the Submit Date as the date that the Mail.dat file is received.  The Submit Data must occur no sooner than 120 days before the Postage Statement Mailing Date.  If the Earliest Submit Date is in the past, the Earliest Submit Date will be ignored and the legacy rule will be applied: The Postage Statement Mailing Date cannot be earlier than the price change before last.  61388

1.5	Track & Report
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
1.5.1	Mailing Reports
1.5.1.1	View Transactions Report
The mailer’s View Transactions Report will be modified to allow sortable columns to be sorted in both ascending and descending order. Currently the columns on the report only sort in ascending order.
The system will show an enhanced download with header information in the View Transactions report.  
The system will provide a likeness of the various postage statements and the PS Form 3607 in a link on the “View Transaction” report. The downloadable PDF versions of postage statements will resemble their usps.com form counterparts. (58144 58141 58138 58136 58131)
1.5.1.2	Mailing Summary Report
The Mailing Summary Report will display ‘Copies/Pieces’ for Periodicals forms.
The Postage Statement Summary Report will be enhanced to include the Full Service discount, for those mailings participating in the program. Additionally, a defect will be repaired to display rates for affixed postage for all applicable statements. Prior to this release, a defect displayed “Unknown” for the affixed postage rate for some mailings submitted using Mail.dat 09-1 files. 53979 54025
1.5.1.3	Mail Quality Report
External users will now see International Manifest Mail verification results in the Mail Quality report.
The number of pieces and jobs on the Mail Quality Reports now match at all levels of the report as appropriate. Previously, a defect reported the wrong number of pieces and jobs once users chose to narrow down the report. 54288
Mail Quality reports no longer falsely report duplicate Intelligent Mail barcode (IMb) tray barcodes. Previously, Mail.dat jobs with multiple postage statements that were finalized simultaneously resulted in duplicate IMb tray error messages on the report if one tray was shared in multiple statements.  60867
1.5.1.4	Consolidated Payment Request (CPP Publishers Only)
If a mailer creates postage statements for a CPP publication by Mail.dat CPP postage payment option and provides a Customer Reference ID in the MPA file, the system will display the Customer Reference ID in a new column in the Consolidated Payment Request screen to the right of the Postage Amount column. [SRS 391, Part 3.4]
For Centralized Postage Payment (CPP) Periodicals publications with postage statements from Mail.dat jobs, the Consolidated Payment Request screen will display the acceptance office information on the first level screen and no longer require clicking on each payment to see this information. [49353, SRS 352 part 3.3]
1.5.1.5	Issue Level Postage Statements
The Periodicals Issue-Level postage statement will include total copies, total pounds, advertising pounds, and total postage for line B11 of Periodicals statements, including downloadable versions. This information did not display prior to this release. Publication title displayed will be based on the publication title assigned to the original entry office for the publication, rather than the finance number and cost center of the logged-on user.  56638 57277 
For the Periodicals Issue Level Report, the following items will be added. [SRS 391, Part 3.2]
1.	Listing of postage statements in the issue level report. This list will include the 
•	Finance Number, City, State, and ZIP Code, of the acceptance office (always available); 
•	Postage Statement Number (always available);
•	Transaction number (available for FIN status);
•	CAPS Transaction number (available for FIN status and if CAPS account)
•	Total postage per transaction (always available)
•	Copies (always available)
•	Pieces (always available)
•	Postage Statement Status [UPD, FIN, FPP]
•	Customer Reference ID

2.	The system will display in the Advertising Percent field the range from the least Advertising Percent to the greatest Advertising Percent among the postage statements selected for the issue level report.
3.	The system will display in the Copy Weight field the range from the least copy weight to the greatest copy weight among the postage statements selected for the issue level report.
4.	The system will eliminate the Sequence Number field and not display the postage statement sequence number from the Mail.dat file.
5.	The system will provide page numbering in the format page 1 of n for the PDF download format. 
The system will provide a new Publication Report with additional features and flexibility and in the same format compared to the issue level report. [59510, SRS 391, Part 3.3]
1.	The system will display all the issue dates, volume numbers, and issue numbers in the Publication Report postage statement list and in the header fields on the postage statement.
2.	For the Publication Report, the system will allow the current selection by issue date or range of dates; by issue number and volume number or issue numbers and volume numbers; by mailing date, multiple mailing dates, or range of mailing dates; by original file submission date, multiple original file submission dates, or range of original file submission dates; by one or more Job IDs; by one or more Mailing Group ID; and by one or more Customer Group ID.
1.6	Manage Electronic Verification Activity (eVS)
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
1.6.1	Duplicate Manifest Processing
eVS will filter any manifest file consisting entirely of Package Identification Codes (PICs) for which a postage statement has already been created. Any manifest file meeting these requirements will be processed as a self-contained postage statement with a status of ‘Error – Duplicate’. This status will allow the mailer and USPS to determine the correct handling of the resulting postage statement. 
If the file represents unique packages that have violated the 180-day uniqueness policy for PICs, an eVS Admin user will process the postage statement and postage will be collected. If the file was received by eVS in error and is redundant data only, an eVS Admin user will close the postage statement and no postage will be collected.
1.6.2	Duplicate Package Adjustment
eVS will ensure revenue protection by identifying multiple packages mailed using the same PIC. The Product Tracking System (PTS) will provide eVS with a weekly extract listing PICs that show activity indicative of multiple packages mailed under a single PIC. Packages delivered to multiple ZIPs, packages delivered on multiple days, and packages receiving a ‘Duplicate’ scan event will be included in this extract. 
eVS monthly reconciliation will include an additional adjustment for Duplicate Packages when applicable. Mailers will be assessed an average per piece charge for these packages. The average per piece charge will be calculated based on the unmanifested per piece charge logic used in the system today.
1.6.3	Postage Extract
eVS will provide a Postage Extract containing piece-level postage payment information. This report will be returned to PTS for the mailer to retrieve from their password-protected FTP site. Mailers may choose to receive the postage extract, or an extract with piece-level data omitting postage payment information. Individual mailers may also opt not to receive the Postage Extract.
eVS will include the following information for each Header Record: the Header Record or Transaction ID, CAPS Transaction ID, EFN (or sub-header record), Mailing Date, Transmission Date, and Entry Facility ZIP.
eVS will mimic the PTS model and aggregate the extract data by linking PIC-level data with the appropriate EFN. eVS will include the following information for each Detail Record: PIC, Mail Class, Processing Category, Weight, Length, Height, Width, Dimensional Weight, Destination ZIP, Destination ZIP+4, Destination Rate Indicator, Rate Indicator, Zone, Extra Service Codes (1st, 2nd, 3rd), Fees for Extra Service Codes ((1st, 2nd, 3rd), Discount Type, Discount Amount, Surcharge Type, Surcharge Amount, Manifest Postage, and USPS Calculated Manifest Postage.
1.6.4	eVS Defect Fixes
For all users with access to the electronic Verification System (eVS), this release repairs a defect that presented all zeroes in the Monthly Account Summary section of the Monthly Account and Sampling Summary page for older months. 57258
Additionally, postage statement generation will be enhanced to prevent accidental duplication of postage statements from a single manifest file after manual resubmission of failed files. 57387
Manifest file loading and processing received some minor performance improvements to increase ease-of-use. 57026
The Corrected Header Error Report is now available to eVS users; previously, the report would not display. Additionally, the title on the report page has been changed to “Corrected Header Error Report” instead of “Header Error Report”.  59989

1.7	Manage Electronic Return Activity (PRS)
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
1.7.1	Duplicate Manifest Processing
PRS will filter any manifest file consisting entirely of Package Identification Codes (PICs) for which a postage statement has already been created. Any manifest file meeting these requirements will be processed as a self-contained postage statement with a status of ‘Error – Duplicate’. This status will allow the mailer and USPS to determine the correct handling of the resulting postage statement. 
If the file represents unique packages that have violated the 180-day uniqueness policy for PICs, an eVS Admin user will process the postage statement and postage will be collected. If the file was received by PRS in error and is redundant data only, an eVS Admin user will close the postage statement and no postage will be collected.
1.7.2	Duplicate Package Adjustment
PRS will ensure revenue protection by identifying multiple packages mailed using the same PIC. The Product Tracking System (PTS) will provide PRS with a weekly extract listing PICs that show activity indicative of multiple packages mailed under a single PIC. Packages delivered to multiple ZIPs, packages delivered on multiple days, and packages receiving a ‘Duplicate’ scan event will be included in this extract. 
PRS monthly reconciliation will include an additional adjustment for Duplicate Packages when applicable. Mailers will be assessed an average per piece charge for these packages. The average per piece charge will be calculated based on the unmanifested per piece charge logic used in the system today.
1.7.3	Error Warning Report
PRS will generate an Error-Warning (EW) report containing all unique PRS errors and warnings. This report will be returned to PTS for inclusion with the Confirmation-Error-Warning (CEW) report PTS provides to the mailers for each manifest file received. The PRS EW report will be provided in the same format used today for the PTS CEW report.
For any Header Record with an error or warning, PRS will include the Header Record or Transaction ID, EFN (or sub-header record), Mailing Date, Transmission Date, PRS Status – error or warning, and PRS Message – detailing the error or warning. A PRS Header Record error indicates that postage has not been collected for any associated PICs; all PRS Header Record errors are also displayed in the Manifest Header Error Report in PRS.
PRS will mimic the PTS model and aggregate this data by linking PIC-level data with the appropriate EFN. For any Detail Record with an error or warning, PRS will include the PIC, line number, PRS Status – error or warning, and PRS Message – detailing the error or warning. A PRS Detail Record error indicates that postage has not been collected for that PIC; all PRS Detail Record errors are also displayed in the Manifest Detail Error Report in PRS. Manifest Detail Error records may be corrected by submitting a corrected detail record using the same PIC on a new manifest prior to the 10th of the subsequent month (i.e. the end of the Mailer Reconciliation period).
1.7.4	Postage Extract
PRS will provide a Postage Extract containing piece-level postage payment information. This report will be returned to PTS for the mailer to retrieve from their password-protected FTP site. Mailers may choose to receive the postage extract, or an extract with piece-level data omitting postage payment information. Individual mailers may also opt not to receive the Postage Extract.
PRS will include the following information for each Header Record: the Header Record or Transaction ID, CAPS Transaction ID, EFN (or sub-header record), Mailing Date, Transmission Date, and Entry Facility ZIP.
PRS will mimic the PTS model and aggregate the extract data by linking PIC-level data with the appropriate EFN. PRS will include the following information for each Detail Record: PIC, Mail Class, Processing Category, Weight, Length, Height, Width, Dimensional Weight, Destination ZIP, Destination ZIP+4, Destination Rate Indicator, Rate Indicator, Zone, Extra Service Codes (1st, 2nd, 3rd), Fees for Extra Service Codes ((1st, 2nd, 3rd), Discount Type, Discount Amount, Surcharge Type, Surcharge Amount, Manifest Postage, and USPS Calculated Manifest Postage.

1.8	eMIR System
For users with access to Electronic Mail Improvement Reporting (eMIR), the extra white space on the list of individual reports available for viewing will no longer appear. 57111

1.9	Test Environment for Mailers 
The following impacts all mailers using the Test Environment for Mailers (TEM): 
The downloadable version of the Periodicals Postage Statement Register will defaults to a Microsoft Excel (.xls) file. Previously, users had to change the file extension to .xls from a Web page (.html) in the Test Environment for Mailers (TEM). 39356
Mailers with access to MicroStrategy reports will be able to access those reports for the Test Environment for Mailers (TEM) environment. Previously, these reports were only available to mailers in the live environment. 58728
Note:  To view the Postage Statement Register, click Dashboard (PostalOne!) in the Business Customer Gateway, then search for the postage statement. Open the postage statement, then click Register. To view Microstrategy reports, click Mailing Reports (PostalOne!) in the Business Customer Gateway, then click Mail Quality Reports.

NOTE:  If you have any questions or need any assistance regarding the PostalOne!® system please contact our PostalOne!® Help Desk at 1 – 800 – 522 – 9085.

Appendix A – Changes to Version 5

The following table represents the changes from the previous version of release notes for PostalOne! Release 25.0.0.  
Note:  Section numbers referenced below reflect numbers after additions/deletions have been made and may not correspond with the section numbers of the original (or revised) document.  Minor grammatical and spelling changes made are not included in the table below.

Section	Change Type	Change	
	Add	The following release note was added to various sections within the External Release Notes:
The footers on the bottom of all PostalOne! pages have been standardized to offer the same information and features as other USPS.com pages. 59915
	
Chapter 1 Introduction	Remove	The following phrase was deleted from the introductory statement of Chapter 1:
“Address Change Service ACS™ and”

The statement is related to assessments for non-compliance.	
1.1.1.2
Full-Service ACS Billing
Non Full-Service	Change	The release note for Non-Full Service in section 1.1.1.2 was changed
From:
In cases of mailpieces with a Full-Service Service Type Identifier (STID) that cannot be immediately matched to eDoc, USPS will attempt to find matching eDoc for 35 days. After this period, the mail owner and data recipient CRID will be determined based on the Mailer Identification Number (MID) from the Intelligent Mail barcode (IMbTM) on the mailpiece. These identified data recipients will be charged for ACS data, which will be available through the normal PostalOne! ACS fulfillment.

To:
Mailpieces with a Full-Service Service Type Identifier (STID) that cannot be matched to eDoc,will not be fulfilled. 
	
1.1.1.3
Full-Service ACS Billing
Invoices		The release note in the Invoice section 1.1.1.3 of Full-Service ACS Billing was changed:
From:
Invoices and statements for Full-Service ACS charges will be mailed to the address in the Customer Registration system for the identified Mail Owner in eDoc.  Non Full-Service invoices and statements will be mailed to the address (in the Customer Registration system) for the owner of the Mailer ID in the IMb™ on the mailpiece. Invoices will normally be mailed on the 24th of each month, though if the balance owed is less than $50, invoices will be mailed on March 24th and September 24th of each year. Payment must be submitted with a copy of the invoice within 30 days of invoice date.

To:
Mail Owners will be invoiced for Full-Service ACS charges.
•	Mail Owner is determined based on MID / CRID from the eDoc
o	Identified by MID – invoice will be sent according to ACS OneCode profile if available
o	Identified by CRID, Permit, or MID with no OneCode profile – invoice will be sent to CRID the MID is linked to in the Mailer ID system (no data distribution profile will be used)
Invoices will normally be mailed on the 24th of each month, though if the balance owed is less than $50, invoices will be mailed on March 24th and September 24th of each year. Payment must be submitted with a copy of the invoice within 30 days of invoice date.	
1.1.1.4
Delinquent Accounts	Add	The following statement was added to release note in section 1.1.1.4 for Delinquent Accounts:
The 10% interest applies, but the account will not be deactivated immediately.  	
1.1.2
Full-Service eDoc Verification and Assessment	Change	The eDoc Verification Report name was changed to Full-Service Error Report in section 1.1.2	
1.1.2
Full-Service eDoc Verification and Assessment	Change	The last two paragraphs in section 1.1.2 Full Service eDoc Verification and Assessment was changed:
From:
The PostalOne! system will create the Full-Service eDoc Verification Error report 30 days after the job is completed in PostalOne! or 30 days after the mailing date of the last finalized postage statement, whichever comes first. PostalOne! considers a job complete when the total pieces for finalized postage statements matches the total pieces in the qualification report. The Full-Service eDoc Verification report will provide information to identify the specific job found with errors and the additional postage charges. The report will identify an additional postage charge for a job as Unpaid status for three days. The mailer will have the option to pay the additional postage charge from a single or multiple permits or request a reconciliation of the charges. If the additional postage is not paid or a reconciliation is not requested, the system will change the status to Overdue after three days. If the additional postage is paid, the job will be marked as Paid. If a reconciliation is requested, the job will be placed in a Pending Review status. When the helpdesk completes the review, the mailer will be notified of the results and the job will be updated to a Reviewed - Payment Required status, if additional postage still applies, or a Closed status, if no additional postage charges apply. If no payment is made on the Reviewed - Payment Required status, the system will change the status to Overdue after three days. The Postal Service will work with mailers to secure payment of the additional postage charges for any jobs that are in the overdue status.
A new, Business Service Administrator Verification Assessment Evaluator (VAE), service type will be added to the Business Customer Gateway. The VAE BSA will
•	Receive email notifications or online popup messages alerting them of a Full-Service eDoc Verification Error report
•	Gain access to the PostalOne! Full Service eDoc Verification Error report
•	Make payments through the report for additional postage charges
Details of the Full-Service eDoc verification process are communicated in an updated version of the Guide to Intelligent Mail for Letters and Flats published in June 2010.
To:
The PostalOne! system will create the Full-Service Error report 30 days after the job is completed in PostalOne! or 30 days after the date the last postage statement was finalized, whichever comes first. The PostalOne! system considers a job complete when the total pieces for finalized postage statements matches the total pieces in the qualification report. The Full-Service Error report will provide information to identify the specific job found with errors and the additional postage charges.   The report will provide functionality to allow the eDoc submitter to make payment for the assessment or request reconciliation of the identified errors.  The reconciliation request will be sent to Remediation Team/Help Desk for review:  The Help Desk will review/investigate the reconciliation request and notify mailer of review results.  
While the discount removal will not be activated in this release, Mailers are encouraged to take advantage of the reconciliation process and use the feedback to correct Full-Service verification errors prior to the implementation of the Full-Service Discount Removal on January 2, 2011. Mailings completed prior to January 2, 2011 will not be subject to loss of the Full-Service discount.
A new, Business Service Administrator Verification Assessment Evaluator (VAE), service type will be added to the Business Customer Gateway. The VAE BSA will
•	Receive email notifications or online popup messages alerting them of a Full-Service eDoc Verification Error report
•	Gain access to the PostalOne! Full-Service Error Report
•	Make payments through the report for additional postage charges
The Business Service Administrator Verification Assessment Evaluator (VAE) may delegate the VAE service to other BSAs and approve users for the VAE service.  All BSAs and users will receive email notifications or on-line pop-up notices while accessing the PostalOne! system. 
•	An email notification for the Full-Service eDoc verification errors will be sent if an established threshold is exceeded:
–	If the total amount of disqualified postage is greater than $150  and 
–	The number of compliant pieces is greater than 70%
•	The email notification is sent to the mailer’s appropriate Verification Assessment Evaluator (VAE) 
–	The VAE is assigned by mailers for each CRID (business location)
Details of the Full-Service eDoc verification process are communicated in the June 2010 version of the Guide to Intelligent Mail for Letters and Flats.
	
1.2
Enterprise Administration (eAdmin)	Add	Added section 1.2 Enterprise Administration (eAdmin) and subsections 1.2.1 to the release notes with the following notes.  The numbering for subsequent sections of the release notes have incremented based on the addition of this section.
1.2  Enterprise Administration (eAdmin)
1.2.1  Business Service Administrator
1.2.1.1  Reaccepting the Online Agreement
On November 1, 2010, new Enterprise Administration functionality will be implemented to enable the USPS to update the online agreement and existing external Business Services Administrators (BSA) to reaccept the new agreement.
The grace period to reaccept the new agreement is configured for November 1 through December 15th.  At the start of the period, the new BSA agreement will be replaced with the existing one. During this period, BSAs and associated users may still access the service and location combinations, but the new online agreement must be reaccepted during the grace period. The BSA can defer reacceptance until the final day of the grace period. A ‘New BSA Agreement’ link will be enabled and pop-up reminders will display throughout the grace period. At the end of the grace period and where the BSA did not reaccept, the BSA and all affiliated users’ access at that service and location combination will be disabled.
	
1.3.2
Manage Permits	Remove	The following statement was removed from the release notes in section 1.3.2, Manage Permits:

The Nonprofit Authorization Number will be displayed on the following screens:  Permit Entry, Account Verification and Confirmation.
	
1.3.2
Manage Permits	Change	The following release note was changed and rearranged in section 1.3.2 Manage Permits:
From:
The Postal One! system will distinguish Additional Postage accounts as “AP” wherever 2 character permit types are displayed.  This will distinguish Permit Imprint accounts from Additional Postage accounts.  

To:
The Postal One! system will display “Additional Postage” for ADD-POS accounts wherever the name of the permit type is written out. The system shall display “AP” as the permit type for permit imprint accounts. This will distinguish Permit Imprint accounts from additional postage accounts.
 	
1.3.2
Manage Permits	Change	The bullets for the release notes in this section were changed
From:
•	Text revisions will be made on several screens to use terminology more consistent with other USPS systems and provide better instructions to users.  Graphical improvements will also be made across the screens to improve user experience, which includes a new navigation menu similar to other PostalOne! Mailer pages off Business Customer Gateway, removal of irrelevant display fields on screens, and additional sorting capabilities on tabs displayed within Manage Permits.
•	The PostalOne! system will prompt a user to update name and address information on permit account records based on the current CRID information stored in users’ Business Customer Gateway profiles.
•	Permit Validation will be improved for BSA users to enhance the address checking performed during validation attempts and to store failure reasons in the PostalOne! system database.
To:
•	Text revisions will be made on several screens to use terminology more consistent with other USPS systems and provide better instructions to users.  Graphical improvements will also be made to improve user experience, which includes a new navigation menu similar to other PostalOne! Mailer pages of the Business Customer Gateway. Other changes include removal of irrelevant display fields on screens, and additional sorting capabilities on tabs displayed within Manage Permits.
•	The PostalOne! system will as a back end process update name and address information on permit account records if there is a CRID match between permit records and information stored in Business Customer Gateway profiles.
•	Permit Validation will be improved for BSA users by enhancements to the address checking performed during validation attempts and by storing failure reasons currently displayed to the user but not visible to the PostalOne! Help Desk.
	
1.4.2
Electronic Data Exchange
	Change	The following release note in section 1.4.2 was changed
From:
Mailers will not be able to cancel files submitted using Mail.dat files or Mail.XML messaging if the job has been frozen for processing by a postal employee. Previously, a defect allowed such jobs to be cancelled. 50327

To:
Mailers can no longer cancel files by submitting Mail.dat files or Mail.XML messages if the job has been frozen for dashboard processing by a postal employee. Previously, a defect allowed such jobs to be cancelled. 50327
	
1.4.2.1.1
Mail.dat Client Application	Add	The following release notes were added to section 1.4.2.1.1 :
When a Mail.dat job was rejected due to a validation failure, users were sometimes unable to view the validation errors on the Job Validation / Upload Details screen.  The problem was intermittent and only affected users when they had a Job ID that was used by another mailer with a different provider code.  The PostalOne! system has been updated to properly retrieve submission history information for the job, so that the validation errors are always displayed.  61349
The standard error output by the Java API for XML Web Services (JAX-WS) library will now only include error messages. Previously, informational messages were also included which affected the internal error handling processes of some mailers. 59376	
1.4.2.1.2.a
Mail.dat Processing
General	Add	The following release notes were added to section 1.4.2.1.2.a:
Postage statement generation will include all statements in a mailing, even if Carrier Sequencing Date is not included. Previously, statement generation did not include child statements if this date was blank, even when the date was not required for the prices claimed. 58688 
When there is only one billable postage statement (for MLOCR or list mail) the PostalOne! system will no longer generate a master statement for one billable postage statement (MLOCR or otherwise). The billable statement will include all detailed information and postage verification features. 56487
The PostalOne! system will no longer use the Full Service Participation Indicator field in the .seg file as a postage statement generation variable for Non Periodical postage statements. 60009
	
1.4.2.1.2.a
Mail.dat Processing
General
Priority Mail	Add	Add the following release note to Priority Mail in  section 1.4.2.1.2 Mail.dat Processing:
•	Priority Mail
The system will be discontinuing support of Priority Mail in Mail.dat effective with the deployment of Release 26.0 (January, 2011).  There are currently issues recorded related to Priority Mail and Mail.dat, however because of the discontinued support of Priority Mail in Mail.dat the Postal Service will not expend resources to resolve those issues in this release (Release 25.0).  Users may continue to submit Priority Mail files until January, 2011 as some functionality does remain in Mail.dat and will work correctly
	
1.4.2.1.2.a
Mail.dat Processing
General
Periodicals	Remove	The following release note was removed from section  1.4.2.1.2 Mail.dat Processing:
For Mail.dat jobs with Government Periodicals having a Federal Agency Code, the system will allow the In-County prices and generate the correct In-County postage line items. [28924, SRS 352, part 3.25]
	
1.4.2.1.2.a
Mail.dat Processing
General
Periodicals	Change	Change the release note in section 1.4.2.1.2.a Mail.dat Processing
From:
The PostalOne! system was incorrectly calculating periodical container charges. Mailers do not pay the container price for carrier route, 5-digit carrier routes, and 5-digit/scheme pallets, sacks, and tray for containers with a mixture of In-County and Out-County pieces. The system will be updated to ensure that the postage statement is generated correctly and that the mailer will no longer be charged for these pieces. 60988. 

To:
The PostalOne! system was incorrectly calculating Periodicals container charges. In the case that a pallet, sack, or tray, at the carrier route, 5-digit carrier routes, or 5-digit/scheme presort level has a mixture of In-County pieces and Outside County pieces, the system will be updated to ensure that the postage statement is generated correctly and that there is no container charge for this container . Previously, the system incorrectly generated a container charge for this container. 60988.	
1.4.2.1.2.a.
Mail.dat Processing
 General
Copalletization	Add	The following release notes were added to Mail.dat Processing, General in the Copalletization section:
Copalletized jobs with different presentation categories will be accepted when submitted through Mail.dat files. For those cases where MLOCR mail is copalletized with other mail, validation now allows consolidation jobs to claim HDR Mail.dat Presentation Category “P” (Conventional Presort), even if the job includes one or more original MLOCR jobs with HDR Mail.dat Presentation Category “M” (MLOCR).  51028
The PostalOne! system will allow linkage of an origin container of type V, S, 1, 2, 3, 4, 5 to a consolidator container of type V in the .oci file.  Currently, the PostalOne! system validates that container type is the same value when linking origin containers to consolidator containers in the .oci file.  61264.
The PostalOne! system will convert container types of S, 1, 2, 3, 4, 5 to container type of V prior to releasing the data to SASP.  This applies to the origin CSM data, as well as the consolidator’s OCI data.  61265
When an origin job is linked to multiple consolidator jobs, the PostalOne! system will correctly link the origin job handling units (trays) to the consolidator jobs.  The system currently links all of the handling units from the origin job, causing creation of handling units that do not belong to the consolidator job, and have not been created in SASP. 63261
	
1.4.2.1.2.a. 
Mail.dat Processing
 General
Copalletization	Change	Added Team Track reference 61263 to second release note in the Copalletization section of Mail.dat Processing:  1.4.2.1.2.a	
1.4.2.1.2.b
Mail.dat Processing
Validation	Add	The following release note was added to section 1.4.2.1.2.b Validation:
A new validation will be added to prevent a mailer from submitting a PDR and an IMR file within the same job.  Currently, the PostalOne! system accepts mailing with both files present, which creates invalid piece barcodes after postage statement finalization.  54074  
	
1.4.2.1.2.b
Mail.dat Processing General
Validation	Remove	The release note in section  1.4.2.1.2 b Validations has been removed
From: For Mail.dat jobs, a validation will be added that rejects update or change job submissions that change the Segment file if containers on that segment have already been marked as ready to pay.  56888
	
1.4.2.2.1
Mail.XML Processing
General	Add	The following release note was added to section 1.4.2.2.1, Mail.XML Processing – General:
The PostalOne! system now truncates any error messages too long to fit in the logging database. Previously, very large Mail.XML MailPieceCreateRequest messages received corrupted responses if errors resulted from the submission that were larger than the database supports. 61437	
1.4.2.2.1
Mail.XML Processing
General	Change	The ETR reference for Leading Zero was corrected from 56740 to 57640	
1.4.3.1
Postal Wizard
International	Add	The following release note was added to the Postal Wizard section for International Mail:
International postage statements no longer display an “Affixed Account” label next to mailer information when entering a postage statement. 63383
	
1.4.3.3
Postal Wizard
Postage Statement Processing	Add	The following release note was added to1.4.3.3 Postal Wizard Postage Statement processing:
Printed postage statements no longer display the release number at the top of the page. Previously, an obsolete release number was listed. 63069
	
1.4.5.1
Dashboard
Postage Statements	Remove	The following release notes were removed:
Mailers who own part of an electronically-submitted job and are not the preparer of that job will see all results in the verification worksheets, if any are associated with the mailing. 49422
The downloadable Portable Document Format (.pdf) version of postage statement receipt page will match the online version. Previously, Periodicals receipts downloaded in .pdf format displayed incorrect totals. 49562
	
1.4.5.1
Dashboard
Postage Statements	Remove	The ETR reference 58710 attached to the ninth release note in the Postage Statement section 1.4.5.1 was removed.	
1.4.5.1
Dashboard
Postage Statements	Add	The following release notes were added to the Postage Statement section (new number 1.4.5.1):
Finalized postage statements now appear as finalized on the Dashboard if finalization results in a transaction number. Previously, errors during finalization allowed some statements to be billed and receive transaction numbers, but did not update the status of the statement. 52001 54100
The downloadable Portable Document Format (.pdf) version of Periodicals postage statements now correctly reports total postage and total addressed pieces. Previously, pdf generation did not include the classroom or nonprofit discount in total calculations and total addressed pieces always displayed as zero (0), even though all other versions of the postage statement displayed the correct information. 57890 58658
The downloadable postage statements for Standard Mail and Package Services statements now match online statements by displaying weights in pounds to four digits after the decimal. Previously, these statements did not match the online versions of the statement. 59054
Issue-level Periodicals postage statements now display the correct advertising percentage. Previously, a defect displayed the incorrect advertising percentage on issue-level statements. 59211
Limited Circulation Discounts are now included in total postage calculations for issue-level Periodicals postage statements. Previously, this discount was missing. 59923
For a Standard Mail Mail.dat job submitted with pieces that have a price of Single Piece the PostalOne! system will create both the Standard Mail postage statement(s) for the presorted piece prices and the First-Class Mail postage statement(s) for the Single Piece prices. If appropriate, the First Class postage statements will be combined to master statements and the Standard Mail postage statements will be combined to master statements. All postage statements for the job will appear in the same mailing group.  Previously, the system was incorrectly combining the Standard Mail and First Class Mail statements into the same combined statement and causing a timestamp error preventing postage statement finalization.  57428
	
1.4.5.1
Dashboard Postage Statements
	Add	Add the following release note to section 1.4.5.1 and 2.2.6.1 Postage Statements:
The PostalOne! system will use the postage statement number for a non-consolidated child postage statement to update the Total Postage and Total Adjusted Postage fields, to ensure that the postage amounts from sections D and E are added to the correct postage statement.   Previously, the postage amount from sections D and E were added to the first available non-consolidated child statement, since the process was unclear of the correct statement that the postage amount should be added to.  56843
	
1.4.5.2
Dashboard
Qualification Report	Change	The release note in  section 1.4.5.2 was changed
From:
Qualification Reports will receive a few minor changes. The report now highlights rows as necessary, though previously some lines did not display highlighting if the 3DG piece count for AADC Letter Trays exceeded 149 or ADC Flat Trays exceeded 89. All reports now display an accurate piece count. Previously, for some jobs submitted using Mail.dat files, the Qualification Report erroneously counted some pieces twice. Printing the Qualification Report no longer cuts off the sides of the report.  54214 49522 51772

To:
Qualification Reports received a few minor changes. The report now highlights rows as necessary, though previously some lines did not display highlighting if ADC for MADC tray exceeds 89, ADC/5DG/5DGS/3DG/3DGS for Tray ZIP Destination is less than 90, AADC/5DG/5DGS for Tray ZIP Destination is less than 150, 3DG/3DGS claimed at the 3DG/3DGS price for Tray ZIP Destination is less than 150 or 3DG claimed at the 3DG price for ADC Flat Tray exceeds 89. Printing the Qualification Report no longer cuts off the sides of the report.  49522 51772
	
1.4.5.3
Dashboard
Reconciliation Report	Change	The note for ETR 54089 (report now displays the correct total postage amount. Previously, a rounding error sometimes displayed totals as much as five cents wrong.) was removed from  section 1.4.5.3 Reconciliation Report.  The release note now only includes ETRs 54123 and 51767 and reads:
The Reconciliation Report received several minor fixes. Printing the report no longer cuts off the sides of the report. Additionally, for postage statements submitted using Mail.dat files, shortage pieces now count towards the total number of pieces, allowing statements with shortage pieces to be reconciled if all other pieces are accounted for.  54123 51767	
1.4.5.9
Mailing Dates
	Add	The following release notes were added to information regarding Mailing Date in section 1.4.5.9:
The PostalOne! system will record a new date for Earliest Submit Date.  The Earliest Submit Date is the date that the system can receive a new Mail.dat file that contains a Postage Statement Mailing Date that is applicable to the new price change.  A system administrator or a database script will be able to update the Earliest Submit Date during a normal maintenance window.  61385 
The PostalOne! system will record the Submit Date as the date that the Mail.dat file is received.  The Submit Data must occur no sooner than 120 days before the Postage Statement Mailing Date.  If the Earliest Submit Date is in the past, the Earliest Submit Date will be ignored and the legacy rule will be applied: The Postage Statement Mailing Date cannot be earlier than the price change before last..  61388

1.5.1.3
Mail Quality Report	Add	The following release notes were added to section 1.5.1.3  Mail Quality Reports:
The number of pieces and jobs on the Mail Quality Reports now match at all levels of the report as appropriate. Previously, a defect reported the wrong number of pieces and jobs once users chose to narrow down the report. 54288
Mail Quality reports no longer falsely report duplicate Intelligent Mail barcode (IMb) tray barcodes. Previously, Mail.dat jobs with multiple postage statements that were finalized simultaneously resulted in duplicate IMb tray error messages on the report if one tray was shared in multiple statements.  60867
	
1.5.1.5
Issue Level Postage Statement	Remove	The following release note was removed from section  1.5.1.5 Issue Level Postage Statements:
Processing category will be accurate. 57279	
1.6.5
eVS Defect Fixes	Add	The following release notes were added to section  1.6.5 eVS Defect Fixes:
Manifest file loading and processing received some minor performance improvements to increase ease-of-use. 57026
The Corrected Header Error Report is now available to eVS users; previously, the report would not display. Additionally, the title on the report page has been changed to “Corrected Header Error Report” instead of “Header Error Report”.  59989
	
1.9
TEM	Add	Added a Note to section 1.9 – TEM
Note:  To view the Postage Statement Register, click Dashboard (PostalOne!) in the Business Customer Gateway, then search for the postage statement. Open the postage statement, then click Register. To view Microstrategy reports , click Mailing Reports (PostalOne!) in the Business Customer Gateway, then click Mail Quality Reports.