A Guide to Intelligent Mail for Letters and Flats

**December 2008**

**V4**

TABLE OF CONTENTS

[**1** **Purpose** **4**](#purpose)

[2 Intelligent Mail® Requirements 5](#intelligent-mail-requirements)

[2.1 Start-the-Clock Information 8](#start-the-clock-information)

[2.2 Address Correction Information 8](#address-correction-information)

[2.2.1 Future Release: Address Correction Information
8](#future-release-address-correction-information)

[2.3 Mailer ID 9](#mailer-id)

[2.4 Unique Intelligent Mail Barcodes
9](#unique-intelligent-mail-barcodes)

[2.5 Service Type Identifiers 10](#service-type-identifiers)

[2.5.1 Use of Ancillary Service Endorsements and Service Type IDs to
Receive Address Corrections
11](#use-of-ancillary-service-endorsements-and-service-type-ids-to-receive-address-corrections)

[2.5.2 Forms of Address Corrections and Options for Handling
Undeliverable-as-Addressed Mail with Intelligent Mail Barcode
12](#forms-of-address-corrections-and-options-for-handling-undeliverable-as-addressed-mail-with-intelligent-mail-barcode)

[2.5.3 Ancillary Service Endorsements with Basic or Full-Service
Mailings
13](#ancillary-service-endorsements-with-basic-or-full-service-mailings)

[2.5.4 Precedence of Ancillary Service Endorsements and Service Type ID
Values
14](#precedence-of-ancillary-service-endorsements-and-service-type-id-values)

[2.5.5 Electronic Service Requested 14](#electronic-service-requested)

[2.5.6 Quick Service Guide Listing of Service Type Identifiers
15](#quick-service-guide-listing-of-service-type-identifiers)

[2.5.7 First-Class Mail Service Type Identifiers
16](#first-class-mail-service-type-identifiers)

[2.5.8 Standard Mail Service Type Identifiers
20](#standard-mail-service-type-identifiers)

[2.5.9 Periodicals Service Type Identifiers
25](#periodicals-service-type-identifiers)

[2.5.10 Bound Printed Matter Service Type Identifiers
29](#bound-printed-matter-service-type-identifiers)

[3 Electronic Mailing Documentation and Postage Statements
33](#electronic-mailing-documentation-and-postage-statements)

[3.1 Mixed Mailings 35](#mixed-mailings)

[3.2 Future Release: Combined Mailings of Standard Mail and Periodicals
36](#future-release-combined-mailings-of-standard-mail-and-periodicals)

[3.3 Copalletization 36](#copalletization)

[3.3.1 Periodicals Scenario 37](#periodicals-scenario)

[3.3.2 Standard Mail Flat-size Bundles Scenario
38](#standard-mail-flat-size-bundles-scenario)

[3.3.3 First-Class Mail in Trays Scenario
40](#first-class-mail-in-trays-scenario)

[3.3.4 Standard Mail in Trays Scenario
42](#standard-mail-in-trays-scenario)

[3.4 Future Release: Manifest Mailings
44](#future-release-manifest-mailings)

[3.5 Spoilage and Shortage 44](#spoilage-and-shortage)

[3.5.1 Piece Level Spoilage and Shortage
46](#piece-level-spoilage-and-shortage)

[3.6 Multi-Line Optical Character Reader (MLOCR) Mailers
46](#multi-line-optical-character-reader-mlocr-mailers)

[3.7 Continuous Mailers 47](#continuous-mailers)

[3.8 Customer Supplier Agreements (CSA)
48](#customer-supplier-agreements-csa)

[3.8.1 Using the *PostalOne!* Transportation Management System
49](#using-the-postalone-transportation-management-system)

[3.8.2 Applying the Customer Supplier Agreement
49](#applying-the-customer-supplier-agreement)

[3.9 Creating Appointments 50](#creating-appointments)

[3.9.1 Joint Scheduling: 50](#joint-scheduling)

[3.10 Mail.dat 53](#mail.dat)

[3.10.1 Mail.dat 09-1 -- *PostalOne!* System Implementation
53](#mail.dat-09-1-postalone-system-implementation)

[3.10.2 Piece Electronic Documentation for Non-Sequential Intelligent
Mail Barcodes
53](#piece-electronic-documentation-for-non-sequential-intelligent-mail-barcodes)

[3.10.3 Piece Electronic Documentation for Sequential Intelligent Mail
Barcodes
54](#piece-electronic-documentation-for-sequential-intelligent-mail-barcodes)

[3.10.4 Handling Unit Information 55](#handling-unit-information)

[3.10.5 Container Information (Pallets or APC)
56](#container-information-pallets-or-apc)

[3.10.6 Postage Information 58](#postage-information)

[3.10.7 Future Release: Mail.dat Owner/Mailing Agent Updates
59](#future-release-mail.dat-ownermailing-agent-updates)

[3.11 Mail.XML 59](#mail.xml)

[3.12 Future Release: Electronic Documentation Using Mail.XML (formerly
Wizard Web Services)
60](#future-release-electronic-documentation-using-mail.xml-formerly-wizard-web-services)

[3.12.1 Mail.XML™ Version 6.0 Changes - *PostalOne!* System
Implementation
60](#mail.xml-version-6.0-changes---postalone-system-implementation)

[3.12.2 Piece Electronic Documentation for Non-Sequential Intelligent
Mail Barcodes
60](#piece-electronic-documentation-for-non-sequential-intelligent-mail-barcodes-1)

[3.12.3 Piece Electronic Documentation for Sequential Intelligent Mail
Barcodes
61](#piece-electronic-documentation-for-sequential-intelligent-mail-barcodes-1)

[3.12.4 Container Information (Pallets or APCs)
63](#container-information-pallets-or-apcs)

[3.12.5 Appointment Information 65](#appointment-information)

[3.12.6 Postage Information 65](#postage-information-1)

[3.13 Postal Wizard (PW) 65](#postal-wizard-pw)

[3.13.1 Piece Electronic Documentation for Sequential Intelligent Mail
Barcodes
65](#piece-electronic-documentation-for-sequential-intelligent-mail-barcodes-2)

[3.13.2 Piece Electronic Documentation Using Mailing ID
65](#piece-electronic-documentation-using-mailing-id)

[3.13.3 Postage Information 65](#postage-information-2)

[3.14 Mail Owner and Mail Preparer Identification in Electronic
Documentation
66](#mail-owner-and-mail-preparer-identification-in-electronic-documentation)

[3.14.1 Non-Sequential Piece Identifiers
66](#non-sequential-piece-identifiers)

[3.14.2 Sequential Piece Identifiers 67](#sequential-piece-identifiers)

[3.14.3 Order of Preference 67](#order-of-preference)

[3.14.4 Obtaining a Mail Owner CRID 68](#obtaining-a-mail-owner-crid)

[4 Mailer Feedback 70](#mailer-feedback)

[4.1 Overview 70](#overview)

[4.2 Available Feedback 70](#available-feedback)

[4.2.1 Start-the-Clock for BMEU Mail 71](#start-the-clock-for-bmeu-mail)

[4.2.2 Start-the-Clock for Drop Ship and Origin Entered Mail Transported
by Mailer
71](#start-the-clock-for-drop-ship-and-origin-entered-mail-transported-by-mailer)

[4.2.3 Start-the-Clock for Plant-Load Mail
72](#start-the-clock-for-plant-load-mail)

[4.2.4 Start-the-Clock Using Customer Supplier Agreements
73](#start-the-clock-using-customer-supplier-agreements)

[4.2.5 Full-Service Container Visibility
73](#full-service-container-visibility)

[4.2.6 Full-Service Change of Address Detail Report
74](#full-service-change-of-address-detail-report)

[4.2.7 Full-Service Nixie Detail Report
74](#full-service-nixie-detail-report)

[4.3 Full-Service Data Provisioning to Multiple Parties
75](#full-service-data-provisioning-to-multiple-parties)

[4.4 Data Distribution to Third-Parties
75](#data-distribution-to-third-parties)

[4.5 Profile Set-up 76](#profile-set-up)

[4.5.1 Static Relationships 76](#static-relationships)

[4.5.2 Dynamic Relationships 76](#dynamic-relationships)

[Appendix A: Service Type Identifier Matrix
78](#appendix-a-service-type-identifier-matrix)

[Appendix B: Data Distribution Scenarios
115](#appendix-b-data-distribution-scenarios)

[OneCode ACS Scenarios 115](#__RefHeading___Toc216230347)

[Confirm Scenarios 118](#__RefHeading___Toc216230348)

[Start-the-Clock Scenarios 120](#__RefHeading___Toc216230349)

[Multiple Services 121](#__RefHeading___Toc216230350)

[Appendix C: Data Distribution Scenario Chart
123](#appendix-c-data-distribution-scenario-chart)

[Appendix D: Future Capabilities and Development Resources Mapping
126](#appendix-d-future-capabilities-and-development-resources-mapping)

Change Log -- Version 3

-   Section 2: Added nonautomation definition for Intelligent Mail
    barcoded mailpieces.

-   Section 2.2: Added BPM defintion for Address Correction Information.

-   Section 2.2: Updated Periodical ACS data matching rules.

-   Section 2.4: Clarified rules for Intelligent Mail barcode
    uniqueness.

-   Section 2.5.2: Clarified the section applies to pieces with
    Intelligent Mail barcodes.

-   Section 2.5.6: Added columns for Service Type IDs for nonautomation
    mailpieces.

-   Section 2.5.8.3.5: Updated Service Type IDs for ECR mailpieces.

-   Section 3: Updated language for Postal Wizard.

-   Section 3.8.2.1: Clarified how to update eDoc for unscheduled trips.

-   Section 3.9.2: Clarified required piece documentation for POSTNET
    mailpieces.

-   Section 3.9.3: Removed restriction on including ECR mailpieces in
    IMR file.

-   Section 4.4.9: Clarified timing rules for submitting electronic
    documentation and Cast of Characters for third-party data
    distribution.

-   Various: Removed references to PDR.XML.

Change Log -- Version 4

-   Change Request 001: Clarification of Uniqueness Between Basic and
    Full-Service

-   Change Request 003: Add Agency Scenario to Cast of Characters

-   Change Request 004: Wording Change to 3.4 (IM Barcode Lower
    Repeated)

-   Change Request 005: Add Appendix D "Future Capabilties and
    Development Resource Mapping"

-   Change Request 006: Replace Mail.XML 5.0 with Mail.XML 6.0

-   Change Request 007: Clarification of Spoilage Section

-   Change Request 008: Update to Feedback Methods

-   Change Request 009: Update to Reflect IMR

-   Change Request 011: Better Define Non-automation

-   Change Request 012: Add FAST Joint Scheduling Details

-   Change Request 013: Update Mail.XML Message Names

-   Change Request 014: Update to Reflect Release 1

-   Change Request 015: Cast of Characters Timing

# Purpose

This **Guide to Intelligent Mail Letters and Flats** is intended to
provide technical solutions to questions arising from the Federal
Register Notice named "Implementation of New Standards for Intelligent
Mail® Barcodes" that can be found at
<http://pe.usps.com/FederalRegisterNotices.asp>. You should be familiar
with that notice prior to reading this guide. The solutions in this
guide are intended for implementation concurrently with the requirements
in the Federal Register notice, currently scheduled for May, 2009. This
guide:

-   Provides details on the changes required to existing electronic
    documentation solutions needed to support full-service and basic
    mailings.

```{=html}
<!-- -->
```
-   Provides guidance on how to prepare your mail and electronic
    documentation in compliance with full-service and basic
    requirements.

-   Provides direction on Service Type Identifiers and ancillary service
    endorsements used for the full-service and basic options.

-   Identifies the data that will be provided at no additional charge
    for full-service compliance.

In addition, this guide also describes what will be available in the
first release of the Intelligent Mail Program. Where noted, it
additionally describes what functionality will be included in a future
release. Reference the Intelligent Mail Timeline for the timing of the
various Intelligent Mail Program releases.

Those unfamiliar with electronic documentation today should begin their
study with the *PostalOne!*® Getting Started Guide which can be found at
<http://www.usps.com/postalone/guides.htm>. The PostalOne! Getting
Started Guide discusses the benefits of electronic documentation and how
to participate in electronic documentation programs. Additional
resources about the various electronic documentation solutions can be
found in the Guides and Tools section on the *PostalOne!* website at
<http://www.usps.com/postalone/guides.htm>.

For those familiar with existing electronic documentation solutions,
this document will help you understand the changes required to implement
the full-service option. This document will describe how you should
populate your electronic documentation files and how you must create or
update your electronic appointments to comply with the full-service
option.

This document also describes the information that will be available from
full-service mailings. Mailings that comply with full-service
requirements will be provided start-the-clock and address correction
information for mailings/mailpieces that comply with full-service
requirements.

**Note: All references to specifications in this document are subject to
update as operational or pricing initiative details are finalized.**

# Intelligent Mail® Requirements

We are offering two options for using Intelligent Mail® (IM) barcodes: a
basic option and a full-service option. A nonautomation mailpiece may
also carry an Intelligent Mail barcode.

**Nonautomation**

With the implementation of the Intelligent Mail® barcode, the option
will still exist to submit mailpieces that carry an Intelligent Mail
barcode but that do not receive automation prices.  At a minimum, the
nonautomation Intelligent Mail barcode will include a USPS-assigned
Mailer ID, the class of mail indicated in a Service Type ID field, and
the optional endorsement line (OEL) information in the Barcode ID field
if an OEL is printed on a flat-sized mailpiece.  The mailpiece may also
include routing information in the ZIP Code field (no ZIP, 5-digit ZIP,
9-digit ZIP and 11-digit ZIP allowed).  There is also a Serial Number
field that may be populated with any numbers the mailer chooses.

**Basic Option**

For the basic option, mailers use the Intelligent Mail® barcode on their
letter and flat-sized mailpieces. At a minimum, the basic option
Intelligent Mail barcode will include the same CASS certified delivery
point information that is included in the current POSTNET barcode, a
USPS assigned Mailer ID, the class of mail indicated in a Service Type
ID field, and the optional endorsement line (OEL) information in the
Barcode ID field if an OEL is printed on a flat-sized mailpiece. There
is also a Serial Number field that may be populated with any numbers the
mailer chooses.

**Full-Service Option**

Full-service mailings require unique Intelligent Mail barcodes on
mailpieces, unique Intelligent Mail tray labels used on trays and sacks,
and unique Intelligent Mail container labels used on pallets or other
containers (when containerized). The Intelligent Mail barcode on the
full-service mailpieces must indicate the Mail Class using a Service
Type ID, a USPS assigned Mailer ID, OEL information in the Barcode ID
field, if an OEL is used on a flat-sized mailpiece, delivery point
routing code information that has been CASS certified, and unique serial
numbers in the Serial Number field. Additional requirements include the
use of an approved electronic method to transmit postage statements and
mailing documentation to the USPS. This documentation describes how
mailpieces are linked to trays or sacks, and to containers (if
applicable), and is required to match the preparation of the mail to
qualify for the full-service option. FAST will be used, as defined in
the customer/supplier agreement, to create appointments for origin
entered mail that is transported by the mailer. The FAST system is also
used to schedule appointments for dropshipment mailings (except for
mailings entered at a DDU), which typically do not require a
customer/supplier agreement.

Complete information on how to populate and create Intelligent Mail®
barcodes for your mailpieces, Intelligent Mail tray barcodes for
handling units and Intelligent Mail container barcodes for containers
can be found at <http://ribbs.usps.gov/>.

The following table shows, by price categories, the availability of
full-service features. 

A checkmark in the ACS column means that pieces of the mail category
shown in the left column that are prepared in accordance with the
full-service standards can receive ACS notifications at no extra
charge.  An \"x\" means that if ACS is available, the applicable ACS
prices apply. 

A checkmark in the Price column means that pieces of the mail category
in the left column that are prepared in accordance with the full-service
standards are eligible for the applicable price differential in the Fall
of 2009.  Those price differentials, which may vary by mail category,
will be included in the prices expected to be announced in February
2009. 

   

While \"Start-the-Clock\" applies to a mailing, a checkmark means that a
full-service mailing with volume from the mail category in the left
column would generate Start-the-Clock information that would be provided
to the Mail Owner and Mail Preparer.  An \"x\" means that a mailing made
up exclusively of this mail category is not eligible for the
full-service option.

  ------------------ --------------------------------- --------------------- ----------- -----------
  **Mail Category**                                    **Start-the-Clock**   **ACS**     **Price
                                                                                         Fall 2009**

  **First-Class                                        ** **                              
  Mail**                                                                                 

                     Automation Letters                                                

                     Automation Flats                                                  

                     Automation Cards                                                  

                                                                                         

  **Standard Mail**                                    ** **                              

                     Automation Letters                                                

                     Automation Flats                                                  

                     Basic ECR Letters                                                 

                     High-Density ECR Letters                                          

                     Saturation ECR Letters                                            

                     Basic ECR Flats                                        *x*         

                     High-Density ECR Flats                                 *x*         

                     Saturation ECR Flats              *x*                   *x*         *x*

                                                                             * *         * *

  **Periodicals -                                      ** **                              
  Outside-County**                                                                       

                     Barcoded Letters                                                  

                     Barcoded Machinable Flats                                         

                     Barcoded Nonmachinable Flats                                      

                     Carrier Route Basic Letters/Flats                                 

                     Carrier Route HD Letters/Flats                                    

                     Carrier Route Sat. Letters/Flats                                  

                     ** **                             *** ***                           

  **Periodicals -                                      ** **                              
  In-County**                                                                            

                     Automation Letters                                                

                     Automation Flats                                                  

                     Carrier Route Basic Letters/Flats                                 

                     Carrier Route HD Letters/Flats                                    

                     Carrier Route Sat. Letters/Flats                                  

                     ** **                             *** ***                           

  **Bound Printed                                      ** **                              
  Matter**                                                                               

                     Barcoded Presort Flats - non-DDU                                  

                     Barcoded Presort Flats - DDU                           *x*         

                     Barcoded CR Flats                                      *x*         
  ------------------ --------------------------------- --------------------- ----------- -----------

***Figure 1: Mail Eligible for Full-Service***

Only the types of letters and flats in the above table are eligible for
full-service when they have Intelligent Mail barcodes with correct
delivery point routing codes and other fields as required by standards,
and when they are part of mailings that meet all other full-service
requirements per DMM standards.

The following are among those not eligible for full-service benefits or
prices:

-   First-Class Mail letters and flats mailed at nonautomation presorted
    prices

-   First-Class Mail letters and flats mailed at single-piece prices

-   Letters of any class mailed at nonautomation prices (either
    machinable or nonmachinable)

-   Periodicals nonbarcoded letters and flats

-   Standard Mail flats mailed at nonautomation prices

-   Standard Mail flats mailed at saturation ECR prices

-   Bound Printed Matter nonbarcoded flats

## Start-the-Clock Information

Full-service mailers who submit electronic documentation for their
mailings will receive information stating when their mail is inducted.
This information will be provided to the Mail Preparer and the Mail
Owner as identified in the By/For section of the electronic
documentation submitted with the mailing. Start-the-Clock data will not
be sent until the mailing has been verified and accepted by the USPS.

## Address Correction Information

Mailers will qualify for address correction notices at no additional
charge by both participating in the full-service option and using the
address correction information to update their address records.

### Future Release: Address Correction Information 

Mailers who do not update an address record after notification may be
charged for subsequent change-of-address (COA) and
undeliverable-as-addressed (Nixie) notices for that address. A COA
notice will be considered duplicate if the same name/address combination
is provided to the Mail Owner as identified in the electronic
documentation within a specified period of time. Similar procedures will
be used to determine if a Nixie notice to the same Mail Owner for the
same delivery point is a duplicate.

Mailers of First-Class Mail full-service pieces will receive all COA and
Nixie address correction records without additional charges for
subsequent notices. There will be no limit on the number or the length
of time that address correction notices will be provided. Compliance
with the Move Update standard remains required, and mailers must meet
this requirement regardless of their receipt of address correction
notices at no additional charge.

Mailers of Standard Mail and Bound Printed Matter (BPM) full-service
pieces will receive the first unique COA/Nixie notice at no additional
charge. Subsequent notices for the same COA record or Nixie notice will
continue to be provided at no additional charge for 30 calendar days
after the initial notice. Beginning on the 31st day after the COA/Nixie
notice is first made available to the mailer, the mailer will be charged
for subsequent notices provided for the same COA record or Nixie notice.
The price will be the current price in effect for additional automated
notices for Standard Mail letters and for electronic notices for
Standard Mail or Bound Printed Matter flats. Compliance with the Move
Update standard for Standard Mail mailpieces remains required, and
mailers must meet this requirement regardless of their receipt of
address correction notices at no additional charge.

Periodicals full-service mailers will receive the first unique COA/Nixie
notice at no additional charge. Subsequent notices for the same COA
record or Nixie will be at no additional charge for 60 calendar days
after the initial notice. Beginning on the 61st day after the COA/Nixie
notice is first made available to the mailer, the mailer will be charged
for subsequent notices provided for the same COA record or Nixie notice.
The price will be the current price in effect for electronic notices.

Charges for additional address correction notices will be applied by
mail class. Address correction notices provided for one class of mail
will not be considered in determining charges for address correction
notices within another class of mail.

Address correction notices outside the free window will be charged to
the permit originally used to pay for the mailpiece. The owner of the
permit will have access to an online metrics report tracking the number
of COA/Nixie records charged to the permit by MID on the mailpiece.

COA and Nixie records generated as a function of full-service usage will
be provided to the Full-Service System. The Full-Service System will be
responsible for providing COA/Nixie records to mail owners (or
designated recipients), tracking the number of notices over time,
determining the additional charges due and transmitting the appropriate
permit information and fees to PostalOne!. The system will also furnish
the keyline information, if this is included in the electronic
documentation, as part of the address correction information under the
full-service option.

## Mailer ID

The Mailer ID (MID) is a unique 6-digit or 9-digit numeric code assigned
to mailers based on their annual mail volumes. A Mailer ID is required
in all Intelligent Mail barcodes and is used to identify the Mail Owner
or Mail Preparer of the mailpiece and to send information to the company
associated with the MID regarding the quality of their mailings.

Under the full-service option, when Mail Owners elect to use their own
6-digit or 9-digit Mailer ID and unique serial numbers for mailpieces,
Mail Preparers will be required to honor the 6-digit or 9-digit Mailer
ID and unique numbering as architected by the Mail Owner. Regardless of
whose Mailer ID is in the Intelligent Mail barcode, identification of
the Mail Owner must be included in the electronic documentation, as
explained in the Mail Owner and Mail Preparer Identification part of the
Electronic Documentation section of this document.

Those interested in obtaining a Mailer ID should contact their local
Bulk Mail Entry Unit (BMEU). BMEU personnel will assist mailers in
completing a Mailer ID application form and obtaining a Mailer ID. The
form can also be found at <http://ribbs.usps.gov/>.

## Unique Intelligent Mail Barcodes

Basic-option mailpieces may carry a unique Intelligent Mail barcode but
uniqueness is not required. In contrast, full-service option mailpieces
are required to have a unique Intelligent Mail barcode on the mailpiece,
and unique tray/sack and container barcodes, and provide electronic
mailing information to the Postal Service. There is an exception to
these requirements if the mailing contains fewer than 10,000 pieces,
when postage is affixed to each piece at the correct price, or when each
piece is of identical weight and the mailpieces are separated by price.

Note: A Mailer ID and Serial Number combination used on a basic
mailpiece may not be reused on a full-service mailpiece within 45 days.

Two of the fields in the Intelligent Mail barcode are used to maintain
barcode uniqueness.

1)  Mailer ID: A 6-digit or 9-digit number assigned by the Postal
    Service that uniquely identifies the Mail Owner or Mail Preparer.

2)  Serial Number: A 6-digit or 9-digit sequence number used to further
    identify the mailpiece or mailing.

The combination of these two fields is used to create a unique mailpiece
identifier in the Intelligent Mail barcode, as required for full-service
mailpieces. Intelligent Mail barcodes with the same Mailer ID and Serial
Number cannot be repeated within mailings of the same mail category
within 45 calendar days of the date the mailpiece carrying the
Intelligent Mail barcode was inducted into the USPS mailstream.
Mailpiece uniqueness is not enforced across mail classes meaning two
mailpieces could carry the same Mailer ID and Serial Number combination
within the 45 day uniqueness period as long as they were in different
mail classes (e.g. First-Class Mail and Standard Mail). Mail class is
part of the Service Type ID field. Any Intelligent Mail barcode can be
kept unique for longer than 45 calendar days.

## Service Type Identifiers

The Service Type Identifier is used to identify the class of mail and
the services requested for that mailpiece. In addition, the Service Type
Identifier defines whether the full-service or basic option has been
selected for a given mailpiece. It is also used to determine the
disposition of undeliverable-as-addressed mail, and the form of address
correction (or none) that a mailer desires.

Mailers will qualify for automated address correction notices at no
additional charge by participating in full-service and using the
provided information to update their address records. The Service Type
ID in the full-service Intelligent Mail barcode needs to be coded to
reflect the appropriate treatment required for the mailpiece should the
mailpiece be determined to be undeliverable or to require forwarding.
For example, there is a specific Service Type ID that should be used for
a full-service First-Class® Mail mailpiece when the mailer wants
forwardable mailpieces forwarded and other undeliverable mailpieces
returned. A different Service Type ID will be used on the First-Class
Mail full-service Intelligent Mail mailpiece if the mailer wants the
piece to be disposed if it is unable to be forwarded.

Those interested in the OneCode Confirm® service for full-service or
basic mailpieces must still purchase a Confirm® service subscription and
indicate the request for the Confirm service in the Service Type ID on
the mailpiece. In addition, address correction information will also be
available for purchase for basic mailpieces through the OneCode ACS
system. Those interested in receiving address correction data on basic
mailpieces should obtain a OneCode ACS subscription and indicate the
request for that service in the Service Type ID.

Finally, those who use the Intelligent Mail barcode prior to May 2009
should note that many of today's Service Type IDs will change in May
2009 to a new code corresponding to the basic and full-service options.
The Service Type IDs that are available today are defined in the
Intelligent Mail Barcode Technical Resource Guide which has been posted
at <http://ribbs.usps.gov/>. The new set of Service Type IDs will become
active in May 2009 as part of the basic and full-service options are
available in Appendix A of this document.

This section describes how to populate the Service Type ID field in the
Intelligent Mail barcode for both full-service and basic mailpieces.
Full-service mailpieces using the appropriate Service Type Identifier
will receive address correction information, subject to Postal Service
specified conditions. Address correction services can also be purchased
for a basic or non-automation mailpiece using the appropriate Service
Type Identifier. Start-the-clock information will be provided for
full-service mailings regardless of the Service Type ID used. Use the
Service Type ID Reference Matrix in Appendix A to identify the correct
Service Type ID reference for your full-service and basic mailpieces. 
You can also use that reference to find the appropriate Service Type ID
in the Intelligent Mail Barcode Technical Resource Guide which will be
posted at <http://ribbs.usps.gov/>.

**Note: Mailers that wish to receive address correction information on
non-automation mailpieces should use the corresponding Service Type ID
for basic option mailpieces unless otherwise defined in Appendix A.**

### Use of Ancillary Service Endorsements and Service Type IDs to Receive Address Corrections

Mailers can request to receive address corrections for any
undeliverable-as-addressed (UAA) mailpieces. In addition, a mailer can
also instruct the Postal Service on how they want any UAA mailpieces to
be handled. For example, a mailer can indicate their desire to have any
UAA mailpieces either forwarded, returned-to-sender, or disposed.

Different mail classes have different "default" treatments of UAA mail.
Within First-Class Mail, the "default" treatment for mail that cannot be
delivered is for it to be either forwarded or returned to the sender. In
Periodicals class, the "default" treatment of UAA mail is to forward
mailpieces for the first 60 calendar days following a customer's move
date and dispose of as waste all other UAA. For Standard Mail and Bound
Printed Matter, the "default" treatment of UAA mail is to dispose of it
as waste.

A mailer can instruct the Postal Service to handle any UAA mailpieces in
a manner different than the default treatment provided for the class of
mail. First-Class Mail mailers can tell the Postal Service to dispose of
undeliverable-as-addressed mailpieces rather than forwarding or
returning the mailpieces. A Standard Mail mailer can indicate their
desire to have any undeliverable mail that can be forwarded sent to the
addressee's new address and all other mail disposed as waste.

The process for instructing the Postal Service of the mailer's intent to
have their UAA mail treated in a manner different than the default
treatment requires the mailer to provide an **ancillary service
endorsement** that describes how to handle any UAA mailpieces. Ancillary
service endorsements are typically printed on a mailpiece and recognized
by the Postal Service when processing UAA mail. The valid ancillary
service endorsements and their common abbreviation that is used within
this document are:

Address Service Requested (ASR)

Change Service Requested (CSR)

Forwarding Service Requested (FSR)

Return Service Requested (RSR)

Temp-Return Service Requested (TRSR ) -- for First-Class Mail mailpieces
only

Electronic Service Requested (ACS or OneCode ACS® only) (ESR)

When a mailer uses an ancillary service endorsement on a mailpiece, they
are requesting additional services in conjunction with the handling of
their UAA mail than is typically provided. The presence of an ancillary
service endorsement is also the mailer acknowledgement that they **agree
to pay** to receive these extra services if a charge applies. As an
example, the use of Address Service Requested on a Standard Mail
mailpiece will provide forwarding if a change-of-address is on file and
return of undeliverable mailpieces at a weighted fee. Since forwarding
is not provided as part of Standard Mail processing, the mailer has to
pay separately to have mailpieces forwarded and returned.

Ancillary service endorsements work either standalone or in conjunction
with the Postal Service's ACS and OneCode ACS® programs. When an
ancillary service endorsement is used outside of the ACS and OneCode ACS
programs, the process of notifying a mailer that a mailpiece was UAA is
done via a hard copy (PS Form 3547) notice or by returning the
mailpiece. This hard copy notice provides a photocopy of the UAA
mailpiece with either the moving customer's new address or the reason
why the mailpiece could not be delivered. When an ancillary service
endorsement is used in conjunction with either the ACS or the OneCode
ACS program, an electronic notification of the UAA occurrence is
provided. This electronic notice also provides the moving customer's new
address or the reason why a mailpiece could not be delivered. The only
ancillary service endorsements available within ACS or OneCode ACS are
Address Service Requested and Change Service Requested. For more
information regarding ancillary service endorsements, see DMM 507.

### Forms of Address Corrections and Options for Handling Undeliverable-as-Addressed Mail with Intelligent Mail Barcode

Mailers have several options to receive address corrections and to
instruct the Postal Service on how to handle their
undeliverable-as-addressed mail that carries an Intelligent Mail
barcode. The various means by which a mailer can receive address
corrections are:

-   None

-   Manual address corrections

-   Traditional ACS

-   OneCode ACS

#### Indicating "None" as the Form of Address Correction 

A mailer that does not want to receive any address correction notices
would prepare their mail without including a printed ancillary service
endorsement on the mailpiece and would not use a Service Type ID that is
associated with the provision of address corrections. Note that pieces
with an alternative addressing format (such as the addressee's name and
"Or Current Resident" and the delivery address) must not use an
ancillary service endorsement.

#### Indicating "Manual Address Corrections" as the Form of Address Correction

Mailers that want to receive manual address corrections can do so by
printing an ancillary service endorsement on the mailpiece to trigger
the fulfillment of a hard copy correction notice. For example, a
First-Class Mail mailer that wants to get a hard copy address correction
notice on any mailpieces that were forwarded would use "Address Service
Requested" on their mail. This would cause a hard copy address
correction notice (PS Form 3547) to be provided. A fee would be charged
for the provision of the hard copy address correction notice in this
example. In another example, a First-Class Mail mailer that wants all
UAA mail to be returned would print "Return Service Requested" on the
mail. This would result in all UAA mail being returned-to-sender with
the reason for non-delivery or the moving customer's new address affixed
to the mailpiece.

If manual address correction notices are desired, be sure to use the
correct Service Type ID. If the Service Type ID reflects either
Traditional ACS or OneCode ACS, the correction notice will be provided
electronically and not in hard copy format.

#### Indicating "Traditional ACS" as the Form of Address Correction

Traditional ACS describes the original ACS program that uses a separate
Participant ID and optional Keyline printed on the mailpiece to fulfill
an electronic address correction. The Participant ID is always a
7-character alpha structure that is preceded by a pound sign symbol, for
example, #BWNABCD.

To trigger fulfillment of electronic address corrections through the
Traditional ACS program a mailer must print an ancillary service
endorsement on the mailpiece **and** show the Service Type ID associated
with Traditional ACS.

#### Indicating "OneCode ACS" as the Form of Address Correction

OneCode ACS refers to the program that fulfills address corrections
based on information specified in the Intelligent Mail barcode Service
Type ID field. The OneCode ACS infrastructure and processing methodology
is used as the basis for fulfilling address corrections provided as part
of basic and full-service mailings when a mailpiece is correctly
formatted with the required elements.

For address corrections through the OneCode ACS program to work
properly, mailers must use a Service Type ID that instructs the Postal
Service on how to treat undeliverable-as-addressed mailpieces. In
addition, mailpieces may also require the printing of an ancillary
service endorsement on the mailpiece. See the section "**Use of
Ancillary Service Endorsements and Service Type IDs to Receive Address
Corrections."**

It is important to fully understand the effect that the presence of a
printed ancillary service endorsement will have on the processing of
undeliverable-as-addressed mailpieces and how printed ancillary service
endorsements will be treated when used with a Service Type ID that does
not provide an electronic or automated address correction. For example,
using "Change Service Requested" on a Standard Mail® mailpiece without
using a Service Type ID to trigger an electronic or automated address
correction will result in a hard copy address correction notice and the
applicable charge for each UAA mailpiece. Mailers must pay careful
attention to the ancillary service endorsement shown on a mailpiece to
insure it provides the desired results. See the section "Use of
Ancillary Service Endorsement and Service Type IDs to Receive Address
Corrections" below.

### Ancillary Service Endorsements with Basic or Full-Service Mailings

Mailings made under either basic or full-service must use either a
printed ancillary service endorsement or a Service Type ID, or both, to
indicate the desired handling of any UAA mailpieces **whenever a
handling other than the default handling of UAA mail is desired**. A
printed ancillary service endorsement is **always** required to be
present on Standard Mail or Bound Printed Matter mailpieces in addition
to being specified in the Service Type ID whenever handling other than
the default UAA treatment is desired. This is true regardless of whether
the mailer is seeking hard copy address correction notices or electronic
address correction notices through ACS or OneCode ACS.

First-Class Mail mailpieces require a printed ancillary service
endorsement on the mailpiece if the mailer desires to receive hard copy
address correction notices. If the mailer desires electronic address
correction notices through the traditional ACS program the mailer must
use both a printed ancillary service endorsement and a matching Service
Type ID. First-Class Mail letter mailers that want to receive electronic
address corrections through OneCode ACS, or as part of full-service
mailings, are not required to have a printed ancillary service
endorsement but must have the appropriate Service Type ID. First Class
Mail flats mailers must use a printed ancillary service endorsement and
the appropriate Service Type ID in order to receive address correction
notices through OneCode ACS as part of basic or full-service for
mailpieces that are undeliverable for reasons other than a customer
move. See Appendix A for additional information.

Basic mailings that do not want to receive address corrections must not
include a printed ancillary service endorsement.

Any First-Class Mail mailpieces that the mailer prefers to have the
Postal Service dispose rather than return-to-sender must have a Service
Type ID that indicates "Change Service Requested" and the Mailer ID must
be enrolled in either the Traditional ACS or the OneCode ACS programs.

### Precedence of Ancillary Service Endorsements and Service Type ID Values

> **When a mailpiece bears a printed ancillary service endorsement, the
> printed endorsement takes [priority]{.underline} over the Service Type
> ID contained in the Intelligent Mail barcode.**

If a conflict exists between a printed ancillary service endorsement and
the UAA disposition indicated in the Service Type ID, [the handling of
the UAA mailpiece will be done according to the printed ancillary
endorsement.]{.underline} For example, a Standard Mail mailpiece with
"Address Service Requested" printed on it will cause a UAA mailpiece to
be forwarded and all other UAA to be returned even if the Service Type
ID is for "Change Service Requested" to suggest the mailer's intention
that any UAA mailpieces should be disposed. Or, a First-Class Mail
mailpiece bearing the printed endorsement of "Address Service Requested"
will result in all UAA mail being forwarded and returned regardless of
any other indication made in the Service Type ID.

> **Where a UAA mailpiece has a printed ancillary service endorsement
> that conflicts with the Service Type ID, the [mailer will be
> responsible for all appropriate fees]{.underline} associated with the
> handling provided based on the printed ancillary service
> endorsement.**

Mailers must be careful when using any printed ancillary service
endorsement to make certain that it matches their intended use and does
not conflict with the Service Type ID. This is especially true within
Standard Mail and Bound Printed Matter. Care should also be taken if
envelopes are pre-printed with an ancillary service endorsement and then
used on multiple mailings or for different classes of mail to make
certain the endorsement is valid in all uses.

### Electronic Service Requested

Electronic Service Requested is an umbrella endorsement that requires
the presence of another ancillary service endorsement value to have
meaning. A mailer indicates the ancillary service endorsement to
describe how to treat UAA mailpieces in the Service Type ID as part of
OneCode ACS, or in the mailer profile data when used on mail as part of
the traditional ACS program.

To help minimize the potential for conflicts between the printed
ancillary service endorsement and the Service Type ID in the Intelligent
Mail barcode, mailers should consider using the alternative ancillary
service endorsement "Electronic Service Requested". Using Electronic
Service Requested enables a mailer to have greater flexibility in using
the same envelope for mailings in different mail classes or to obtain
different UAA treatments for mail in the same mail class. Mailers should
not use Electronic Service Requested on any envelope that is not
requesting address correction services.

This endorsement can only be in conjunction with the ACS and OneCode ACS
programs. Using Electronic Service Requested on any mailpiece with an
Intelligent Mail barcode requires the inclusion of a Service Type ID
that identifies the specific mailpiece treatment and address correction
desired. Electronic Service Requested cannot be used to acquire manual
address corrections or for mail for which no address corrections are
desired. Use of Electronic Service Requested outside of ACS or OneCode
ACS causes unnecessary and costly additional workload for the Postal
Service.

To determine if using Electronic Service Requested is appropriate and
will meet the mailer's desired handling of UAA mail; see the
Constraints, Notes and Action columns in Appendix A Service Type
Identifier Matrix.

### Quick Service Guide Listing of Service Type Identifiers

The table below serves as a quick reference to enable you identify the
appropriate Service Type Identifier for your mailing, based on how you
will present your mail, the disposition desired for any
undeliverable-as-addressed mailpieces, how you wish to (or wish not to)
receive address correction notices, and whether you will be receiving
Confirm information. For a more complete description of address
correction options by class of mail see Appendix A Service Type
Identifier Matrix. Use the reference shown in the below table to locate
the equivalent description in Appendix A Service Type Identifier Matrix.

+--------+--------------+------+-------+------+------+------+-----+
| Class  | Address      | B    | Basic | Full | Full | Non- | N   |
|        | Correction   | asic | w/Co  | w/o  | w/   |      | on- |
|        | Option       | w/o  | nfirm | Con  | Con  | Auto |     |
|        |              | Con  |       | firm | firm | w/o  | A   |
|        |              | firm |       |      |      |      | uto |
|        |              |      |       |      |      | Con  | w/  |
|        |              |      |       |      |      | firm |     |
|        |              |      |       |      |      |      | C   |
|        |              |      |       |      |      |      | onf |
|        |              |      |       |      |      |      | irm |
+--------+--------------+------+-------+------+------+------+-----+
| *      | No Address   | 300  | 310   | 260  | 270  | 700  | 310 |
| *First | Corrections  |      |       |      |      |      |     |
| -Class |              |      |       |      |      |      |     |
| Mail** |              |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Manual       | 700  | 040   | 036  | 041  | 700  | 040 |
|        | Corrections  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Traditional  | 080, | 140,  | 081, | 141, | 080, | 1   |
|        | ACS          | 082  | 240   | 083  | 241  | 082  | 40, |
|        |              |      |       |      |      |      | 240 |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 080  | 140   | 081  | 141  | 080  | 140 |
|        | -- ASR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 080  | 140   | 081  | 141  | 080  | 140 |
|        | -- ASR       |      |       |      |      |      |     |
|        | Option 2     |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 082  | 240   | 083  | 241  | 082  | 240 |
|        | -- CSR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 082  | 240   | 083  | 241  | 082  | 240 |
|        | -- CSR       |      |       |      |      |      |     |
|        | Option 2     |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
| **P    | Manual       | 704  | 044   | 264  | 274  | 704  | 044 |
| eriodi | Corrections  |      |       |      |      |      |     |
| cals** |              |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Traditional  | 784, | 244,  | 038, | 045, | 784, | 2   |
|        | ACS          | 782  | 144   | 783  | 145  | 782  | 44, |
|        |              |      |       |      |      |      | 144 |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 784  | 244   | 038  | 045  | 784  | 244 |
|        | -- ASR       |      |       |      |      |      |     |
|        |              |      |       |      |      |      |     |
|        | w/o printed  |      |       |      |      |      |     |
|        | Ancillary    |      |       |      |      |      |     |
|        | Service      |      |       |      |      |      |     |
|        | Endorsement  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 782  | 144   | 783  | 145  | 782  | 144 |
|        | -- ASR       |      |       |      |      |      |     |
|        |              |      |       |      |      |      |     |
|        | w/ printed   |      |       |      |      |      |     |
|        | Ancillary    |      |       |      |      |      |     |
|        | Service      |      |       |      |      |      |     |
|        | Endorsement  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
| **Stan | No Address   | 301  | 311   | 261  | 271  | 702  | 311 |
| dard** | Corrections  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Manual       | 702  | 042   | 037  | 043  | 702  | 042 |
|        | Corrections  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Traditional  | 090, | 142,  | 091, | 143, | 090, | 1   |
|        | ACS          | 092  | 242   | 093  | 243  | 092  | 42, |
|        |              |      |       |      |      |      | 242 |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 090  | 142   | 091  | 143  | 090  | 142 |
|        | -- ASR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 092  | 242   | 093  | 243  | 092  | 242 |
|        | -- CSR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
| *      | No Address   | 401  | N/A   | 265  | N/A  | 706  | N/A |
| *BPM** | Corrections  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Manual       | 706  | N/A   | 466  | N/A  | 706  | N/A |
|        | Corrections  |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | Traditional  | 424, | N/A   | 423, | N/A  | 424, | N/A |
|        | ACS          | 431  |       | 430  |      | 431  |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 424  | N/A   | 423  | N/A  | 424  | N/A |
|        | -- ASR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
|        | OneCode ACS  | 431  | N/A   | 430  | N/A  | 431  | N/A |
|        | -- CSR       |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+
| *      | No Address   | 700, | 050,  | 700, | 050, | 700, | 0   |
| *First | Corrections  | 708  | 052   | 708  | 052  | 708  | 50, |
| -Class |              |      |       |      |      |      | 052 |
| Mail   |              |      |       |      |      |      |     |
| Reply  |              |      |       |      |      |      |     |
| Mail** |              |      |       |      |      |      |     |
+--------+--------------+------+-------+------+------+------+-----+

***Figure 2: Guide to Service Type Identifiers***

### First-Class Mail Service Type Identifiers

First-Class Mail mailpieces should use one of the following Service Type
Identifiers unless additional services are requested (i.e. Confirm). The
Service Type Identifier is used as the mail is processed to determine
how an Undeliverable as Addressed (UAA) mailpiece should be handled. For
example, the sender can request to have all First-Class Mail UAA
mailpieces disposed of and receive an address correction notice if they
are undeliverable, regardless of whether there is a change of address
record on file. The Service Type Identifier Appendix at the end of this
document contains a table that illustrates the information below and
provides additional Service Type Identifiers to use if requesting the
Confirm service.

#### First-Class Mail Nonautomation Service Type Identifiers

These Service Type Identifiers apply to non-automation and single-piece
First-Class Mail as defined in the Domestic Mail Manual (DMM).

##### First-Class Mail Nonautomation **Not Purchasing Address Correction** 

If the mailer does not want to purchase electronic address correction or
hard copy address correction notices for nonautomation mailpieces that
have an Intelligent Mail barcode, use a Service Type ID shown below.

-   Nonautomation First-Class Mail where the sender requests no
    ancillary services (therefore the normal handling that First-Class
    Mail mailpieces are forwarded if a change of address record is on
    file or returned to the sender if not forwardable) must use
    **Service Type ID 700**. A printed ancillary service endorsement
    must not be present on the envelope.

##### First-Class Mail Nonautomation **Purchasing Manual Address Correction** Notices

If the mailer wants to receive hard copy address correction notices
based on the printing of an ancillary service endorsement for
nonautomation mailpieces, use the Service Type ID shown below.

-   Nonautomation mailers that want all of their First-Class Mail UAA
    handled according to an on-piece endorsement or mailers that wish to
    obtain hard copy address corrections must use **Service Type ID
    700**. The mailer must include the printed ancillary service
    endorsement on the mailpiece that is applicable for the desired
    mailpiece disposition. No electronic address correction information
    is provided with this Service Type ID. Additional fees for hard copy
    address correction notices may apply.

##### First-Class Mail Nonautomation **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information
through use of the Traditional ACS program.

-   Nonautomation First-Class Mail for which the sender purchases
    electronic address correction information through the Traditional
    ACS process must use **Service Type ID 080.** A printed ancillary
    service endorsement must be shown on the envelope. The mailer must
    use the appropriate ACS Participant ID to match the UAA disposition
    desired. Address correction information will be provided through the
    sender's ACS subscription. Fees associated with the fulfillment of
    address corrections as part of the mailer's use of Traditional ACS
    are applicable.

##### First-Class Mail Nonautomation **Purchasing Address Correction Using OneCode ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of electronic address correction
information.

-   Nonautomation First-Class Mail for which the sender desires to
    purchases electronic address correction information for mailpieces
    that are undeliverable-as-addressed must use a Service Type ID that
    provides the mailpiece disposition and address correction option
    desired. Address correction information will be provided through the
    sender's OneCode ACS subscription. Fees are applicable for any
    mailpiece dispositions and address corrections as may be
    appropriate. To understand the impact of the different Service Type
    IDs and how they will affect the treatment of UAA mailpieces, refer
    to Appendix A.

    -   Address Service Requested -- use **Service Type ID 080**

    -   Address Service Requested Option 2 -- use **Service Type ID
        080**

    -   Change Service Requested -- use **Service Type ID 082**

    -   Change Service Requested Option 2 -- use **Service Type ID 082**

#### First-Class Mail Basic Service Type Identifiers

##### First-Class Mail Basic Option **Not Purchasing Address Correction** 

If the mailer does not want to purchase electronic address correction or
hard copy address correction notices as part of the basic service
option, use a Service Type ID shown below.

-   Basic First-Class Mail where the sender requests no ancillary
    services (mailpieces are forwarded if a change of address record is
    on file or returned to the sender if not forwardable) must use
    **Service Type ID 300**.

##### First-Class Mail Basic Option **Purchasing Manual Address Correction** Notices

If the mailer wants to receive hard copy address correction notices
based on the printing of an ancillary service endorsement as part of the
basic service option, use the Service Type ID shown below.

-   Basic mailers that want all of their First-Class Mail UAA handled
    according to an on-piece endorsement or mailers that wish to obtain
    hard copy address corrections must use **Service Type ID 700**. The
    mailer must include the printed ancillary service endorsement on the
    mailpiece that is applicable for the desired mailpiece disposition.
    No electronic address correction information is provided with this
    Service Type ID. Additional fees for hard copy address correction
    notices may apply.

##### First-Class Mail Basic Option **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information
through use of the Traditional ACS program.

-   Basic First-Class Mail for which the sender purchases electronic
    address correction information through the Traditional ACS process
    must use **Service Type ID 080 or 082.** A printed ancillary service
    endorsement must be present on the envelope to match the desired
    disposition. The mailer must use the appropriate ACS Participant ID
    to match the UAA disposition desired. Address correction information
    will be provided through the sender's ACS subscription. Fees
    associated with the fulfillment of address corrections as part of
    the mailer's use of Traditional ACS are applicable.

##### First-Class Mail Basic Option **Purchasing Address Correction Using OneCode ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of electronic address correction
information.

-   Basic First-Class Mail for which the sender desires to purchases
    electronic address correction information for mailpieces that are
    undeliverable-as-addressed must use a Service Type ID that provides
    the mailpiece disposition and address correction option desired.
    Address correction information will be provided through the sender's
    OneCode ACS subscription. Fees are applicable for any mailpiece
    dispositions and address corrections as may be appropriate. To
    understand the impact of the different Service Type IDs and how they
    will affect the treatment of UAA mailpieces, refer to Appendix A.

    -   Address Service Requested -- use **Service Type ID 080**

    -   Address Service Requested Option 2 -- use **Service Type ID
        080**

    -   Change Service Requested -- use **Service Type ID 082**

    -   Change Service Requested Option 2 -- use **Service Type ID 082**

#### First-Class Mail Full-Service Service Type Identifiers

Electronic address correction information will be provided for
full-service mailpieces under the OneCode ACS option and using one of
the Service Type Identifiers defined in this section.

##### First-Class Mail Full-Service **Not Purchasing Address Correction** Notices

If the mailer does not want to receive any electronic address correction
or hard copy address correction notices as part of the full service
option, use a Service Type ID shown below.

-   Full-service First-Class Mail where the sender wants mailpieces to
    be forwarded if a change of address record is on file or returned to
    the sender if not forwardable must use **Service Type ID 260**. A
    printed ancillary service endorsement must not be shown on the
    mailpiece.

##### First-Class Mail Full-Service **Purchasing Manual Address Correction** Notices

If the mailer wants to receive hard copy address correction notices
based on the printing of an ancillary service endorsement as part of the
basic service option, use the Service Type ID shown below.

-   Full-service mailers that want all of their First-Class Mail UAA
    handled according to an on-piece endorsement or mailers that wish to
    obtain hard copy address corrections must use **Service Type ID
    036**. The mailer must include the printed ancillary service
    endorsement on the mailpiece that is applicable for the desired
    mailpiece disposition. No electronic address correction information
    is provided with this Service Type ID. Additional fees for hard copy
    address correction notices may apply.

##### First-Class Mail Full-Service **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information
through use of the Traditional ACS program.

-   Full-service First-Class Mail for which the sender purchases
    electronic address correction information through the Traditional
    ACS process must use **Service Type ID 081 or 083.** A printed
    ancillary service endorsement must be shown on the mailpiece. The
    mailer must use the appropriate ACS Participant ID to match the UAA
    disposition desired. Address correction information will be provided
    through the sender's ACS subscription. Fees associated with the
    fulfillment of address corrections as part of the mailer's use of
    Traditional ACS are applicable.

##### First-Class Mail Full-Service **Receiving Electronic Address Correction Information Using OneCode ACS**

Electronic address correction will be provided as specified by the
Postal Service for First-Class Mail UAA mail when provided using the
appropriate OneCode ACS Service Type ID. This includes address
corrections due to a customer's change-of-address or other reason.

The Service Type Identifiers defined in this section identify when the
sender is requesting the receipt of electronic address correction
information.

-   Full-service First-Class Mail for which the sender wants electronic
    address correction information for mailpieces that are
    undeliverable-as-addressed must use a Service Type ID that provides
    the mailpiece disposition and address correction option desired.
    Address correction information will be provided through the
    full-service program. To understand the impact of the different
    Service Type IDs and how they will affect the treatment of UAA
    mailpieces, refer to Appendix A. The following are the Service Type
    IDs eligible for receiving address corrections as part of
    First-Class Mail Full-Service:

    -   Address Service Requested Option 2 -- use **Service Type ID
        081**

    -   Change Service Requested -- use **Service Type ID 083**

    -   Change Service Requested Option 2 -- use **Service Type ID 083**

**Receiving electronic address corrections as part of full-service
mailing does not eliminate the mailer's requirement to comply with the
Move Update standards.**

### Standard Mail Service Type Identifiers

Standard Mail should use one of the following Service Type Identifiers
unless additional services are requested (i.e. Confirm). The Service
Type Identifier is used as the mail is processed to determine how an
Undeliverable as Addressed (UAA) mailpiece should be handled. For
example, the sender can request to have their Standard Mail forwarded
and receive an address correction notice. The Service Type Identifier
Appendix at the end of this document contains a table that illustrates
the information below and provides additional Service Type Identifiers
to use if requesting the Confirm service.

**Where any disposition of a UAA mailpiece is chosen that does not
result in the Standard Mail UAA mailpiece being disposed, additional
fees will apply. This is true even when address correction is provided
as part of a Full-Service mailing.**

#### Standard Mail Nonautomation Service Type Identifiers

The following Service Type Identifiers apply to nonautomation,
machinable and non-machinable Standard Mail as defined in the DMM.
Saturation Enhanced Carrier Route Flats should also use these Service
Type IDs.

##### Standard Mail Nonautomation **Not Purchasing Address Correction** Notices

Standard Mail nonautomation mailers that do not want any address
correction service must use **Service Type ID 702 without any ancillary
service endorsement printed** on the mailpiece.

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Standard Mail Nonautomation **Purchasing Manual Address Correction** Notices

Address correction information may be purchased separately for Standard
Mail nonautomation mailpieces. Mailers that want to receive a hard copy
address correction notice must use the below Service Type ID(s). Note:
The presence of a printed ancillary service endorsement on the mailpiece
is the mailer's indication that they agree to pay for any hard copy
address corrections and additional postage due fees to handle UAA
mailpieces.

-   Nonautomation Standard Mail mailers that want all of their UAA mail
    handled according to an on-piece endorsement must use **Service Type
    ID 702.** The mailer must include the printed ancillary service
    endorsement on the mailpiece to indicate the desired mailpiece
    disposition. No electronic address correction information is
    provided with this Service Type ID. Note: Additional charges for
    hard copy address corrections and mailpiece handling dispositions
    are associated with this option.

##### Standard Mail Nonautomation **Purchasing Electronic Address Correction Using Traditional ACS** 

Electronic address correction information may be purchased separately
for Standard Mail nonautomation mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Nonautomation Standard Mail for which the sender purchases
    electronic address correction information through the Traditional
    ACS process must use **Service Type ID 090 or 092.** A printed
    ancillary service endorsement that matches the desired mailpiece
    disposition is required. The mailer must use the appropriate ACS
    Participant ID to match the UAA disposition desired. Address
    correction information will be provided through the sender's ACS
    subscription. Fees associated with the fulfillment of address
    corrections as part of the mailer's use of Traditional ACS are
    applicable.

##### Standard Mail Nonautomation **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information may be purchased separately
for Standard Mail nonautomation mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the OneCode ACS program.

-   Nonautomation Standard Mail mailpieces for which the sender
    purchases address correction information and for which the sender
    requests disposal for all UAA mailpieces must use **Service Type ID
    090** and must bear the printed endorsement Electronic Service
    Requested or Change Service Requested on the mailpiece. Address
    correction information will be provided through the sender's OneCode
    ACS subscription.

-   Nonautomation Standard Mail mailpieces for which the sender
    purchases address correction information and the sender requests
    that mailpieces be forwarded if a change of address record is on
    file or returned to the sender when it cannot be forwarded must use
    **Service Type ID 092** and must bear the endorsement Electronic
    Service Requested or Address Service Requested on the mailpiece.
    Address correction information will be provided through the sender's
    OneCode ACS subscription. Note: Additional charges for mailpiece
    handling are associated with this option.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

#### Standard Mail Basic Service Type Identifiers

##### Standard Mail Basic Option **Not Purchasing Address Correction** Notices

Standard Mail basic mailers that do not want any address correction
service must use **Service Type ID 301 without any ancillary service
endorsement printed** on the mailpiece.

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Standard Mail Basic Option **Purchasing Manual Address Correction** Notices

Address correction information may be purchased separately for Standard
Mail basic mailpieces. Mailers that want to receive a hard copy address
correction notice must use the below Service Type ID(s). Note: The
presence of a printed ancillary service endorsement on the mailpiece is
the mailer's indication that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.

-   Basic Standard Mail mailers that want all of their UAA mail handled
    according to an on-piece endorsement must use **Service Type ID
    702.** The mailer must include the printed ancillary service
    endorsement on the mailpiece to indicate the desired mailpiece
    disposition. No electronic address correction information is
    provided with this Service Type ID. Note: Additional charges for
    hard copy address corrections and mailpiece handling dispositions
    are associated with this option.

##### Standard Mail Basic **Purchasing Electronic Address Correction Using Traditional ACS** 

Electronic address correction information may be purchased separately
for Standard Mail basic mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Basic Standard Mail for which the sender purchases electronic
    address correction information through the Traditional ACS process
    must use **Service Type ID 090 or 092.** A printed ancillary service
    endorsement that matches the desired mailpiece disposition is
    required. The mailer must use the appropriate ACS Participant ID to
    match the UAA disposition desired. Address correction information
    will be provided through the sender's ACS subscription. Fees
    associated with the fulfillment of address corrections as part of
    the mailer's use of Traditional ACS are applicable.

##### Standard Mail Basic Option **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information may be purchased separately
for Standard Mail basic mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the OneCode ACS program.

-   Basic Standard Mail mailpieces for which the sender purchases
    address correction information and for which the sender requests
    disposal for all UAA mailpieces must use **Service Type ID 090**and
    must bear the printed endorsement Electronic Service Requested or
    Change Service Requested on the mailpiece. Address correction
    information will be provided through the sender's OneCode ACS
    subscription.

-   Basic Standard Mail mailpieces for which the sender purchases
    address correction information and the sender requests that
    mailpieces be forwarded if a change of address record is on file or
    returned to the sender when it cannot be forwarded must use
    **Service Type ID 092** and must bear the endorsement Electronic
    Service Requested or Address Service Requested on the mailpiece.
    Address correction information will be provided through the sender's
    OneCode ACS subscription. Note: Additional charges for mailpiece
    handling are associated with this option.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

#### Standard Mail Full-Service Service Type Identifiers

##### Standard Mail Full-Service **Not Purchasing Address Correction** Notices

Standard Mail full-service mailers that do not want any address
correction service must use **Service Type ID 261** **without any
ancillary service endorsement printed** on the mailpiece.

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Standard Mail Full-Service **Purchasing Manual Address Correction** Notices

Address correction information may be purchased separately for Standard
Mail full-service mailpieces. Mailers that want to receive a hard copy
address correction notice must use the appropriate Service Type ID(s).
Note: The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they agree to pay for any hard
copy address corrections and additional postage due fees to handle UAA
mailpieces.

-   Full-service Standard Mail mailers that want all of their UAA mail
    handled according to an on-piece endorsement must use **Service Type
    ID 037**. The mailer must include the printed ancillary service
    endorsement on the mailpiece to indicate the desired mailpiece
    disposition. No electronic address correction information is
    provided with this Service Type ID. Note: Additional charges for
    hard copy address corrections and mailpiece handling dispositions
    are associated with this option.

##### Standard Mail Full-Service **Purchasing Electronic Address Correction Using Traditional ACS** 

Electronic address correction information may be purchased separately
for Standard Mail full-service mailpieces using the Traditional ACS
program.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Full-service Standard Mail for which the sender purchases electronic
    address correction information through the Traditional ACS process
    must use **Service Type ID 091 or 093.** A printed ancillary service
    endorsement that matches the desired mailpiece disposition is
    required. The mailer must use the appropriate ACS Participant ID to
    match the UAA disposition desired. Address correction information
    will be provided through the sender's ACS subscription. Fees
    associated with the fulfillment of address corrections as part of
    the mailer's use of Traditional ACS are applicable.

##### Standard Mail Full-Service **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information will be provided within a
full-service mailing, as specified by the Postal Service, for Standard
Mail full-service mailpieces using the Service Type Identifier defined
below.

-   Full-service Standard Mail mailpieces for which the sender purchases
    address correction information and for which the sender requests
    disposal for all UAA mailpieces must use **Service Type ID 093** and
    must bear the printed endorsement Electronic Service Requested or
    Change Service Requested on the mailpiece. Address correction
    information will be provided through the full-service program.

-   Full-service Standard Mail mailpieces for which the sender purchases
    address correction information and the sender requests that those
    mailpieces be forwarded if a change of address record is on file or
    returned to the sender when it cannot be forwarded must use
    **Service Type ID 091** and must bear the endorsement Electronic
    Service Requested or Address Service Requested on the mailpiece.
    Address correction information will be provided through the
    full-service program. Note: Additional charges for mailpiece
    handling are associated with this option to pay for the forwarding
    and return of undeliverable Standard Mail.

##### Standard Mail Full-Service **Enhanced Carrier Route Mailpieces**

Electronic address correction information will not be provided for no
additional charge for Standard Mail enhanced carrier route flats within
a full-service mailing. Standard Mail full-service enhanced carrier
route flats should use the Service Type Identifier defined below.

-   Full-service Standard Mail enhanced carrier route mailpieces for
    which the sender does not wish to purchase address correction
    information should use **Service Type ID 093** and must **NOT** bear
    an ancillary printed endorsement on the mailpiece. No address
    correction information will be provided for these mailpieces.

-   Full-service Standard Mail enhanced carrier route mailpieces for
    which the sender wishes to purchase address correction information
    should use **Service Type ID 093** and must bear an ancillary
    printed endorsement Electronic Service Requested or Change Service
    Requested on the mailpiece. Address correction information will be
    provided for these mailpieces for existing charges.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

### Periodicals Service Type Identifiers

Periodicals mailpieces should use one of the following Service Type
Identifiers unless additional services are requested (i.e. Confirm). The
Service Type Identifier is used as the mail is processed to determine
how an Undeliverable as Addressed (UAA) mailpiece should be handled. For
example, the sender can request to have an unforwardable UAA mailpiece
returned to the sender. The Service Type Identifier Appendix at the end
of this document contains a table that illustrates the information below
and provides additional Service Type Identifiers to use if requesting
the Confirm service.

Mailing at Periodicals class requires that the mailer take address
corrections through either electronic address correction services, via
hard copy PS Form 3579, or through physical return of the mailpiece.

The [absence of any printed ancillary service endorsement]{.underline}
on a mailpiece indicates the mailer wants UAA mail to be forwarded for
the first 60 calendar days after a customer's move and [all other UAA to
be disposed]{.underline}.

The [presence of the printed ancillary service endorsement "Address
Service Requested"]{.underline} on a mailpiece indicates the mailer
wants UAA mail to be forwarded for the first 60 calendar days after a
customer's move and [all other UAA to be
returned-to-sender]{.underline}.

#### Periodicals Mail Nonmachinable Service Type Identifiers

##### Periodicals Mail Nonmachinable **Purchasing** **Manual** **Address Correction** Notices

Mailing at Periodicals class requires that the mailer take address
corrections through either electronic address correction services, via
hard copy PS Form 3579, or through physical return of the mailpiece.

-   Nonmachinable Periodicals Mail where the mailer wishes to have
    forwardable mailpieces forwarded for the first 60 calendar days
    after the customer has moved and have all other UAA mailpieces
    disposed and receives hard copy address correction notices for all
    undeliverable mail must use **Service Type ID 704** without any
    ancillary service endorsement printed on the mailpiece. Manual
    address correction notice fee associated with undeliverable
    Periodicals mailpieces charged.

-   Nonmachinable Periodicals Mail where the mailer wishes to have
    forwardable mailpieces forwarded for the first 60 calendar days
    after the customer has moved and have all other UAA mailpieces
    returned and receives hard copy address correction notices for all
    undeliverable mail must use **Service Type ID 704 and print "Address
    Service Requested"** and show their return address on the front of
    the mailpiece. Manual address correction notice fee and returned
    mailpiece fees associated with undeliverable Periodicals mailpieces
    charged.

##### Periodicals Mail Nonmachinable **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece.

-   Nonmachinable Periodicals mailpieces for which the sender receives
    address correction information through Traditional ACS and that the
    sender **want UAA mailpieces forwarded for the first 60** calendar
    days after the customer moves and to have **all other UAA be
    disposed** must use **Service Type ID 784**. The mailpiece must not
    show a printed ancillary service endorsement on the mailpiece. Fees
    for address correction apply.

-   Nonmachinable Periodicals mailpieces for which the sender receives
    address correction information and that the sender wants **UAA mail
    to be forwarded for the first 60 calendar days** after the customer
    moves and to have **all other UAA be returned to the sender** must
    use **Service Type ID 782 and print "Address Service Requested"**
    and show their return address on the front of the mailpiece. Fees
    for address correction and return of mailpieces apply. See DMM 507
    for these requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for nonmachinable
Periodicals mailers. These options will provide the mailer with an
electronic address correction notice only. No PS Form 3579 hard copy
address correction notices provided under this service.

##### Periodicals Mail Nonmachinable **Purchasing Electronic Address Correction Using OneCode ACS**

The Service Type Identifiers defined in this section identify when the
sender is receiving address correction information based on use of the
OneCode ACS program.

-   Nonmachinable Periodicals mailpieces for which the sender receives
    address correction information and that the sender wants **UAA mail
    to be forwarded for the first 60 calendar days** after the customer
    moves and to have **all other UAA be disposed** must use **Service
    Type ID 784**. The mailpiece **must not show** a printed ancillary
    service endorsement. Fees for address correction apply.

-   Nonmachinable Periodicals mailpieces for which the sender purchases
    address correction information and that the sender wants **UAA mail
    to be forwarded for the first 60 calendar days** after the customer
    moves and to have **all other UAA be returned to the sender** must
    use **Service Type ID 782 and must print "Address Service
    Requested"** and must show their return address on the front of the
    mailpiece. Additional requirements and fees apply. See DMM 507 for
    these requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for nonmachinable
Periodicals mailers. These options will provide the mailer with an
electronic address correction notice only. No PS Form 3579 hard copy
address correction notices provided under this service.

#### Periodicals Mail Basic Option Service Type Identifiers

##### Periodicals Mail Basic Option **Purchasing** **Address Manual Correction** Notices

Mailing at Periodicals class requires that the mailer take address
corrections through either electronic address correction services, via
hard copy PS Form 3579, or through physical return of the mailpiece.

-   Basic Periodicals Mail where the mailer wishes to have forwardable
    mailpieces forwarded for the first 60 calendar days after the
    customer has moved and have all other UAA mailpieces disposed and
    receives hard copy address correction notices for all undeliverable
    mail must use **Service Type ID 704** without any ancillary service
    endorsement printed on the mailpiece. Manual address correction
    notice fee associated with undeliverable Periodicals mailpieces
    charged.

-   Basic Periodicals Mail where the mailer wishes to have forwardable
    mailpieces forwarded for the first 60 calendar days after the
    customer has moved and have all other UAA mailpieces returned and
    receives hard copy address correction notices for all undeliverable
    mail must use **Service Type ID 704 and print "Address Service
    Requested"** and show their return address on the front of the
    mailpiece. Manual address correction notice fee and returned
    mailpiece fees associated with undeliverable Periodicals mailpieces
    charged.

##### Periodicals Mail Basic Option **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece.

-   Basic Periodicals mailpieces for which the sender receives address
    correction information through Traditional ACS and that the sender
    **want UAA mailpieces forwarded for the first 60** calendar days
    after the customer moves and to have **all other UAA be disposed**
    must use **Service Type ID 784**. The mailpiece must not show a
    printed ancillary service endorsement on the mailpiece. Fees for
    address correction apply.

-   Basic Periodicals mailpieces for which the sender receives address
    correction information and that the sender wants **UAA mail to be
    forwarded for the first 60 calendar days** after the customer moves
    and to have **all other UAA be returned to the sender** must use
    **Service Type ID 782 and print "Address Service Requested"** and
    show their return address on the front of the mailpiece. Fees for
    address correction and return of mailpieces apply. See DMM 507 for
    these requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for basic Periodicals
mailers. These options will provide the mailer with an electronic
address correction notice only. No PS Form 3579 hard copy address
correction notices provided under this service.

##### Periodicals Mail Basic Option **Purchasing Electronic Address Correction Using OneCode ACS**

The Service Type Identifiers defined in this section identify when the
sender is receiving address correction information based on use of the
OneCode ACS program.

-   Basic Periodicals mailpieces for which the sender receives address
    correction information and that the sender wants **UAA mail to be
    forwarded for the first 60 calendar days** after the customer moves
    and to have **all other UAA be disposed** must use **Service Type ID
    784**. The mailpiece **must not show** a printed ancillary service
    endorsement. Fees for address correction apply.

-   Basic Periodicals mailpieces for which the sender purchases address
    correction information and that the sender wants **UAA mail to be
    forwarded for the first 60 calendar days** after the customer moves
    and to have **all other UAA be returned to the sender** must use
    **Service Type ID 782 and must print "Address Service Requested"**
    and must show their return address on the front of the mailpiece.
    Additional requirements and fees apply. See DMM 507 for these
    requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for basic Periodicals
mailers. These options will provide the mailer with an electronic
address correction notice only. No PS Form 3579 hard copy address
correction notices provided under this service.

#### Periodicals Mail Full-Service Service Type Identifiers

Mailing at Periodicals class requires that the mailer take address
corrections through either electronic address correction services, via
hard copy PS Form 3579, or through physical return of the mailpiece.

The [absence of a printed ancillary service endorsement]{.underline} on
a mailpiece indicates the mailer wants UAA mail to be forwarded for the
first 60 calendar days after a customer's move and [all other UAA to be
disposed]{.underline}.

The [presence of a printed ancillary service endorsement]{.underline} on
a mailpiece indicates the mailer wants UAA mail to be forwarded for the
first 60 calendar days after a customer's move and [all other UAA to be
returned-to-sender]{.underline}.

##### Periodicals Mail Full-Service **Purchasing** **Address Manual Correction** Notices

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of hard copy address correction
information on the mailpiece.

-   Full-service Periodicals Mail where the mailer wishes to have
    forwardable mailpieces forwarded for the first 60 calendar days
    after the customer has moved and have all other UAA mailpieces
    disposed and receives hard copy address correction notices for all
    undeliverable mail must use **Service Type ID 264** without any
    ancillary service endorsement printed on the mailpiece. Manual
    address correction notice fee associated with undeliverable
    Periodicals mailpieces charged.

-   Full-service Periodicals Mail where the mailer wishes to have
    forwardable mailpieces forwarded for the first 60 calendar days
    after the customer has moved and have all other UAA mailpieces
    returned and receives hard copy address correction notices for all
    undeliverable mail must use **Service Type ID 264 and print "Address
    Service Requested"** and show their return address on the front of
    the mailpiece. Manual address correction notice fee and returned
    mailpiece fees associated with undeliverable Periodicals mailpieces
    charged.

##### Periodicals Mail Full-Service **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction based on use of
the Traditional ACS program.

-   Full-service Periodicals mailpieces for which the sender receives
    address correction information through Traditional ACS and that the
    sender **want UAA mailpieces forwarded for the first 60** calendar
    days after the customer moves and to have **all other UAA be
    disposed** must use **Service Type ID 038**. The mailpiece must not
    show a printed ancillary service endorsement on the mailpiece. Fees
    for address correction apply.

-   Full-service Periodicals mailpieces for which the sender receives
    address correction information and that the sender wants **UAA mail
    to be forwarded for the first 60 calendar days** after the customer
    moves and to have **all other UAA be returned to the sender** must
    use **Service Type ID 038 and print "Address Service Requested"**
    and show their return address on the front of the mailpiece. Fees
    for address correction and return of mailpieces apply. See DMM 507
    for these requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for basic Periodicals
mailers. These options will provide the mailer with an electronic
address correction notice only. No PS Form 3579 hard copy address
correction notices provided under this service.

##### Periodicals Mail Full-Service **Requesting Address Correction Using OneCode ACS**

Electronic address correction information will be provided within a
full-service mailing, as specified by the Postal Service, for
Periodicals Mail full-service mailpieces using the Service Type
Identifier defined below.

The Service Type Identifiers defined in this section identify when the
sender is receiving address correction information based on use of the
OneCode ACS program under the full-service option.

-   Full-service Periodicals mailpieces for which the sender receives
    address correction information and that the sender wants **UAA mail
    to be forwarded for the first 60 calendar days** after the customer
    moves and to have **all other UAA be disposed** must use **Service
    Type ID 038**. The mailpiece **must not show** a printed ancillary
    service endorsement.

-   Full Periodicals mailpieces for which the sender purchases address
    correction information and that the sender wants **UAA mail to be
    forwarded for the first 60 calendar days** after the customer moves
    and to have **all other UAA be returned to the sender** must use
    **Service Type ID 783 and must print "Address Service Requested"**
    and must show their return address on the front of the mailpiece.
    Additional requirements and fees apply. See DMM 507 for these
    requirements.

Note: Periodicals address notification Options 2, 4, 5, and 6 only, as
shown in Publication 8 and 8B, are provided for basic Periodicals
mailers. These options will provide the mailer with an electronic
address correction notice only. No PS Form 3579 hard copy address
correction notices are provided under this service.

### Bound Printed Matter Service Type Identifiers

Bound Printed Matter mailpieces should use one of the following Service
Type Identifiers. The Service Type Identifier is used as the mail is
processed to determine how an Undeliverable as Addressed (UAA) mailpiece
should be handled. For example, the sender can request to have UAA
mailpieces disposed of and receive an electronic address correction
notice that provides the new address information or specifies the reason
for non-delivery.

While there is no Move Update requirement for Bound Printed Matter,
address correction information will be made available for flat-size
mailpieces entered as full-service mailings and eligible for the barcode
discount when they carry an Intelligent Mail barcode. The Service Type
Identifier Appendix at the end of this document contains a table that
illustrates the information below.

#### Bound Printed Matter Nonautomation Service Type Identifiers 

##### Bound Printed Matter Nonautomation **Not Purchasing Address Correction** Notices 

If the mailer does not want to receive any electronic address correction
or hard copy address correction notices as part of the nonautomation
mailpieces, use a Service Type ID below.

-   Nonautomation Bound Printed Matter where the sender wants any
    undeliverable mailpieces disposed of as waste and no electronic or
    hard copy address correction notice must use **Service Type ID 706
    without the presence of any printed ancillary service endorsement on
    the mailpiece.**

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Bound Printed Matter Nonautomation **Purchasing Manual Address Correction** Notices 

Address correction information may be purchased separately for Bound
Printed Matter Flat mailpieces. Mailers that want to receive a hard copy
address correction must use the below Service Type ID(s). Note: The
presence of a printed ancillary service endorsement on the mailpiece is
the mailer's indication that they agree to pay for any hard copy address
correction notices and additional postage due fees to handle UAA
mailpieces.

-   Nonautomation Bound Printed Matter where the sender wants any
    undeliverable mailpieces disposed of as waste and a hard copy
    address correction notice provided must use **Service Type ID 706.**
    The mailer must include the printed ancillary service endorsement on
    the mailpiece to indicate the desired mailpiece disposition. No
    electronic address correction information is provided with this
    Service Type ID. Note: Additional charges for hard copy address
    corrections and mailpiece handling dispositions are associated with
    this option.

##### Bound Printed Matter Nonautomation **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Nonautomation Bound Printed Matter for which the sender purchases
    electronic address correction information through the Traditional
    ACS process must use **Service Type ID 424 or 431.** A printed
    ancillary service endorsement that matches the desired mailpiece
    disposition is required. The mailer must use the appropriate ACS
    Participant ID to match the UAA disposition desired. Address
    correction information will be provided through the sender's ACS
    subscription. Fees associated with the fulfillment of address
    corrections as part of the mailer's use of Traditional ACS and
    postage due fees as appropriate are applicable.

##### Nonautomation Bound Printed Matter **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information may be purchased separately
for Bound Printed Matter nonautomation mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the OneCode ACS program.

-   Nonautomation Bound Printed Matter mailpieces for which the sender
    purchases address correction information and for which the sender
    requests disposal for all UAA mailpieces must use **Service Type ID
    431** and must bear the printed endorsement Electronic Service
    Requested or Change Service Requested on the mailpiece. Address
    correction information will be provided through the sender's OneCode
    ACS subscription.

-   Nonautomation Bound Printed Matter mailpieces for which the sender
    purchases address correction information and the sender requests
    that those mailpieces be forwarded if a change of address record is
    on file or returned to the sender when it cannot be forwarded must
    use **Service Type ID 424** and must bear the endorsement Electronic
    Service Requested or Address Service Requested on the mailpiece.
    Address correction information will be provided through the sender's
    OneCode ACS subscription. Note: Additional charges for mailpiece
    handling are associated with this option.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

#### Bound Printed Matter Basic Service Type Identifiers 

##### Bound Printed Matter Basic **Not Purchasing Address Correction** Notices 

If the mailer does not want to receive any electronic address correction
or hard copy address correction notices as part of the basic service
option, use a Service Type ID below.

-   Basic Bound Printed Matter where the sender wants any undeliverable
    mailpieces disposed of as waste and no electronic or hard copy
    address correction notice must use **Service Type ID 401 without the
    presence of any printed ancillary service endorsement on the
    mailpiece.**

##### Bound Printed Matter Basic **Purchasing Manual Address Correction** Notices 

Address correction information may be purchased separately for Bound
Printed Matter Flat mailpieces. Mailers that want to receive a hard copy
address correction must use the below Service Type ID(s). Note: The
presence of a printed ancillary service endorsement on the mailpiece is
the mailer's indication that they agree to pay for any hard copy address
correction notices and additional postage due fees to handle UAA
mailpieces.

-   Basic Bound Printed Matter where the sender wants any undeliverable
    mailpieces disposed of as waste and a hard copy address correction
    notice provided must use **Service Type ID 706.** The mailer must
    include the printed ancillary service endorsement on the mailpiece
    to indicate the desired mailpiece disposition. No electronic address
    correction information is provided with this Service Type ID. Note:
    Additional charges for hard copy address corrections and mailpiece
    handling dispositions are associated with this option.

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Bound Printed Matter Basic **Purchasing Electronic Address Correction Using Traditional ACS**

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Basic Bound Printed Matter for which the sender purchases electronic
    address correction information through the Traditional ACS process
    must use **Service Type ID 424 or 431.** A printed ancillary service
    endorsement that matches the desired mailpiece disposition is
    required. The mailer must use the appropriate ACS Participant ID to
    match the UAA disposition desired. Address correction information
    will be provided through the sender's ACS subscription. Fees
    associated with the fulfillment of address corrections as part of
    the mailer's use of Traditional ACS and postage due fees as
    appropriate are applicable.

##### Basic Option Bound Printed Matter **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information may be purchased separately
for Bound Printed Matter basic mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the OneCode ACS program.

-   Basic Bound Printed Matter mailpieces for which the sender purchases
    address correction information and for which the sender requests
    disposal for all UAA mailpieces must use **Service Type ID 431** and
    must bear the printed endorsement Electronic Service Requested or
    Change Service Requested on the mailpiece. Address correction
    information will be provided through the sender's OneCode ACS
    subscription.

-   Basic Bound Printed Matter mailpieces for which the sender purchases
    address correction information and the sender requests that those
    mailpieces be forwarded if a change of address record is on file or
    returned to the sender when it cannot be forwarded must use
    **Service Type ID 424** and must bear the endorsement Electronic
    Service Requested or Address Service Requested on the mailpiece.
    Address correction information will be provided through the sender's
    OneCode ACS subscription. Note: Additional charges for mailpiece
    handling are associated with this option.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

#### Bound Printed Matter Full-Service Service Type Identifiers 

##### Bound Printed Matter Flats Full-Service **Not Purchasing Address Correction** Notices

Bound Printed Matter Flats full-service mailers that do not want any
address correction service must use **Service Type ID 265 without any
ancillary service endorsement printed** on the mailpiece.

##### Bound Printed Matter Flats Full-Service **Purchasing Manual Address Correction** Notices

Address correction information may be purchased separately for Bound
Printed Matter full-service mailpieces. Mailers that want to receive a
hard copy address correction notice must use the below Service Type
ID(s). Note: The presence of a printed ancillary service endorsement on
the mailpiece is the mailer's indication that they agree to pay for any
hard copy address corrections and additional postage due fees to handle
UAA mailpieces.

-   Full-service Bound Printed Matter Flats mailers that want all of
    their UAA mail handled according to an on-piece endorsement must use
    **Service Type ID 466**. The mailer must include the printed
    ancillary service endorsement on the mailpiece to indicate the
    desired mailpiece disposition. No electronic address correction
    information is provided with this Service Type ID. Note: Additional
    charges for hard copy address corrections and mailpiece handling
    dispositions are associated with this option.

**The presence of a printed ancillary service endorsement on the
mailpiece is the mailer's indication that they are requesting manual
address correction and that they agree to pay for any hard copy address
corrections and additional postage due fees to handle UAA mailpieces.**

##### Bound Printed Matter Full-Service **Purchasing Electronic Address Correction Using Traditional ACS** 

Electronic address correction information may be purchased separately
for Bound Printed Matter full-service mailpieces.

The Service Type Identifiers defined in this section identify when the
sender is requesting the purchase of address correction information on
the mailpiece based on participation in the Traditional ACS program.

-   Full-service Bound Printed Matter for which the sender purchases
    electronic address correction information through the Traditional
    ACS process must use **Service Type ID 423 or 430.** A printed
    ancillary service endorsement that matches the desired mailpiece
    disposition is required. The mailer must use the appropriate ACS
    Participant ID to match the UAA disposition desired. Address
    correction information will be provided through the sender's ACS
    subscription. Fees associated with the fulfillment of address
    corrections as part of the mailer's use of Traditional ACS are
    applicable.

##### Bound Printed Matter Full-Service **Requesting Electronic Address Correction Using OneCode ACS** 

Electronic address correction information will be provided within a
full-service mailing, as specified by the Postal Service, for Bound
Printed Matter full-service mailpieces using the Service Type Identifier
defined below.

-   Full-service Bound Printed Matter mailpieces for which the sender
    will receive address correction information as a function of
    full-service and for which the sender requests disposal for all UAA
    mailpieces must use **Service Type ID 430** and must bear the
    printed endorsement Electronic Service Requested or Change Service
    Requested on the mailpiece. Address correction information will be
    provided through the full-service program.

-   Full-service Bound Printed Matter mailpieces for which the sender
    will receive address correction information as a function of
    full-service and the sender requests that those mailpieces be
    forwarded if a change of address record is on file or returned to
    the sender when it cannot be forwarded must use **Service Type ID
    423** and must bear the endorsement Electronic Service Requested or
    Address Service Requested on the mailpiece. Address correction
    information will be provided through the full-service program. Note:
    Additional charges for mailpiece handling are associated with this
    option to pay for the forwarding and return of undeliverable Bound
    Printed Matter Mail.

Mailers should carefully review Appendix A and understand how ancillary
service endorsements may impact the treatments of UAA mail and fees that
may be associated with such treatments.

# Electronic Mailing Documentation and Postage Statements

Today, mailings that claim discounts and require minimum volumes must be
accompanied by a postage statement and presort documentation (when
documentation is required). Mailers typically furnish hard copy postage
statements and documentation or supply a computer terminal at their site
for Postal Service acceptance personnel to view their documentation. For
the full-service option, mailers will be required to use one of three
methods, namely Mail.dat, Mail.XML (which will replace Wizard Web
Services) or Postal Wizard (PW), to send their electronic mailing
information to the *PostalOne!* system. The *PostalOne!* system is an
information-management system that translates customer-generated
electronic information into postage statements and supporting
documentation, such as qualification and container reports. This
electronic mailing information is used for business mail verification,
acceptance, and induction processes. By submitting documents
electronically, mailers will be able to avoid the creation of
paper-based forms and use this technology to manage their mailing data.
Some mailers have already transitioned to electronic submission of their
postage statements and mailing documentation.

Access to the *PostalOne!* system is required to submit electronic
documentation using any of the three methods outlined above (Mail.dat,
Mail.XML, PW). Detailed instructions on how to obtain access to the
*PostalOne!* system can be found at
<http://www.usps.com/postalone/howto.htm> where you will also find a
link to the Online Application Form. Those interested in using the PW
should contact their BMEU directly to obtain access. For additional
information on how to sign-up and begin using the *PostalOne!* system
today please see the *PostalOne!* Getting Started Guide at
[http://www.usps.com/postalone/\_pdf/*PostalOne!*StartGuide.pdf](http://www.usps.com/postalone/_pdf/PostalOne!StartGuide.pdf).

As referenced in the Federal Register, full-service implementation will
begin in May 2009. Those interested in transitioning to electronic
submission of mailing documentation prior to May 2009 can find more
information about how to get started at
<http://www.usps.com/postalone/guides.htm>. There they will find guides
that describe the existing specifications and system requirements. Those
interested in understanding how the specifications and system
requirements will change to support full-service should refer to the
full-service version of the technical guides which are posted at
<http://ribbs.usps.gov/>.

**Note: All references to specifications in this document are subject to
update as operational or pricing initiative details are finalized.**

With the full-service option, you will need to submit postage statement
and other mailing documentation electronically using one of three
options. For Release 1, the Mail.dat and Postal Wizard options will be
available with the Mail.XML option available in a future release.

1.  Mail.dat®: Mail.dat is an industry-defined database structure
    consisting of files linked by key fields. For information about
    Mail.dat refer to <http://www.maildat.org/>. For information on how
    you can use Mail.dat to submit electronic information for
    full-service, refer to <http://ribbs.usps.gov/> where you will find
    the *PostalOne!* System Mail.dat Technical Guide for Full-Service.

2.  Mail.XML (formerly Wizard Web Services (WWS)): The Mail.XML
    specification, which will replace the Wizard Web Services, enables
    secure electronic submission of mailing information to the Postal
    Service using eXtensible Markup Language (XML) messaging technology.
    For more information about using Mail.XML for communicating with the
    *PostalOne!* system for full-service*,* refer to the *PostalOne!*
    system product guides and tools and the *PostalOne!* System Mail.XML
    Technical Guide for Full-Service on <http://ribbs.usps.gov/>.

3.  Postal Wizard: The *PostalOne!* system provides the Postal Wizard
    (PW) tool that provides a secure way to submit postage statements
    online. This tool may be used when no electronic documentation is
    necessary for compliance with full-service requirements. 
    (Qualification reports for mailings of less than 10,000 pieces are
    not required when postage is affixed to each piece at the correct
    price, or when each piece is of identical weight and the mailpieces
    are separated by price).

  ----------------- ------------------ -------------------------- ----------------------------------------------------------------
  **Data Exchange   **Business         **What you need to develop **Where the information will be available**
  Specification**   Data/Functions**   your software              
                                       (Specifications and        
                                       Guides)**                  

  Mail.dat (Release eDoc/Postage       Mail.dat 09-1              [[www.maildat.org]{.underline}](http://www.maildat.org/)
  1)                Statements         Specification              

                                       *PostalOne!* System        [[http://ribbs.usps.gov/]{.underline}](http://ribbs.usps.gov/)
                                       Mail.dat Technical Guide   
                                       for Full-Service           

                                                                   

  Mail.XML (Release Full-service Data  Mail.XML Specification     [[www.mailxml.org]{.underline}](http://www.mailxml.org/)
  1)                Distribution       version 6.0-A              

                                       *PostalOne!* Technical     [[http://ribbs.usps.gov/]{.underline}](http://ribbs.usps.gov/)
                                       Guide for Mail.XML 6.0     

                                                                  

  Mail.XML (future  eDoc/Postage       Mail.XML Specification     [[www.mailxml.org]{.underline}](http://www.mailxml.org/)
  release)          Statements/Web     version 6.0                
                    Services                                      
                    Appointments                                  

                                       *PostalOne!* Technical     [[http://ribbs.usps.gov/]{.underline}](http://ribbs.usps.gov/)
                                       Guide for Mail.XML 6.0     
  ----------------- ------------------ -------------------------- ----------------------------------------------------------------

***Figure 3: Specification and Guide Reference***

In addition to the presort documentation required today, the
full-service mailer's electronic documentation will contain information
about Intelligent Mail barcodes applied to mailpieces, trays, sacks, and
containers (where required as part of a customer/supplier agreement).
The documentation must include the unique Intelligent Mail barcode
applied to each mailpiece in a mailing, the unique Intelligent Mail®
Tray barcode applied to each tray or sack, as well as the unique
Intelligent Mail® Container barcode applied to each container in a
mailing (when containerization is required). The documentation must also
describe how mailpieces are linked to (or nested within) handling units,
such as trays and sacks, and how mailpieces and handling units are
linked to containers (when containerization is required). The
documentation must also identify the preparer of the mailing and the
mailer for whom the mailing is prepared (i.e., Mail Owner, if
applicable). Both the Mail.dat and Mail.XML file specifications will
support this required nesting and barcode information.

## Mixed Mailings 

The USPS will allow full-service and basic option mailpieces with
Intelligent Mail barcodes as well as pieces with POSTNET barcodes to be
combined in a single mailing, including copalletized mailings, when
appropriate documentation is provided.

Mailers who mix POSTNET, basic and full-service mailpieces in a bundle,
sack, tray or pallet and who wish to qualify the full-service mailpieces
as full-service must meet the following requirements:

1\) Include a mailpiece record in the mailpiece electronic documentation
for each POSTNET and basic option mailpiece in the mailing (see the
Piece Electronic Documentation sections of this document for details on
what must be included). This includes identifying each piece in the
electronic documentation as full-service, basic or POSTNET.

2\) Include a value of "M" for "Mixed" in the Full-Service Participation
Indicator field of the Segment (SEG) record for Mail.dat for Release 1.
In a future release, a value of "M" would be included in the
Full-Service Participation Indicator field in the MailingGroupData
message for Mail.XML.

3\) Follow all of the requirements for full-service mailings with the
exception that the POSTNET and basic option mailpieces in the mailing
are not required to include a unique Intelligent Mail barcode.

## Future Release: Combined Mailings of Standard Mail and Periodicals 

For Combined Mailings of Periodicals and Standard Mail Flats, the mailer
enters a service agreement approved by Business Mailer Support. This
agreement includes the mailing standards requirements for the Pilot
Program Combined Mailings of Periodicals and Standard Mail Flats that
defines the mail preparation, the standardized documentation, and the
postage calculations. Outside county containers are prorated by the
weight of the Periodicals in the container. Outside county chargeable
bundles are prorated by the copies of Periodicals in the bundle. Mailers
may use Mail.dat version 09-1 to send the data for these mailings. They
would populate the following fields:

  ------------------- ------------------------ --------------------------
  **File**            **Field**                **Appropriate Values**

  MPU                 Surcharge                N = Not Oversized

  SEG                 Principle Processing     FL = Flats
                      Category                 

  MPU                 Flat Machinability       Y = Machinable on ASFM 100
                                               or U = Machinable on USFM
                                               100

  SEG                 Class Defining           6 = Std/Periodical
                      Preparation              Comailings

  SEG                 Mailing Agreement Type   E = Combined Mail, Full
                                               Service, Basic Option
  ------------------- ------------------------ --------------------------

***Figure 4: Mail.dat for Combined Mailings***

In a future release, mailers may also use Mail.XML to provide this data
and would populate the following:

  ---------------------------- ------------------- -------------------------
  **File**                     **Field**           **Appropriate Values**

  LineItemSummaryData          Surcharge Type      N = No Surcharge

  SubmitPostageStatementData   Form Type           SM = Standard Mailing

  PeriodicalLineItemData       Machinable Flag     Y = Machinable
                               Indicator           
  ---------------------------- ------------------- -------------------------

***Figure 5: Mail.XML for Combined Mailings***

Periodicals pending application may be included in the Mail.dat file for
this combined mailing. For each Outside County container and Outside
County bundle, the container types, container levels, entry levels and
package levels must be the ones supported for Outside County chargeable
containers.  If full-service mailpieces are included, the PDR file will
be processed for these pieces and shall support the service measurement,
ACS and Confirm services if applicable.

## Copalletization

The copalletized portion of a mailing job is either:

-   bundles (flat-size mailpieces) of multiple Periodicals publications
    or editions on pallets;

-   bundles (flat-size pieces) of Standard Mail;

-   trays or sacks containing First-Class Mail letter or flat-size
    mailpieces of one Mail Owner commingled on pallets with trays or
    sacks of letter or flat-size mailpieces from a different mailing of
    the same Mail Owner or from one or more other Mail Owners;

-   trays or sacks containing Standard Mail letter or flat-size
    mailpieces of one Mail Owner commingled on pallets with trays or
    sacks of letter or flat-size mailpieces from a different mailing of
    the same Mail Owner or from one or more other Mail Owners.

Copalletized pallets may contain a mixture of any combination of
full-service, basic, POSTNET automation and non-automation
bundles/trays/sacks. Electronic documentation, as described in sections
3.10 , 3.11 and 3.12 of this document, must be provided for all
copalletized bundles/trays regardless of whether full-service
bundles/trays/sacks are included.

### Periodicals Scenario

For copalletization, the Mail Preparer at the originating site, the
consolidator at the copalletization site and the Postal Service enter a
service agreement approved by Business Mailer Support. For purposes of
this guide, a consolidator may be the same party as Mail Preparer. For
Periodicals, the DMM 707.27.2.1 states that this agreement shall
include: the mailer\'s name and address, the mailing office, procedures
and quality control measures for the copalletized mailing, the expected
date of the first mailing, and a sample of the standardized
documentation.

Periodicals mailers preparing full-service mailpieces in bundles that
will be copalletized at the ADC (or finer) level must follow all of the
requirements for full-service. Periodicals mailers preparing basic
mailpieces in bundles that will be copalletized at the ADC (or finer)
level will create the electronic documentation and postage statements
but are not required to create mailpiece level documentation. The
bundles shall be sorted to the sack level called the virtual sack. The
bundles may be physically in the sacks or on a pallet to be shipped to
the consolidator. The electronic documentation will also indicate, at
the virtual sack level, which bundles will be sent to a consolidator for
copalletization. In Mail.dat version 09-1, the creator of the
Periodicals bundle will place an "O" in the "Other Mail.dat Indicator"
field in CSM to indicate the original documentation. This will indicate
which bundles will be processed for copalletization. In a future
release, this is accomplished in Mail.XML 6.0 by placing an "O" in the
copalletization indicator in the OriginalContainerLinkage message set.
The electronic documentation must include the correct rate type and
service level indicator in the .CQT record for Mail.dat. In a future
release, the original container's identification must be linked with the
new identity through the OriginalContainerLinkage message set for
Mail.XML. This electronic data will be sent to the Postal Service to
generate standardized documentation and postage statements for the
portion of the mailing that is not being copalletized. The copalletized
bundles and the electronic documentation are then sent to the
consolidation site.

Consolidators at the consolidation site will receive the original
electronic data for the Periodicals bundles that will be copalletized.
The consolidator will move the bundles onto the correct pallets. When
creating a copalletized Periodicals mailing, the consolidator will use
the electronic data received from the creator of the Periodicals mailing
to create a new set of electronic data. Mail.dat version 09-1 files will
be updated by the consolidator with the new container information and
linked with the original Mail.dat files through the Original Container
Information (OCI) file created by the consolidator using the following
fields.

  -------------- --------------------------- -----------------------------
  **Mail.dat**                               

  **File**       **Field**                   **Appropriate Values**

  CSM            Other Mail.dat Indicator    L = Linked Information

  OCI            Original Job ID             Job ID from original Mail.dat

  OCI            Original Container ID       Container ID from original
                                             Mail.dat

  OCI            Original Segment ID         Segment ID from original
                                             Mail.dat

  OCI            Original User License Code  User License Code of the user
                                             that submitted the original
                                             Mail.dat

  OCI            Original Display Container  Display Container ID from
                 ID                          original Mail.dat

  OCI            Original Container Barcode  Container Barcode from
                                             original Mail.dat (if
                                             existed)

  OCI            New Job ID                  The new Job ID assigned to
                                             this job by the consolidator

  OCI            New Container ID            The Container ID assigned be
                                             the consolidator
  -------------- --------------------------- -----------------------------

***Figure 6: Mail.dat for Periodicals Copalletization***

In a future release, Mail.XML messages may also be updated by the
consolidator with the new container information and linked with the
original Mail.XML messages through the Original Container Linkage Create
and Cancel Request/Response message sets created by the consolidator.

  ------------------- ------------------------ --------------------------
  **Mail.XML**                                 

  **File**            **Block**                **Description**

  Original Container  Submitting Party         The Mailer ID, Customer
  Linkage Create      Identifier               Registration ID, or
  Request                                      Scheduler ID of the party
                                               who submitted the original
                                               Mail.XML

  Original Container  Submitting Software      Software information
  Linkage Create                               including software
  Request                                      approval information from
                                               the USPS

  Original Container  Original Container       Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               original container and the
                                               other for Mail.XML mailing
                                               group and container
                                               information for the
                                               original container plus
                                               the required container
                                               barcode.

  Original Container  Linked Container         Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               copalletized/new container
                                               and the other for Mail.XML
                                               mailing group and
                                               container information for
                                               the copalletized/new
                                               container plus the
                                               required container
                                               barcode.
  ------------------- ------------------------ --------------------------

***Figure 7: Mail.XML for Periodicals Copalletization***

This electronic documentation can be accessed by the Postal Service
acceptance office for the consolidator and will be used to create the
standardized documentation and the postage statements for the
copalletized mailing. The postage statements will be for each USPS
Publication Number and Issue in the copalletized mailing.

### Standard Mail Flat-size Bundles Scenario

For Standard Mail copalletization the mailer must have an approved
service agreement with Business Mailer Support. To copalletize different
Standard Mail flat-size mailings, the mailer must consolidate on pallets
all independently sorted bundles from each mailing to achieve the finest
presort level for the mailing as required in DMM 705.8.7.4.  Standard
Mail mailers preparing full-service mailpieces in bundles that will be
copalletized must follow all of the requirements for full-service and
prepare the electronic data to support the standardized documentation.
Standard Mail mailers preparing basic mailpieces in bundles that will be
copalletized must prepare electronic data to support the standardized
documentation and postage statements but are not required to create
mailpiece level electronic documentation.

The bundles selected for copalletization shall be sorted to the sack
level called the virtual sack. The bundles may be physically in the
sacks or on a pallet to be shipped to the consolidator. The electronic
documentation will also indicate, at the virtual sack level, which
bundles will be sent to a consolidator for copalletization. In Mail.dat
version 09-1, the creator of the Standard Mail bundle will place an "O"
in the "Other Mail.dat Indicator" field in CSM to indicate the original
documentation. This will indicate which bundles will be processed for
copalletization. In a future release, this is accomplished in Mail.XML
6.0 by providing original container information and linking the original
container information with linked container information through the
OriginalContainerLinkageCreateRequest message. The electronic
documentation must include the correct rate type and service level
indicator in the CQT for Mail.dat and, in a future release, in the
OriginalContainerLinkageCreateRequest message for Mail.XML. This
electronic data will be sent to the postal service to generate
standardized documentation and postage statements for the portion of the
mailing that is not being sent to the consolidator for copalletization.
The copalletized bundles and the electronic documentation are then sent
to the consolidation site.

Consolidators at the origin site who copalletize Standard Mail will
receive the original electronic data for the bundles that will be
copalletized. The consolidator will move the bundles onto the correct
pallets. When creating a copalletized Standard Mail mailing, the
consolidator will use the electronic data received from the creator of
the Standard Mail mailing to create a new set of electronic data.
Mail.dat version 09-1 files will be updated by the consolidator with the
new container information and linked with the original Mail.dat files
through the Original Container Information (OCI) file created by the
consolidator.

  -------------- --------------------------- -----------------------------
  **Mail.dat**                               

  **File**       **Field**                   **Appropriate Values**

  CSM            Other Mail.dat Indicator    L = Linked Information

  OCI            Original Job ID             Job ID from original Mail.dat

  OCI            Original Container ID       Container ID from original
                                             Mail.dat

  OCI            Original Segment ID         Segment ID from original
                                             Mail.dat

  OCI            Original User License Code  User License Code of the user
                                             that submitted the original
                                             Mail.dat

  OCI            Original Display Container  Display Container ID from
                 ID                          original Mail.dat

  OCI            Original Container Barcode  Container Barcode from
                                             original Mail.dat (if
                                             existed)

  OCI            New Job ID                  The new Job ID assigned to
                                             this job by the consolidator

  OCI            New Container ID            The Container ID assigned be
                                             the consolidator
  -------------- --------------------------- -----------------------------

***Figure 8: Mail.dat for Standard Mail Flat Bundle Copalletization***

In a future release, Mail.XML messages will be updated by the
consolidator with the new container information and linked with the
original Mail.XML messages through the
OriginalContainerLinkageCreateRequest message created by the
consolidator.

  ------------------- ------------------------ --------------------------
  **Mail.XML**                                 

  **File**            **Block**                **Description**

  Original Container  Submitting Party         The Mailer ID, Customer
  Linkage Create      Identifier               Registration ID, or
  Request                                      Scheduler ID of the party
                                               who submitted the original
                                               Mail.XML

  Original Container  Submitting Software      Software information
  Linkage Create                               including software
  Request                                      approval information from
                                               the USPS

  Original Container  Original Container       Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               original container and the
                                               other for Mail.XML mailing
                                               group and container
                                               information for the
                                               original container plus
                                               the required container
                                               barcode.

  Original Container  Linked Container         Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               copalletized/new container
                                               and the other for Mail.XML
                                               mailing group and
                                               container information for
                                               the copalletized/new
                                               container plus the
                                               required container
                                               barcode.
  ------------------- ------------------------ --------------------------

***Figure 9: Mail.XML for Standard Mail Flat Bundle Copalletization***

This electronic documentation can be accessed by the Postal Service
acceptance office for the consolidator and will be used to create the
standardized documentation and the postage statements for the
copalletized mailing.

### First-Class Mail in Trays Scenario

For First-Class Mail copalletization the mailer must have an approved
service agreement with Business Mailer Support. First-Class Mail mailers
preparing full-service mailpieces in trays that will be copalletized
must follow all of the requirements for full-service and prepare the
electronic data to support the standardized documentation.

First-Class Mail mailers preparing basic mailpieces in trays that will
be copalletized must prepare electronic data to support the standardized
documentation and postage statements but are not required to create
mailpiece level electronic documentation. All trays prepared as part of
a copalletized mailing, regardless of whether they will be copalletized,
must have an Intelligent Mail Tray barcode applied to the tray.

In Mail.dat version 09-1, the creator of the First-Class Mail tray will
place an "O" in the "Other Mail.dat Indicator" field in CSM to indicate
the original documentation. This will indicate which trays will be
processed for copalletization. In a future release, this is accomplished
in Mail.XML 6.0 by providing original container information and linking
the original container information with linked container information
through the OriginalContainerLinkageCreateRequest message. The
electronic documentation must include the correct rate type and service
level indicator in the CQT record for Mail.dat and must provide correct
identification of containers through the Mail.XML messages. This
electronic data will be sent to the Postal Service to generate
standardized documentation and postage statements for the entire mailing
at the origin site (including trays indicated for copalletization) and
all trays are included in the origin site postage statement. The
copalletized trays are then sent to the consolidation site for
copalletization.

Consolidators at the origin site who copalletize First-Class Mail will
receive the original electronic data for the trays that will be
copalletized. The consolidator will move the trays onto the correct
pallets. When creating a copalletized First-Class Mail mailing, the
consolidator will use the electronic data received from the creator of
the First-Class Mail mailing to create a new set of electronic data.
Mail.dat version 09-1 files will be updated by the consolidator with the
new container information and linked with the original Mail.dat files
through the Original Container Information (OCI) file created by the
consolidator.

  -------------- --------------------------- -----------------------------
  **Mail.dat**                               

  **File**       **Field**                   **Appropriate Values**

  CSM            Other Mail.dat Indicator    L = Linked Information

  OCI            Original Job ID             Job ID from original Mail.dat

  OCI            Original Container ID       Container ID from original
                                             Mail.dat

  OCI            Original Segment ID         Segment ID from original
                                             Mail.dat

  OCI            Original User License Code  User License Code of the user
                                             that submitted the original
                                             Mail.dat

  OCI            Original Display Container  Display Container ID from
                 ID                          original Mail.dat

  OCI            Original Container Barcode  Container Barcode from
                                             original Mail.dat (if
                                             existed)

  OCI            New Job ID                  The new Job ID assigned to
                                             this job by the consolidator

  OCI            New Container ID            The Container ID assigned be
                                             the consolidator
  -------------- --------------------------- -----------------------------

***Figure 10: Mail.dat for First-Class Mail Tray Copalletization***

In a future release, Mail.XML messages may also be updated by the
consolidator with the new container information and linked with the
original Mail.XML messages through the Original Container Linkage Create
and Cancel Request/Response message sets created by the consolidator.

  ------------------- ------------------------ --------------------------
  **Mail.XML**                                 

  **File**            **Block**                **Description**

  Original Container  Submitting Party         The Mailer ID, Customer
  Linkage Create      Identifier               Registration ID, or
  Request                                      Scheduler ID of the party
                                               who submitted the original
                                               Mail.XML

  Original Container  Submitting Software      Software information
  Linkage Create                               including software
  Request                                      approval information from
                                               the USPS

  Original Container  Original Container       Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               original container and the
                                               other for Mail.XML mailing
                                               group and container
                                               information for the
                                               original container plus
                                               the required container
                                               barcode.

  Original Container  Linked Container         Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               copalletized/new container
                                               and the other for Mail.XML
                                               mailing group and
                                               container information for
                                               the copalletized/new
                                               container plus the
                                               required container
                                               barcode.
  ------------------- ------------------------ --------------------------

***Figure 11: Mail.XML for First-Class Mail Tray Copalletization***

This electronic documentation can be accessed by the Postal Service
acceptance office for the consolidator.

### Standard Mail in Trays Scenario

For Standard Mail copalletization the mailer must have an approved
service agreement with Business Mailer Support. Standard Mail mailers
preparing full-service mailpieces in trays that will be copalletized
must follow all of the requirements for full-service. Standard Mail
mailers preparing basic mailpieces in trays that will be copalletized
must prepare electronic data to support the standardized documentation
and postage statements but are not required to create mailpiece level
electronic documentation. All trays prepared as part of a copalletized
mailing, regardless of whether they will be copalletized, must have an
Intelligent Mail Tray barcode applied to the tray.

In Mail.dat version 09-1, the creator of the Standard Mail tray will
place an "O" in the Other Mail.dat Indicator field in CSM to indicate
the original documentation. This will indicate which trays will be
processed for copalletization. In a future release, this is accomplished
in Mail.XML 6.0 by utilizing the OriginalCOntainerLinkageCreateRequest
message set. The electronic documentation must include the correct rate
type and service level indicator in the CQT for Mail.dat and correct
identification of containers through the Mail.XML message set.. This
electronic data will be sent to the Postal Service to generate
standardized documentation and postage statements for the entire mailing
at the origin site (including trays indicated for copalletization) and
all trays are included in the origin site postage statement. The
copalletized trays are then sent to the consolidation site for
copalletization.

Consolidators at the consolidation site will receive the original
electronic data for the trays that will be copalletized. The
consolidator will move the trays onto the correct pallets. When creating
a copalletized mailing with Standard Mail trays, the consolidator will
use the electronic data received from the origin to create a new set of
electronic data. Mail.dat version 09-1 files will be updated by the
consolidator with the new container information and linked with the
original Mail.dat files through the Original Container Information (OCI)
file created by the consolidator.

  -------------- --------------------------- -----------------------------
  **Mail.dat**                               

  **File**       **Field**                   **Appropriate Values**

  CSM            Other Mail.dat Indicator    L = Linked Information

  OCI            Original Job ID             Job ID from original Mail.dat

  OCI            Original Container ID       Container ID from original
                                             Mail.dat

  OCI            Original Segment ID         Segment ID from original
                                             Mail.dat

  OCI            Original User License Code  User License Code of the user
                                             that submitted the original
                                             Mail.dat

  OCI            Original Display Container  Display Container ID from
                 ID                          original Mail.dat

  OCI            Original Container Barcode  Container Barcode from
                                             original Mail.dat (if
                                             existed)

  OCI            New Job ID                  The new Job ID assigned to
                                             this job by the consolidator

  OCI            New Container ID            The Container ID assigned be
                                             the consolidator
  -------------- --------------------------- -----------------------------

***Figure 12: Mail.dat for Standard Mail Tray Copalletization***

In a future release, Mail.XML messages may also be updated by the
consolidator with the new container information and linked with the
original Mail.XML messages through the Original Container Linkage Create
and Cancel Request/Response message sets created by the consolidator.

  ------------------- ------------------------ --------------------------
  **Mail.XML**                                 

  **File**            **Block**                **Description**

  Original Container  Submitting Party         The Mailer ID, Customer
  Linkage Create      Identifier               Registration ID, or
  Request                                      Scheduler ID of the party
                                               who submitted the original
                                               Mail.XML

  Original Container  Submitting Software      Software information
  Linkage Create                               including software
  Request                                      approval information from
                                               the USPS

  Original Container  Original Container       Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               original container and the
                                               other for Mail.XML mailing
                                               group and container
                                               information for the
                                               original container plus
                                               the required container
                                               barcode.

  Original Container  Linked Container         Has two blocks, one for
  Linkage Create                               Mail.dat job and container
  Request                                      information for the
                                               copalletized/new container
                                               and the other for Mail.XML
                                               mailing group and
                                               container information for
                                               the copalletized/new
                                               container plus the
                                               required container
                                               barcode.
  ------------------- ------------------------ --------------------------

***Figure 13: Mail.XML for Standard Mail Tray Copalletization***

This electronic documentation can be accessed by the Postal Service
acceptance office for the consolidator.

## Future Release: Manifest Mailings

With authorization from the USPS, mailers may participate in a manifest
mailing program. This program requires mailers to utilize an automated
system to document postage and fees for all pieces in a mailing paid via
permit imprint indicia. Each piece in the mailing is assigned a unique
identification number that may be compared with the manifest. To
participate in the program, mailers must develop or use a computerized
system that generates documentation to support mailings. When using the
sequential manifesting options listed below, both the unique
identification number on the mailpiece and the unique Intelligent Mail
barcode must be sequential and contiguous.

Mailers participating in the manifest mailing program can use either the
sequential or non-sequential piece electronic documentation options
described in this document for Mail.dat or Mail.XML. Mailers will place
the unique identification number (human readable) as well as the
Intelligent Mail barcode applied to the mailpiece in the electronic
documentation. When using Mail.dat for sequential or non-sequential
piece electronic documentation, the unique identification number is
placed in the Piece ID field and the Intelligent Mail barcode is placed
in the IM Barcode field of the Piece Detail Record (PDR) file.
Mailpieces that are planned but are not created would be identified by
placing a "W" or an "S" (when a postage adjustment is desired) and by
"X" and "T" when postage adjustment is not desired in the Wasted Or
Shortage Piece Indicator field (in Mail.dat 09-1 -W and X are used for
Wasted, S and T for Shortage). If the manifest mailer is using the
unique Intelligent Mail barcode as the unique identification number on
the mailpiece, they may populate the IM Barcode Range File (IMR record)
-- with job id, containerid, IMR ID, class, lowerrange, upperrange,
By/For, full-service indicator, piece count, closing character in
Mail.dat 09-1. These fields in Mail.dat 09-1 are populated with 15
digits (6/9 digit Mailer ID, 9/6 digit Serial Number) Sequences must be
contiguous and may not overlap among containers in a mailing or between
mailings by class during the 45-day period for barcode uniqueness.

When using Mail.XML for the non-sequential piece electronic
documentation, the unique identification number is placed in the
MailPieceID xml block and the Intelligent Mail barcode is placed in the
IMB xml block of the MailPieceCreateRequest message's PDRMailpieceblock
or MailPieceblock. Mailpieces that are planned but are not created would
be identified by placing a "W" or "X" for wasted or an "S" or a "T" for
shortage in the WastedPieceIndicator field (available in Mail.XML
version 6.0). When using Mail.XML for the sequential piece electronic
documentation, the first unique identification number used is placed in
the SerialNumber9/6 field of the IMBarcodeLowerSerialization field and
the last unique identification number used is placed in the
SerialNumber9/6 field of the IMBarcodeUpperSerialization field
(available in Mail.XML version 6.0 in the PieceRange XML block) while
the Mailer IDs are placed in the Mailer ID 6/9 field within the same XML
blocks. Mailpieces that are planned but are not created would be
identified by creating a record in the MailPieceCreate or Update request
message for each mailpiece and placing a "W" or an "S" in the
WastedPieceIndicator field (available in Mail.XML version 6.0).

## Spoilage and Shortage

During the course of a mailing, there are typically mailpieces that were
included in the electronic documentation but were never created. The
electronic documentation will need to be updated to reflect adjustments
to a mailing due to spoilage (wasted), shortages, or other anomalies
that affect the piece count of a postage statement or mailing job.

Spoiled mailpieces are those pieces for which electronic documentation
has been provided to the USPS but during the production of the pieces
get spoiled for any number of reasons. Shortages can occur in mailing
environments where a mailer may not mail a whole container (pallet or
handling unit), but rather will mail only a partial container (pallet or
handling unit). In a shortage specific postage adjustment where the
entire container will not be included in the mailing, the mailer will be
required to cancel or delete the whole container at the Mail.dat CSM
(Container Summary) file level. In the case where only part of a
container will be excluded from the mailing, the mailer must send a
Mail.dat PDR (in a future release Mail.XML MailPieceCreate and
MailPieceUpdate messages) which sets the WastedPiece Indicator field to
'S\' or 'W' for the mailpieces that will not be included in the mailing.
In version 09-1 of Mail.dat, a value of 'S' will be placed in the Wasted
or Shortage Piece Indicator field to identify shortage pieces and "W"
will be used for spoiled (wasted) mailpieces. In a future release, this
is accomplished in version 6.0 of Mail.XML by placing an "S" in the
WastedPiece Indicator field for shortage mailpieces and a "W" for
spoiled mailpieces.

Shortage and spoilage related postage adjustments must occur against
postage statements that have not been finalized. If all postage
statements for a mailing have been finalized, then spoilage related
postage adjustments will only occur through the existing refund request
process.

While the ultimate goal of the USPS is to mandate the provision of piece
level electronic information for spoilage, certain mailer technologies
do not currently support that capability. For full-service, the USPS
will allow postage adjustments to occur without specific piece level
information for certain mailing environments as technologies and
processes are defined to move to providing piece specific spoilage
information. Regardless of the method used, the spoiled pieces must be
made available for verification prior to adjusted postage statement(s)
finalization.

In non-manifest mail environments today, two options exist for spoilage
related postage adjustment.

-   Solution 1: Mailers may identify the dollar amount and specific
    postage statements of spoiled pieces and request the USPS to adjust
    postage for the spoiled pieces.

-   Solution 2: Mailers that cannot specify the specific postage
    statements of the spoiled mailpieces request the postage adjustment
    dollar amount and the USPS will select the postage statement.

Regardless of the option selected above, the USPS will support the two
following solutions for providing spoilage information in Mail.dat 09-1
and, in a future release, Mail.XML v6.0 versions.

Solution 1: The mailer will be allowed to provide a mailer generated
postage statement sequence number and all other required fields that
identify unique postage processing. This will be accomplished in
Mail.dat using the new, optional Postage Statement Header File that will
provide linkage with the CSM containers to identify containers on a
postage statement. This new Postage Statement Header file will also be
linked with the PAR file through a Unique Record Identifier field,
linking an adjustment transaction to a unique postage statement. The new
postage statement header file will then be used, if provided, in
conjunction with the PAR file to adjust postage. In a future release,
this will be accomplished in Mail.XML using the new
PostageAdjustmentCreateRequest/Response Message which will refer to an
existing postage statement by providing the StatementID.

Solution 2: In the absence of the Mail.dat Postage Statement Header file
(this does not apply to Mail.XML since all postage statement documents
in Mail.XML can be uniquely identified), which is optional, the mailer
will submit postage adjustment information. In Mail.dat, a PAR record is
submitted to adjust postage. Upon receipt of postage adjustment
information, the USPS will then find the best possible postage statement
that is not yet finalized and supports the adjustments for the spoiled
pieces. For this solution, the USPS will adjust the most recently
created postage statement related to the Mail.dat submitted for the
mailing (tied to the mailer's Permit number) and adjust postage based
upon spoiled piece count and the dollar amount provided by the mailer.
If the most recent postage statement generated tied to the PAR
transaction does not have enough pieces or copies to fulfill the
spoilage adjustment, then the next most recently generated postage
statement will be adjusted. This process will be repeated until the
correct number of mailpieces has been deducted from postage statements
to accommodate the spoilage adjustment. If no finalized postage
statements are available for the mailing, then the USPS identified
refund process will need to be initiated by the customer.

In a future release, a Mail.XML PostageAdjustmentCreatemessage is used
to adjust postage. If postage was filed through Mail.XML then the
postage statement can be uniquely identified. However if the postage
statement was created based upon Mail.dat data sent to the USPS and the
Mail.XML message is used to adjust postage then the unique postage
statement identifier may not be available. In that case, the USPS will
follow exact same rules identified above for a Mail.dat PAR adjustment
without unique postage identification. The USPS will find the most
recent and eligible postage statement for adjustment. If no finalized
postage statements are available for the mailing, then the USPS
identified refund process will need to be initiated by the customer.

### Piece Level Spoilage and Shortage

Mailers have the ability to identify the specific mailpiece that was
spoiled and where in the mailing a mailpiece was spoiled. In this
scenario, updated piece level electronic documentation through Mail.dat
or Mail.XML would be submitted to *PostalOne!* to identify the specific
mailpieces that were spoiled. The original electronic documentation
would indicate the handling unit to which this mailpiece was associated.
These electronic updates can be sent via Mail.dat using the PDR or
Mail.XML using the Mail.XML MailPieceCreate and MailPieceUpdate
Request/Response messages. For either option, the mailer will indicate
the wasted piece by placing a \'W\' in the WastedPiece Indicator field
for the mailpieces that were spoiled.

## Multi-Line Optical Character Reader (MLOCR) Mailers

An MLOCR Mailer is any Mail Preparer who uses Multi-Line Optical
Character Reader (MLOCR) or Bar Code Sorter machines to sort mail that
has the name and address applied to the mailpiece prior to processing on
the MLOCR machine. These mailpieces may have an Intelligent Mail barcode
applied by the Mail Owner (or other party) prior to sortation on the
MLOCR machine. Mail Preparers are required to honor requests from the
Mail Owners to use the Mail Owner's Mailer ID in the Intelligent Mail
barcode on the mailpiece. There are three options the MLOCR Mailer can
employ for applying the Intelligent Mail barcode to mail sorted on an
MLOCR machine.

Option 1: Use the MID and Serial Number Applied by the Mail Owner

Mail Owners (or other parties) may apply an Intelligent Mail barcode to
the mailpiece when the name and address is applied. If the full-service
mailpieces already have a unique Intelligent Mail barcode applied, the
MLOCR Mailer may capture the Mailer ID and/or Serial Number of the
original Intelligent Mail barcode on the mailpiece and use that to
populate the piece level electronic documentation for a full-service
mailpiece. In addition, the MLOCR Mailer may also use the captured
Mailer ID and/or Serial Number to populate the Mailer ID and Serial
Number field in the new Intelligent Mail barcode if the MLOCR Mailer
applies a new Intelligent Mail barcode on the mailpiece. By applying a
new Intelligent Mail barcode, the MLOCR Mailer can alter the delivery
point portion of the Intelligent Mail barcode to comply with the USPS
delivery point standards.

Option 2: Use the Mail Owner's MID

The Mail Owner may direct the MLOCR Mailer to use the Mail Owner's
Mailer ID in the Intelligent Mail barcode sprayed by the MLOCR Mailer on
the mailpieces. In this option, the MLOCR Mailer would generate a unique
Serial Number for full-service mailpieces to use with the Mail Owner's
Mailer ID in the Intelligent Mail barcode. To create the unique Serial
Number, the MLOCR mailer may assign a range of Serial Numbers to a
specific machine, thus maintaining uniqueness across multiple machines
without requiring the machines to communicate. Alternatively, the MLOCR
Mailer may connect the machines in their facility to communicate with a
central database which will control the Serial Number generation process
and ensure unique Serial Numbers are applied across all mailpieces using
a specific Mailer ID. The MLOCR Mailer may also use other proprietary
methods of generating a serial number providing that the Intelligent
Mail barcode remains unique for the required time period.

Option 3: Use the MLOCR Mailer MID

The MLOCR Mailer can use his/her own Mailer ID to apply an Intelligent
Mail barcode on the mailpiece. In this option, the MLOCR Mailer would
generate a unique Serial Number for full-service mailpieces to use with
the MLOCR Mailer's Mailer ID in the Intelligent Mail barcode. To create
the unique Serial Number, the MLOCR mailer may assign a range of Serial
Numbers to a specific machine, thus maintaining uniqueness across
multiple machines without requiring the machines to communicate.
Alternatively, the MLOCR Mailer may connect the machines in their
facility to communicate with a central database which will control the
Serial Number generation process and ensure unique Serial Numbers are
applied across all mailpieces using a specific Mailer ID. The MLOCR
Mailer may also use other proprietary methods of generating a serial
number providing that the Intelligent Mail barcode remains unique for
the required time period.

Typically, the mail from each Mail Owner will be run separately on a
machine and information captured from that process will be used to
identify the Mail Owner in the By/For section of the electronic
documentation for those mailpieces. If that mail already contains mail
from multiple mail owners, the MLOCR Mailer would populate the By/For
section of the electronic documentation to identify the single source of
that mail (i.e. the MLOCR Mailer's customer).

When a Mail Owner has provided a small amount of mail, the MLOCR Mailer
has the option to combine that mail with mail from other low volume Mail
Owners and will not be required to identify the Mail Owners associated
to those mailpieces. The MLOCR Mailer is allowed to jackpot mail from
customers who provide less daily volume than 1% of the total average
daily volume processed at the MLOCR Mailer's facility or 3,000 pieces
(whichever is less). If the MLCOR Mailer chooses to jackpot multiple
customers using their own MID, they will be responsible for the address
quality of those pieces.

When mailpieces are rejected on an operation and grouped together across
Mail Owners to be re-run on a MLOCR machine, those mailpieces may use
the Mailer ID of the MLOCR Mailer and will not be required to identify
the Mail Owner in the electronic documentation. If the mailpiece is not
successfully processed when re-run, that mailpiece will be mailed at
machinable or single-piece prices and may or may not have an Intelligent
Mail barcode applied.

The permit number will be included in the Local Permit Reference Number
field of the MPA record in Mail.dat for all permit mail. The permit
number will be included in the permitNumber field of the
MailingAgentData message of the PostageStatementCreate message of
Mail.XML. Nonprofit Standard Mail must have the permit number whatever
the postage type is used to pay for the pieces.

For a normal MLOCR operation, the electronic documentation will be
submitted with qualification and postage data after first pass of the
mail through the MLOCR. For full-service mailings, the electronic
documentation will be updated with handling unit and container data
after second pass. Mailings prepared using a One-Pass Finalization
method will have electronic documentation submitted prior to production
of the combined mailing. After the mail is run, an update including the
actual sorter data will be submitted electronically.

## Continuous Mailers

A continuous Mailer is defined as one that regularly:

1.  Dispatches portions of the mailing to the USPS at multiple times
    throughout the production period of the total mailing.

2.  Provides a USPS Qualification Report for the multiple dispatches.

3.  May submit portions of the mailing to the USPS before qualification
    and postage documentation can be finalized.

Continuous Mailers will submit and generate documentation as follows:

1.  Create electronic documentation for each mailing prepared over the
    course of the production day. The production day is the period of
    time (not to exceed 24 hours) when mail is produced and dispatched.
    Submit the electronic documentation for the original planned mailing
    (e.g., list or One-Pass Finalization mailers) prior to production or
    after first pass (for MLOCR/BCS environment) to *PostalOne!.*
    Manifest mailers will submit documentation prior to production
    unless approved by Business Mailer Support. Payment for that
    production day will occur with the updated, final submission to the
    *PostalOne!* system or as stipulated in the mailer's postage payment
    system agreement.

> If portions of the planned mailing as originally submitted in the
> electronic documentation are not dispatched during the production day
> and these portions will be moved to the next day's mailing, then the
> updated, final submission to *PostalOne!* must reflect the removal of
> those pieces and the proper qualification of all remaining pieces in
> the dispatched portion. The non-dispatched portion which is moved to a
> different mailing must be re-qualified for the prices for which they
> are prepared.

2.  Alternatively, mailings submitted across multiple days will be
    represented in an original submission of electronic documentation.
    In this scenario, payment is made as stipulated in the mailer's
    postage payment system agreement for the containers dispatched
    during each production day, provided that the documentation
    represents pieces associated to physical handling units and physical
    containers. Payment is accomplished by updating the electronic
    documentation and marking those containers as ready to pay.

Continuous Mailers will have Customer Supplier Agreements (CSA) with the
Postal Service as described in this guide. The CSA will define how and
when the mailing must be dispatched for start-the-clock purposes.
Container information will be submitted to the *PostalOne!* system for
all the containers on the associated postage statement for that
production day. Dispatch information for the containers that are
complete and ready for acceptance and payment will be submitted to
*PostalOne!* in a transportation update.

## Customer Supplier Agreements (CSA)

A Customer Supplier Agreement (CSA) is a written agreement that confirms
for a commercial mailer the origin-entry preparation requirements,
acceptance window, and schedule of transportation times. For complete
details on how to use a CSA, reference the Guide to Customer Supplier
Agreements which can be found at <http://ribbs.usps.gov/>.

The objective of a CSA is:

-   To formalize agreement on criteria used to determine Start the Clock
    Day-Zero (Day-0) to create a common understanding between the USPS
    and mailers.

-   To approve later acceptance times and describe the separation
    requirements to qualify for those times.

-   To provide a structured format to support presort software developed
    to create separations and container labels for full-service
    requirements.

-   To describe separation and containerization standards requested of
    the mailer that are not covered in the required or optional
    containerization requirements described in the Domestic Mail Manual
    (DMM).

**Note: CSA preparation requirements take precedence when applicable.**

A CSA will be created if the following conditions exist:

-   For any mailer entering mail that is origin entered and verified at
    the mailer's facility (for example, a DMU)

-   For any mailer entering mail after critical acceptance time or a
    large volume mailer entering mail at an agreed upon acceptance time
    before critical acceptance time at an origin Bulk Mail Entry Unit
    (BMEU)

The CSA is a standardized format based on a template that will establish
an agreement between the USPS and mailer, and includes an agreed upon
effective date. The CSA confirms for a business mailer the origin-entry
preparation requirements, and the acceptance window and schedule of
transportation times for all origin entered mail classes with a CSA. For
complete details on how to use a CSA, reference the Guide to Customer
Supplier Agreements which can be found at <http://ribbs.usps.gov/>.

### Using the *PostalOne!* Transportation Management System

Mailers with a PostalOne! Transportation Management System (TMS) have
the capability to dynamically assign handling units (i.e., trays) to
transportation routes. Examples of dynamic assignment are: a tray for
ZIP Code 600 is run through the TMS at 9 am and receives an airline
assignment, another tray for ZIP Code 600 is run through the TMS at 11
am and receives a surface assignment; or a tray for ZIP Code 945 is run
through the TMS at 3 pm and receives an airline assignment of American
Airlines, a tray for ZIP Code 945 is run through the TMS at 6 pm and
receives an airline assignment of Continental Airlines. The CSA for
mailers using a TMS will identify the appropriate dispatch to which
those assignments will be associated. The contingency plan for sites
with TMS is: if there is no connection to S-AMS for less than one hour,
the mailer with run all the trays for air transportation prepared during
that time through the TMS to get the air assignment. If there is no
connection to S-AMS for longer than one hour, the mailer is not required
to run trays prepared during that time through TMS to get a route
assignment. The mailer is still responsible for providing Intelligent
Mail Tray barcodes in their electronic documentation regardless of an
available connection to S-AMS. The CSA air container separations will
show the same Container Destination Zip Codes in that column in Exhibit
6.

The CSA for mailers with a TMS will contain surface separations along
with a default air separation. That default air separation will likely
be broken into multiple lines in the CSA downloadable file so that the
various labeling options may be accurately reflected. The TMS can also
be used to make surface separations with those separations entered into
the TMS by loading the CSA file or through a manual data entry process.
The CSA will contain labeling instructions for the surface separations
as well.

### Applying the Customer Supplier Agreement

Physical or logical containers are associated to trips by including the
trip number in the Truck or Dispatch Number field of the .CSM file in
Mail.dat or the ContainerInfoData message in Mail.XML and completing the
Dispatch Date/Time fields. Often, because of the volume produced at the
facility, the Postal Service will provide multiple trailers to a single
entry point. For example, if the facility produces enough volume that
will be transported on air transportation to fill three trailers, the
Postal Service would provide three separate trips (i.e., trailers).
These trips would each have a different trip number and might leave at
different times throughout the day. The association of all of the trips
going to a single entry point is called a logical dispatch.

When mailers can identify the specific trip on which a container
(logical or physical) will be transported, that trip number should be
used to associate containers to the trip in their electronic
documentation. When mailers do not know on which specific trip a
container will be transported, then they would associate those
containers to the logical dispatch. This is accomplished by associating
the containers to the trip number of the last physical dispatch of the
logical dispatch in the electronic documentation. If any information is
logical, then the whole dispatch will be a logical dispatch.

When the physical dispatches in the CSA will not accommodate the mail
volume for that day, mailers will request additional USPS transportation
according to their plant load agreement. When this situation occurs,
these physical dispatches will be subject to the CAT of the last
scheduled dispatch.

## Creating Appointments

The USPS requires appointment scheduling for drop ship mail and for
expedited plant loads at USPS facilities to enable more efficient
resource planning and service performance. Expedited plant loads are
those shipments where the mailer is transporting the mail to the USPS
facilities. The USPS FAST (Facility Access and Shipment Tracking) system
is the business processing engine that provides customers with
appointment scheduling capabilities for DBMC, DADC, and DSCF drop
shipments.

A Mail Owner or mailing agent must request a user account within the
*PostalOne!* system, which performs authentication and authorization
services for the FAST system.

There are two ways to create, update, cancel, and manage appointment
scheduling:

1\. By utilizing IDEAlliance Mail.XML (previously known as TM
Specification) Specification and *PostalOne!*/FAST Web services to
provide appointment logistics and content information. Information may
be provided using pure Web services (pure Web Services is defined as a
transaction where all logistics and all container detail information is
provided in the XML transaction by the customer), or Web Services in
conjunction with Mail.dat (Web Services with Mail.dat is defined as a
transaction where all logistics information is provided in the
customer's XML file and all or partial container detail information is
provided by the *PostalOne!* system from *PostalOne!* Mail.dat database.
All or partial container detail already exists in the *PostalOne!*
system and is appended to customer's XML transaction and sent to FAST).

2\. By accessing the FAST website at
[https://fast.usps.com](https://fast.usps.com/), to request an
appointment. This online FAST process does not allow the customer to
provide content (container) detail information, such as IM Container
barcode, weight, pieces, and many other characteristics. One time
appointments created online must be updated via Mail.XML to provide
container information via pure Web services or via Web services with
Mail.dat for full-service option.

The customer can send a content update with a "T" transportation update
data transaction using Mail.dat for recurring appointments only. A 'T'
transportation update to provide content details to *PostalOne!* and
FAST for Full-service option is a valid content update method but this
Mail.dat 'T' update method does not apply to one time appointments. One
time appointments created online or through Web Services must be updated
via Mail.XML to provide container information.

For details on how to create appointments using Web Services, refer to
the *PostalOne! -* FAST Web Services Technical Guide found at
<http://www.usps.com/postalone/_pdf/FASTWebServicesTechnicalGuide.pdf>
or <http://www.usps.com/postalone/autodropshipschedule.htm> and the
Mail.XML Specifications found at the IDEAlliance website
[www.maildat.org](http://www.maildat.org/).

For details on how to create appointments via the FAST online system,
refer to the FAST Customer User guide found at
<https://fast.usps.com/userguide/CustomerUserGuide.pdf>.

### Joint Scheduling:

Joint Scheduling process is defined as an appointment management process
where more than one business entity is involved in providing electronic
data for a single appointment; logistics data (Facility, Day, time) or
content detail data (Container details) for a single appointment. The
Full-service requires that the content details data must be provided to
the USPS electronically. There are three possible scenarios to perform
joint scheduling electronically through Mail.XML with the PostalOne! --
FAST systems.

#### Scenario 1 

This scenario pertains to an existing relationship and understanding
between a Printer A and a Logistics company B, where the two parties
already know the future content and transportation needs of each other.
One business entity works with the other business entity, compiles all
logistics and content detail information and creates the appointment
with content details. So, in this scenario, one business entity is
sending all the data or referring to all data within the PostalOne! --
FAST systems for a single appointment.

-   Logistics company B works with Printer A and both understand each
    others on going business needs.

-   Printer A provides details on its containers to the Logistics
    company B for Appointment C.

-   Printer A, who may have already sent the container information to
    the PostalOne! system as part of eDoc, may just give the Primary Key
    data for Printer A's containers to Logistics company B.

    a.  The Printer A may use an excel sheet or may use Mail.XML Pickup
        messages or DeliveryContent messages to communicate the
        container data to the Consolidator A.

-   The Logistics company B refers to the container Key
    information(provided by Printer A, already in the PostalOne! System,
    when Logistics Company B creates the appointment with container
    details that belong to Printer A.

In this scenario, both Printer A and Logistics company B are eligible to
receive their closeout data through Mail.XML. Logistics company B will
receive the closeout data for all containers and Printer A will receive
the data only for Printer A containers on the Appointment C.

Communication method that Printer A uses to communicate Container Data
to Logistics B :

-   Mail.XML - DeliveryContentCreateRequest/Response

-   Mail.XML - DeliveryContentCancelRequest/Response

-   Mail.XML - DeliveryContentQueryRequest/Response

-   Can simply be an Excel file or a data file

Communication method that Printer A uses to create content within
PostalOne! -- FAST systems.

-   Mail.dat file set (CSM)

Messages Logistics company B uses to create/manage the appointment and
tie the Printer A's content data to the appointment:

-   Mail.XML - DeliveryApptCreateRequest/Response

-   Mail.XML - DeliveryApptUpdateRequest / Response

-   Mail.XML - DeliveryApptCancelRequest / Response

-   Mail.XML - DeliveryApptQueryRequest / Response

#### Scenario 2

This scenario pertains to an existing relationship and understanding
between a Printer A and a Logistics company B, where the two parties
already know the future content and transportation needs of each other.

In this scenario, two separate business entities provide electronic
information for one appointment.

-   Printer A creates a 'stand alone' content (information on
    containers) in the FAST system and receives one or more Content IDs
    from the FAST system for the containers.

-   Printer A then provides the Content Ids from the FAST system to
    Logistics company B.

-   The Logistics company B creates the Appointment C and in Logistics
    company B's appointment request, refers to the Content IDs that the
    Printer A received from the FAST System. The content created by the
    Printer A gets tied to an appointment created by the Logistics
    company.

In this scenario, both Printer A and Logistics B are eligible to receive
their closeout data through Mail.XML. Printer A will receive the data
only for Printer A containers on the Appointment C and Logistics B will
receive the closeout data for all containers on the Appointment C.

Communication method that Printer A uses to create content within
PostalOne! -- FAST systems.

-   Mail.XML - DeliveryContentCreateRequest/Response

-   Mail.XML - DeliveryContentCancelRequest/Response

-   Mail.XML - DeliveryContentQueryRequest/Response

Communication method that Printer A uses to communicate the Content IDs
to Logistics B company

-   Mail.dat file set (CSM)

-   Can simply be an Excel file or a data file

Messages Logistics company B uses to create/manage the appointment and
tie the Printer A's content data to the appointment:

-   Mail.XML - DeliveryApptCreateRequest/Response

-   Mail.XML - DeliveryApptUpdateRequest / Response

-   Mail.XML - DeliveryApptCancelRequest / Response

-   Mail.XML - DeliveryApptQueryRequest / Response

-   

#### Scenario 3 

This scenario pertains to an LTL (Less than a Load) environment where
the Logistics Company B has no common understanding about the contents
or logistics needs of a Printer A. In this scenario, two separate
business entities provide electronic information for one appointment.

The small LTL logistics provider B always has certain Shell appointments
(only Facility, day/time is identified) created in the FAST system to
Facilities where he takes the mail. The company B does not know the
content information and don't know whose content they may be hauling
once they are hired.

-   A small logistics company B creates an appointment C only with
    Logistics information (Shell Appointment).

-   Printer A starts shopping for a Logistics provider who can take some
    containers to a USPS facility. The Printer A finds Logistics company
    B and asks Logistics company B for an appointment ID.

-   Printer A, after receiving the appoint ID C, then sends Content
    message to FAST while tying the Content to the company B's
    appointment.

-   The Logistics company's Shell appointment gets tied to already
    existing content within the FAST system.

In this scenario, both Printer A and Logistics B are eligible to receive
their closeout data through Mail.XML. Printer A will receive the data
only for Printer A's containers on the Appointment C and Logistics B
will receive the closeout data for all containers on the appointment.

Communication method that Logistics company B uses to create Shell
appointments

-   DeliveryApptShellRequest / Response

-   DeliveryApptShellUpdateRequest / Response

-   DeliveryApptShellCancelRequest / Response

Communication method that Printer A uses to create/manage Content in the
PostalOne! -- FAST system.

-   Mail.XML - DeliveryApptCreateRequest/Response

-   Mail.XML - DeliveryApptUpdateRequest / Response

-   Mail.XML - DeliveryApptCancelRequest / Response

-   Mail.XML - DeliveryApptQueryRequest / Response

Communication method that Printer A uses to tie its content to Logistics
company B's Appointment ID in the FAST system

-   Mail.XML - DeliveryApptUpdateRequest / Response

## Mail.dat

Mail.dat is an industry-defined database structure consisting of files
linked by key fields. A Mail.dat submission to the *PostalOne!* system
consists of 20 files, each with its own record type, from which the USPS
can extract data necessary to create the postage statement and required
documentation. Mail.dat is one method mailers can use to submit
electronic data which includes postage statement information to the
Postal Service. Currently, the *PostalOne!* system supports Mail.dat
versions 07-1, 08-1, and Mail.dat version 08-2. Starting January 1,
2009, no new users will be activated in *PostalOne!* using these
versions. Starting May 11, 2009, *PostalOne!* will support only versions
08-2 and 09-1. Those interested in using Mail.dat for comprehensive
business function full-service support should use version Mail.dat 09-1.

**Note: When a site converts to Mail.dat version 09-1, the entire site
must convert (i.e. all Mail.dat submissions for that mailer location
must be version 09-1).**

For information about Mail.dat and how you can use Mail.dat to submit
electronic information refer to
[http://www.maildat.org/](http://www.maildat.org/ ) and
<http://ribbs.usps.gov/> where you will find the *PostalOne!* System
Mail.dat Technical Guide for Full-Service. Note: all references to
specifications in this document are subject to update as operational or
pricing initiative details are finalized.

### Mail.dat 09-1 -- *PostalOne!* System Implementation 

Mail.dat 09-1 will add functionality needed for the full-service option
as follows:

1.  Provides the capability to link logical handling units and
    containers to physical handling units and containers to support
    Multi-Line Optical Character Reader (MLOCR) and Barcode Sorters
    (BCS) in continuous mailing environments;

2.  Supports piece level electronic documentation requirements for basic
    and full-service options;

3.  Allows for linkage of original handling units (tray, sacks) with new
    handling units in the copalletization mailings along with a new
    copalletization original and Linked indicator;

4.  Allows the ability to identify move update method at a higher level
    for faster and convenient postage processing;

5.  Allows identification of specific postage statements for spoilage
    related adjustments.

6.  Creates the rate cells necessary to identify and distinguish between
    basic and full-service pieces. Mail.dat 09-1 also improves
    identification of spoilage at a rate level.

7.  Supports all methods of identifying the Mail Owner and Mail Preparer
    for the By/For relationship.

> The change requests for 09-1 can be accessed at the IDEAlliance change
> management Web site found at
> <http://pmstage.freecom.at/pmstage/index.php>.

### Piece Electronic Documentation for Non-Sequential Intelligent Mail Barcodes

As part of the full-service option, mailers are required to uniquely
number their mailpieces and provide information for every mailpiece in
their mailing except for mailings that do not require documentation to
support presort (mailings of fewer than 10,000 pieces with postage
affixed to each piece at the correct rate or if all pieces are of
identical weight, the pieces are separated by rate). When the
Intelligent Mail barcodes used on the mailpieces are not sequentially
numbered, mailpiece information will be given as an individual record
for each piece in the mailing. Individual piece records must also be
provided when multiple Mailer IDs are mixed in a bundle/handling unit
(e.g. trays, tubs, sacks).

Individual Piece Records are identified in Mail.dat in the Piece Detail
Record (.PDR) file. The Intelligent Mail barcode must be provided in the
Piece IM Barcode field of the .PDR file.

If the mailpiece has a POSTNET instead of an Intelligent Mail barcode,
complete the Piece Barcode field of the .PDR instead of the Piece IM
Barcode field.

The mechanism for compliance with move update requirements should be
provided in the Move Update Method field in the .PDR or .SEG for
Mail.dat and in the MailPieceCreate or MailPieceUpdate message for
Mail.XML. The Full-Service Level Indicator field in the Container
Quantity Record (.CQT) file should be populated to indicate
full-service, basic, or non-automation rate at which the mailpieces
associated to that .CQT record are being mailed

The Mail Owner must be identified in the electronic documentation
through one of the mechanisms outlined in the Mail Owner and Mail
Preparer Identification in Electronic Documentation section of this
document. The three means of identifying the Mail Owner include:

1\) Providing the Mailer ID of the Mail Owner,

2\) The Customer Registration ID (CRID) of the Mail Owner,

3\) The Permit Number/Permit ZIP+4/Permit Type of the Mail Owner.

For detailed specifications on how to populate the PDR or
MailPieceCreate and MailPieceUpdate messages , refer to the Mail.dat
Specification or Mail.XML Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

### Piece Electronic Documentation for Sequential Intelligent Mail Barcodes

Mailers who use sequential serial numbers in the Intelligent Mail
barcodes they apply to mailpieces can use this option to identify
mailpiece data in their electronic documentation. This option cannot be
used when the serial numbers in the Intelligent Mail barcode are
non-sequential for mailpieces in a bundle/handling unit.

The Intelligent Mail barcode sequences are included in the IM Barcode
Upper and Lower Serialization fields of the Intelligent Mail Range
Record (.IMR) file. These fields are populated with 15 digits (6/9 digit
Mailer ID, 9/6 digit Serial Number). This new file will allow the
association of multiple ranges to a single .CSM record. When handling
units are used, the IMR record must associate to the handling unit and
not the mother pallet. Sequences must be contiguous and may not overlap
among containers in a mailing or between mailings during the 45-day
period for barcode uniqueness.

Sequential Intelligent Mail barcode mailpieces that are not included in
a mailing should be indicated as described in the Spoilage and Shortage
section of this document.

The mechanism for compliance with move update requirements should be
provided in the Move Update Method field in the Segment Record (.SEG)
file in 09-1 and at the piece level in Piece Detail Record (PDR) in 08-2
and in 09-1. The ServiceLevelIndicator field in the .CQT file should be
populated to indicate full-service, basic, POSTNET, or Other (for
non-automation mailpieces) which provides the level at which the
mailpieces associated to that .CQT record are being mailed.

The Mail Owner must be identified in the electronic documentation
through one of the mechanisms outlined in the Mail Owner and Mail
Preparer Identification in Electronic Documentation section of this
document.

In Mail.XML 6.0, the piece range information can be provided by
utilizing the MailPieceCreate or MailPieceUpdate Request/Response
messages that support both piece detail and piece ranging information.

For detailed specifications on how to populate Mail.dat files, refer to
the Mail.dat Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

### Handling Unit Information

Handling Unit is the term used to describe the equipment (tray, tub,
sack, and bundle) used to carry an aggregate of mailpieces sorted to a
specific rate level for a ZIP Code destination. For full-service
mailings, the Intelligent Mail tray barcode label will be required on
trays, tubs, and sacks. (Note: for bundles, the Intelligent Mail barcode
of the top mailpiece of the bundle is used to identify the handling unit
but mailers are not required to identify which mailpiece is the top
mailpiece in their electronic documentation.) Mailers will populate the
serial number field of the Intelligent Mail tray barcode with a unique
number for each handling unit (e.g. trays, tubs, sacks) in the mailing.
These Intelligent Mail tray barcodes must remain unique for 45 calendar
days from the date the mail in those handling units is inducted.

For full-service mailings there are two types of handling units that can
be identified in the electronic documentation: physical handling units
and logical handling units.

#### Physical Handling Units

Most mailers will identify the specific handling unit into which a
mailpiece is sorted, typical of a list mailing environment, as the
physical handling unit used in electronic documentation. A physical
handling unit is created in Mail.dat in the Container Summary Record
(.CSM) file. Mailers will create a .CSM record for each handling unit
they produce and will place the Intelligent Mail tray barcode for that
handling unit in the Label: IM Container or IM Tray Barcode field of the
.CSM record for the handling unit.

For detailed specifications on how to populate the .CSM file, refer to
the Mail.dat Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

#### Logical Handling Units (Trays only)

For MLOCR origin mailings, the situation often arises where multiple
handling units are created with the same presort level and ZIP Code
destination but the mailer cannot identify to which specific handling
unit an individual mailpiece was sorted. In these instances, the mailer
will treat this group of handling units (with the same presort level and
ZIP Code destination) as a single, logical unit called a logical
handling unit. A mailpiece is then associated to the logical handling
unit, without identifying the specific physical handling unit into which
it was sorted.

![](media/image1.jpeg){width="4.427083333333333in"
height="1.3541666666666667in"}***Figure 14: Logical Handling Units***

Both physical and logical handling units are identified in Mail.dat in
the Container Summary Record (.CSM) file. Logical handling units are
created as records in the .CSM file and are identified as logical
handling units by including an "L" in the Container Type field. Logical
handling units will not have an Intelligent Mail tray barcode in the
[Label: IM Container or IM Tray
Barcode](#Label24CharacterContainerBarcode6) field.

Physical handling units are also created as records in the .CSM file and
are identified as physical handling units by including the Intelligent
Mail Tray barcode from the physical handling unit in the Label: IM
Container or IM Tray Barcode field and populating the Sibling Container
Indicator field with "Y".

Physical handling units are then associated to logical handling units by
placing the Container ID of the logical handling unit (from the
Container ID field of the .CSM record) in the Sibling Container
Reference ID field of the physical handling unit .CSM record.

![](media/image2.wmf)***Figure 15: Association of Logical Handling Units
to Physical Handling Units***

For detailed specifications on how to populate the .CSM file, refer to
the Mail.dat Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

### Container Information (Pallets or APC)

Container is the term used to describe the mail containers (pallet,
gaylord, all-purpose container (APC), etc.) used to carry an aggregate
of handling units. Full-service mailings require container labels that
include a unique Intelligent Mail container barcode (when
containerization is required). Mailers will populate the serial number
field of the Intelligent Mail container barcode with a unique number for
each physical container. These Intelligent Mail container barcodes must
remain unique for 45 calendar days from the date the mail in those
containers is inducted.

For full-service mailings there are two types of containers that can be
identified in the electronic documentation: physical containers and
logical containers.

#### Physical Containers

Most mailers will identify the specific physical container in which a
physical or logical handling unit was placed. A physical container is
created in Mail.dat in the Container Summary Record (.CSM) file. Mailers
will create a .CSM record for each container they produce and will place
the Intelligent Mail Container barcode for that container in the Label:
IM Container or IM Tray Barcode field of the .CSM record for the
container.

For detailed specifications on how to populate the .CSM file, refer to
the Mail.dat Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

#### Logical Containers (Pallets or APCs)

For MLOCR origin mailings, the situation often arises where multiple
containers are created with the same presort level that will be inducted
at the same location but the mailer cannot identify to which specific
container an individual handling unit was sorted. In these instances,
the mailer will treat this group of containers (with the same presort
level to the same induction location) as a single, logical unit called a
logical container. A handling unit is then associated to the logical
container, without identifying the specific physical container into
which it was sorted.

![](media/image3.jpeg){width="4.458333333333333in" height="1.375in"}

> ***Figure 16: Logical Containers***

Typically, a single physical container is identified in the electronic
documentation with its associated Intelligent Mail Container barcode.
However, when MLOCR mailers create multiple containers to be inducted at
the same location at the same presort level, they can be identified as a
logical container. A logical container must be associated to at least
one physical container.

Both physical and logical containers are identified in Mail.dat in the
Container Summary Record (.CSM) file. Logical containers are created as
records in the .CSM file and are identified as logical containers with
an "M" in the Container Type field. Logical containers will not have an
Intelligent Mail Container barcode in the [Label: IM Container or IM
Tray Barcode](#Label24CharacterContainerBarcode6) field.

Physical containers are also created as records in the .CSM file and are
identified as physical containers by including the Intelligent Mail
Container barcode on the physical container in the [Label: IM Container
or IM Tray Barcode](#Label24CharacterContainerBarcode6) field and the
Sibling Container Indicator field in the .CSM is populated with "Y".

Physical containers are then associated to logical containers by placing
the Container ID of the logical container (from the Container ID field
of the .CSM record) in the Sibling Container Reference ID field of the
physical container .CSM record.

In the following example there would be four records in the .CSM file
corresponding to three "physical" containers.

![](media/image4.wmf)***Figure 17: Association of Physical Containers to
Logical Containers***

For detailed specifications on how to populate the .CSM file, refer to
the Mail.dat Specification which can be found at
<http://www.maildat.org/> or
[http://www.idealliance.org](http://www.idealliance.org/) and the
*PostalOne!* System Mail.dat Technical Guide for Full-Service which can
be found at http://ribbs.usps.gov/.

#### Associating Handling Units to Containers

Physical handling units are associated to the appropriate logical
containers. This association is made by including the Container ID of
the parent, logical container (from the Container ID field of the .CSM
record) in the Parent Container Reference ID field of the .CSM record of
the child, physical handling unit. Multiple physical handling units can
be associated with a single logical container.

### Postage Information

Physical bundles and handling units (trays or sacks) must be used for
Periodicals where postage is applicable for Outside County Containers
and bundles.

The Mail.dat file may be used to enter the electronic postage statements
for either full-service or basic mailing. The *PostalOne!* system uses
information in the following files to generate a postage statement: HDR,
SEG, CSM, CQT, PQT, MPU, CPT, MCR, and MPA. There is a billable postage
statement electronically entered for each Job ID, Permit Number, Post
Office of Mailing ZIP Code (Origin Post Office), Mailing Date (Container
Ship Date in the CSM), CAPS Reference Number, Processing Category, and
Mailing Class. For Periodicals, the Publication Number replaces the
permit number and there are additional Postage Statement generation
variables: Periodicals Issue Date, and Frequency. The users in Mail.dat
09-1 can now use a Postage statement Record file to manage and specify
the final postage statement(s) created per CSM. User Ready to Pay
Sequence Number container. The *PostalOne!* User Guide for Mail.dat
lists all the postage statement generation variables in table 3.1 Key
Postage Statement Generation Fields. The acceptance personnel finalize
each of these postage statements to debit the account for the amount of
each postage statement.

The Postal Service maintains a record of the Publication Number at the
Original Entry and the Additional Entry office indicating if a
publication has a Centralized Periodicals Payment (CPP) program
agreement. Publications that participate in the CPP program may elect to
be debited for each postage statement as it is finalized as described
above. In this case the Pricing and Classification Service Center (PCSC)
in New York (office that manages the CPP program) may remain the
Original Entry office but the publication will no longer be part of the
CPP program. Either a full-service mailing or a basic mailing may choose
this option.

Publications that participate in the CPP program may consolidate and
defer payment for a single publication issue and for the postage
statements at an acceptance office (generally a Detached Mail Unit DMU)
for a period not to exceed fourteen (14) days after the last day of
mailing of the main file of the issue. The CPP program agreement
requires funds approximately equal to the postage for the normal or
regular issue of the publication to be held in escrow. Either a
full-service or a basic mailing may use the consolidated and deferred
payment option. To use this option, the Mail.dat file MPA Postage
Payment Option for the USPS Publication Number must be set to C=CPP. The
USPS Publication Number must be on record with a current CPP program
agreement. The acceptance personnel will enter the USPS Verified copy
weights and accept the postage statement rather than finalize it. The
publisher signed on as Owner or the acceptance personnel may change the
advertising percentage until the time of payment. Before the fourteen
(14) day period expires, the publisher will sign onto the Owner view to
make a Consolidated and Deferred Payment Request. All of the postage
statements for the issue at each acceptance office will appear for
selection into the Payment Request. The Owner will select the
appropriate postage statements for the payment and submit the payment to
debit the account a single payment for each acceptance office. If the
Consolidated and Deferred Payment Request is not entered before the 14
day period expires, the payment debit will automatically occur.

### Future Release: Mail.dat Owner/Mailing Agent Updates

The *PostalOne!* system will allow a preparer or owner to update a
Mail.dat job sent by either entity as long as Owner's Permit Number and
Permit ZIP + 4 Code information are provided in the MPA record. Mail
Preparer functionality will remain the same for Mail.dat submission,
authentication, and authorization. Mail Owner functionality is being
modified to allow a Mail Owner to update a Mail.dat job filed by a Mail
Preparer, as long as the Mail Owner's identification was provided by the
Mail Preparer in the Mail.dat job. This functionality will be supported
in the full-service release of *PostalOne!.*

##  Mail.XML

Mail.XML version 6.0 will enable the secure electronic submission of
mailing information to the USPS. Mail.XML will also allow mailers to
submit and retrieve data electronically. This specification serves four
distinct functions;

1\) FAST Appointment Scheduling: these messages are used to create and
manage appointments in FAST and are part of the specification formerly
known as the IDEAlliance Transaction Messaging (TM) specification.

2\) Data Distribution and Feedback: these messages allow mailers to
receive information about their mailings (i.e. Start-the-Clock,
Container Scans, ACS, and Nixie data data).

3\) Customer Identification: these messages are used to obtain a
customer identifiers and define relationships between customer
identifiers.

4\) Electronic Documentation (future release): these messages are used
to communicate final postage statements and qualification reports and
meet the electronic documentation requirements for full-service.

## Future Release: Electronic Documentation Using Mail.XML (formerly Wizard Web Services)

Wizard Web Services currently accommodates all domestic postage
statements and includes the other postal documents, including
Qualification Reports, involved in the mailing process. These will all
be supported in the new Mail.XML services. In addition, Mail.XML will
provide the ability to electronically access USPS data and perform
business functions related to full-service.

For more information about using Mail.XML to communicate with the
*PostalOne!* system*,* refer to the *PostalOne!* system product guides
and tools and the *PostalOne!* System Mail.XML Technical Guide for
Full-Service on http://ribbs.usps.gov/.

### Mail.XML™ Version 6.0 Changes - *PostalOne!* System Implementation 

Mail.XML's next version will create one industry Web services
specification combining the existing Web services defined by the USPS
(i.e. WWS) and the Web Services defined under the current Mail.XML
umbrella. Mail.XML 6.0 also allows create, update, and cancel
transactions for the Cast of Characters (brokering of information)
messages. Mail.XML will also allow the support of electronic
documentation and end-to-end mailing supply chain business process
management for a multitude of business processes. Mail.XML will include
Qualification reports, container and bundle reports, spoilage,
eDropShip, containerization nesting, postage statements, piece detail
and piece ranging and many other business process related communication.
The Mail.XML's version 6.0 supports copalletization, mixed mailing,
manifest mailing, and business processes specific to MLOCR and
continuous mailing environments.

### Piece Electronic Documentation for Non-Sequential Intelligent Mail Barcodes

As a part of full-service, mailers must provide information for every
mailpiece in their mailing except for mailings that do not require
documentation to support presort (mailings of fewer than 10,000 pieces
with postage affixed to each piece at the correct price or if all pieces
are of identical weight, the pieces are separated by price). When the
Intelligent Mail barcodes used on the mailpieces are not sequentially
numbered, mailpiece information will be given as an individual record
for each piece in the mailing. Individual piece records must also be
provided when multiple Mailer IDs are mixed in a non sequential piece
range within a bundle/handling unit (e.g. trays, tubs, sacks).

Individual Piece Records are identified in Mail.XML MailPieceCreate and
MailPieceUpdate Request/Response messages in the individual
PDRMailPieceBlk XML block. The Intelligent Mail Barcode must be provided
in the IMB type data type. The mechanism for compliance with move update
requirements should be provided in the MoveComplianceUpdateMethod field.
The ServiceLevelIndicator field in the XML block of PDRMailPieceBlk XML
block or PieceRangeBlk should be populated with "F" for full-service
mailpieces, "B" for basic mailpieces, "P" for POSTNET mailpieces, and
"O" for other mailpieces such as non-automation (available in version
6.0).

The Mail Owner must be identified in the electronic documentation
through one of the mechanisms outlined in the Mail Owner and Mail
Preparer Identification in Electronic Documentation section of this
document. The three means of identifying the Mail Owner include:

1.  Providing the Mailer ID of the Mail Owner,

2.  Providing the Customer Registration ID (CRID) of the Mail Owner, or

3.  Providing the Permit Number/Permit ZIP+4/Permit Type of the Mail
    Owner.

For detailed specification on how to populate the individual data type
or the Mail Piece Data message, refer to the Mail.XML Software
Development Guide for Full-Service which can be found at
http://ribbs.usps.gov/.

### Piece Electronic Documentation for Sequential Intelligent Mail Barcodes

Mailers who use sequential serial numbers in the Intelligent Mail
barcodes they apply to mailpieces should use this option to identify
mailpiece data in their electronic documentation. This option may not be
provided for any full-service mailing when either of the following
conditions exists:

-   Multiple Mailer IDs in the Intelligent Mail barcode are mixed in a
    bundle/handling unit

-   Serial numbers in the Intelligent Mail barcode are non-sequential
    for mailpieces in a bundle/handling unit.

The Intelligent Mail barcode sequences must be provided in the
IMBUpperSerialization and IMBLowerSerialization fields in the XML block
of PieceRangeBlk. These fields are to be populated with 15 digits (6/9
digit Mailer ID, 9/6 digit Serial Number) of the Intelligent Mail
barcode. Sequences may not overlap among containers in a mailing or
between mailings during the 45-day period for barcode uniqueness. The
ServiceLevelIndicator field in the XML block of PDRMailPieceBlk XMl
block or PieceRangeBlk should be populated with "F" for full-service
mailpieces, "B" for basic mailpieces, "P" for POSTNET mailpieces, and
"O" for Other such as non-automation mailpieces (available in version
6.0).

Sequential Intelligent Mail barcode mailpieces that are not included in
a mailing should be indicated as described in the Spoilage and Shortage
section of this document.

Compliance with move update requirements should be provided in the
MoveUpdateComplianceMethod field.

The Mail Owner must be identified in the electronic documentation
through one of the mechanisms outlined in the Mail Owner and Mail
Preparer Identification in Electronic Documentation section of this
document. In the MailPieceCreate and MailPieceUpdate messages, three
means of identifying the Mail Owner include providing the Mailer ID of
the Mail Owner, the CRID of the Mail Owner, or the Permit Number/Permit
ZIP+4/Permit Type of the Mail Owner. For Periodicals mailings, the Mail
Owner must be identified through a USPS Publication Number/Permit
ZIP+4/Permit Type. If the Piece messages are not used, then the By/For
relationships must be expressed in the publisherData or permitHolderData
data type.

For detailed specification on how to populate the batch data type or the
Mail Piece Data message, refer to the Mail.XML Software Development
Guide for Full-Service which can be found at http://ribbs.usps.gov/.

#### Handling Unit Information

Handling Unit is the term used to describe the mail containers (tray,
tub, sack, and bundle) used to carry an aggregate of mailpieces sorted
to a specific rate level for a ZIP Code destination. For full-service
mailings, the Intelligent Mail tray barcode label will be required on
trays, tubs, and sacks

**Note: for bundles, the Intelligent Mail barcode of the top mailpiece
of the bundle is used to identify the handling unit but mailers are not
required to identify which mailpiece is the top mailpiece in their
electronic documentation.**

Mailers will populate the serial number field of the Intelligent Mail
tray barcode with a unique number for each handling unit (e.g. trays,
tubs, sacks) in the mailing. These Intelligent Mail tray barcodes must
remain unique for 45 calendar days from the date the mail in those
handling units is inducted.

For full-service mailings there are two types of handling units that can
be identified in the electronic documentation: physical handling units
and logical handling units.

#### Physical Handling Units

Most mailers will identify the specific handling unit into which a
mailpiece was sorted, typical of a list mailing environment, as a
physical handling unit used in electronic documentation. A physical
handling unit is created in Mail.XML in the ContainerInfoData data type
of the Qualification Report message. Mailers will create a
ContainerInfoData record for each handling unit they produce and will
place the Intelligent Mail tray barcode for that handling unit in the
ContainerBarcode field of the ContainerinfoData record for the handling
unit.

For detailed specification on how to populate the ContainerInfoData data
type or the Qualification Report message, refer to the Mail.XML Software
Development Guide for Full-Service which can be found at
http://ribbs.usps.gov/.

#### Logical Handling Units (Trays)

In MLOCR origin mailings, the situation often arises where multiple
handling units are created with the same presort level and ZIP Code
destination but the mailer cannot identify to which specific handling
unit an individual mailpiece was sorted. In these instances, the mailer
will treat this group of handling units (with the same presort level and
ZIP Code destination) as a single, logical unit called a logical
handling unit. A mailpiece is then associated to the logical handling
unit, without identifying the specific physical handling unit into which
it was sorted.

![](media/image1.jpeg){width="4.427083333333333in"
height="1.3541666666666667in"}***Figure 18: Logical Handling Units***

Both physical and logical handling units are identified in Mail.XML in
the ContainerInfoData data type of the Qualification Report message.
Logical handling units are created as records in the ContainerInfoData
message. Logical handling units will not have an Intelligent Mail Tray
barcode in the ContainerBarcode field.

Physical handling units are also created as records in the
ContainerInfoData message and are identified as physical handling units
by including the Intelligent Mail Tray barcode from the physical
handling unit in the ContainerBarcode field

Physical handling units are then associated with logical handling units
by placing the CustomerContainerID of the logical handling unit in the
ParentContainerID field of the physical handling unit.

![](media/image5.wmf)***Figure 19: Association of Physical Handling
Units to Logical Handling Units***

For detailed specification on how to populate the ContainerInfoData data
type or the Qualification Report message, refer to the PostalOne!
Technical Guide for Mail.XML 6.0 which can be found at
http://ribbs.usps.gov/.

### Container Information (Pallets or APCs)

Container is the term used to describe the mail containers (pallet,
gaylord, all-purpose container (APC), etc.) used to carry an aggregate
of handling units. Full-service mailings must apply container labels
that include a unique Intelligent Mail container barcode when the mail
is containerized. Mailers will populate the serial number field of the
Intelligent Mail container Barcode with a unique number for each
container. These Intelligent Mail container barcodes must remain unique
for 45 calendar days from the date the mail in those containers is
inducted.

For full-service mailings there are two types of containers that can be
identified in the electronic documentation: physical containers and
logical containers.

#### Physical Containers

Most mailers will identify the specific container in which a physical or
logical handling unit was placed. A physical container is created in
Mail.XML in the ContainerInfoData data type of the Qualification Report
message. Mailers will create a ContainerInfoData record for each
container they produce and will place the Intelligent Mail Container
barcode for that container in the ContainerBarcode field.

For detailed specification on how to populate the ContainerInfoData data
type or the Qualification Report message, refer to the Mail.XML Software
Development Guide for Full-Service which can be found at
http://ribbs.usps.gov/.

#### Logical Containers (Pallets or APCs)

In MLOCR origin mailings, the situation often arises where multiple
containers are created with the same presort level that will be inducted
at the same location but the mailer cannot identify to which specific
container an individual handling unit was sorted. In these instances,
the mailer will treat this group of containers (with the same presort
level to the same induction location) as a single, logical unit called a
logical container. A handling unit is then associated to the logical
container, without identifying the specific physical container into
which it was sorted.

> ![](media/image3.jpeg){width="4.458333333333333in"
> height="1.375in"}***Figure 20: Logical Containers***

Typically, a single physical container is identified in the electronic
documentation with its associated Intelligent Mail container barcode;
however, when mailers create multiple containers to be inducted at the
same location at the same presort level; they can be identified as a
logical container. A logical container must be associated to at least
one physical container.

Both physical and logical containers are identified in Mail.XML in the
ContainerInfoData data type of the Qualification Report message. Logical
containers are created as records in ContainerInfoData but have no
Intelligent Mail container barcode in the ContainerBarcode field.

Physical containers are also created as records in ContainerInfoData and
are identified as physical containers by including the Intelligent Mail
container barcode on the physical container in the
[ContainerBarcode](#Label24CharacterContainerBarcode6) field.

Physical containers are associated to logical containers by placing the
customerContainerID of the logical container in the parentContainerID
field of the physical container.

For detailed Mail.XML Software Development Guide for Full-Service which
can be found at http://ribbs.usps.gov/.

In the following example there would be four records in
ContainerInfoData corresponding to three "physical" containers.

![](media/image6.wmf)***Figure 21: Association of Physical Containers to
Logical Containers***

#### Associating Handling Units to Containers

Handling units are associated to containers by associating the physical
handling units to the appropriate logical container. This association is
made by including the CustomerContainerID (from the CustomerContainerID
field of the ContainerInfoData data type) of the logical container
record in the ParentContainerID field of the ContainerInfoData record of
the physical handling unit. Multiple physical handling units can be
associated to a single logical container.

### Appointment Information

Please refer to the sub-section on appointments under the Mail.dat
section for more details.

### Postage Information

The Mail.XML messages may be used to enter the electronic postage
statements for either full-service or basic mailing. The acceptance
personnel finalize each of these postage statements to debit the account
for the amount of each postage statement.

## Postal Wizard (PW)

The *PostalOne!* system offers the Postal Wizard as a tool that provides
a secure way to submit postage statements online. This tool may be used
when no electronic documentation is necessary for compliance with
full-service requirements.  (Qualification reports for mailings of less
than 10,000 pieces are not required when postage is affixed to each
piece at the correct price, or when each piece is of identical weight
and the mailpieces are separated by price). 

The PW Submit-a-Form tool automatically populates the permit holder
section of the postage statement based on the account number provided,
and it guides the user through the completion of the rest of the form
based on the type of mailing. The tool automatically validates the
information entered and calculates the postage. The user submits the
form directly to a Postal acceptance unit once the form is completed.
For more information on how to use the PW refer to the Getting Started
Guide found at <http://www.usps.com/postalone/guides.htm>*.*

### Piece Electronic Documentation for Sequential Intelligent Mail Barcodes

When unique sequential sequence numbers are used on mailpieces
documented in PW, mailers may provide the range of sequence numbers used
by entering the Lowest Sequence Number and Highest Sequence Number in
the PW. Unique sequential sequence numbers cannot be reused within 45
calendar days from the date of mailing.

###  Piece Electronic Documentation Using Mailing ID

When a customer is not required to submit a qualification report, the
serial number field of each Intelligent Mail barcode can be populated
with a mailing serial number that is unique to the mailing but common to
all pieces in the mailing. This unique mailing serial number must not be
reused for a period of 45 calendar days from the date of mailing. Unique
mailing serial numbers must be populated in the PW entry screen field.

### Postage Information

The PW submissions may be used to enter the electronic postage
statements for either full-service or basic mailing. The acceptance
personnel finalize each of these postage statements to debit the account
for the amount of each postage statement.

##  Mail Owner and Mail Preparer Identification in Electronic Documentation

Often, Mail Owners will use the services of a mail service provider to
prepare and pay for their mailings. When this situation occurs, the mail
service provider is acting on behalf of the Mail Owner, creating a
By/For relationship with the USPS (the mail is prepared By the mail
service provider, For the Mail Owner). For Mail.dat (and Mail.XML in a
future release), there are a number of options that exist to reflect
this relationship in electronic documentation. For the Mail Owner or
Mail Preparer to participate in full-service data provisioning which
requires a profile, they must be identified by their Mailer ID in the
By/For of the electronic documentation.

### Non-Sequential Piece Identifiers

When the serial numbers applied in the Intelligent Mail barcodes of a
mailing are not sequential, the creator of the electronic documentation
may use one of the single piece options in the .PDR or, in a future
release, Mail.XML MailPieceCreate and MailPieceUpdate messages identify
the Mail Owner of the mailing.

#### Option 1: Mailer Owner MID 

> Mail service providers can include the Mail Owner MID in the
> electronic documentation, identifying the Mail Owner for whom they
> have prepared the mailpiece.
>
> **Mail.dat**

-   Mailer ID of Mail Owner in MPA: Mailer ID of the company which owns
    the mailpieces indicated in the MPA record.

-   Mailer ID of Mail Owner in CPT AND Host Statement Component ID in
    MCR (to identify appropriate component to use from CPT): Mailer ID
    of the company which owns the mailpieces indicated in the PDR
    records (all of which associate to a single CQT record).

> **Future Release: Mail.XML**

-   Mail Owner in the Piece messages**:** Mailer ID of the company which
    owns the mailpiece indicated in the Mail.XML MailPieceCreate and
    MailPieceUpdate messages .

#### Option 2: Mail Owner Permit Number

> Mail service providers can include the Permit Number of the Mail Owner
> in the electronic documentation.
>
> **Mail.dat**

-   Mail Owner's Lcl Permit Ref Num and Mail Owner's Lcl Permit Ref
    Num-Type in MPA with Mailer Facility ID in SEG: Permit Number/Permit
    ZIP+4/Permit Type of the company which owns the mailpieces indicated
    in the CSM record.

> **Future Release: Mail.XML**

-   Permit Number and Permit Type in MailerData: the Permit Number of
    the company which owns the mailpiece indicated in the Mail.XML
    message (available in version 6.0).

#### Option 3: Mail Owner Customer Registration Identifier (CRID)

> Mail service providers can include the CRID in the electronic
> documentation, identifying the Mail Owner for whom they have prepared
> the mailing or portion thereof.
>
> **Mail.dat**

-   Mail Owner Identifier in CPT AND Host Statement Component ID in MCR
    (to identify appropriate component to use from CPT): CRID of the
    company which owns the mailpieces indicated in the PDR records (all
    of which associate to a single CQT record).

-   Mail Owner Identifier in MPA: CRID of the company which owns the
    mailpieces indicated in the PDR records (all of which associate to a
    single MPA record).

> **Future Release: Mail.XML**

-   Mail Owner in the piece messages: CRID of the company which owns the
    mailpieces indicated in the Mail.XML message.

-   Customer Registration ID in MailerData: CRID of the company which
    owns the mailpieces indicated in the Mail.XML message.

### Sequential Piece Identifiers

When the serial numbers applied in the Intelligent Mail barcodes of a
mailing are sequential, the creator of the electronic documentation may
use the ranging options to identify the Mail Owner of the mailing.
However, when there are multiple Mail Owner MID's in the same container,
the ranging option cannot be used.

#### Option 1: Mailer Owner MID 

> Mail service providers can include the Mail Owner MID in the
> electronic documentation, identifying the Mail Owner for whom they
> have prepared the mailpiece.
>
> **Mail.dat**

-   Mail Owner MID in Intelligent Mail Range (IMR): Mailer ID of the
    company which owns the mailpieces indicated in the IMR record.

> **Future Release: Mail.XML**

-   Mail Owner MID in the piece messages IntelligentMailRange block**:**
    Mailer ID of the company which owns the mailpiece indicated in the
    Mail.XML message.

#### Option 2: Mail Owner Permit Number

> Mail service providers can include the Permit Number of the Mail Owner
> in the electronic documentation.
>
> **Mail.dat**

-   Not Available: The IMR associates to a CSM record which does not tie
    to a specific MPA record (which is where the Permit Number currently
    is provided) and the Permit Number field was not added to the IMR
    record..

> **Future Release: Mail.XML**

-   Permit Number and Permit Type in MailerData: the Permit Number of
    the company which owns the mailpiece indicated in the Mail.XML
    message (available in version 6.0)

> **PW**

-   Permit Number, Permit Type, and Zip Code of the Post Office of
    mailing

#### Option 3: Mail Owner Customer Registration Identifier (CRID)

> Mail service providers can include the CRID in the electronic
> documentation, identifying the Mail Owner for whom they have prepared
> the mailing or portion thereof.
>
> **Mail.dat**

-   Mail Owner CRID in Intelligent Mail Range (IMR): CRID of the company
    which owns the mailpieces indicated in the IMR record.

> **Future Release: Mail.XML**

-   Mail Owner CRID in piece message's IntelligentMailRange block: the
    CRID of the Mail Owner of the mailpieces associated to the Mail.XML
    message.

### Order of Preference

If two or more of the options above are populated, the following order
of preference will be used to determine which fields should be used. (In
a future release, a submission of the Mail.XML MailPieceCreate and
MailPieceUpdate messages will always overwrite a submission of the PDR
when both are submitted for the same Mail.dat job.) Logic will be added
in the *PostalOne!* system to notify the submitter of the file when a
submission will not be applied because a file of higher preference in
the list below has been previously submitted. Regardless of method used,
the files must be submitted at or before the time the pieces referenced
in the file become mail.

**For Piece Range Records:**

**Mail Owner -**

1.  Mailer ID of Mail Owner from the IMR

```{=html}
<!-- -->
```
1.  CRID of Mail Owner from the IMR

**Mail Preparer --**

1.  Mailer ID of Mail Preparer from the IMR

```{=html}
<!-- -->
```
1.  CRID of Mail Preparer from the IMR

**For Physical Piece Records:**

**Mail Owner --**

1.  Mailer ID of Mail Owner from the CPT

```{=html}
<!-- -->
```
1.  Mailer ID of Mail Owner from the MPA

2.  CRID of Mail Owner from the CPT

3.  CRID of Mail Owner from the MPA

4.  Mail Owner's Lcl Permit Ref Num/Int'l Bill Num from the MPA

**Mail Preparer --**

1.  Mailer ID of Mail Preparer from the MPA

```{=html}
<!-- -->
```
1.  CRID of Mail Preparer from the MPA

### Obtaining a Mail Owner CRID

The Customer Registration ID is a 10-digit identifier created by the
Customer Registration system to uniquely identify the USPS Customers at
a physical address. For each unique combination of Company Name and
physical address, the USPS will create a new CRID. The CRID is made
available to all USPS systems and applications to identify customers and
associate customer data across those systems. The CRID is the single
unique ID that connects a company's information at a specific geographic
location (physical street address) across all USPS applications and a
CRID will be associated to every Permit Number and Mailer ID that is
issued (there may be multiple Permit Numbers or MIDs associated to a
single CRID). Any USPS Customer who wants to do business electronically
with the USPS can obtain a CRID. The CRID should be treated as an
account number and treated with the appropriate confidentiality. Two
options will exist to obtain a CRID. In the first release of the
Intelligent Mail Program, companies will only be allowed to obtain a
CRID for their company (not for other companies). In a future release,
companies will be able to obtain a CRID for any company. Option 1 will
be implemented first and will be the primary mechanism for distributing
CRIDs in the initial full-service deployment.

Option 1: A company shall be able to request Customer Registration IDs
(CRID) by uploading a pipe delimited file to *PostalOne!* with the
following message format:

  -----------------------------------------------------------------------
  CRID Request File

  Company Name

  Company Address Line 1

  Company Address Line 2

  City

  State

  ZIP Code (5 or 9 digit)
  -----------------------------------------------------------------------

***Figure 22: CRID Request File Layout (Pipe Delimited)***

After receiving the file, the PostalOne! system shall respond with the
CRID of the company (or companies) identified in the file. If a CRID did
not previously exist, the Customer Registration ID system will create a
new CRID to provide in the response file.

When automated, the PostalOne! system shall generate an automatic letter
which will be printed and mailed via USPS mail to the company name and
address for which the CRID was requested. The contents of the letter
shall read:

USPS has created a CRID (Customer Registration ID) for you for the
following company name at the following address with the following CRID:

-   Mail Owner's company name

-   Mail Owner's company address line 1

-   Mail Owner's company address line 2

-   Mail Owner's city

-   Mail Owner's state

-   Mail Owner's ZIP Code (5 or 9 digit )

-   Mail Owner's CRID

The CRID was created on your behalf on the request of the following
Mailing agent:

-   Mailing agent's company name

-   Mailing agent's company address line 1

-   Mailing agent's company address line 2

-   Mailing agent's city

-   Mailing agent's state

-   Mailing agent's ZIP Code (5 or 9 digit )

-   Mailing agent's CRID

-   Mailing agent's email address

-   Mailing agent's phone number

Please make a note of your CRID and understand that the above mentioned
mailing agent will be using your ID to identify your mailings for the
USPS.

Option 2: A company shall be able to request Customer Registration IDs
(CRID) by sending a Mail.XML request with the message format below. The
USPSCRIDCreateRequest and Response messages in the Mail.XML
specification support this data exchange.

  ----------------------------------- -----------------------------------
  Mail Preparer Mail.XML Request      *PostalOne!* Response

  Transaction ID                      Transaction ID

  Tracking ID                         Tracking ID

  Mail Owner's Company Name           Mail Owner's Company Name

  Mail Owner's Company Address Line 1 Mail Owner's Company Address Line 1

  Mail Owner's Company Address Line 2 Mail Owner's Company Address Line 2

  Mail Owner's City                   Mail Owner's City

  Mail Owner's State                  Mail Owner's State

  Mail Owner's ZIP Code (5 or 9       Mail Owner's ZIP Code (5 or 9
  digit)                              digit)

  Mail Owner's CRID                   Mail Owner's CRID

  Mail Owner's Email Address          Mail Owner's Email Address

  Mail Owner's Phone Number           Mail Owner's Phone Number
  ----------------------------------- -----------------------------------

***Figure 23: CRID Request Message***

After receiving the request from the customer through web services, the
PostalOne! system shall respond with the CRID of the company identified
in the message. If the CRID did not previously exist, the Customer
Registration ID system will create a new CRID to provide in the message
response.

When a CRID is requested using this option, the PostalOne! system shall
generate an automatic email if an email address is available and the
contents of the email shall also be printed and mailed via USPS mail to
the company name and address provided in the message. The contents of
the email/printed letter shall be:

USPS has created a CRID (Customer Registration ID) for you for the
following company name at the following address with the following CRID:

-   Mail Owner's company name

-   Mail Owner's company address line 1

-   Mail Owner's company address line 2

-   Mail Owner's city

-   Mail Owner's state

-   Mail Owner's ZIP Code (5 or 9 digit )

-   Mail Owner's CRID

The CRID was created on your behalf on the request of the following
Mailing agent:

-   Mailing agent's company name

-   Mailing agent's company address line 1

-   Mailing agent's company address line 2

-   Mailing agent's city

-   Mailing agent's state

-   Mailing agent's ZIP Code (5 or 9 digit )

-   Mailing agent's CRID

-   Mailing agent's email address

-   Mailing agent's phone number

Please make a note of your CRID and understand that the above mentioned
mailing agent will be using your ID to identify your mailings for the
USPS.

# Mailer Feedback

## Overview

Mailings that comply with full-service requirements will be provided
start-the-clock and address correction information through online
reports and an automated data exchange for mailings/mailpieces that
comply with full-service requirements. When container scans related to
those mailings are available, (USPS will not scan all containers) those
will also be available in online reports and through an automated data
exchange.

## Available Feedback

Online reports and automated data exchange of report data will be
available for mailings that comply with full-service requirements. This
data will be available using the following methods:

**Browser based HTTPS (Hyper Text Transport Protocol - Secure) Download
(Compressed Files)** -- Online web page allowing customers to download
'compressed data' over HTTPS protocol.

**Browser based HTTPS Reports** -- Online web page allowing customers to
view 'reports' over HTTPS.

**Mail.XML Pull (Customer Invokes USPS Web Service)** -- Web Services
Pull model where a customer sends a Web Services based Mail.XML Request
message invoking USPS Web Services to pull data in XML format through a
Mail.XML Web Service method.

**Mail.XML Push (USPS Invokes Customer Web Service)** - Web Services
Mail.XML Push model where the USPS invokes a customer's Web Service
method/URL and pushes XML data to the customer Web Service when the data
is available or a notification is sent to the customer by the USPS that
customer's data is available for download.

+---+------------------+----------+---------+-----------+------------+
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
| O |                  |          |         |           |            |
| p |                  |          |         |           |            |
| t |                  |          |         |           |            |
| i |                  |          |         |           |            |
| o |                  |          |         |           |            |
| n |                  |          |         |           |            |
| s |                  |          |         |           |            |
| f |                  |          |         |           |            |
| o |                  |          |         |           |            |
| r |                  |          |         |           |            |
| D |                  |          |         |           |            |
| a |                  |          |         |           |            |
| t |                  |          |         |           |            |
| a |                  |          |         |           |            |
| E |                  |          |         |           |            |
| x |                  |          |         |           |            |
| c |                  |          |         |           |            |
| h |                  |          |         |           |            |
| a |                  |          |         |           |            |
| n |                  |          |         |           |            |
| g |                  |          |         |           |            |
| e |                  |          |         |           |            |
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
+===+==================+==========+=========+===========+============+
| * | **Data/**        | *        | **      | *         | **Mail.XML |
| * |                  | *Browser | Browser | *Mail.XML | Push (USPS |
| N | **Service**      | based    | based   | Pull      | Invokes    |
| o |                  | HTTPS    | Report  | (Customer | Customer   |
| * |                  | Download | (over   | Invokes   | Web        |
| * |                  | (Co      | H       | USPS Web  | Service)** |
|   |                  | mpressed | TTPS)** | S         |            |
|   |                  | Files)** |         | ervice)** |            |
+---+------------------+----------+---------+-----------+------------+
| * | **S              | No       | Yes     | Yes       | Yes        |
| * | tart-the-Clock** |          |         |           |            |
| 1 |                  |          |         |           |            |
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
+---+------------------+----------+---------+-----------+------------+
| * | **Container      | No       | Yes     | Yes       | Yes        |
| * | V                |          |         |           |            |
| 2 | isibility/Scan** |          |         |           |            |
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
+---+------------------+----------+---------+-----------+------------+
| * | **ACS**          | Yes      | No      | Yes       | Yes        |
| * |                  |          |         |           |            |
| 3 |                  |          |         |           |            |
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
+---+------------------+----------+---------+-----------+------------+
| * | **Nixie Detail** | Yes      | No      | Yes       | Yes        |
| * |                  |          |         |           |            |
| 4 |                  |          |         |           |            |
| * |                  |          |         |           |            |
| * |                  |          |         |           |            |
+---+------------------+----------+---------+-----------+------------+

***Figure 24: Data Exchange Methods***

### Start-the-Clock for BMEU Mail

Full-service mailings will be provided a start-the-clock summary online
report and automated data exchange for BMEU verified mail. The report
provides information on when the mail is inducted (received by the
Postal Service) for mail processing at a USPS mail processing facility.
BMEU Start-the-Clock is not available until the unit has completed any
verification activities and processed the postage statement for account
debiting. The StartTheClockBMEUBlock XML block in the StartTheClock
Delivery/Response messages in the Mail.XML specification supports this
data exchange.

  ------------------- -------------- ------------ ---------- ------------- -------------------
  **Start-the-Clock                                                        
  -- BMEU Mailings**                                                       

  **Job ID/           **Class of     **Origin     **Origin   **Arrival     **Start-the-Clock
  Transaction ID**    Mail**         Facility**   Facility   Date/Time**   Date (Day 0)**
                                                  Locale                   
                                                  Key**                    

  9878988880          Standard Mail  Baltimore    V22931     03/01/2008    03/01/2008
                                     P&DC                    15:25 EDT     

  6668765468          Standard Mail  Baltimore    V22931     03/02/2008    03/02/2008
                                     P&DC                    11:00 EDT     

  ACI88867            First-Class    Dulles P&DC  X29745     03/02/2008    03/03/2008
                      Mail                                   20:00 EDT     
  ------------------- -------------- ------------ ---------- ------------- -------------------

***Figure 25: Start-the-Clock for BMEU Entered Mail Report***

### Start-the-Clock for Drop Ship and Origin Entered Mail Transported by Mailer

Mailers presenting full-service mailings will be provided a
start-the-clock summary online report and automated data exchange for
drop ship mail and for mail that is transported by the mailer to the
USPS origin facility. The report will provide information on when
full-service mailings were inducted into the USPS system.
Start-the-clock information will not be made available to customers
until the unit has completed any verification activities and processed
the postage statement for account debiting. StartTheClockDropShipBlock
XML block in the StartTheClock Delivery/Response messages in the
Mail.XML specification supports this data exchange.

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="10"><strong>Start-the-Clock - Drop Ship
Mailings</strong></td>
</tr>
<tr class="even">
<td><strong>Appt Num</strong></td>
<td><strong>Class of Mail</strong></td>
<td><strong>USPS Induction Facility</strong></td>
<td><strong>USPS Induction Locale Key</strong></td>
<td><p><strong>Appt</strong></p>
<p><strong>Date and Time</strong></p></td>
<td><strong>Arrival</strong></td>
<td><p><strong>Unload</strong></p>
<p><strong>Start</strong></p></td>
<td><p><strong>Unload</strong></p>
<p><strong>End</strong></p></td>
<td><strong>Appt Status</strong></td>
<td><strong>Start-the-Clock Date (Day 0)</strong></td>
</tr>
<tr class="odd">
<td>623456789</td>
<td>Standard Mail</td>
<td>Atlanta SCF</td>
<td>X10054</td>
<td>02/18/2008 14:00 EDT</td>
<td>02/18/2008 14:25 EDT</td>
<td>02/18/2008 14:25 EDT</td>
<td>02/18/2008 14:55 EDT</td>
<td>CLOSED</td>
<td>02/18/2008</td>
</tr>
<tr class="even">
<td>723456789</td>
<td>Standard Mail</td>
<td>Dulles P&amp;DC</td>
<td>X29745</td>
<td> 02/15/2008 12:00 EDT</td>
<td>02/15/2008 12:00 EDT</td>
<td>02/15/2008 12:20 EDT</td>
<td>02/15/2008 12:50 EDT</td>
<td>CLOSED</td>
<td>02/15/2008</td>
</tr>
<tr class="odd">
<td>92345R0215</td>
<td>Periodicals</td>
<td><p>New York</p>
<p>SCF</p></td>
<td>V19160</td>
<td> 02/15/2008 09:00 EDT</td>
<td>02/02/2008 09:00 EDT</td>
<td>02/02/2008 09:00 EDT</td>
<td>02/02/2008 09:15 EDT</td>
<td>CLOSED</td>
<td>02/02/2008</td>
</tr>
</tbody>
</table>

***Figure 26: Start-the-Clock for Drop Ship Mailings Report***

### Start-the-Clock for Plant-Load Mail

Mailers presenting full-service mailings will be provided a
start-the-clock summary online report and automated data exchange for
USPS transported mail. The report will provide information on when
full-service USPS transported mailings were ready to be transported and
that information will be used to determine the start-the-clock date
(i.e. which day is Day 0). Mailers that can specify the dispatch to
which a container was assigned will include that information in their
electronic documentation and will receive a different Mail Release time
for each mail Group. If the electronic documentation does not nest
containers to specific trips, then the Mail Release time is when the
entire mailing is complete and the mailing will be treated as a single
group, regardless of the number of trips. Start-the-clock information
for both options will not be made available to customers until the unit
has completed any verification activities and processed the postage
statement for account debiting. StartTheClockPlantLoadBlock XML block in
the StartTheClock Delivery/Response messages in the Mail.XML
specification supports this data exchange.

The following table shows the start-the-clock report for an environment
where the entire mailing is associated to a single dispatch that is
released when the mailing is complete.

  ------------------- ------------- ------------- ------------ ---------- ------------- -------------------
  **Start-the-Clock                                                                     
  -- Single Group                                                                       
  Plant Load                                                                            
  Mailings**                                                                            

  **Job ID/           **Dispatch    **Class of    **Origin     **Origin   **Mail        **Start-the-Clock
  Transaction ID**    Number**      Mail**        Facility**   Facility   Released      Date (Day 0)**
                                                               Locale     Date/Time**   
                                                               Key**                    

  723456789           123456-0219   Standard Mail Baltimore    V22931     02/19/2008    02/19/2008
                                                  P&DC                    14:00 EDT     

  987657666           123456-0301   First-Class   Dulles P&DC  X29745     03/01/2008    03/01/2008
                                    Mail                                  14:25 EDT     

  ACI15678            123456-0302   First-Class   Dulles P&DC  X29745     03/02/2008    03/02/2008
                                    Mail                                  11:00 EDT     
  ------------------- ------------- ------------- ------------ ---------- ------------- -------------------

***Figure 27: Start-the-Clock for Single Group Plant Load Report***

Mailers that can specify the dispatch on which a specific container was
transported in their electronic documentation will receive a different
Mail Release time for each mail dispatch. In this situation, a mailing
will have one start-the-clock record for each dispatch to which
containers were associated. The following sample depicts the multiple
dispatch environment.

  ------------------- ------------- ------------- ------------ ---------- ------------- -------------------
  **Start-the-Clock                                                                     
  -- Multiple Group                                                                     
  Plant Load                                                                            
  Mailings**                                                                            

  **Job ID/           **Dispatch    **Class of    **Origin     **Origin   **Mail        **Start-the-Clock
  Transaction ID**    Number**      Mail**        Facility**   Facility   Released      Date (Day 0)**
                                                               Locale     Date/Time**   
                                                               Key**                    

  723456789           123456-0219   First-Class   Dulles P&DC  X29745     02/19/2008    02/19/2008
                                    Mail                                  11:00 EDT     

  723456789           234567-0219   First-Class   Baltimore    V22931     02/19/2008    02/19/2008
                                    Mail          P&DC                    13:25 EDT     

  723456789           345678-0219   Standard Mail Baltimore    V22931     02/19/2008    02/20/2008
                                                  P&DC                    18:15 EDT     
  ------------------- ------------- ------------- ------------ ---------- ------------- -------------------

***Figure 28: Start-the-Clock for Multiple Group Plant Load Report***

### Start-the-Clock Using Customer Supplier Agreements

The Start-the-Clock event for origin-entered mail that is transported on
USPS transportation is based on the mail ready time as indicated by
mailers in their electronic documentation. This time will be the planned
departure time of the dispatch to which the container was associated in
the electronic documentation

The CSA will establish a time by which all of the containers must be
ready to load onto USPS transportation. This time will be called the
Container Ready Time and will be established for every dispatch in the
CSA transported by USPS.

The Start-the-Clock date will be advanced one day for Continuous Mailers
creating logical containers with dispatches both before and after the
CAT. Although mail received by the USPS before the CAT will be processed
on the date of presentation to USPS, limited knowledge of which physical
mail pieces were accepted before the CAT require the Start-the-Clock to
occur on the entire logical container at once.

### Full-Service Container Visibility

Mailers presenting full-service mailings will be provided a report
showing induction scans of full-service containers. This report of
container visibility information is only available from the USPS
processing facilities where scanning capabilities are implemented. The
container visibility report will only be provided for the containers on
shipments that have been scanned during the induction process. The
FullServiceContainerVisibility Delivery and Response messages in the
Mail.XML specification support this data exchange.

  ---------------- -------------- ----------- ------------ ----------- ----------------------- ------------- ------------- ------------- ---------------
  **Containers                                                                                                                           
  Visibility --                                                                                                                          
  Container                                                                                                                              
  Scans/Status**                                                                                                                         

  **Appt Num**     **Job ID/      **Mailing   **USPS       **USPS      **IM Container          **Container   **Induction   **Induction   **Induc-tion
                   Trans-action   Group ID**  Induction    Induction   Barcode**               Scan          Status**      Issue Desc**  Issue
                   ID**                       Facility**   Facility                            Date/time**                               Resol-ution**
                                                           Locale                                                                        
                                                           Key**                                                                         

  623456789        A6189999       555678      Atlanta SCF  X10054      99M423905469898432348   2/19/2008     Accepted      None          
                                                                                               14:25 EDT                                 

  623456789        A6189999       555678      Atlanta SCF  X10054      99M423905469898432349   2/19/2008     Accepted      None          
                                                                                               14:27 EDT                                 

  623456789        A6189999       555678      Atlanta SCF  X10054      99M423905469898432350   2/19/2008     Accepted      None          
                                                                                               14:31 EDT                                 
  ---------------- -------------- ----------- ------------ ----------- ----------------------- ------------- ------------- ------------- ---------------

***Figure 29: Container Visibility Report***

### Full-Service Change of Address Detail Report 

Mailers presenting full-service mailings will be provided a Change of
Address detail online report and automated data exchange. The report
will provide information including the original Intelligent Mail barcode
on the piece, the move effective date, and the old and new addresses.
The keyline that was provided in the electronic documentation will also
be provided when the electronic documentation specification support the
ability to provide that information. The FullServiceAddressCorrection
Delivery and Response message in the Mail.XML specification supports
this data exchange.

![](media/image7.png){width="6.985433070866142in"
height="0.8015748031496063in"}![](media/image8.png){width="7.0in"
height="1.2090551181102362in"}

***Figure 30: Change of Address Detail Report***

### Full-Service Nixie Detail Report 

Mailers presenting full-service mailings will be provided a Nixie detail
online report and automated data exchange. The report will provide
information including the original Intelligent Mail barcode on the
piece, the nixie reason, and the original address on the mailpiece. The
keyline that was provided in the electronic documentation will also be
provided when the electronic documentation specification support the
ability to provide that information. The FullServiceNixieDetailDelivery
and Response messages in the Mail.XML specification supports this data
exchange.

![](media/image9.wmf){width="5.993055555555555in"
height="1.417361111111111in"}

***Figure 31: Nixie Detail Report***

## Full-Service Data Provisioning to Multiple Parties

Under the full-service option, companies will receive address correction
information and start-the-clock information to advise them of when the
USPS took possession of their mailings. This data will be made available
using two methods.

1.  Businesses or organizations that have users with accounts in the
    USPS systems may view data online.

2.  Businesses or organizations may receive their data through an
    automated data exchange process.

To view data online or to obtain data through an automated data exchange
process, a login ID and a password to the USPS *PostalOne!* system is
required. To use Intelligent Mail barcodes, mailers will need a Mailer
ID (MID). To obtain a Mailer ID, complete and submit an Application for
Mailer ID to the local MDA or BMEU Manager. The USPS will also be
providing an online Mailer ID application and provisioning process. When
issued, Mailer IDs will be recorded in *PostalOne!* as having been
issued to a Mail Owner or a Mail Preparer/Agent.

## Data Distribution to Third-Parties

The primary parties to every mailing are the owner who commissioned the
mailing and the preparer who actually defines the mailpieces and submits
the electronic documentation. Owners may also prepare their own
mailings. These parties are referred to as the Mail Owner and the Mail
Preparer and are responsible for controlling access to data/information
about their mailings. For the Mail Owner or Mail Preparer to participate
in full-service data provisioning to third-parties, they must be
identified by their Mailer ID in the By/For of the electronic
documentation.

The Mail Owner may allow other parties access to data or information
about their mailings. For example, parties interested in OneCode ACS
data from a mailing for which they were not the Mail Owner may receive
the OneCode ACS data when authorized by the Mail Owner. OneCode ACS
information for a specific mailpiece may only be distributed to one
party. Start-the-Clock data from a mailing will be distributed to both
the Mail Owner and Mail preparer unless other authorization from the
Mail Owner or Mail Preparer has been received. Access to Confirm
information will continue to be determined by either the Confirm
Subscriber ID (which does not have to belong to either a Mail Owner or
Mail Preparer) on the mailpiece or provided in the Cast of Characters.
Confirm data may be distributed to multiple parties if each is
identified in a Cast of Characters message. To use Cast of Characters to
distribute Confirm data to a third-party, the electronic documentation
(including Cast of Characters) must be received by the USPS and the
postage statement must be finalized three hours prior to induction of
the mail. No ACS or Start-the-Clock data may be distributed to a
third-party unless the electronic documentation and Cast of Characters
messages are received by the USPS prior to the induction of the mail.

There are two types of authorization Mail Owners/Preparers can grant:
static and dynamic. Profiles may be set up for a specific Mailer ID with
effective start and end dates. A profile effective start data must be at
least 24 hours in the future.

When a Mail Owner/Preparer desires to engage a third-party to manage
their data for a specific Mailer ID and service they will create a
static relationship. For example, a Mail Owner who holds a Mailer ID may
hire a service provider to receive all ACS data associated to their
Mailer ID and obtain that information on their behalf. A Mail Owner who
holds a Mailer ID may also authorize their Mail Preparer to receive all
data associated with mailings that specific Mail Preparer created. The
CastOfCharactersCreate messages supports this capability.

There are other cases when the Mail Owner/Preparer engages a third-party
to manage only a portion of the data for a specific Mailer ID and
service. For example, a Mail Owner who holds a Mailer ID may decide to
use a third-party service provider to receive and report on OneCode
Confirm data from a single mailing. In this example, the relationship
cannot be a Static Relationship because the third-party is only
providing services for a single mailing.

## Profile Set-up

### Static Relationships

To create a Static Relationship profile, the Owner of the Mailer ID
first must have a user account in the *PostalOne!* system and then they
must establish a relationship profile in the *PostalOne!* system that
identifies the access permissions others can have relative to the
Owner's mailings of a specified Mailer ID. A different profile can be
created for each service (i.e. different third-parties can be authorized
to receive OneCode Confirm and OneCode ACS data for the same Mailer ID).
To create a Mail Owner/Mailing Agent Agreement, a user associated to the
Mail Owner will login to the *PostalOne!* system and grant access to the
third-party identified using a Mailer ID of the third-party. Three
levels of access may be provided: Complete, Partial Access (Partial
Preparer, or Partial MID on Piece) and Delegated.

Upon creation of a Static Relationship profile with an access level of
"Complete", all data for the service type defined and associated to the
Mailer ID in the profile would be provided only to the third-party
identified in the profile. This relationship applies whether the Mailer
ID is on the mailpiece or identified in the electronic documentation as
either the Mail Owner or the Mail Preparer.

Upon creation of a "Partial -- Mail Preparer" relationship, all data for
the service in the profile associated to the Mailer ID in the profile
would be provided to the third-party identified in the profile when the
third-party is the Mail Preparer for those mailpieces. This relationship
applies whether the Mailer ID is on the mailpiece or identified in the
electronic documentation as either the Mail Owner or the Mail Preparer.

Upon creation of a "Partial -- MID on Piece" relationship, all data for
the ACS service associated to the Mailer ID in the profile would be
provided to the owner of the Mailer ID on the mailpiece.

If Mail Owners do not want to actively manage their profile, they may
delegate control of their profile to a selected agent. This selected
agent may be either a Mail Preparer or a Third-Party. The agent will
determine to whom data collected should be provided. This access would
be marked as "Delegated" in the profile. To create "Delegated" access, a
Mail Owner may either alter their profile directly in *PostalOne!* or
complete a paper form authorizing the change. Mail Owners may delegate
control for one or all services when setting up their profiles. The
delegated agent may then set-up one of the other profile options:
Complete, Partial, or Dynamic for the data

### Dynamic Relationships

To enable a Dynamic Relationship, a user associated to the Mail
Owner/Preparer that holds the Mailer ID would update the profile for
that Mailer ID to allow access to the users associated with the third-
party provider. This access would be marked as "Partial Access" in the
profile and would enable to the third-party to receive only the portion
of the data associated to that Mailer ID identified in a Cast of
Characters file. The Mail Owner/Preparer would then submit a Cast of
Characters message to identify a mailing (or portion of a mailing) and
the service for which data should be provided to the third-party. This
relationship applies whether the Mailer ID is on the mailpiece or
identified in the electronic documentation as either the Mail Owner or
the Mail Preparer.

A Cast of Characters message may be submitted by a Mail Owner for all
mailpieces prepared on their behalf. A Mail Preparer may submit a Cast
of Characters message for mailpieces they have prepared when a dynamic
profile exists. A Cast of Characters message will only be applied to
ACS, Start-the-Clock and Container Visibility data received three hours
after the transmission of the Cast of Characters message.

# Appendix A: Service Type Identifier Matrix {#appendix-a-service-type-identifier-matrix .unnumbered}

The description that follows describes Service Type Identifiers that
apply to the May 2009 implementation of basic and full-service options
for Intelligent Mail. If you need to identify Service Type Identifiers
to use in your current Intelligent Mail barcodes, refer to the
Intelligent Mail Barcode Technical Resource Guide, which can be found at
http://ribbs.usps.gov/.

Appendix A provides a detailed description of the various address
correction options available within basic and full-service mailings and
the Service Type IDs that provide the different UAA handling treatments.
Note: Mailers that wish to receive address correction information on
non-automation mailpieces should use the corresponding Service Type ID
for basic option mailpieces unless otherwise defined in Appendix A.

Appendix A is divided into

-   No address correction or ancillary services desired for handling of
    UAA mailpieces

-   Using Traditional ACS in conjunction with the Intelligent Mail
    barcode

-   Using OneCode ACS

-   Obtaining manual address corrections or for other ancillary services
    not available in ACS or OneCode ACS

To use Appendix A, follow the below steps:

Step 1 Determine the Class of Mail that is appropriate.

Step 2 Determine whether the Mailing Type will be either basic or
full-service.

Step 3 Determine whether or not you want to receive ACS Detail Records.

Step 4 Determine if you want to receive Confirm services.

Step 5 Select the Mailpiece Disposition desired for any
undeliverable-as-addressed pieces. Note that Mailpiece Dispositions are
often similar with minor differences. Select the Mailpiece Disposition
that best meets your needs.

Step 6 Determine whether the associated Mailpiece Disposition requires
the use of an ancillary service endorsement. If not, skip to Step 8.

Step 7 Determine whether to use a "Recommended Ancillary Service
Endorsement" or an "Allowable Ancillary Service Endorsement" on your
mailpiece by checking the column "Action taken if barcode unreadable".

Step 8 Understand the fees, if any, that will be associated with the use
of the Service Type ID and/or the ancillary service endorsement.

Step 9 Check the Constraints and the Notes columns for applicable
information.

> Step 10 When you are certain that you have correctly identified all
> options and understand the Constraints and Notes, use the Service Type
> ID specific to that line item during creation of the Intelligent Mail
> barcode.

<table style="width:100%;">
<colgroup>
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 3%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 11%" />
</colgroup>
<thead>
<tr class="header">
<th><blockquote>
<p><strong>Service Type ID</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Class of Mail</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>IMb Service Option</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>ACS Detail Record Provided to Mailer</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Confirm Services</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Mailpiece Disposition</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Requires an On-Piece, Text Printed ASE</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Recommended ASE Printed on Piece</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Allowable Ancillary Service Endorsement Printed on
Piece</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Address Change Service (ACS) Option</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Fees</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Provides data that can be used to meet the Move Update
Requirement</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Constraints</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Notes</strong></p>
</blockquote></th>
<th><blockquote>
<p><strong>Action taken if barcode is unavailable or
invalid</strong></p>
</blockquote></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><strong>700</strong></td>
<td>First-Class Mail</td>
<td>Non-Auto</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td></td>
<td> </td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="even">
<td><strong>300</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="odd">
<td><strong>700</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td></td>
<td>Manual address correction fee charged for forwarded mailpieces.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>700</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>700</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail returned with reason for non-delivery or new address
affixed to mailpiece</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>700</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded if Temp COA. All other UAA returned with
reason for non-delivery affixed.</td>
<td>Y</td>
<td>Temp-Return Service Requested</td>
<td>Temp-Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>310</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="even">
<td><strong>040</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td></td>
<td>Manual address correction fee charged for forwarded mailpieces.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>040</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>040</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail returned with reason for non-delivery or new address
affixed to mailpiece</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>040</strong></td>
<td>First-Class Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded if Temp COA. All other UAA returned with
reason for non-delivery affixed.</td>
<td>Y</td>
<td>Temp-Return Service Requested</td>
<td>Temp-Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>080</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td> Once Mailer ID established as Address Service Requested Option 1,
the same Mailer ID cannot be used for ASR Option 2 or CSR Option 2</td>
<td>Electronic address correction notices provided on forwarded mail
only.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided.
Forwardable Mail Forwarded, all other UAA mail returned<br />
<br />
(B) If ASR, Hard copy, manual correction to be provided at manual
correction fee on forwarded pieces only.</td>
</tr>
<tr class="odd">
<td><strong>080</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 2,
the same Mailer ID cannot be used for ASR Option 1 or CSR Option 2</td>
<td>Electronic address correction notices provided for all forwarded and
returned mailpieces.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided.
Forwardable Mail Forwarded, all other UAA mail returned<br />
<br />
(B) If ASR, Hard copy, manual correction to be provided at manual
correction fee on forwarded pieces only. All other UAA returned with
on-piece</td>
</tr>
<tr class="even">
<td><strong>082</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td><p>Change Service Requested</p>
<p>(A)</p></td>
<td><p>Electronic Service Requested</p>
<p>(B)</p></td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 1, the
same Mailer ID cannot be used for CSR Option 2 or ASR Option 2</td>
<td>All undeliverable-as-address mail disposed of and OneCode ACS notice
provided for all transactions</td>
<td>(A) If CSR, All undeliverable mail will be returned with new address
or reason for non-delivery affixed.(B) If ESR, No separate ACS or hard
copy notice provided, mail will be forwarded or returned as
eligible.</td>
</tr>
<tr class="odd">
<td><strong>082</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 2, the
same Mailer ID cannot be used for CSR Option 1 or ASR Option 2</td>
<td></td>
<td>(A) If CSR, All undeliverable mail will be returned with new address
or reason for non-delivery affixed.<br />
<br />
(B) If ESR, No separate ACS or hard copy notice provided, mail will be
forwarded or returned as eligible.</td>
</tr>
<tr class="even">
<td><strong>080</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>082</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>140</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded.All other UAA returned with reason for
non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested(A)</td>
<td>Address Service Requested(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td> Once Mailer ID established as Address Service Requested Option 1,
the same Mailer ID cannot be used for ASR Option 2 or CSR Option 2</td>
<td>Electronic address correction notices provided on forwarded mail
only.</td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="odd">
<td><strong>140</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 2,
the same Mailer ID cannot be used for ASR Option 1 or CSR Option 2</td>
<td>Electronic address correction notices provided for all forwarded and
returned mailpieces.</td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="even">
<td><strong>240</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 1, the
same Mailer ID cannot be used for CSR Option 2 or ASR Option 2</td>
<td>All undeliverable-as-address mail disposed of and OneCode ACS notice
provided for all transactions.</td>
<td>(A) If CSR, All undeliverable mail will be returned with new address
or reason for non-delivery affixed.<br />
<br />
(B) If ESR, No separate ACS or hard copy notice provided, mail will be
forwarded or returned as eligible.</td>
</tr>
<tr class="odd">
<td><strong>240</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded, all other UAA mail disposed</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Change Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 2, the
same Mailer ID cannot be used for CSR Option 1 or ASR Option 2</td>
<td>Forwardable mail forwarded, all other undeliverable-as-address mail
disposed. OneCode ACS notices provided for all transactions.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided. Mail is
forwarded or returned as eligible.<br />
<br />
(B) If CSR, All undeliverable mail will be returned with new address or
reason for non-delivery affixed.</td>
</tr>
<tr class="even">
<td><strong>140</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1 or Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>240</strong></td>
<td>First-Class Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1 or Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>700</strong></td>
<td>First-Class Reply Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="odd">
<td><strong>050</strong></td>
<td>First-Class Reply Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Origin</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>708</strong></td>
<td>Business Reply Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="odd">
<td><strong>052</strong></td>
<td>Business Reply Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Origin</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>260</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA returned</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="odd">
<td><strong>036</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td></td>
<td>Manual address correction fee charged for forwarded mailpieces.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>036</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>036</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail returned with reason for non-delivery or new address
affixed to mailpiece</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>036</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded if Temp COA. All other UAA returned with
reason for non-delivery affixed.</td>
<td>Y</td>
<td>Temp-Return Service Requested</td>
<td>Temp-Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>081</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided. All other UAA returned with reason for non-delivery
affixed.</td>
<td>N</td>
<td>Electronic Service Requested(A)</td>
<td>Address Service Requested (B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td> Once Mailer ID established as Address Service Requested Option 1,
the same Mailer ID cannot be used for ASR Option 2 or CSR Option 2</td>
<td>Separate address correction provided for forwarded pieces only.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided, mail
forwarded and returned as appropriate.(B) If ASR, Hard copy, manual
correction to be provided at manual correction fee on forwarded pieces
only.</td>
</tr>
<tr class="even">
<td><strong>081</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 2,
the same Mailer ID cannot be used for ASR Option 1 or CSR Option 2</td>
<td>Electronic address correction notices provided for all forwarded and
returned mailpieces.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided, mail
forwarded and returned as appropriate.<br />
<br />
(B) If ASR, Hard copy, manual correction to be provided at manual
correction fee on forwarded pieces only.</td>
</tr>
<tr class="odd">
<td><strong>083</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 2,
the same Mailer ID cannot be used for ASR Option 1 or CSR Option 2</td>
<td>All undeliverable-as-address mail disposed of and OneCode ACS notice
provided for all transactions.</td>
<td>(A) If ESR, mail is forwarded or returned as appropriate, No
separate ACS or hard copy notice provided.<br />
<br />
(B) If CSR, All undeliverable mail will be returned with new address or
reason for non-delivery affixed.</td>
</tr>
<tr class="even">
<td><strong>083</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested(A)</td>
<td>Electronic Service Requested(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 2, the
same Mailer ID cannot be used for CSR Option 1 or ASR Option 2</td>
<td>Forwardable mail forwarded, all other undeliverable-as-address mail
disposed. OneCode ACS notices provided for all transactions.</td>
<td>(A) If ESR, mail is forwarded or returned as appropriate, No
separate ACS or hard copy notice provided.(B) If CSR, All undeliverable
mail will be returned with new address or reason for non-delivery
affixed.</td>
</tr>
<tr class="odd">
<td><strong>081</strong></td>
<td>First-Class Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>083</strong></td>
<td>First-Class Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>270</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded, all other UAA returned</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Forwardable mail forwarded, all other UAA returned w/reason
affixed</td>
</tr>
<tr class="even">
<td><strong>041</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded with separate notice of new address
provided.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td></td>
<td>Manual address correction fee charged for forwarded mailpieces.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>041</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded.<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>041</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail returned with reason for non-delivery or new address
affixed to mailpiece</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="odd">
<td><strong>041</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded if Temp COA. All other UAA returned with
reason for non-delivery affixed.</td>
<td>Y</td>
<td>Temp-Return Service Requested</td>
<td>Temp-Return Service Requested</td>
<td> </td>
<td></td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Treated according to endorsement.</td>
</tr>
<tr class="even">
<td><strong>141</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded .<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 1,
the same Mailer ID cannot be used for ASR Option 2 or CSR Option2</td>
<td>Electronic address correction notices provided for all forwarded
mailpieces.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided, mail
forwarded and returned as appropriate.<br />
<br />
(B) If ASR, Hard copy, manual correction to be provided at manual
correction fee on forwarded pieces only.</td>
</tr>
<tr class="odd">
<td><strong>141</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded .<br />
All other UAA returned with reason for non-delivery affixed.</td>
<td>N</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Address Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Address Service Requested Option 2,
the same Mailer ID cannot be used for ASR Option 1 or CSR Option 2</td>
<td>Electronic address correction notices provided for all forwarded and
returned mailpieces.</td>
<td>(A) If ESR, No separate ACS or hard copy notice provided, mail
forwarded and returned as appropriate.<br />
<br />
(B) If ASR, Hard copy, manual correction to be provided at manual
correction fee on forwarded pieces only.</td>
</tr>
<tr class="even">
<td><strong>241</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested(A)</td>
<td>Electronic Service Requested(B)</td>
<td><p>Option 1</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 1, the
same Mailer ID cannot be used for CSR Option 2 or ASR Option 2</td>
<td>All undeliverable-as-address mail disposed of and OneCode ACS notice
provided for all transactions.</td>
<td>(A) If CSR, All undeliverable mail will be returned with new address
or reason for non-delivery affixed.(B) If ESR, mail is forwarded or
returned as appropriate, No separate ACS or hard copy notice
provided.</td>
</tr>
<tr class="odd">
<td><strong>241</strong></td>
<td>First-Class Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>Change Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td><p>Option 2</p>
<p>(See Constraints)</p></td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td>Once Mailer ID established as Change Service Requested Option 2, the
same Mailer ID cannot be used for CSR Option 1 or ASR Option 2</td>
<td>Forwardable mail forwarded, all other undeliverable-as-addressed
mail disposed. OneCode ACS notices provided for all transactions.</td>
<td>(A) If CSR, All undeliverable mail will be returned with new address
or reason for non-delivery affixed.<br />
<br />
(B) If ESR, mail is forwarded or returned as appropriate, No separate
ACS or hard copy notice provided.</td>
</tr>
<tr class="even">
<td><strong>141</strong></td>
<td>First-Class Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>241</strong></td>
<td>First-Class Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td>Option 1<br />
or<br />
Option 2</td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a per ancillary service endorsement</td>
<td>If ESR or specific endorsement, Traditional ACS processing will be
provided as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>700</strong></td>
<td>First-Class Reply Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="odd">
<td><strong>050</strong></td>
<td>First-Class Reply Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Origin</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>708</strong></td>
<td>Business Reply Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="odd">
<td><strong>052</strong></td>
<td>Business Reply Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Origin</td>
<td>N/A</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong>N</strong></td>
<td>N/A</td>
<td> </td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>704</strong></td>
<td>Periodicals Class</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td> </td>
<td>Fees charged at current pricing schedule</td>
<td> </td>
<td> </td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
</tr>
<tr class="odd">
<td><strong>704</strong></td>
<td>Periodicals Class</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>PS Form 3579 manual correction provided on first forwarded mailpiece
after 60 days. Returned pieces at single piece rate</td>
<td>Y</td>
<td>Return address must show on the addressed side of mailpiece</td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
</tr>
<tr class="even">
<td><strong>044</strong></td>
<td>Periodicals Class</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td> </td>
<td>Fees charged at current pricing schedule</td>
<td> </td>
<td> </td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
</tr>
<tr class="odd">
<td><strong>044</strong></td>
<td>Periodicals Class</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>PS Form 3579 manual correction provided on first forwarded mailpiece
after 60 days. Returned pieces at single piece rate</td>
<td>Y</td>
<td>Return address must show on the addressed side of mailpiece</td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
</tr>
<tr class="even">
<td><strong>784</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>Periodicals Option 2</td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td></td>
<td> </td>
<td>Mailpiece forwarded for first 60 days. After first 60 days,
mailpiece disposed and address correction provided.<br />
<br />
All other undeliverable mail disposed and address correction provided
with reason for non-delivery.</td>
</tr>
<tr class="odd">
<td><strong>782</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 2</td>
<td>OneCode ACS pricingReturned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record at first occurrence</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="even">
<td><strong>782</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 4</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record after 60 days of COA</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="odd">
<td><strong>784</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).<br />
<br />
Forwardable mail forwarded first 60 days after customer move, all other
UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Unreadable Intelligent Mail barcode not applicable.<br />
<br />
Mailpiece will forward or waste as appropriate.</td>
</tr>
<tr class="even">
<td><strong>782</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).Forwardable mail forwarded first 60 days after customer
move, all other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS feeSingle piece rate if ASR used</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Not applicable</td>
</tr>
<tr class="odd">
<td><strong>244</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>Periodicals OneCode ACS option 2 provided</td>
<td></td>
<td>Y</td>
<td></td>
<td> </td>
<td>Mailpiece forwarded for first 60 days. After first 60 days,
mailpiece disposed and address correction provided.<br />
<br />
All other undeliverable mail disposed and address correction provided
with reason for non-delivery.</td>
</tr>
<tr class="even">
<td><strong>144</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 2</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record at first occurrence</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="odd">
<td><strong>144</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 4</td>
<td>OneCode ACS pricingReturned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record after 60 days of COA</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="even">
<td><strong>244</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).<br />
<br />
Forwardable mail forwarded first 60 days after customer move, all other
UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Mailpiece forwarded for first 60 days. After first 60 days,
mailpiece disposed and address correction provided.<br />
<br />
All other undeliverable mail disposed and address correction provided
with reason for non-delivery.</td>
</tr>
<tr class="odd">
<td><strong>144</strong></td>
<td>Periodicals Class</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).<br />
<br />
Forwardable mail forwarded first 60 days after customer move, all other
UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee<br />
<br />
Single piece rate if ASR used</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
</tr>
<tr class="even">
<td><strong>264</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td> </td>
<td>Fees charged at current pricing schedule</td>
<td> </td>
<td> </td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
</tr>
<tr class="odd">
<td><strong>264</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>PS Form 3579 manual correction provided on first forwarded mailpiece
after 60 days. Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Allows use of barcode for automation rates and the use of hard copy
address corrections.</td>
<td>If no endorsement, mailpiece will forward, waste, or return p/d as
appropriate. Any address corrections will be hard copy PS Form
3579.</td>
</tr>
<tr class="even">
<td><strong>038</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>Periodicals OneCode ACS option 2 provided</td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td></td>
<td> </td>
<td>Mailpiece forwarded for first 60 days. After first 60 days,
mailpiece disposed and address correction provided.<br />
<br />
All other undeliverable mail disposed and address correction provided
with reason for non-delivery.</td>
</tr>
<tr class="odd">
<td><strong>783</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 2</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record at first occurrence</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="even">
<td><strong>783</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 4</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record after 60 days of COA</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="odd">
<td><strong>038</strong></td>
<td>Periodicals Class</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).Forwardable mail forwarded first 60 days after customer
move, all other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Unreadable Intelligent Mail barcode not applicable.Mailpiece will
forward or waste as appropriate.</td>
</tr>
<tr class="even">
<td><strong>783</strong></td>
<td>Periodicals Class</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).<br />
<br />
Forwardable mail forwarded first 60 days after customer move, all other
UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee<br />
<br />
Single piece rate if ASR used</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Not applicable</td>
</tr>
<tr class="odd">
<td><strong>274</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>N/A</td>
<td>PS Form 3579 manual correction provided on first forwarded mailpiece
after 60 days. Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Allows use of barcode for automation rates and the use of hard copy
address corrections.</td>
<td>If no endorsement, mailpiece will forward, waste, or return p/d as
appropriate. Any address corrections will be hard copy PS Form
3579.</td>
</tr>
<tr class="even">
<td><strong>045</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td> </td>
<td>Fees charged at current pricing schedule</td>
<td> </td>
<td> </td>
<td> </td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
</tr>
<tr class="odd">
<td><strong>045</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>Periodicals OneCode ACS option 2 provided</td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td></td>
<td> </td>
<td>Mailpiece forwarded for first 60 days. After first 60 days,
mailpiece disposed and address correction provided.<br />
<br />
All other undeliverable mail disposed and address correction provided
with reason for non-delivery.</td>
</tr>
<tr class="even">
<td><strong>145</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 2</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record at first occurrence</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="odd">
<td><strong>145</strong></td>
<td>Periodicals Class</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>Forwardable mail forwarded first 60 days after customer move, all
other UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>Periodicals Option 4</td>
<td>OneCode ACS pricing<br />
<br />
Returned pieces at single piece rate</td>
<td>Y</td>
<td> </td>
<td>Provides an ACS record after 60 days of COA</td>
<td>Mail will forward for 60 days, all future copies and UAA pieces
returned to sender postage due.</td>
</tr>
<tr class="even">
<td><strong>045</strong></td>
<td>Periodicals Class</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).Forwardable mail forwarded first 60 days after customer
move, all other UAA disposed</td>
<td>N</td>
<td>Must not be endorsed</td>
<td>Must not be endorsed</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Unreadable Intelligent Mail barcode not applicable.Mailpiece will
forward or waste as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>145</strong></td>
<td>Periodicals Class</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF).<br />
<br />
Forwardable mail forwarded first 60 days after customer move, all other
UAA returned</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td>As recorded in Traditional ACS Mailer Profile</td>
<td>Traditional ACS fee<br />
<br />
Single piece rate if ASR used</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Allows use of barcode for automation rates and the use of
Traditional ACS.</td>
<td>Not applicable</td>
</tr>
<tr class="even">
<td><strong>702</strong></td>
<td>Standard Mail</td>
<td>Non-Auto</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td> </td>
<td><strong>N</strong></td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>All UAA mail Disposed</td>
</tr>
<tr class="odd">
<td><strong>301</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td> </td>
<td><strong>N</strong></td>
<td> </td>
<td> </td>
<td>All UAA mail Disposed</td>
</tr>
<tr class="even">
<td><strong>702</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Manual address correction fees (hard copy) and postage due fees as
applicable</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>702</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>702</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Weighted fee charged for returns</td>
<td>N</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>702</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Single piece postage for returned pieces,</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>311</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td> </td>
<td>N</td>
<td> </td>
<td> </td>
<td>All UAA mail Disposed</td>
</tr>
<tr class="odd">
<td><strong>042</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Manual address correction fees (hard copy) and postage due fees as
applicable</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>042</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>042</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Weighted fee charged for returns</td>
<td>N</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>042</strong></td>
<td>Standard Mail</td>
<td>Basic Option</td>
<td>N</td>
<td>Destination</td>
<td>All UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Single piece postage for returned pieces,</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>090</strong></td>
<td>Standard Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y (forwarded mail only)</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed to mailpiece.</td>
<td>Y</td>
<td>Address Service Requested(A)</td>
<td>Electronic Service Requested(B)</td>
<td>Option 1</td>
<td>Address correction for forwards OneCode ACS pricing. Weighted fee
charged for returns</td>
<td>Y</td>
<td> </td>
<td>If the mailer is more concerned with getting their UAA mailpiece
back then they should use ASR.If the mailer is more concerned with the
ACS notice and avoiding hard copy corrections they should use ESR.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.(B) If ESR, all UAA mailpieces disposed without
address correction.</td>
</tr>
<tr class="even">
<td><strong>092</strong></td>
<td>Standard Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Change Service Requested<br />
(B)</td>
<td>Option 1</td>
<td>Address correction OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td> </td>
<td>(A) If ESR, all UAA mailpieces disposed without address
correction.<br />
<br />
(B) If CSR, all UAA mailpieces disposed and separate manual address
correction provided at fee.</td>
</tr>
<tr class="odd">
<td><strong>090</strong></td>
<td>Standard Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>092</strong></td>
<td>Standard Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>142</strong></td>
<td>Standard Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y (forwarded mail only)</td>
<td>Destination</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed to mailpiece.</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td>Option 1</td>
<td>Address correction for forwards OneCode ACS pricing.<br />
<br />
Weighted fee charged for returns</td>
<td>Y</td>
<td> </td>
<td>If the mailer is more concerned with getting their UAA mailpiece
back then they should use ASR.<br />
If the mailer is more concerned with the ACS notice and avoiding hard
copy corrections they should use ESR.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.<br />
<br />
(B) If ESR, all UAA mailpieces disposed without address correction.</td>
</tr>
<tr class="even">
<td><strong>242</strong></td>
<td>Standard Mail</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested(A)</td>
<td>Change Service Requested(B)</td>
<td>Option 1</td>
<td>Address correction OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td> </td>
<td>(A) If ESR, all UAA mailpieces disposed without address
correction.(B) If CSR, all UAA mailpieces disposed and separate manual
address correction provided at fee.</td>
</tr>
<tr class="odd">
<td><strong>142</strong></td>
<td>Standard Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>242</strong></td>
<td>Standard Mail</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>261</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td> </td>
<td>N</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>All UAA mail disposed</td>
</tr>
<tr class="even">
<td><strong>037</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Manual address correction fees (hard copy) and postage due fees as
applicable</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>037</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>037</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Weighted fee charged for returns</td>
<td>N</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>037</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Single piece postage for returned pieces,</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>091</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>Y (forwarded mail only)</td>
<td>None</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed to mailpiece.</td>
<td>Y</td>
<td>Address Service Requested(A)</td>
<td>Electronic Service Requested(B)</td>
<td>Option 1</td>
<td>Address correction for forwards OneCode ACS pricing. Weighted fee
charged for returns</td>
<td>Y</td>
<td> </td>
<td>If the mailer is more concerned with getting their UAA mailpiece
back then they should use ASR.If the mailer is more concerned with the
ACS notice and avoiding hard copy corrections they should use ESR.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.(B) If ESR, all UAA mailpieces disposed without
address correction.</td>
</tr>
<tr class="odd">
<td><strong>093</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested<br />
(A)</td>
<td>Change Service Requested<br />
(B)</td>
<td>Option 1</td>
<td>Address correction OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td> </td>
<td>(A) If ESR, all UAA mailpieces disposed without address
correction<br />
<br />
(B) If CSR, all UAA mailpieces disposed and separate manual address
correction provided at fee.</td>
</tr>
<tr class="even">
<td><strong>091</strong></td>
<td>Standard Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>093</strong></td>
<td>Standard Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>271</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td>All UAA mail disposed</td>
</tr>
<tr class="odd">
<td><strong>043</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Manual address correction fees (hard copy) and postage due fees as
applicable</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>043</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>All UAA mail disposed</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>043</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>Forwardable mailpieces forwarded. All other UAA returned with reason
for non-delivery affixed.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Weighted fee charged for returns</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="even">
<td><strong>043</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>N</td>
<td>Destination</td>
<td>All UAA returned with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Single piece postage for returned pieces,</td>
<td>Y</td>
<td>Electronic Service Requested not allowed.</td>
<td> </td>
<td>Mailpiece handled according to on-piece endorsement resulting in
manual address corrections and or mailpiece return as appropriate.</td>
</tr>
<tr class="odd">
<td><strong>143</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>Y<br />
(forwarded mail only)</td>
<td>Destination</td>
<td>Forwardable mail forwarded, all other UAA returned with reason for
non-delivery affixed to mailpiece.</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td>Option 1</td>
<td>Address correction for forwards OneCode ACS pricing.<br />
<br />
Weighted fee charged for returns</td>
<td>Y</td>
<td> </td>
<td>If the mailer is more concerned with getting their UAA mailpiece
back then they should use ASR.<br />
If the mailer is more concerned with the ACS notice and avoiding hard
copy corrections they should use ESR.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.<br />
<br />
(B) If ESR, all UAA mailpieces disposed without address correction.</td>
</tr>
<tr class="even">
<td><strong>243</strong></td>
<td>Standard Mail</td>
<td>Full Service</td>
<td>Y</td>
<td>Destination</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested(A)</td>
<td>Change Service Requested(B)</td>
<td>Option 1</td>
<td>Address correction OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td> </td>
<td>(A) If ESR, all UAA mailpieces disposed without address
correction.(B) If CSR, all UAA mailpieces disposed and separate manual
address correction provided at fee.</td>
</tr>
<tr class="odd">
<td><strong>143</strong></td>
<td>Standard Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>243</strong></td>
<td>Standard Mail</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>Destination</td>
<td>Requests use of Traditional ACS data in address block. Mailpiece
disposition according to ancillary service request recorded in mailer
profile (UMF) Both options of Address Service or Change Service
available</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to a single class and ancillary service
endorsement.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>706</strong></td>
<td>BPM</td>
<td>Non-Auto</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed of in delivery unit</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong> </strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>All UAA mail disposed of in delivery unit</td>
</tr>
<tr class="even">
<td><strong>401</strong></td>
<td>BPM</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed of in delivery unit</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td><strong> </strong></td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>All UAA mail disposed of in delivery unit</td>
</tr>
<tr class="odd">
<td><strong>706</strong></td>
<td>BPM</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. All other UAA returned.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Returned mailpieces pay Zone Rate fee.<br />
Forwarded mailpiece pay manual address correction fee.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td><strong> </strong></td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="even">
<td><strong>706</strong></td>
<td>BPM</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed of in CFS unit</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td><strong> </strong></td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="odd">
<td><strong>706</strong></td>
<td>BPM</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. All other UAA returned.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Mailer pays both forwarding and/or returned postage on returned
mailpieces.</td>
<td><strong> </strong></td>
<td>Electronic Service Requested not allowed</td>
<td><strong> </strong></td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="even">
<td><strong>706</strong></td>
<td>BPM</td>
<td>Basic Option</td>
<td>N</td>
<td>None</td>
<td>All UAA mail returned to sender at zone rate with reason for
non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Returned mailpieces pay Zone Rate fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="odd">
<td><strong>424</strong></td>
<td>BPM</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y<br />
(forwarded mailpieces only)</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. Other UAA returned at Zone Rate</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td> </td>
<td>OneCode ACS pricing.<br />
<br />
UAA returned at postage due fees</td>
<td>Y</td>
<td> </td>
<td>Must be endorsed Address Service Requested or Electronic Service
Requested</td>
<td>(A) If ASR, mailpiece forwarded new address provided at manual
address correction fee.<br />
<br />
(B) If ESR, all UAA disposed as UBBM and no manual address correction
provided.</td>
</tr>
<tr class="even">
<td><strong>424</strong></td>
<td>BPM</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Forwardable pieces forwarded, Undeliverable pieces returned to
sender with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td>SPF1</td>
<td>Address correction OneCode ACS pricing. Forwardable pieces shipper
paid at single piece letter or flat rate. Undeliverable pieces returned
to sender at single piece rate.</td>
<td>Y</td>
<td> </td>
<td>Address corrections provided for forwarded pieces only.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.<br />
<br />
(B) If ESR, all UAA mailpieces disposed without address correction.</td>
</tr>
<tr class="odd">
<td><strong>431</strong></td>
<td>BPM</td>
<td>Basic Option (OneCode ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested(A)</td>
<td>Change Service Requested(B)</td>
<td> </td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td>Must be endorsed Change Service Requested or Electronic Service
Requested</td>
<td>(A) If CSR, mailpiece disposed and hard copy address correction
provided at manual address correction fee.(B) If ESR, all UAA disposed
as UBBM and no manual address correction provided.</td>
</tr>
<tr class="even">
<td><strong>424</strong></td>
<td>BPM</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block.</td>
<td>Y</td>
<td><p>Address Service Requested</p>
<p>(A)</p></td>
<td>Electronic Service Requested<br />
(B)</td>
<td> </td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to both a single class and ancillary
option.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>(A) If Unendorsed or ESR, all UAA mailpieces disposed without
address correction.<br />
<br />
(B) If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>431</strong></td>
<td>BPM</td>
<td>Basic Option (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block.</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested<br />
(B)</td>
<td> </td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to both a single class and ancillary
option.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>(A) If Unendorsed or ESR, all UAA mailpieces disposed without
address correction.<br />
<br />
(B) If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="even">
<td><strong>265</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed of in delivery unit</td>
<td>N</td>
<td>N/A</td>
<td>N/A</td>
<td> </td>
<td></td>
<td> </td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>All UAA mail disposed of in delivery unit</td>
</tr>
<tr class="odd">
<td><strong>466</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. All other UAA returned.</td>
<td>Y</td>
<td>Address Service Requested</td>
<td>Address Service Requested</td>
<td> </td>
<td>Returned mailpieces pay Zone Rate fee.<br />
Forwarded mailpiece pay manual address correction fee.</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="even">
<td><strong>466</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail disposed of in CFS unit</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Change Service Requested</td>
<td> </td>
<td>Manual address correction fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="odd">
<td><strong>466</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. All other UAA returned.</td>
<td>Y</td>
<td>Forwarding Service Requested</td>
<td>Forwarding Service Requested</td>
<td> </td>
<td>Mailer pays both forwarding and/or returned postage on returned
mailpieces.</td>
<td><strong> </strong></td>
<td>Electronic Service Requested not allowed</td>
<td><strong> </strong></td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="even">
<td><strong>466</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>N</td>
<td>None</td>
<td>All UAA mail returned to sender at zone rate with reason for
non-delivery affixed.</td>
<td>Y</td>
<td>Return Service Requested</td>
<td>Return Service Requested</td>
<td> </td>
<td>Returned mailpieces pay Zone Rate fee</td>
<td>Y</td>
<td>Electronic Service Requested not allowed</td>
<td> </td>
<td>Handled according to printed ancillary service endorsement</td>
</tr>
<tr class="odd">
<td><strong>423</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>Y<br />
(forwarded mail only)</td>
<td>None</td>
<td>Forwardable mail forwarded locally at no charge, non-locally postage
due. Other UAA returned at Zone Rate</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td> </td>
<td>OneCode ACS pricing.<br />
<br />
UAA returned at postage due fees</td>
<td>Y</td>
<td> </td>
<td>Must be endorsed Address Service Requested or Electronic Service
Requested</td>
<td>(A) If ASR, mailpiece forwarded new address provided at manual
address correction fee.<br />
<br />
(B) If ESR, all UAA disposed as UBBM and no manual address correction
provided.</td>
</tr>
<tr class="even">
<td><strong>423</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>Y<br />
(forwards only)</td>
<td>None</td>
<td>Forwardable pieces forwarded, Undeliverable pieces returned to
sender with reason for non-delivery affixed.</td>
<td>Y</td>
<td>Address Service Requested<br />
(A)</td>
<td>Electronic Service Requested<br />
(B)</td>
<td>SPF1</td>
<td>Address correction OneCode ACS pricing. Forwardable pieces shipper
paid at single piece letter or flat rate. Undeliverable pieces returned
to sender at single piece rate.</td>
<td>Y</td>
<td> </td>
<td>Address corrections provided for forwarded pieces only.</td>
<td>(A) If ASR, mailpiece forwarded to new address with manual address
correction (PS Form 3547) provided at fee. All other UAA mailpieces
returned at weighted fee.<br />
<br />
(B) If ESR, all UAA mailpieces disposed without address correction.</td>
</tr>
<tr class="odd">
<td><strong>430</strong></td>
<td>BPM</td>
<td>Full Service</td>
<td>Y</td>
<td>None</td>
<td>All UAA mail disposed of:</td>
<td>Y</td>
<td>Electronic Service Requested(A)</td>
<td>Change Service Requested(B)</td>
<td> </td>
<td>OneCode ACS pricing</td>
<td>Y</td>
<td> </td>
<td>Must be endorsed Change Service Requested or Electronic Service
Requested</td>
<td>(A) If CSR, mailpiece disposed and hard copy address correction
provided at manual address correction fee.(B) If ESR, all UAA disposed
as UBBM and no manual address correction provided.</td>
</tr>
<tr class="even">
<td><strong>423</strong></td>
<td>BPM</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block.</td>
<td>Y</td>
<td><p>Address Service Requested</p>
<p>(A) Requested</p></td>
<td>Electronic Service Requested<br />
(B)</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to both a single class and ancillary
option.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>(A) If Unendorsed or ESR, all UAA mailpieces disposed without
address correction.<br />
<br />
(B) If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
<tr class="odd">
<td><strong>430</strong></td>
<td>BPM</td>
<td>Full Service (Traditional ACS purchased separately)</td>
<td>Y</td>
<td>None</td>
<td>Requests use of Traditional ACS data in address block.</td>
<td>Y</td>
<td>Change Service Requested</td>
<td>Electronic Service Requested<br />
(B)</td>
<td></td>
<td>Traditional ACS pricing</td>
<td>Y</td>
<td>MID is not linked to the requested service, but the Traditional ACS
participant ID is limited to both a single class and ancillary
option.</td>
<td>Mailpiece disposition and address corrections provided as described
in Pub 8a</td>
<td>(A) If Unendorsed or ESR, all UAA mailpieces disposed without
address correction.<br />
<br />
(B) If specific endorsement, Traditional ACS processing will be provided
as identified in the endorsement and the mailer profile.</td>
</tr>
</tbody>
</table>

# Appendix B: Data Distribution Scenarios {#appendix-b-data-distribution-scenarios .unnumbered}

The following scenarios illustrate how the data distribution rules
defined above would be used. In these scenarios, assume the following
companies are involved in a mailing.

Company A: Mail Owner (MID 123456789)

Company B: Mail Preparer (MID 987654321)

Company C: Service Provider (MID 111111111)

Company D: Mail Owner (MID 000123456)

Company E: Mail Preparer (MID 000987654321)

[]{#__RefHeading___Toc216230347 .anchor}**OneCode ACS Scenarios**

Scenario 1:

Company A prepares their own mailings using their Mailer ID, 123456789.
Company A wants to receive OneCode ACS data.

-   Company A would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Preparer and indicate the Mailer ID on the mailpiece is that of the
    Mail Owner.

-   Company A would receive OneCode ACS data through the Mailer ID on
    the mailpiece.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 2:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wishes to receive OneCode ACS data.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company B as the Mail
    Preparer and indicate the Mailer ID on the mailpiece is that of the
    Mail Owner.

-   Company A would receive OneCode ACS data through the Mailer ID on
    the mailpiece.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 3:

Company A hires Company B to prepare their mailing and Company B uses
its own Mailer ID 987654321 on the mailpieces. Company A wishes to
receive OneCode ACS data.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company A would receive OneCode ACS data through the By/For
    information in the electronic documentation.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 4:

Company A hires Company B to prepare their mailing and Company B uses
its own Mailer ID 987654321 on the mailpieces. Company A wishes to send
their OneCode ACS data to Company B whenever Company B is their Mail
Preparer.

-   Company A has set up a static partial profile in *PostalOne!*
    authorizing Company B to receive the OneCode ACS data for Company A
    when Company B prepares the mail.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company B would receive OneCode ACS data through the static profile
    in *PostalOne!*.

-   No Cast of Characters message would be required.

Scenario 5:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wishes to send all of their OneCode ACS data to Company C.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the OneCode ACS data for Company A
    under all circumstances.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company C would receive OneCode ACS data through the static profile
    in *PostalOne!*.

-   No Cast of Characters message would be required.

Scenario 6:

Company A hires Company B to prepare their mailing and Company B uses
its own Mailer ID 987654321 on the mailpieces. Company A wishes to send
all of their OneCode ACS data to Company C.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the OneCode ACS data for Company A
    under all circumstances.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company C would receive OneCode ACS data through a combination of
    the By/For information and the static profile in *PostalOne!*.

-   No Cast of Characters message would be required.

Scenario 7:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wishes to send all of their OneCode ACS data to Company B for
this mailing.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company B to receive the OneCode ACS data when a Cast of Characters
    file has been submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and directing OneCode ACS data for those mailpieces to
    Company B.

-   Company B would receive OneCode ACS data for the mailing through the
    dynamic profile in *PostalOne!* and Cast of Characters.

Scenario 8:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wishes to send all of their OneCode ACS data to Company B for
this mailing.

-   Company A has NOT set up a dynamic profile in *PostalOne!*
    authorizing Company B to receive the OneCode ACS data when a Cast of
    Characters has been submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and directing OneCode ACS data for those mailpieces to
    Company B.

-   Company B would NOT receive OneCode ACS data for the mailing.

-   Company A would receive their OneCode ACS data for the mailing.

-   An error message would be send to the submitter of the Cast of
    Characters.

Scenario 9:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A has delegated all data access to Company B.

-   Company A has transferred control of their Mailer ID to Company B in
    their static Delegated profile in *PostalOne!*. Company B has set up
    the profile to receive the OneCode ACS data.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company B would receive the OneCode ACS data through the profile.

-   No Cast of Characters message would be required.

Scenario 10:

Company A hires Company B and Company E to prepare their mailing and
requests Company B and Company E to use company A's (Mail Owner) Mailer
ID 123456789 on the mailpieces. Company A wishes to receive OneCode ACS
data.

-   Company B would submit electronic documentation to *PostalOne!* to
    indicate the Mailer ID on the mailpiece is that of the Mail Owner.

-   Company E would submit electronic documentation to *PostalOne!* to
    indicate the Mailer ID on the mailpiece is that of the Mail Owner.

-   Company A would receive OneCode ACS data through the Mailer ID on
    the mailpiece.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 11:

Company A hires Company B and Company E to prepare their mailing and the
Mail Preparers use their own Mailer ID (Company B, Mailer ID 987654321
and Company E, Mailer ID 000987654321) on the mailpieces. Company A
wishes to receive OneCode ACS data.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company E would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company A would receive OneCode ACS data through the By/For
    information in the electronic documentation.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 12:

Company A hires Company B and Company E to prepare their mailing and
requests Company B and Company E to use company A's (Mail Owner) Mailer
ID 123456789 on the mailpieces. Company A wishes to send their OneCode
ACS data to Company B whenever Company B is their Mail Preparer and
Company E whenever Company E is their Mail Preparer.

-   Company A has set up a static Partial profile in *PostalOne!*
    authorizing both Company B and Company E to receive the OneCode ACS
    data for Company A when they prepare the mail.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company E would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company B would receive OneCode ACS data through the static profile
    in *PostalOne!* for the mailpieces they prepared

-   Company E would receive OneCode ACS data through the static profile
    in *PostalOne!* for the mailpieces they prepared.

-   No Cast of Characters message would be required.

Scenario 13:

Company A hires Company B and Company E to prepare their mailing and the
Mail Preparers use their own Mailer ID (Company B, Mailer ID 987654321
and Company E, Mailer ID 000987654321) on the mailpieces. Company A
wishes to send their OneCode ACS data to Company B whenever Company B is
their Mail Preparer and Company E whenever Company E is their Mail
Preparer.

-   Company A has set up a static Partial profile in *PostalOne!*
    authorizing Company B to receive the OneCode ACS data for Company A
    when they prepare the mail.

-   Company A has NOT set up a static Partial profile in *PostalOne!*
    authorizing Company E to receive the OneCode ACS data for Company A
    when they prepare the mail.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company E would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company B would receive OneCode ACS data through the static profile
    in *PostalOne!* for the mailpieces they prepared

-   Company E would NOT receive OneCode ACS data for the mailpieces they
    prepared. Company A would receive their OneCode ACS data for the
    mailing prepared by Company E.

-   No Cast of Characters message would be required.

Scenario 14:

Company A hires Company B and Company E to prepare their mailing and the
Mail Preparers use their own Mailer ID (Company B, Mailer ID 987654321
and Company E, Mailer ID 000987654321) on the mailpieces. Company A
wishes to send their OneCode ACS data to Company C.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the OneCode ACS data for Company A
    under all circumstances.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company E would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company C would receive OneCode ACS data through a combination of
    the By/For information and the static profile in *PostalOne!*.

-   No Cast of Characters message would be required.

Scenario 15:

Company A and Company D hire Company B to prepare their mailing and the
Company B uses their own Mailer ID, 987654321, on the mailpieces.
Company A wishes to send their OneCode ACS data to Company C for this
mailing only. Company D wishes to receive OneCode ACS data.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company C to receive the OneCode ACS data when a Cast of Characters
    file is submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A and Company D as
    the Mail Owners.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and directing One Code ACS data for those mailpieces to
    Company C.

-   Company C would receive OneCode ACS data through the Cast of
    Characters file. .

-   Company D would receive OneCode ACS data through the By/For in the
    electronic documentation.

    []{#__RefHeading___Toc216230348 .anchor}**Confirm Scenarios**

Scenario 16:

Company A prepares their own mailings using their Mailer ID, 123456789.
Company A wants to receive OneCode Confirm data. Company A is a Confirm
subscriber and their Mailer ID, 123456789, is also their Subscriber ID.

-   Company A would submit electronic documentation to *PostalOne!*
    which will indicate that the Mailer ID on the mailpiece is that of
    the Mail Owner.

-   Company A would receive OneCode Confirm data through the Mailer ID
    on the mailpiece.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 17:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company B wants to receive OneCode Confirm data. Company B is a Confirm
subscriber.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company B to receive the OneCode Confirm data when a Cast of
    Characters file is submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and Company B's Confirm Subscriber ID to direct One Code
    Confirm data for those mailpieces to Company B.

-   Company B would receive OneCode Confirm data through the Cast of
    Characters.

Scenario 18:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A and Company B want to receive OneCode Confirm data. Company A
and Company B are Confirm subscribers.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company B to receive the OneCode Confirm data when a Cast of
    Characters file is submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and Company A's Confirm Subscriber ID to direct One Code
    Confirm data for those mailpieces to Company A.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and Company B's Confirm Subscriber ID to direct One Code
    Confirm data for those mailpieces to Company B.

-   Company A would receive OneCode Confirm data through the Cast of
    Characters.

-   Company B would receive OneCode Confirm data through the Cast of
    Characters.

Scenario 19:

Company A hires Company B to prepare their mailing and Company B uses
their own Mailer ID, 987654321, on the mailpieces. Company A wants to
receive OneCode Confirm data. Company B does NOT want to receive OneCode
Confirm data. Company A and Company B are Confirm subscribers. Company
B's their Mailer ID, 987654321, is also their Subscriber ID.

-   Company B has set up a dynamic profile in *PostalOne!* authorizing
    Company A to receive the OneCode Confirm data when a Cast of
    Characters file is submitted.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company A or B would submit a Cast of Characters Create Request
    message to *PostalOne!* identifying the mailpieces included in the
    mailing and Company A's Confirm Subscriber ID to direct One Code
    Confirm data for those mailpieces to Company A.

-   Company B would submit a Cast of Characters Create Request message
    to *PostalOne!* identifying the mailpieces included in the mailing
    and Company B's Confirm Subscriber ID to stop One Code Confirm data
    for those mailpieces going to Company B.

-   Company B would NOT receive OneCode Confirm data.

-   Company A would receive OneCode Confirm data through the Cast of
    Characters.

Scenario 20:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wants Company C to receive OneCode Confirm data. Company C is
a Confirm subscriber.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the OneCode Confirm data for
    Company A including Company C's Confirm Subscriber ID.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company C would receive OneCode Confirm data through the static
    profile.

-   No Cast of Characters message would be required.

Scenario 21:

Company A hires Company B to prepare their mailing and requests Company
B to use company C's (Mail Owner) Mailer ID 111111111 on the mailpieces.
Company A wants Company C to receive OneCode Confirm data. Company C is
a Confirm subscriber and their Mailer ID, 111111111, is also their
Subscriber ID.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company C would receive OneCode Confirm data through the Mailer ID
    on the mailpiece.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 22:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wants Company C to receive OneCode Confirm data. Company A is
a Confirm subscriber and their Mailer ID, 123456789, is also their
Subscriber ID.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the OneCode Confirm data for
    Company A.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company C would receive OneCode Confirm data through the Mailer ID
    on the mailpieces.

-   No Cast of Characters message would be required.

Scenario 23:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company B uses a OneCode Confirm Service Type Code on the mailpieces.
Company A is not a Confirm subscriber.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company A will not receive the OneCode Confirm data.

    []{#__RefHeading___Toc216230349 .anchor}**Start-the-Clock
    Scenarios**

Scenario 24:

Company A hires Company B to prepare their mailing and Company B uses
their own Mailer ID, 987654321, on the mailpieces. Company A and Company
B both want to receive Start-the-Clock data.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company A as the Mail
    Owner.

-   Company B would receive Start-the-Clock data through the Mailer ID
    on the mailpiece.

-   Company A would receive Start-the-Clock data as the submitter of the
    electronic documentation.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 25:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A and Company B both want to receive Start-the-Clock data.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company A would receive Start-the-Clock data through the Mailer ID
    on the mailpiece.

-   Company B would receive Start-the-Clock data as the submitter of the
    electronic documentation.

-   No Static or Dynamic profile would be required.

-   No Cast of Characters message would be required.

Scenario 26:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.
Company A wants Company C to receive Start-the-Clock data. Company B
wants to receive Start-the-Clock data.

-   Company A has set up a static Complete profile in *PostalOne!*
    authorizing Company C to receive the Start-the-Clock data for
    Company A.

-   Company B would submit electronic documentation to *PostalOne!*
    indicating that the Mailer ID on the mailpiece is that of the Mail
    Owner.

-   Company C would receive Start-the-Clock data through the static
    profile.

-   Company B would receive Start-the-Clock data as the submitter of the
    electronic documentation.

-   No Cast of Characters message would be required.

    []{#__RefHeading___Toc216230350 .anchor}**Multiple Services**

Scenario 27:

Company A hires Company B to prepare their mailing and requests Company
B to use company A's (Mail Owner) Mailer ID 123456789 on the mailpieces.

Company A wants to receive OneCode ACS information. Company A wants
OneCode Confirm information to go to Company C only for this mailing.
Company C is a Confirm subscriber. Company A always wants
Start-the-Clock data to go to a Company C. Company B wants to receive
Start-the-Clock data.

-   Company A has set up a static complete profile in *PostalOne!*
    authorizing Company C to receive the Start-the-Clock data for
    Company A.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company C to receive the Confirm data for Company A.

-   Company A would submit a Cast of Characters Create Request message
    to *PostalOne!* identifying the mailpieces included in the mailing
    and Company C's Confirm Subscriber ID to direct One Code Confirm
    data for those mailpieces to Company C.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company B as the Mail
    Preparer and indicate the Mailer ID on the mailpiece is that of the
    Mail Owner.

-   Company A would receive OneCode ACS data through the Mailer ID on
    the mailpieces.

-   Company C would receive Start-the-Clock data through the static
    profile.

-   Company C would receive OneCode Confirm data through the dynamic
    profile and Cast of Characters message.

-   Company B would receive Start-the-Clock data as the submitter of the
    electronic documentation.

Scenario 28:

Company A hires Company B to prepare their mailing and requests Company
B to use their own Mailer ID 987654321 on the mailpieces.

Company A wants to receive OneCode Confirm information. Company A wants
OneCode ACS information to go to Company F for this mailing only.
Company A always wants OneCode Confirm data to go to Company C who has a
Confirm subscription. Company A and B want to receive Start-the-Clock
data. Company E wishes to receive appointment close-out information.

-   Company A has set up a static complete profile in *PostalOne!*
    authorizing Company C to receive OneCode Confirm data for Company A.

-   Company A has set up a dynamic profile in *PostalOne!* authorizing
    Company F to receive the OneCode ACS data for Company A.

-   Company A would submit a Cast of Characters Create Request message
    to *PostalOne!* identifying the mailpieces included in the mailing
    and Company F's Mailer ID to direct OneCode ACS data for those
    mailpieces to Company F.

-   Company B would submit electronic documentation to *PostalOne!*
    including By/For information to identify Company B as the Mail
    Preparer and indicate Company A as the Mail Owner.

-   Company A would receive Start-the-Clock data as the Mail Owner.

-   Company F would receive OneCode ACS data through the dynamic profile
    and Cast of Characters message.

-   Company C would receive OneCode Confirm data through the static
    profile.

-   Company B would receive Start-the-Clock data as the submitter of the
    electronic documentation.

-   Company E would receive appointment close-out information from FAST
    as the creator of the appointments.

If there is a need to change data in the Cast of Characters message
after it has been sent to *PostalOne!*, a Cast of Characters Update
Request can be submitted by the same company that submitted the original
request to update data in that message. Cast of Characters requests can
also be cancelled by the company that submitted the original request by
sending a Cast of Characters Cancellation Request message.

For more information on how to use the Cast of Characters messages,
refer to the Mail.XML v6.0 specification which can be found at
[www.idealliance.org](http://www.idealliance.org/).

# Appendix C: Data Distribution Scenario Chart {#appendix-c-data-distribution-scenario-chart .unnumbered}

  ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  Scenario   Notes             MID                Data                                    Documentation                                                              Data               
  Number                       Used               Requested                               Used                                                                       Sent to            
  ---------- ----------------- ------- ---------- ----------- --------- ----------------- --------------- ----------- ----------- ----------- --------- ------------ ------- ---------- -------
                               Owner   Preparer   ACS         Confirm   Start-the-Clock   By/For          Static      Static      Static      Dynamic   Cast of      Owner   Preparer   Third
                                       or Agent                                                           Profile:\   Profile:\   Profile:\   Profile   Characters                      Party
                                                                                                          Delegated   Complete    Partial                                               

  1          No Preparer Used  X                  X                                                                                                                  X                   

  2           One Owner, One   X                  X                                                                                                                  X                   
             Preparer                                                                                                                                                                   

  3           One Owner, One           X          X                                       X                                                                          X                   
             Preparer                                                                                                                                                                   

  4           One Owner, One           X          X                                                                               X                                          X           
             Preparer                                                                                                                                                                   

  5          Third Party       X                  X                                                                   X                                                                 X

  6           Third Party              X          X                                       X                           X                                                                 X

  7           Cast of          X                  X                                                                                           X         X                    X           
             Characters                                                                                                                                                                 

  8          Missing Profile,  X                  X                                                                                                     X            X                   
             Owner wants data                                                                                                                                                           
             to go to 3rd                                                                                                                                                               
             Party                                                                                                                                                                      

  9          Delegated Control X                  X                                                       X                                                                  X           

  10         Multiple          X                  X                                       X                                                                          X                   
             Preparers, One                                                                                                                                                             
             Owner                                                                                                                                                                      

  11         Multiple                  X          X                                       X                                                                          X                   
             Preparers, One                                                                                                                                                             
             Owner                                                                                                                                                                      

  12         Multiple                  X          X                                                       X                                                                  X           
             Preparers, One                                                                                                                                                             
             Owner                                                                                                                                                                      

  13         Two preparers,            X          X                                                       One                                                        One     One         
             one static                                                                                                                                                                 
             profile                                                                                                                                                                    

  14         Multiple                  X          X                                       X               X                                                                             X
             Preparers, One                                                                                                                                                             
             Owner, Third                                                                                                                                                               
             Party Receipt                                                                                                                                                              

  15         Multiple Owners,          X          X                                       X                                                   X         X            X                  X
             One Preparer --                                                                                                                                                            
             Data from one                                                                                                                                                              
             mailing can go to                                                                                                                                                          
             multiple sources.                                                                                                                                                          
             Data for each                                                                                                                                                              
             owner only goes                                                                                                                                                            
             to one location                                                                                                                                                            

  16         No Preparer Used  X                              X                                                                                                      X                   

  17         Preparer is a     X                              X                                                                               X         X                    X           
             Confirm                                                                                                                                                                    
             subscriber                                                                                                                                                                 

  18         Owner and         X                              X                                                                               X         X            X       X           
             preparer both                                                                                                                                                              
             Confirm                                                                                                                                                                    
             subscribers                                                                                                                                                                

  19         Owner and                 X                      X                                                                               X         X            X                   
             preparer both                                                                                                                                                              
             Confirm                                                                                                                                                                    
             subscribers                                                                                                                                                                

  20         Third Party is a  X                              X                                                       X                                                                 X
             Confirm                                                                                                                                                                    
             subscriber                                                                                                                                                                 

  21         Third Party MID           X                      X                                                                                                                         X
             Used                                                                                                                                                                       

  22         Owner is a        X                              X                                                       X                                                                 X
             Confirm                                                                                                                                                                    
             subscriber                                                                                                                                                                 

  23         No Confirm        X                              X                           X                                                                                             
             Subscriber ID                                                                                                                                                              

  24         One owner, one            X                                X                 X                                                                          X       X           
             preparer                                                                                                                                                                   

  25          One owner, one   X                                        X                 X                                                                          X       X           
             preparer                                                                                                                                                                   

  26         Owner delegates   X                                        X                 X               X                                                                  X          X
             start-the-clock                                                                                                                                                            
  ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

# Appendix D: Future Capabilities and Development Resources Mapping {#appendix-d-future-capabilities-and-development-resources-mapping .unnumbered}

+------------------------------+---------------------------------------+
| **[A Guide to Intelligent    | **[References]{.mark}**               |
| Mail for Letters and         |                                       |
| Flats]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| **[1. Purpose]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| Implementation of New        | <http://pe.                           |
| Standards for Intelligent    | usps.com/FederalRegisterNotices.asp>. |
| Mail Barcodes                |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* Getting Started | <http                                 |
| Guide                        | ://www.usps.com/postalone/guides.htm> |
+------------------------------+---------------------------------------+
| Additional resources about   | <http                                 |
| the various electronic       | ://www.usps.com/postalone/guides.htm> |
| documentation                |                                       |
|                              |                                       |
| "Guide and Tools" section of |                                       |
| the *PostalOne!* website     |                                       |
+------------------------------+---------------------------------------+
| **[2. Intelligent Mail       |                                       |
| Requirements]{.mark}**       |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| The Intelligent Mail Barcode | <http://ribbs.usps.gov/onecodesolu    |
| Technical Resource Guide     | tion/USPSIMB_Tech_Resource_Guide.pdf> |
+------------------------------+---------------------------------------+
| Intelligent Mail Barcode     | <http://ribbs.usps.gov/o              |
| Specifications               | necodesolution/SPUSPS-B-3200E001.pdf> |
+------------------------------+---------------------------------------+
| List of Intelligent Mail     | <ht                                   |
| Barcode Resources            | tp://ribbs.usps.gov/onecodesolution/> |
+------------------------------+---------------------------------------+
| **[Intelligent Mail Tray     |                                       |
| barcode]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Specifications for the       | <http:                                |
| 10/24-digit tray label       | //ribbs.usps.gov/files/intelligent_ma |
| specifications               | il_tray_label/mailer_web_content.cfm> |
+------------------------------+---------------------------------------+
| Specifications for the       | <http:                                |
| 24-digit tray label          | //ribbs.usps.gov/files/intelligent_ma |
| specifications               | il_tray_label/mailer_web_content.cfm> |
+------------------------------+---------------------------------------+
| **[Content Identification    |                                       |
| Number (CIN)]{.mark}**       |                                       |
+------------------------------+---------------------------------------+
| Information on CIN, DMM      | <ht                                   |
| 708.6.0                      | tp://pe.usps.com/text/dmm300/708.htm> |
+------------------------------+---------------------------------------+
| **[Intelligent Mail          |                                       |
| Container Placards with      |                                       |
| unique barcodes]{.mark}**    |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Intelligent Mail Container   | <http://ribbs                         |
| Barcode specifications       | .usps.gov/files/intelligent_mail_cont |
|                              | ainer_barcode/imcontainerbarcode.htm> |
+------------------------------+---------------------------------------+
| Information for the          | <ht                                   |
| preparation of Pallet DMM    | tp://pe.usps.com/text/dmm300/705.htm> |
| 705.8.0                      |                                       |
+------------------------------+---------------------------------------+
| **[Optional placard format   |                                       |
| with Intelligent Mail        |                                       |
| Container Barcode            |                                       |
| specifications and           |                                       |
| self-adhesive]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Optional placard format with | <http://ribbs                         |
| Intelligent Mail Container   | .usps.gov/files/intelligent_mail_cont |
|                              | ainer_barcode/imcontainerbarcode.htm> |
| Barcode specifications       |                                       |
+------------------------------+---------------------------------------+
| **[2.1 Start-the-Clock       |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[2.2 Address Correction    |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[2.2.1]{.mark} Future      |                                       |
| Release: Address Correction  |                                       |
| Information**                |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[2.3 Mailer ID             |                                       |
| (MID)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Contact your local Business  | <http://www.                          |
| Mail Entry Unit to obtain    | usps.com/ncsc/locators/find-bme.html> |
| the                          |                                       |
|                              |                                       |
| Mailer ID at USPS Locators & |                                       |
| Lookups for "Business Mail   |                                       |
| Entry"                       |                                       |
+------------------------------+---------------------------------------+
| Mailer ID Application        | <http://ribbs.usp                     |
| Process, Mailer ID           | s.gov/onecodesolution/IMD/imdmid.cfm> |
| Application (doc) &          |                                       |
|                              |                                       |
| (PDF) and Additional         |                                       |
| Accounts Information         |                                       |
+------------------------------+---------------------------------------+
| Mailer ID in the             | <ht                                   |
| "Intelligent Mail Barcode    | tp://ribbs.usps.gov/onecodesolution/> |
| Technical                    |                                       |
|                              |                                       |
| Resource Guide" Section      |                                       |
| 3.3.3                        |                                       |
+------------------------------+---------------------------------------+
| **[2.4 Unique Intelligent    |                                       |
| Mail Barcode]{.mark}**       |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| The Intelligent Mail Barcode | <http://ribbs.usps.gov/onecodesolu    |
| Technical Resource Guide     | tion/USPSIMB_Tech_Resource_Guide.pdf> |
+------------------------------+---------------------------------------+
| Intelligent Mail Barcode     | <http://ribbs.usps.gov/o              |
| Specifications               | necodesolution/SPUSPS-B-3200E001.pdf> |
+------------------------------+---------------------------------------+
| **[2.5 Service Type          |                                       |
| Identifier]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Service Type ID in the       | <ht                                   |
| "Intelligent Mail Barcode    | tp://ribbs.usps.gov/onecodesolution/> |
| Technical                    |                                       |
|                              |                                       |
| Resource Guide" Section      |                                       |
| 3.3.2                        |                                       |
+------------------------------+---------------------------------------+
| [**Confirm Service**]{.mark} |                                       |
+------------------------------+---------------------------------------+
| Those interested in the      | <http://w                             |
| OneCode Confirm Service for  | ww.usps.com/cpim/ftp/pubs/pub197.pdf> |
| full service                 |                                       |
|                              |                                       |
| or basic mailpiece must      |                                       |
| still purchase a Confirm     |                                       |
| service                      |                                       |
|                              |                                       |
| subscription and indicate    |                                       |
| the request for the Confirm  |                                       |
| service in                   |                                       |
|                              |                                       |
| the Service Type ID on the   |                                       |
| mailpiece.                   |                                       |
|                              |                                       |
| Learn about the Intelligent  |                                       |
| Mail^®^ barcode format for   |                                       |
| OneCode Confirm              |                                       |
|                              |                                       |
| by reviewing the Confirm     |                                       |
| Service Featuring OneCode    |                                       |
| Confirm User                 |                                       |
|                              |                                       |
| Guide (Pub. 197).            |                                       |
|                              |                                       |
| For more information on the  |                                       |
| Confirm^®^ service, please   |                                       |
| call the Confirm Customer    |                                       |
| Help Desk at 800-238-3150,   |                                       |
| option 1.                    |                                       |
+------------------------------+---------------------------------------+
| [**OneCode ACS**]{.mark}     |                                       |
+------------------------------+---------------------------------------+
| Address Correction           | <http://ribbs.                        |
| Information will be          | usps.gov/onecodesolution/acsdocs.cfm> |
| available for purchase for   |                                       |
| basic mailpiece through the  | **Documents and Forms:**              |
| OneCode ACS system. Those    |                                       |
|                              | [**3573.pdf**](http:/                 |
| interested in receiving      | /www.usps.com/forms/_pdf/ps3573.pdf)- |
| address correction data on   | OneCode ACS program application form  |
| basic mailpiece              |                                       |
|                              | [**1357-W.pdf**](http://ribbs.        |
| should obtain a OneCode ACS  | usps.gov/onecodesolution/1357-W.pdf)- |
| subscription and indicate    | Web Access Request Form               |
| the                          |                                       |
|                              | [**OneCode                            |
| request for that service in  | ACS**](http://ribbs                   |
| the Service Type ID.         | .usps.gov/onecodesolution/Pub8B.pdf)- |
|                              | DRAFT Publication 8B                  |
| Learn how the process works, |                                       |
| the features available, and  |                                       |
| mailer requirements to       |                                       |
| receive electronic address   |                                       |
| corrections using the        |                                       |
|                              |                                       |
| Intelligent Mail^®^ barcode. |                                       |
| Downloadable OneCode ACS     |                                       |
| application                  |                                       |
|                              |                                       |
| and fulfillment access       |                                       |
| forms.                       |                                       |
|                              |                                       |
| For more information on the  |                                       |
| OneCode ACS, please contact  |                                       |
| the ACS Department via email |                                       |
| at acs@usps.gov or by phone  |                                       |
| at 877-640-0724.             |                                       |
+------------------------------+---------------------------------------+
| **[Service Type ID Reference |                                       |
| Matrix]{.mark}**             |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <htt                                  |
| for Letters and Flats        | p://ribbs.usps.gov/fullserviceguides> |
| Appendix A,                  |                                       |
|                              |                                       |
| to identify the correct      |                                       |
| Service Type ID reference    |                                       |
+------------------------------+---------------------------------------+
| **[2.5.1 Use of Ancillary    |                                       |
| Service Endorsements and     |                                       |
| Service Type IDs to Receive  |                                       |
| Address                      |                                       |
| Corrections]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| For more information         | <http://pe.us                         |
| regarding ancillary service  | ps.com/text/dmm300/507.htm#wp1112929> |
|                              |                                       |
| Endorsements: see DMM        | <http://pe.usps                       |
| 507.1.0 Treatment of Mail    | .com/text/qsg300/Q507d.htm#wp1022881> |
| and                          |                                       |
|                              |                                       |
| Quick Service Guide 507d,    |                                       |
| Ancillary Service            |                                       |
| Endorsements                 |                                       |
+------------------------------+---------------------------------------+
| **[2.5.2 Forms of Address    |                                       |
| Corrections and Options for  |                                       |
| Handling                     |                                       |
| Undeliverable-as-Addressed   |                                       |
| Mail with Intelligent Mail   |                                       |
| Barcode]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| > For more information       | <http:/                               |
| > regarding Address          | /pe.usps.com/text/dmm300/507.htm#4_0> |
| > Corrections Service,       |                                       |
| >                            | <http://ribbs.usps.gov/acs.html>      |
| > DMM 507.4.0 Address        |                                       |
| > Corrections Service:       |                                       |
|                              |                                       |
| -   Manual Address           |                                       |
|     Corrections              |                                       |
|                              |                                       |
| -   Traditional ACS          |                                       |
|                              |                                       |
| -   OneCode ACS              |                                       |
+------------------------------+---------------------------------------+
| **[2.5.2.1]{.mark}           |                                       |
| Indicating "None" as the     |                                       |
| Form of Address Correction** |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| For more information         | <http://pe.us                         |
| regarding "No Endorsement"   | ps.com/text/dmm300/507.htm#wp1112929> |
| as the form of Address       |                                       |
| Correction, DMM 507.1.5.1,   | <http://pe.usps                       |
| 1.5.2, 1.5.3 & 1.5.3.K and   | .com/text/qsg300/Q507d.htm#wp1022881> |
|                              |                                       |
| Quick Service Guide 507d,    |                                       |
| Ancillary Service            |                                       |
| Endorsements                 |                                       |
+------------------------------+---------------------------------------+
| **[2.5.2.2]{.mark}           |                                       |
| Indicating "Manual Address   |                                       |
| Corrections" as the Form of  |                                       |
| Address Correction**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| For more information         | <http://pe.us                         |
| regarding "Manual Address    | ps.com/text/dmm300/507.htm#wp1112929> |
| Correction" as               |                                       |
|                              | <http://pe.usps                       |
| the form of Address          | .com/text/qsg300/Q507d.htm#wp1022881> |
| Correction, DMM 507.1.5.1,   |                                       |
| 1.5.2, 1.5.3 & 1.5.3.K and   |                                       |
| Quick Service Guide 507d,    |                                       |
| Ancillary Service            |                                       |
| Endorsements                 |                                       |
+------------------------------+---------------------------------------+
| **[2.5.2.3]{.mark}           |                                       |
| Indicating "Traditional ACS" |                                       |
| as the Form of Address       |                                       |
| Correction**                 |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| For more information         | <http://pe.us                         |
| regarding "Traditional       | ps.com/text/dmm300/507.htm#wp1112929> |
| Address Correction"          |                                       |
|                              | <http://pe.usps                       |
| as the form of Address       | .com/text/qsg300/Q507d.htm#wp1022881> |
| Correction, DMM 507.1.5.1,   |                                       |
| 1.5.2, 1.5.3                 |                                       |
|                              |                                       |
| & 1.5.3.K and Quick Service  |                                       |
| Guide 507d, Ancillary        |                                       |
| Service Endorsements         |                                       |
+------------------------------+---------------------------------------+
| **[2.5.2.4]{.mark}           |                                       |
| Indicating "OneCode ACS" as  |                                       |
| the Form of Address          |                                       |
| Correction**                 |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| For more information         | <http://ribbs.                        |
| regarding "Manual Address    | usps.gov/onecodesolution/acsdocs.cfm> |
| Correction" as               |                                       |
|                              | <http://pe.us                         |
| the form of Address          | ps.com/text/dmm300/507.htm#wp1112929> |
| Correction, DMM 507.1.5.1,   |                                       |
| 1.5.2, 1.5.3 & 1.5.3.K and   | <http://pe.usps                       |
| Quick Service Guide 507d,    | .com/text/qsg300/Q507d.htm#wp1022881> |
| Ancillary Service            |                                       |
| Endorsements                 |                                       |
+------------------------------+---------------------------------------+
| **[2.5.3 Ancillary Service   |                                       |
| Endorsements with Basic or   |                                       |
| Full-Service                 |                                       |
| Mailings]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[2.5.4 Precedence of       |                                       |
| Ancillary Service            |                                       |
| Endorsements and Service     |                                       |
| Type ID Values]{.mark}**     |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[2.5.5 Electronic Service  |                                       |
| Requested]{.mark}**          |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| For more information         | <http://pe.us                         |
| regarding Electronic Service | ps.com/text/dmm300/507.htm#wp1112929> |
| Requested,                   |                                       |
|                              |                                       |
| DMM 507.1.5 F & 507.4.2.6    |                                       |
+------------------------------+---------------------------------------+
| To determine if using        | <htt                                  |
| Electronic Service requested | p://ribbs.usps.gov/fullserviceguides> |
| is appropriate and will meet |                                       |
| the mailer's desired         |                                       |
| handling of UAA mail:        |                                       |
|                              |                                       |
| A Guide to Intelligent Mail  |                                       |
| for Letters and Flats        |                                       |
| Appendix A, to               |                                       |
|                              |                                       |
| identify the correct Service |                                       |
| Type ID reference            |                                       |
+------------------------------+---------------------------------------+
| **[2.5.6 Quick Service Guide |                                       |
| Listing of Service Type      |                                       |
| Identifiers]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <htt                                  |
| for Letters and Flats:       | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| Figure 2: Guide to Service   |                                       |
| Type Identifiers             |                                       |
|                              |                                       |
| Appendix A, Service Type     |                                       |
| Identifier Matrix            |                                       |
+------------------------------+---------------------------------------+
| **[2.5.7 First-Class Mail    |                                       |
| Service Type                 |                                       |
| Identifiers]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 2, Guide to Service   |                                       |
| Type Identifiers             |                                       |
|                              |                                       |
| Appendix A, Service Type     |                                       |
| Identifier Matrix            |                                       |
+------------------------------+---------------------------------------+
| **[2.5.8 Standard Mail       |                                       |
| Service Type                 |                                       |
| Identifiers]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 2, Guide to Service   |                                       |
| Type Identifiers             |                                       |
|                              |                                       |
| Appendix A, Service Type     |                                       |
| Identifier Matrix            |                                       |
+------------------------------+---------------------------------------+
| **[2.5.9 Periodicals Service |                                       |
| Type Identifiers]{.mark}**   |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 2, Guide to Service   |                                       |
| Type Identifiers             |                                       |
|                              |                                       |
| Appendix A, Service Type     |                                       |
| Identifier Matrix            |                                       |
+------------------------------+---------------------------------------+
| **[2.5.10 Bound Printed      |                                       |
| Matter Service Type          |                                       |
| Identifiers]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 2, Guide to Service   |                                       |
| Type Identifiers             |                                       |
|                              |                                       |
| Appendix A, Service Type     |                                       |
| Identifier Matrix            |                                       |
+------------------------------+---------------------------------------+
| **[3 Electronic Mailing      |                                       |
| Documentation and Postage    |                                       |
| Statements]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Detailed instructions on how | <htt                                  |
| to obtain access to the      | p://www.usps.com/postalone/howto.htm> |
| *PostalOne!*                 |                                       |
|                              |                                       |
| system                       |                                       |
+------------------------------+---------------------------------------+
| For additional information   | [http://www.usp                       |
| on how to sign-up and begin  | s.com/postalone/\_pdf/*PostalOne!*Sta |
| using the                    | rtGuide.pdf](http://www.usps.com/post |
|                              | alone/_pdf/PostalOne!StartGuide.pdf). |
| *PostalOne!* system today    |                                       |
| please see the *PostalOne!*  |                                       |
|                              |                                       |
| Getting Started Guide        |                                       |
+------------------------------+---------------------------------------+
| **With the Full-Service      |                                       |
| option, you will need to     |                                       |
| submit postage statement and |                                       |
| other mailing documentation  |                                       |
| electronically using one of  |                                       |
| three options**              |                                       |
+------------------------------+---------------------------------------+
| A\) Mail.dat® is an          | <http://www.maildat.org/>.            |
| industry-defined database    |                                       |
| structure consisting of      |                                       |
|                              |                                       |
| files linked by key fields.  |                                       |
| (Use Mail.dat 09.1           |                                       |
| Specification to develop     |                                       |
|                              |                                       |
| your software for Full       |                                       |
| Service)                     |                                       |
+------------------------------+---------------------------------------+
| A*) PostalOne!* System       | <htt                                  |
| Mail.dat Technical Guide for | p://ribbs.usps.gov/fullserviceguides> |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| B\) Mail.XML (formerly       | [[www.mailxml.org]{                   |
| Wizard Web Services (WWS)),  | .underline}](http://www.mailxml.org/) |
| For more                     |                                       |
|                              |                                       |
| information about using      |                                       |
| Mail.XML for communicating   |                                       |
| with the                     |                                       |
|                              |                                       |
| *PostalOne!* system for      |                                       |
| full-service (use Mail.XML   |                                       |
| 6.0 to develop               |                                       |
|                              |                                       |
| your software for Full       |                                       |
| Service)                     |                                       |
+------------------------------+---------------------------------------+
| B\) Mail.XML refer to the    | <htt                                  |
| *PostalOne!* system product  | p://ribbs.usps.gov/fullserviceguides> |
| guides and                   |                                       |
|                              |                                       |
| tools and the *PostalOne!*   |                                       |
| System Mail.XML Technical    |                                       |
| Guide for                    |                                       |
|                              |                                       |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| C\) The *PostalOne!*         | <htt                                  |
| system provides the Postal   | p://www.usps.com/postalone/howto.htm> |
| Wizard (PW)                  |                                       |
|                              | [http://www.usp                       |
| tool that provides a secure  | s.com/postalone/\_pdf/*PostalOne!*Sta |
| way to submit postage        | rtGuide.pdf](http://www.usps.com/post |
| statements                   | alone/_pdf/PostalOne!StartGuide.pdf). |
|                              |                                       |
| online. Those interested in  | <http://www.                          |
| using the PW should contact  | usps.com/ncsc/locators/find-bme.html> |
| their                        |                                       |
|                              |                                       |
| BMEU directly to obtain      |                                       |
| access:                      |                                       |
+------------------------------+---------------------------------------+
| C\) The Postal Wizard (PW)   | For First-Class Mail:                 |
| tool may be used when no     | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/234.htm> |
| electronic documentation is  |                                       |
| necessary for compliance     | For Standard Mail:                    |
| with                         | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/244.htm> |
| full-service requirements.   |                                       |
| (Qualification reports for   |                                       |
| mailings                     |                                       |
|                              |                                       |
| of less than 10,000 pieces   |                                       |
| are not required when        |                                       |
| postage is                   |                                       |
|                              |                                       |
| affixed to each piece at the |                                       |
| correct price, or when each  |                                       |
| piece is                     |                                       |
|                              |                                       |
| of identical weight and the  |                                       |
| mailpieces are separated by  |                                       |
| price                        |                                       |
+------------------------------+---------------------------------------+
| **[3.1 Mixed                 |                                       |
| Mailings]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Section 3.10.2 Piece         |                                       |
| Electronic Documentation for |                                       |
|                              |                                       |
| Non-Sequential Intelligent   |                                       |
| Mail Barcodes                |                                       |
+------------------------------+---------------------------------------+
| **[3.2 Future Release:       |                                       |
| Combined Mailings of         |                                       |
| Standard Mail &              |                                       |
| Periodicals]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 4. Mail.dat for       |                                       |
| Combined Mailings &          |                                       |
|                              |                                       |
| Figure 5, Mail.XML for       |                                       |
| Combined Mailings            |                                       |
+------------------------------+---------------------------------------+
| **[3.3                       |                                       |
| Copalletization]{.mark}**    |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Section 3.10, 3.11 & 3.12    |                                       |
+------------------------------+---------------------------------------+
| **[3.3.1 Periodicals         |                                       |
| Scenario]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 6, Mail.dat for       |                                       |
| Periodicals Copalletization  |                                       |
| &                            |                                       |
|                              |                                       |
| Figure 7. Mail.XML for       |                                       |
| Periodicals Copalletization  |                                       |
+------------------------------+---------------------------------------+
| DMM 707.27.1 states that     | <http://pe.us                         |
| this agreement shall         | ps.com/text/dmm300/707.htm#wp1292574> |
| include: the mailer\'s       |                                       |
|                              |                                       |
| name and address, the        |                                       |
| mailing office, procedures   |                                       |
| and quality                  |                                       |
|                              |                                       |
| control measures for the     |                                       |
| copalletized mailing, the    |                                       |
| expected date                |                                       |
|                              |                                       |
| of the first mailing, and a  |                                       |
| sample of the standardized   |                                       |
|                              |                                       |
| documentation                |                                       |
+------------------------------+---------------------------------------+
| **[3.3.2 Standard Mail       |                                       |
| Flat-Size Bundles            |                                       |
| Scenario]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 8, Mail.dat for       |                                       |
| Standard Mail Flat Bundle    |                                       |
| Copalletization & Figure 9.  |                                       |
| Mail.XML for Standard Mail   |                                       |
| Flat Bundle Copalletization  |                                       |
+------------------------------+---------------------------------------+
| To copalletize different     | <http://pe.us                         |
| Standard Mail flat-size      | ps.com/text/dmm300/705.htm#wp1380958> |
| mailings, the mailer         |                                       |
|                              |                                       |
| must consolidate on pallets  |                                       |
| all independently sorted     |                                       |
| bundles from                 |                                       |
|                              |                                       |
| each mailing to achieve the  |                                       |
| finest presort level for the |                                       |
| mailing as                   |                                       |
|                              |                                       |
| required DMM 705.8.7.4       |                                       |
+------------------------------+---------------------------------------+
| **[3.3.3 First-Class Mail in |                                       |
| Trays Scenario]{.mark}**     |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 10, Mail.dat for      |                                       |
| First-Class Mail Tray        |                                       |
| Copalletization &            |                                       |
|                              |                                       |
| Figure 11. Mail.XML for      |                                       |
| First-Class Mail Tray        |                                       |
| Copalletization              |                                       |
+------------------------------+---------------------------------------+
| **[3.3.4 Standard Mail in    |                                       |
| Trays Scenario]{.mark}**     |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 12, Mail.dat for      |                                       |
| Standard Mail Tray           |                                       |
| Copalletization &            |                                       |
|                              |                                       |
| Figure 13. Mail.XML for      |                                       |
| Standard Mail Tray           |                                       |
| Copalletization              |                                       |
+------------------------------+---------------------------------------+
| **[3.4 Future Release:       |                                       |
| Manifest Mailings]{.mark}**  |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| For more information         | <ht                                   |
| regarding Manifest Mailing   | tp://pe.usps.com/text/dmm300/705.htm> |
|                              |                                       |
| System, see DMM 705.2.0      |                                       |
+------------------------------+---------------------------------------+
| **[3.5 Spoilage and          |                                       |
| Shortage]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| USPS will support the two    | <http://www.maildat.org/>             |
| following solutions for      |                                       |
| providing                    | [[www.mailxml.org]{                   |
|                              | .underline}](http://www.mailxml.org/) |
| Spoilage information in      |                                       |
| Mail.dat 09.1 and Mail.XML   | <htt                                  |
| 6.0                          | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.dat |                                       |
| Technical Guide for          |                                       |
| Full-Service                 |                                       |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide for          |                                       |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| **[3.5.1 Piece Level         |                                       |
| Spoilage and                 |                                       |
| Shortage]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| USPS will support the two    | <http://www.maildat.org/>             |
| following solutions for      |                                       |
| providing                    | [[www.mailxml.org]{                   |
|                              | .underline}](http://www.mailxml.org/) |
| Spoilage information in      |                                       |
| Mail.dat 09.1 and Mail.XML   | <htt                                  |
| 6.0                          | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.dat |                                       |
| Technical Guide for          |                                       |
| Full-Service                 |                                       |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide for          |                                       |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| **[3.6 Multi-Line Optical    |                                       |
| Character Reader (MLOCR)     |                                       |
| Mailers]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.7 Continuous            |                                       |
| Mailers]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Continuous Mailers will have | <ht                                   |
| Customer Supplier Agreements | tp://ribbs.usps.gov/GuidetoCSAv1.doc> |
|                              |                                       |
| (CSA) with the Postal        |                                       |
| Service.                     |                                       |
+------------------------------+---------------------------------------+
| **[3.8 Customer Supplier     |                                       |
| Agreements (CSA)]{.mark}**   |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 14, Customer Supplier |                                       |
| Agreements File Layout       |                                       |
+------------------------------+---------------------------------------+
| Guide to Customer Supplier   | <ht                                   |
| Agreements (CSA)             | tp://ribbs.usps.gov/GuidetoCSAv1.doc> |
+------------------------------+---------------------------------------+
| **[3.8.1 Using the           |                                       |
| *PostalOne!* Transportation  |                                       |
| Management System]{.mark}**  |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| For more information         | <ht                                   |
| regarding air & surface      | tp://ribbs.usps.gov/GuidetoCSAv1.doc> |
| container separations refer  |                                       |
| to: Customer Supplier        |                                       |
| Agreements (CSA) with the    |                                       |
| Postal Service.              |                                       |
+------------------------------+---------------------------------------+
| For more information         | <http://www.                          |
| regarding *PostalOne!*       | usps.com/postalone/transportmgmt.htm> |
| Transportation               |                                       |
|                              |                                       |
| Management System            |                                       |
+------------------------------+---------------------------------------+
| **[3.8.2 Applying the        |                                       |
| Customer Supplier            |                                       |
| Agreement]{.mark}**          |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Guide to Customer Supplier   | <ht                                   |
| Agreements (CSA)             | tp://ribbs.usps.gov/GuidetoCSAv1.doc> |
+------------------------------+---------------------------------------+
| **[3.9]{.mark} Creating      |                                       |
| Appointments**               |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| For details on how to create | <http://www.usps.com/postalone/_p     |
| appointments using Web       | df/FASTWebServicesTechnicalGuide.pdf> |
| Services, refer to the:      | or                                    |
| *PostalOne! -* FAST Web      | <http://www.usps.co                   |
| Services Technical Guide and | m/postalone/autodropshipschedule.htm> |
| the                          |                                       |
|                              | [www.m                                |
| Mail.XML Specifications      | aildat.org](http://www.maildat.org/). |
| found at the IDEAlliance     |                                       |
| website                      |                                       |
+------------------------------+---------------------------------------+
| For details on how to create | <https://fast.usps.                   |
| appointments via the FAST    | com/userguide/CustomerUserGuide.pdf>. |
| online system, refer to the  |                                       |
| FAST Customer User guide:    |                                       |
+------------------------------+---------------------------------------+
| **[3.9.1 Joint]{.mark}       |                                       |
| Scheduling**                 |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.10 Mail.dat]{.mark}**   |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information for Mail.dat and | [http://www.mai                       |
| how you can use Mail.dat to  | ldat.org/](http://www.maildat.org/ ). |
| submit                       |                                       |
|                              |                                       |
| electronic information refer |                                       |
| to:                          |                                       |
+------------------------------+---------------------------------------+
| Currently, the *PostalOne!*  | <htt                                  |
| system supports Mail.dat     | p://ribbs.usps.gov/fullserviceguides> |
| versions 07-1,               |                                       |
|                              |                                       |
| 08-1, and Mail.dat version   |                                       |
| 08-2, For more information   |                                       |
| regarding                    |                                       |
|                              |                                       |
| *PostalOne!* System Mail.dat |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.1 Mail.dat 09.1      |                                       |
| *PostalOne!* System          |                                       |
| Implementation]{.mark}**     |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information for Mail.dat and | <http://www.maildat.org/>             |
| how you can use Mail.dat to  |                                       |
| submit                       |                                       |
|                              |                                       |
| electronic information refer |                                       |
| to:                          |                                       |
+------------------------------+---------------------------------------+
| The change requests for      | <http://                              |
| Mail.dat 09-1 can be         | pmstage.freecom.at/pmstage/index.php> |
| accessed at the              |                                       |
|                              |                                       |
| IDEAlliance change           |                                       |
| management Web site found at |                                       |
+------------------------------+---------------------------------------+
| **[3.10.2 Mail.dat Piece     |                                       |
| Electronic Documentation for |                                       |
| Non-Sequential Intelligent   |                                       |
| Mail Barcodes]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information on Documentation | For First-Class Mail:                 |
| Standards for Automation     | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/234.htm> |
| Mailing DMM 234 & 244        |                                       |
| (Qualification reports for   | For Standard Mail:                    |
| mailings of                  | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/244.htm> |
| less than 10,000 pieces are  |                                       |
| not required when postage is |                                       |
| affixed                      |                                       |
|                              |                                       |
| to each piece at the correct |                                       |
| price, or when each piece is |                                       |
| of                           |                                       |
|                              |                                       |
| identical weight and the     |                                       |
| mailpieces are separated by  |                                       |
| price)                       |                                       |
+------------------------------+---------------------------------------+
| For detailed specifications  | <http://www.maildat.org/> or          |
| on how to populate the PDR   | [http://www.ideallian                 |
| or                           | ce.org](http://www.idealliance.org/). |
|                              |                                       |
| MailPiece Create and         |                                       |
| MailPieceUpdate messages,    |                                       |
| refer to the                 |                                       |
|                              |                                       |
| Mail.dat Specification or    |                                       |
| Mail.XML Specification       |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.dat | <htt                                  |
| Technical Guide &            | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.3 Mail.dat Piece     |                                       |
| Electronic Documentation for |                                       |
| Sequential Intelligent Mail  |                                       |
| Barcodes]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| For detailed specifications  | <http://www.maildat.org/> or          |
| on how to populate the PDR   | [http://www.ideallian                 |
| or                           | ce.org](http://www.idealliance.org/). |
|                              |                                       |
| MailPieceCreate and          |                                       |
| MailPieceUpdate messages ,   |                                       |
| refer to the                 |                                       |
|                              |                                       |
| Mail.dat Specification or    |                                       |
| Mail.XML Specification       |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.dat | <htt                                  |
| Technical Guide &            | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.4 Mail.dat Handling  |                                       |
| Unit Information]{.mark}**   |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.10.4.1 Mail.dat         |                                       |
| Physical Handling            |                                       |
| Unit]{.mark}**               |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Complete information for     | <http://www.maildat.org/> or          |
| detailed specifications on   | [http://www.ideallia                  |
| how to populate              | nce.org](http://www.idealliance.org/) |
|                              |                                       |
| the .CSM file, refer to the  |                                       |
| Mail.dat Specification:      |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.dat | <htt                                  |
| Technical Guide &            | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.4.2 Mail.dat Logical |                                       |
| Handling Units (Trays        |                                       |
| only)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 15, Logical Handling  |                                       |
| Units &                      |                                       |
|                              |                                       |
| Figure 16, Association of    |                                       |
| Logical Handling Units to    |                                       |
|                              |                                       |
| Physical Handling Units      |                                       |
+------------------------------+---------------------------------------+
| Complete information for     | <http://www.maildat.org/> or          |
| detailed specifications on   | [http://www.ideallian                 |
| how to populate              | ce.org](http://www.idealliance.org/). |
|                              |                                       |
| the .CSM file, refer to the  |                                       |
| Mail.dat Specification:      |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.dat | <htt                                  |
| Technical Guide &            | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.5 Mail.dat Container |                                       |
| Information (Pallets or      |                                       |
| APC)]{.mark}**               |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.10.5.1 Mail.dat         |                                       |
| Physical                     |                                       |
| Containers]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Complete information for     | <http://www.maildat.org/> or          |
| detailed specifications on   | [http://www.ideallian                 |
| how to populate              | ce.org](http://www.idealliance.org/). |
|                              |                                       |
| the .CSM file, refer to the  |                                       |
| Mail.dat Specification:      |                                       |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.dat | <htt                                  |
| Technical Guide &            | p://ribbs.usps.gov/fullserviceguides> |
|                              |                                       |
| *PostalOne!* System Mail.XML |                                       |
| Technical Guide              |                                       |
+------------------------------+---------------------------------------+
| **[3.10.5.2 Mail.dat Logical |                                       |
| Containers (Pallets or       |                                       |
| APCs)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 17, Logical           |                                       |
| Containers &                 |                                       |
|                              |                                       |
| Figure 18, Association of    |                                       |
| Physical Containers to       |                                       |
|                              |                                       |
| Logical Containers           |                                       |
+------------------------------+---------------------------------------+
| **[3.10.5.3 Mail.dat         |                                       |
| Associating Handling Units   |                                       |
| to Containers]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| **A Guide to Intelligent     | <http                                 |
| Mail for Letters and Flats** | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Complete information for     | <http://www.maildat.org/> or          |
| detailed specifications on   | [http://www.ideallian                 |
| how to populate              | ce.org](http://www.idealliance.org/). |
|                              |                                       |
| the .CSM file, refer to the  |                                       |
| Mail.dat Specification:      |                                       |
+------------------------------+---------------------------------------+
| **[3.10.6 Postage            |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information for Mail.dat     | <htt                                  |
| lists all the postage        | p://ribbs.usps.gov/fullserviceguides> |
| statement generation         |                                       |
|                              |                                       |
| variables in table 3.1 Key   |                                       |
| Postage Statement Generation |                                       |
| Field can                    |                                       |
|                              |                                       |
| be found in the *PostalOne!* |                                       |
| System Mail.dat Technical    |                                       |
| Guide                        |                                       |
+------------------------------+---------------------------------------+
| **[3.10.7 Future Release:    |                                       |
| Mail.dat Owner/Mailing Agent |                                       |
| Updates]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.11 Mail.XML (Formerly   |                                       |
| Wizard Web                   |                                       |
| Services)]{.mark}**          |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information for Mail.XML and | [[www.mailxml.org]{                   |
| how you can use Mail.XML to  | .underline}](http://www.mailxml.org/) |
| submit                       |                                       |
|                              |                                       |
| electronic information refer |                                       |
| to:                          |                                       |
+------------------------------+---------------------------------------+
| Complete information about   | <htt                                  |
| using Mail.XML to            | p://ribbs.usps.gov/fullserviceguides> |
| communicate                  |                                       |
|                              |                                       |
| with the *PostalOne!*        |                                       |
| system*,* can be found in    |                                       |
| the *PostalOne!*             |                                       |
|                              |                                       |
| system product guides and    |                                       |
| tools and the *PostalOne!*   |                                       |
| System                       |                                       |
|                              |                                       |
| Mail.XML Technical Guide for |                                       |
| Full-Service:                |                                       |
+------------------------------+---------------------------------------+
| **[3.12 Future               |                                       |
| Release]{.mark} Electronic   |                                       |
| Documentation Using Mail.XML |                                       |
| (Formerly Wizard Web         |                                       |
| Services)**                  |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.1 Mail.XML Version   |                                       |
| 6.0 Changes -- *PostalOne!*  |                                       |
| System                       |                                       |
| Implementation]{.mark}**     |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.2 Mail.XML Piece     |                                       |
| Electronic Documentation for |                                       |
| Non-Sequential Intelligent   |                                       |
| Mail Barcodes]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Information on Documentation | For First-Class Mail:                 |
| Standards for Automation     | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/234.htm> |
| Mailing DMM 234 & 244        |                                       |
| (Qualification reports for   | For Standard Mail:                    |
| mailings of                  | <ht                                   |
|                              | tp://pe.usps.com/text/dmm300/244.htm> |
| less than 10,000 pieces are  |                                       |
| not required when postage is |                                       |
| affixed                      |                                       |
|                              |                                       |
| to each piece at the correct |                                       |
| price, or when each piece is |                                       |
| of                           |                                       |
|                              |                                       |
| identical weight and the     |                                       |
| mailpieces are separated by  |                                       |
| price)                       |                                       |
+------------------------------+---------------------------------------+
| Complete information about   | <htt                                  |
| using Mail.XML to            | p://ribbs.usps.gov/fullserviceguides> |
| communicate                  |                                       |
|                              |                                       |
| with the *PostalOne!*        |                                       |
| system*,* can be found in    |                                       |
| the *PostalOne!*             |                                       |
|                              |                                       |
| system product guides and    |                                       |
| tools and the *PostalOne!*   |                                       |
| System                       |                                       |
|                              |                                       |
| Mail.XML Technical Guide for |                                       |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| **[3.12.3 Mail.XML Piece     |                                       |
| Electronic Documentation for |                                       |
| Sequential Intelligent Mail  |                                       |
| Barcodes]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| Complete information about   | <htt                                  |
| using Mail.XML to            | p://ribbs.usps.gov/fullserviceguides> |
| communicate                  |                                       |
|                              |                                       |
| with the *PostalOne!*        |                                       |
| system*,* can be found in    |                                       |
| the *PostalOne!*             |                                       |
|                              |                                       |
| system product guides and    |                                       |
| tools and the *PostalOne!*   |                                       |
| System                       |                                       |
|                              |                                       |
| Mail.XML Technical Guide for |                                       |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| **[3.12.3.1 Mail.XML         |                                       |
| Handling Unit                |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.3.2 Mail.XML         |                                       |
| Physical Handling            |                                       |
| Units]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.3.3 Mail.XML Logical |                                       |
| Handling Units (Trays        |                                       |
| only)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 19, Logical Handling  |                                       |
| Units &                      |                                       |
|                              |                                       |
| Figure 20, Association of    |                                       |
| Physical Handling Units to   |                                       |
|                              |                                       |
| Logical Handling Units       |                                       |
+------------------------------+---------------------------------------+
| **[3.12.4 Mail.XML Container |                                       |
| Information (Pallets or      |                                       |
| APCs)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.4.1 Mail.XML         |                                       |
| Physical                     |                                       |
| Containers]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| *PostalOne!* System Mail.XML | <htt                                  |
| Technical Guide for          | p://ribbs.usps.gov/fullserviceguides> |
| Full-Service                 |                                       |
+------------------------------+---------------------------------------+
| **[3.12.4.2 Mail.XML Logical | []{.mark}                             |
| Containers (Pallets or       |                                       |
| APCs)]{.mark}**              |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 21, Logical           |                                       |
| Containers &                 |                                       |
|                              |                                       |
| Figure 22, Association of    |                                       |
| Physical Containers to       |                                       |
|                              |                                       |
| Logical Containers           |                                       |
+------------------------------+---------------------------------------+
| **[3.12.4.3 Mail.XML         |                                       |
| Associating Handling Units   |                                       |
| to Containers]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.5 Appointment        |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.12.6 Postage            |                                       |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.13 Postal Wizard        |                                       |
| (PW)]{.mark}**               |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| The *PostalOne!*             | <http                                 |
| system offers the Postal     | ://www.usps.com/postalone/guides.htm> |
| Wizard as a tool that        |                                       |
|                              |                                       |
| provides a secure way to     |                                       |
| submit postage statements    |                                       |
| online.                      |                                       |
|                              |                                       |
| Complete information on how  |                                       |
| to use the PW refer to the   |                                       |
| Getting                      |                                       |
|                              |                                       |
| Started Guide                |                                       |
+------------------------------+---------------------------------------+
| **[3.13.1 PW Piece           |                                       |
| Electronic Documentation for |                                       |
| Sequential Intelligent Mail  |                                       |
| Barcodes]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.13.2 PW Piece           |                                       |
| Electronic Documentation     |                                       |
| Using Mailing ID]{.mark}**   |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.13.3 PW Postage         | []{.mark}                             |
| Information]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.14 Mailer Owner and     |                                       |
| Mail Preparer Identification |                                       |
| in Electronic                |                                       |
| Documentation]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.14.1 Non-Sequential     |                                       |
| Piece Identifiers]{.mark}**  |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.14.2 Sequential Piece   |                                       |
| Identifiers]{.mark}**        |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.14.3 Order of           |                                       |
| Preference]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[3.14.4 Obtaining a Mailer |                                       |
| Owner CRID]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 23, CRID Request File |                                       |
| Layout &                     |                                       |
|                              |                                       |
| Figure 24, CRID Request      |                                       |
| Message                      |                                       |
+------------------------------+---------------------------------------+
| **[4. Mailer                 |                                       |
| Feedback]{.mark}**           |                                       |
|                              |                                       |
| **[4.1 Overview]{.mark}**    |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[4.2 Available             |                                       |
| Feedback]{.mark}**           |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| The data will be available   |                                       |
| using the following methods: |                                       |
|                              |                                       |
| -   FTP                      |                                       |
|                              |                                       |
| -   Browser based HTTPS      |                                       |
|     (Hyper Text Transport    |                                       |
|     Protocol-Secure)         |                                       |
|     Download (Compressed     |                                       |
|     Files)                   |                                       |
|                              |                                       |
| -   Browser based HTTPS      |                                       |
|     Reports                  |                                       |
|                              |                                       |
| -   Mail.XML Pull (Customer  |                                       |
|     Invokes USPS Web         |                                       |
|     Service)                 |                                       |
|                              |                                       |
| -   Mail.XML Push (USPS      |                                       |
|     Invokes Customer Web     |                                       |
|     Service)                 |                                       |
|                              |                                       |
| Figure 25, Data Exchange     |                                       |
| Methods                      |                                       |
+------------------------------+---------------------------------------+
| **[4.2.1 Start-the-Clock for |                                       |
| BMEU Mail]{.mark}**          |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 26, Start-the-Clock   |                                       |
| for BMEU Entered Mail Report |                                       |
+------------------------------+---------------------------------------+
| **[4.2.2 Start-the-Clock for |                                       |
| Drop Ship and Origin Entered |                                       |
| Mail Transported by          |                                       |
| Mailer]{.mark}**             |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 27, Start-the-Clock   |                                       |
| for Drop Ship Mailings       |                                       |
| Report                       |                                       |
+------------------------------+---------------------------------------+
| **[4.2.3 Start-the-Clock for |                                       |
| Plant-Load Mail]{.mark}**    |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 28, Start-the-Clock   |                                       |
| for Single Group Plant Load  |                                       |
| Report &                     |                                       |
|                              |                                       |
| Figure 29, Start-the-Clock   |                                       |
| for Multiple Group Plant     |                                       |
| Load Report                  |                                       |
+------------------------------+---------------------------------------+
| **[4.2.4]{.mark}             |                                       |
| Start-the-Clock Using        |                                       |
| Customer Supplier            |                                       |
| Agreements**                 |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[4.2.5 Full-Service        |                                       |
| Container                    |                                       |
| Visibility]{.mark}**         |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 30, Container         |                                       |
| Visibility Report            |                                       |
+------------------------------+---------------------------------------+
| **[4.2.6 Full-Service Change |                                       |
| of Address Detail            |                                       |
| Report]{.mark}**             |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 31, Change of Address |                                       |
| Detail Report                |                                       |
+------------------------------+---------------------------------------+
| **[4.2.7 Full-Service Nixie  |                                       |
| Detail Report]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Figure 32, Nixie Detail      |                                       |
| Report                       |                                       |
+------------------------------+---------------------------------------+
| **[4.3 Full-Service Data     |                                       |
| Provisioning to Multiple     |                                       |
| Parties]{.mark}**            |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats:       | ://ribbs.usps.gov/fullserviceguides>. |
|                              |                                       |
| Appendix B; Data             |                                       |
| Distribution Scenarios &     |                                       |
|                              |                                       |
| Appendix C: Data             |                                       |
| Distribution Scenario Chart  |                                       |
+------------------------------+---------------------------------------+
| **[4.4. Data Distribution to |                                       |
| Third-Parties]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
| Appendix B;                  |                                       |
|                              |                                       |
| Data Distribution Scenarios  |                                       |
| & Appendix C: Data           |                                       |
| Distribution                 |                                       |
|                              |                                       |
| Scenario Chart               |                                       |
+------------------------------+---------------------------------------+
| **[4.5 Profile               |                                       |
| Set-up]{.mark}**             |                                       |
|                              |                                       |
| **[4.5.1 Static              |                                       |
| Relationships]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+
| **[4.5.2 Dynamic             |                                       |
| Relationships]{.mark}**      |                                       |
+------------------------------+---------------------------------------+
| A Guide to Intelligent Mail  | <http                                 |
| for Letters and Flats        | ://ribbs.usps.gov/fullserviceguides>. |
+------------------------------+---------------------------------------+