PostalOne! Technical Guide

for Mail.XML 6.0

Version 6.6

December 13, 2008

**USPS Program Manager: Carla Siniscalchi (202) 268-4059**

**Business System Solutions Program Manager: Michael Haskin (314)
604-1452**

**Assurety Consulting Inc. Point of Contact:** Shariq Mirza (703)
292-4106

**Accenture Point of Contact:** Eben Joel (703) 947-1911

***PostalOne!* IT Point of Contact:** Ibrahim Hamid (703) 248-3507

***PostalOne!* IT Point of Contact:** Jeffery Avellanet (703) 248-3525

Table of Contents

[**1.0** **Full-service Mail.XML Technical Guide
5**](#full-service-mail.xml-technical-guide)

[1.1 What is Mail.XML? 5](#what-is-mail.xml)

[1.2 Purpose 6](#purpose)

[2.0 PostalOne! -- FAST Mail.XML Web Services
7](#postalone-fast-mail.xml-web-services)

[2.1 Overview 7](#overview)

[2.2 Access to *PostalOne!* - FAST Web Services
7](#access-to-postalone---fast-web-services)

[2.3 *PostalOne!*-FAST Mail.XML Web Services- supported messages
7](#postalone-fast-mail.xml-web-services--supported-messages)

[Mail.XML 4.0 Specification 7](#mail.xml-4.0-specification)

[Mail.XML 6.0 Specification (Full-Service Release 1 FAST Messages)
10](#mail.xml-6.0-specification-full-service-release-1-fast-messages)

[2.4 Additional Rules/Constraints 14](#additional-rulesconstraints)

[Delivery Appointment Query Response
17](#delivery-appointment-query-response)

[Detail Info Block 22](#detail-info-block)

[2.5 Multistop Support 22](#multistop-support)

[FAST Online Application 23](#fast-online-application)

[Web Services 23](#web-services)

[2.6 Error Codes/Return Values 23](#error-codesreturn-values)

[2.7 CIN Warning Codes and Descriptions
29](#cin-warning-codes-and-descriptions)

[2.8 Fault Codes 32](#fault-codes)

[2.9 Web Service Additional Constraints
32](#web-service-additional-constraints)

[2.10 Message Response Retrieval Request Processing
32](#message-response-retrieval-request-processing)

[2.11 *PostalOne!* WSDL Information 32](#postalone-wsdl-information)

[2.12 SchedulerContent ID 33](#schedulercontent-id)

[2.13 Closeout Messages 33](#closeout-messages)

[2.14 Appointment Shell Cancellation Messages
33](#appointment-shell-cancellation-messages)

[3.0 PostalOne! -- eDoc Mail.XML Messages
34](#postalone-edoc-mail.xml-messages)

[3.1 Overview 34](#overview-1)

[3.2 eDoc and Miscellaneous Messages
34](#edoc-and-miscellaneous-messages)

[Submitting Party 36](#submitting-party)

[Submitting Software 36](#submitting-software)

[3.3 Mail.XML-Specific Message Details
36](#mail.xml-specific-message-details)

[Mailing Group Messages 36](#mailing-group-messages)

[Qualification Report Messages 38](#qualification-report-messages)

[Bundle Detail Messages 46](#bundle-detail-messages)

[Mail Piece Messages 47](#mail-piece-messages)

[Postage Statement (non-Periodicals) Messages
52](#postage-statement-non-periodicals-messages)

[Periodicals Postage Statement Messages
59](#periodicals-postage-statement-messages)

[Payment Messeges 67](#payment-messeges)

[Miscellaneous Messages 67](#miscellaneous-messages)

[3.4 Additional Rules/Constraints 70](#additional-rulesconstraints-1)

[Mail.dat Container Update Messages
70](#mail.dat-container-update-messages-1)

[Container Status Messages 70](#container-status-messages-1)

[3.5 Error Codes/Return Values 71](#error-codesreturn-values-1)

[3.6 Additional Constraints 71](#additional-constraints)

[3.7 WSDL Information 71](#wsdl-information)

[4.0 Full-service Data Distribution -- Release 1.0
72](#full-service-data-distribution-release-1.0)

[4.1 Purpose 72](#purpose-1)

[4.2 Which methods does the *PostalOne!* system support for Full-service
data feedback?
72](#which-methods-does-the-postalone-system-support-for-full-service-data-feedback)

[4.3 What do you need to receive your data through the data exchange
methods identified?
73](#what-do-you-need-to-receive-your-data-through-the-data-exchange-methods-identified)

[Step 1 73](#step-1)

[Step 2 73](#step-2)

[4.4 How do you implement/use the Mail.XML available for Full-service
data distribution?
73](#how-do-you-implementuse-the-mail.xml-available-for-full-service-data-distribution)

[Why use Mail.XML-based Data Distribution?
74](#why-use-mail.xml-based-data-distribution)

[4.5 Data Distribution Authorization Profiles
74](#data-distribution-authorization-profiles)

[Static 74](#static)

[Delegated 74](#delegated)

[Complete 74](#complete)

[Partial -- Mail Preparer 75](#partial-mail-preparer)

[Partial -- MID on Piece 75](#partial-mid-on-piece)

[Dynamic 75](#dynamic)

[4.6 Messages Supported in Release 1.0
75](#messages-supported-in-release-1.0)

[4.7 Messages Not Supported in Release 1 or 2
75](#messages-not-supported-in-release-1-or-2)

[4.8 Push Messages 76](#push-messages)

[4.9 Pull Messages 76](#pull-messages)

[4.10 Messages 76](#messages)

[Push Messages Supported in Release 1 of Full-service implementation:
76](#push-messages-supported-in-release-1-of-full-service-implementation)

[Pull Messages Supported in Release 1 of Full-service implementation:
77](#pull-messages-supported-in-release-1-of-full-service-implementation)

[Cast Of Characters Messages for Release 1 of Full-service
implementation:
77](#cast-of-characters-messages-for-release-1-of-full-service-implementation)

[4.11 Additional Business Rules 78](#additional-business-rules)

[Delivery and Notification Messages:
78](#delivery-and-notification-messages)

[Request and Response Messages 82](#request-and-response-messages)

[Cast Of Characters Messages for Release 1 of Full-service
implementation:
88](#cast-of-characters-messages-for-release-1-of-full-service-implementation-1)

[4.12 Pull Request/Response-Handling Large Transactions
89](#pull-requestresponse-handling-large-transactions)

[APPENDIX A - WSDLs and XSDs 91](#appendix-a---wsdls-and-xsds)

[WSDL for Release 1 91](#wsdl-for-release-1)

[PUSH User Profile XSD 111](#push-user-profile-xsd)

[USER Authentication Info XSD 112](#user-authentication-info-xsd)

[WSDL -- PUSH Model 113](#wsdl-push-model)

[USER Authentication XSD 117](#user-authentication-xsd)

[APPENDIX B -- Message Choreography for Data Distribution
118](#appendix-b-message-choreography-for-data-distribution)

[Appendix C -- Data Distribution Scenarios
120](#appendix-c-data-distribution-scenarios)

[OneCode ACS Scenarios 120](#onecode-acs-scenarios)

[Confirm Scenarios 125](#confirm-scenarios)

[Start-the-Clock Scenarios 127](#start-the-clock-scenarios)

[Multiple Services 128](#multiple-services)

[Appendix D -- Data Distribution Chart
131](#appendix-d-data-distribution-chart)

[Appendix E - eDoc Form Values 134](#appendix-e---edoc-form-values)

[Bundle Detail Levels 134](#bundle-detail-levels)

[Bundle Levels 134](#bundle-levels)

[Carrier Route Number 135](#carrier-route-number)

[Container Charge Container Type 135](#container-charge-container-type)

[Container Charge Entry Facility Type
135](#container-charge-entry-facility-type)

[Container Levels 136](#container-levels)

[Container Type 136](#container-type)

[Enclosing Class 136](#enclosing-class)

[Entry Discount 137](#entry-discount)

[Entry Facility Type 137](#entry-facility-type)

[Flat Rate Indicator 137](#flat-rate-indicator)

[Form Type 137](#form-type)

[Full-service Indicator 138](#full-service-indicator)

[In-County, Outside-County Indicator
138](#in-county-outside-county-indicator)

[Metered Affixed Method 138](#metered-affixed-method)

[Move Update 138](#move-update)

[Packaging Basis 139](#packaging-basis)

[Parcel Barcode Rate 139](#parcel-barcode-rate)

[Periodicals Statement Type 139](#periodicals-statement-type)

[Permit Type 139](#permit-type)

[Postage Payment Method 140](#postage-payment-method)

[Postage Statement Stage 140](#postage-statement-stage)

[Processing Category 140](#processing-category)

[Publication Type 140](#publication-type)

[Rate Category 141](#rate-category)

[Rate Level 142](#rate-level)

[Rate Level Indicator 142](#rate-level-indicator)

[Rate Type 142](#rate-type)

[Recipient Type 143](#recipient-type)

[Sacking Basis 144](#sacking-basis)

[Sortation Level 144](#sortation-level)

[Special Service Code 145](#special-service-code)

[Special Service Subcode 145](#special-service-subcode)

[Status 145](#status)

[Surcharge Discount Type 145](#surcharge-discount-type)

[Surcharge Type 146](#surcharge-type)

[Weight Break Indicator 146](#weight-break-indicator)

[Zone (Qualification Report) 146](#zone-qualification-report)

[Zone 147](#zone)

[Appendix F -- Postage Statement Values by Form Type
148](#appendix-f-postage-statement-values-by-form-type)

[Enclosing Class 148](#enclosing-class-1)

[Entry Discount 148](#entry-discount-1)

[Entry Facility Type 148](#entry-facility-type-1)

[Flat Rate Indicator 149](#flat-rate-indicator-1)

[Nonsub/Nonreq 10% Limit 149](#nonsubnonreq-10-limit)

[Inside-County, Outside-County Indicators
149](#inside-county-outside-county-indicators)

[Mailer Role 149](#mailer-role)

[Metered Affixed Method 150](#metered-affixed-method-1)

[Move Update 150](#move-update-1)

[Packaging Basis 151](#packaging-basis-1)

[Parcel Barcode Rate 151](#parcel-barcode-rate-1)

[Permit Type 151](#permit-type-1)

[Periodicals Statement Type 151](#periodicals-statement-type-1)

[Postage Payment Method 152](#postage-payment-method-1)

[Postage Statement Stage 152](#postage-statement-stage-1)

[Prepared as Standard Mail 152](#prepared-as-standard-mail)

[Price Type 153](#price-type)

[Processing Category 153](#processing-category-1)

[Rate Category 153](#rate-category-1)

[Rate Type 154](#rate-type-1)

[Recipient Type 155](#recipient-type-1)

[Sacking Basis 155](#sacking-basis-1)

[Special Service Code 155](#special-service-code-1)

[Special Service Subcode 156](#special-service-subcode-1)

[Surcharge 156](#surcharge)

[Surcharge Discount Type 156](#surcharge-discount-type-1)

[Weight Break Indicator 157](#weight-break-indicator-1)

[Zone 157](#zone-1)

# Full-service Mail.XML Technical Guide

## What is Mail.XML?

Mail.XML™ is an XML-based IDEAlliance®
([www.mailxml.org](http://www.mailxml.org/)) specification for Web
services, supporting the (SOA) Services Oriented Architecture that is
conversational in nature and platform independent. Web services use
simple HTTP(s) protocol to communicate data over the Internet, hence
bypassing technology-specific restrictions and avoiding network-related
security rules. Sound implementations of Web services are safe, secure,
and platform independent. Additionally, Web services support near
real-time communication, and increase the efficiency of conducting
business in most environments.

Mail.XML 6.0 functionality, when implemented in September 2009, will
surpass any functionality available today through any data interface
with the United States Postal Service® (USPS®). The IDEAlliance Mail.XML
version 6.0 Specification is made up of families of related messages
that provide all the capabilities that the Mail.dat® specification
provided. Additionally, it also supports business functions that
Mail.dat did not provide, such as appointment scheduling management,
Cast of Characters communication, reception of Full-service feedback
data from USPS, and bidirectional data communication to conduct business
with the USPS. The specification also allows users to conduct many
business functions through near real-time communication mechanisms
specifically created to support joint scheduling and transportation
management communications.

**Mail.XML 6.0**

Mail.XML version 6.0 enhances efficiency and ease of transmission for
small and large data volume communications. It includes an attribute
that allows all messages with large data volume to be broken up in as
many unique child transactions as the USPS and the industry believes can
be easily and efficiently supported by the existing network
infrastructure. In other words, a 10 MB file can be broken up into ten
1MB transactions or twenty 500KB transactions. Mail.XML allows for
verification and comprehensive validation of the data in near real time.

When the USPS receives data from you, USPS can respond in near real time
to let you know the status of the transaction and the data received. You
can also let the USPS know, right away, if the data sent by USPS had
problems, was bad or incomplete, or did not belong to you. The
bidirectional communication allows for automatic conflict-resolution
triggering that can result in immediate action.

The IDEAlliance Mail.XML version 6.0 specification, currently scheduled
for implementation by USPS in September 2009, will support Full-service
electronic documentation functionality, including single piece
information, range piece information, nesting of pieces into handling
units and handling units into containers, postage payment, qualification
reports, and electronic documentation management through transaction
updates. The Mail.XML version 6.0 is used for providing data feedback to
you for Full-service, such as StartTheClock, Container Scans, ACS, and
Nixie data. The *PostalOne!*® system is implementing the data feedback
functionality with some miscellaneous Mail.XML messages in May 2009.

The previous versions of Mail.XML already provide the support for the
appointment scheduling business processes with the USPS *PostalOne!* and
FAST systems. The USPS currently supports Mail.XML 2.0 and Mail.XML 4.0
specifications in production and in September will support the
appointment management processes with Mail.XML 6.0 and Mail.XML 4.0.

**The *PostalOne!* team plans to implement the Mail.XML 6.0 Errata-A
version.** Mail.XML 6.0 errata versions are scheduled for publication
once a month, so check for Mail.XML errata versions on the
[www.mailxml.org](http://www.mailxml.org/) site periodically and look
for DMM notifications as well as the External Timeline document for IM
implementation shared with the MTAC 122 work group to learn about any
changes in the *PostalOne! Technical Guide*

## Purpose

The purpose of this Technical Guide is to supplement the IDEAlliance
Mail.XML (previously known as IDEAlliance Mail.dat Transportation
Management (TM)) Specification and to provide Mail.XML users with
specific information regarding USPS implementation. USPS will support
Mail.XML 6.0 as part of the Full-service Program currently scheduled for
release by mid-2009. This document serves as the collection of all
specific rules, standards, accepted values, error messages, etc. for the
USPS implementation of the Mail.XML specification, and will be updated
as the Mail.XML specification changes. USPS will make return codes,
error codes and their descriptions, as well the WSDLs for Release 2
available to the industry on the dates documented in the *External
TimeLine for IM implementation* document made available to the MTAC 122
work group. So, check for an update to this guide at that time.

This guide is divided into multiple sections:

-   Section 1.0 provides an overview of the purpose of the guide.

-   Section 2.0 provides technical information with regard to the
    Mail.XML v6.0 messages that support the *PostalOne!*-FAST Web
    Services interface and can largely be grouped as scheduling-related
    messages. The *PostalOne!* system and FAST will continue to support
    two versions of the Mail.XML specifications; namely Mail.XML 4.0 and
    Mail.XML 6.0 with the implementation of the Full-service program.

-   Section 3.0 discusses Mail.XML electronic documentation (eDoc)
    messages that support *PostalOne!* system and mailer interactions by
    managing, updating and querying mail contents. These messages
    supplement Mail.dat functionality such as qualification reports,
    postage statements, container updates, piece detail and range
    messages, and co-palletization messages. The *PostalOne!* system
    will support the new and enhanced version of these messages as
    described in Mail.XML 6.0 by the release of the Full-service
    program.

-   Sections 4.0 discusses the data distribution and data feedback push
    and pull models to receive StartTheClock, Container Visibility, ACS,
    and Nixie Detail data.

-   The last sections are Appendices for the eDoc messages and provide
    more reference detail.

This guide will be updated as additional information is communicated by
IDEAlliance or by USPS with the release of the errata versions of the
Mail.XML 6.0 specification.

# PostalOne! -- FAST Mail.XML Web Services 

## Overview

The USPS requires appointment scheduling for drop-shipped mail at USPS
facilities for better resource planning and service performance. The
USPS FAST (Facilities Access and Shipment Tracking) system is the
business process engine that allows mailers to schedule appointments.

## Access to *PostalOne!* - FAST Web Services

The FAST system supports two methods to create, update, and cancel
appointments and receive Closeout data. For both processes, a mail owner
or mailing agent must request a user account using the Customer
Registration system, which performs authentication and authorization
services for the FAST and *PostalOne!* systems. The two methods are:

1.  Going online to [http://fast.usps.com](http://fast.usps.com/),
    logging in with your username and password and completing FAST
    Web-based pages to request an appointment at a facility at a certain
    date and time. This process is manual process requiring manual data
    entry. This online FAST process does not require the customer to
    provide content (container) detail information, such as IM Container
    barcode, weight, pieces, and many other characteristics due to the
    manual nature of the process.

2.  Utilizing the IDEAlliance Mail.XML Specification and *PostalOne!* /
    FAST Web Services. In this process, the *PostalOne!* system works as
    the data exchange gateway for the appointment transactions and
    passes the appointment and container detail information, including
    IM Container barcode, class, shape, piece count, weight, zone
    skipping, mail owner information (By/For) and many other content
    characteristics to the FAST system. All messages to and from the
    customer pass through the *PostalOne!* system. The *PostalOne!*
    system can also be leveraged in this usage scenario to pull existing
    content (container detail) information from Mail.dat files submitted
    previously by the customer or the customer\'s business partner. The
    customer can either send all content details directly to FAST
    through the *PostalOne!* - FAST Web Services mechanism, or can
    request the *PostalOne!* system to query and provide all or part of
    the content details to FAST through the *PostalOne!* - FAST Web
    Services mechanism.

The Full-service program requires Mail.XML messages to create or update
appointments within the FAST system for one-time appointments.
Appointments created through the online FAST application must be updated
electronically through Mail.XML with the Intelligent Mail Container
Barcode (IMCB) to receive Full-service discounts.

## *PostalOne!*-FAST Mail.XML Web Services- supported messages

The *PostalOne!* - FAST Mail.XML Web Services interface will continue to
support two versions of the Mail.XML Specifications at a given time.
*PostalOne!* - FAST Mail.XML Web Services will support versions 4.0 and
6.0 of the Mail.XML specification with the release of Full-service.

The following sections provide information about the subset of Mail.XML
messages that will be supported by both the *PostalOne!* system and FAST
in Mail.XML 4.0 and 6.0.

### Mail.XML 4.0 Specification {#mail.xml-4.0-specification .unnumbered}

For Mail.XML 4.0, the *PostalOne!* system and the FAST system support
the following groups of messages as of November 16, 2008:

#### Delivery Appointment Messages {#delivery-appointment-messages .unnumbered}

This family of Mail.XML transportation related messages supports
scenarios where a Shipper requests a Delivery Appointment from the
Consignee. The Consignee may respond a number of ways, all of which are
supported by messages in this message family. Delivery appointment
messages will:

-   Provide the ability to create, update, and cancel drop ship
    appointments

-   Provide the ability to create, update, and cancel First-Class Mail,
    DMU customer-transported appointments

-   Provided the ability to query the availability of slots for drop
    ship appointments

-   Provide the ability to query the availability of slots (based on
    hours of operation) for First-Class DMU/BMEU customer-transported
    appointments

-   Provide the ability to distinguish eVS parcels and submit the
    associated eFile Number for which they were manifested

-   Provide the ability to support new container types and handling
    units

-   Provide the ability to support sibling containers

-   Provide the ability to associate stand-alone contents to a one-time
    appointment

-   Grant the ability to provide the Intelligent Mail Container Barcodes
    (IMCB) associated with the appointment

**Delivery Appointment Messages**

DeliveryApptCreateRequest / DeliveryApptCreateResponse

DeliveryApptUpdateRequest / DeliveryApptUpdateResponse

DeliveryApptCancelRequest / DeliveryApptCancelResponse

DeliveryApptQueryRequest / DeliveryApptQueryResponse

#### Delivery Content Messages {#delivery-content-messages .unnumbered}

This family of Mail.XML transportation related messages supports
scenarios where the *PostalOne!* system sends content information to
FAST without sending any appointment-level information. The Consignee
may respond a number of ways, all of which are supported by messages in
this message family. These sets of messages apply for the scheduling of
drop ship appointments only.

Delivery Content messages provide the:

-   Ability to create, update, and cancel stand-alone content

-   Ability to create, update, and cancel contents for one-time and
    recurring appointments

-   Ability to distinguish eVS parcels and submit the associated eFile
    Number for which they were manifested

-   Support new container types and handling units

-   Support sibling containers

-   Ability for schedulers to query for content created by other mail
    owners/mail preparers

-   Ability to provide the Intelligent Mail Container Barcodes (IMCB)
    associated to the appointment

**Delivery Content Messages**

DeliveryContentCreateRequest / DeliveryContentCreateResponse

DeliveryContentUpdateRequest / DeliveryContentUpdateResponse

DeliveryContentCancelRequest / DeliveryContentCancelResponse

DeliveryContentQueryRequest / DeliveryContentQueryResponse

#### Appointment Shell Messages {#appointment-shell-messages .unnumbered}

This family of Mail.XML transportation-related messages enables mailers
to create appointment shells (appointments with no associated content).
Mail owners and mail preparers can use the Delivery Content Messages to
create and associate content to appointment shells. This family of
messages allows for joint scheduling between schedulers and mail owners
and mail preparers. Appointment shell messages will provide the:

-   Ability to create, update, and cancel recurring appointment shells

-   Ability to create, update, and cancel one-time appointment shells

-   Ability to update the logistics information of an appointment by
    utilizing the appointment shell update message

**Appointment Shell Messages**

DeliveryApptShellRequest / DeliveryApptShellResponse

DeliveryApptShellUpdateRequest / DeliveryApptShellUpdateResponse

DeliveryApptShellCancelRequest / DeliveryApptShellCancelResponse

#### Recurring Appointment Query Messages {#recurring-appointment-query-messages .unnumbered}

This family of Mail.XML transportation related messages allows mailers
to query for active and pending recurring appointments. Recurring
Appointment query messages will provide the:

-   Ability to query for active and pending drop ship recurring
    appointments

-   Ability to query for active First-Class DMU/BMEU verified customer
    transported appointments

**Recurring Appointment Query Messages**

RecurringApptQueryRequest / RecurringApptQueryResponse

#### Appointment Closeout Messages {#appointment-closeout-messages .unnumbered}

This series of messages is pushed from the Consignee to the Shipper when
an appointment is closed. Closeout Messages will provide the:

-   Ability to send closeout information for First-Class DMU/BMEU
    verified customer-transported appointments

-   Ability to send closeout information for drop ship appointments

-   Ability to communicate closeout irregularities

-   Ability to communicate arrival date/time, unload start date/time,
    unload end date/time, and actual pallet counts

-   Ability to indicate if IMCB Pallet Placard scan occurred

-   Ability to communicate if a drop ship appointment will be excluded
    from rating

**Appointment Closeout Messages**

AllDeliveryAppointmentCloseoutRequest

ConsigneeGoodsReceipt

UnscheduledConsigneeGoodsReceipt

### Mail.XML 6.0 Specification (Full-Service Release 1 FAST Messages) {#mail.xml-6.0-specification-full-service-release-1-fast-messages .unnumbered}

The following major enhancements will be incorporated in FAST with
IDEAlliance Mail.XML 6.0:

-   Provide the ability to create, update, and cancel Standard,
    Periodicals, and Package Services class based appointments for
    customer-transported appointments

-   Provide the capability to create, update, cancel recurring
    appointments for customer transported origin entry appointments
    (First-Class Mail, Standard Mail, Periodicals, and Package Services)

-   Provide the capability to create, update, cancel recurring
    appointments for drop ship appointments

-   More than one sibling barcode can be associated with a unique
    container barcode.

-   Leverage the CancelCreate message to move containers from one
    appointment to another when the original appointment was a "No
    Show".

-   Leverage the DeliveryContent messages to add, update, or cancel a
    container to an appointment.

-   Leverage the Delivery Appointment Cancel Create message
    to release containers from one appointment and schedule to another
    when the original appointment status is \"Open\" or "No Show".  

-   Provide closeout information for customer-transported origin entry
    appointments (all mail classes).

Messages Supported by the *PostalOne!* system and FAST in Mail.XML 6.0
-- Full-Service Release 1

Table 2‑1. Supported Mail.XML Messages in Full-service Release 1.0

  ---------------------------------------- ---------------------------------------
  DeliveryApptCreateRequest                DeliveryApptCreateResponse

  DeliveryApptUpdateRequest                DeliveryApptUpdateResponse

  DeliveryApptCancelRequest                DeliveryApptCancelResponse

  DeliveryApptQueryRequest                 DeliveryApptQueryResponse

  DeliveryContentCreateRequest             DeliveryContentCreateResponse

  DeliveryContentUpdateRequest             DeliveryApptShellCreateRequest

  DeliveryContentUpdateResponse            DeliveryApptShellCreateResponse

  DeliveryContentCancelRequest             DeliveryApptShellUpdateRequest

  DeliveryContentCancelResponse            DeliveryApptShellUpdateResponse

  DeliveryContentQueryRequest              DeliveryApptShellCancelRequest

  DeliveryContentQueryResponse             DeliveryApptShellCancelResponse

  PartnerApptQueryRequest                  AllDeliveryAppointmentCloseoutRequest

  PartnerApptQueryResponse                 AllAppointmentCloseoutResponse

  CustomerSupplierAgreementQueryRequest    ConsigneeGoodsReceipt

  CustomerSupplierAgreementQueryResponse   UnscheduledConsigneeGoodsReceipt
  ---------------------------------------- ---------------------------------------

#### Messages NOT Supported for Appointment management by the USPS {#messages-not-supported-for-appointment-management-by-the-usps .unnumbered}

Table 2‑2. Mail.XML Messages Not Supported in Full-service Release 1.0

  ---------------------------------------------- ----------------------------------------
  AllPickUpApptCloseoutRequest                   CustomerRelationIdentifyUpdateRequest

  ApptinductionCloseoutRequest                   CustomerRelationIdentifyUpdateResponse

  ApptinductionCloseoutResponse                  DeliveryApptContentRemoveRequest

  ConsigneeGoodsReceiptNotification              DeliveryApptContentRemoveResponse

  ConsigneeGoodsReceiptDelivery                  DeliveryApptMultiStopUpdateRequest

  CustomerRelationIdentifyQueryRequest           DeliveryReAptRequest

  CustomerRelationIdentifyQueryResponse          DeliveryResponse

  DeliveryApptStatusQueryRequest                 PickupApptCreateRequest

  DeliveryApptStatusQueryResponse                PickupApptCreateResponse

  DeliveryApptTransportationUpdateRequest        PickupApptCancelRequest

  DeliveryApptTransportationUpdateResponse       PickupApptCancelRequest

  UnscheduledConsigneeGoodsReceiptNotification   PickupApptUpdateRequest

  UnscheduledConsigneeGoodsReceiptDelivery       PickupApptUpdateRequest

  GoodsreceiptResponse                           USPSForecastCancelRequest

  OpenApptQueryRequest                           USPSForecastCancelResponse

  OpenApptQueryRequest                           USPSForecastUpdateRequest

  USPSForecastCreateRequest                      USPSForecastUpdateResponse

  USPSForecastCreateResponse                     
  ---------------------------------------------- ----------------------------------------

#### Delivery Appointment Messages {#delivery-appointment-messages-1 .unnumbered}

This family of Mail.XML transportation related messages supports
scenarios where a Shipper requests a Delivery Appointment from the
Consignee. The Consignee may respond a number of ways, all of which are
supported by messages from this message family. Delivery appointment
messages will:

-   Provide the ability to create, update, and cancel First-Class DMU
    customer transported appointments

-   Provide the ability to create, update, and cancel drop ship
    appointments

-   Provide the ability to create, update, and cancel First-Class DMU
    customer transported recurring appointments

-   Provide the ability to create, update, and cancel drop ship
    recurring appointments

-   Provide the ability to query the availability of slots (based on
    hours of operation) for First-Class DMU/BMEU customer transported
    appointments

-   Provide the ability to query the availability of slots for drop ship
    appointment

-   Provide the ability to distinguish eVS parcels and submit the
    associated eFile Number for which they were manifested

-   Provide the ability to support for new container types and handling
    units

-   Provide the ability to support the sibling containers

-   Provide the ability to associate stand-alone contents to a one-time
    appointment

-   Ability to provide the Intelligent Mail Container Barcodes(IMCB)
    associated to the appointment

-   Provide the ability to create, update, and cancel customer
    transported origin entry appointments (First-Class Mail, Standard
    Mail, Periodicals, and Package Services)

-   Provide the ability to create, update, and cancel customer
    transported origin entry recurring appointments (First-Class Mail,
    Standard Mail, Periodicals, and Package Services)

-   Provide the ability to cancel one or more appointments and create a
    new appointment using the delivery appointment cancel create
    message.

-   Provide the ability transfer content(s) from one or more cancelled
    appointments to a newly created appointment using the delivery
    appointment cancel create message.

**Delivery Appointment Messages**

DeliveryApptCreateRequest / DeliveryApptCreateResponse

DeliveryApptUpdateRequest / DeliveryApptUpdateResponse

DeliveryApptCancelRequest / DeliveryApptCancelResponse

DeliveryApptQueryRequest / DeliveryApptQueryResponse

DeliveryApptCancelCreateRequest / DeliveryApptCancelCreateResponse

#### Delivery Content Messages {#delivery-content-messages-1 .unnumbered}

This family of Mail.XML transportation related messages supports
scenarios where the *PostalOne!* system sends content information to
FAST without sending any appointment level information. The Consignee
may respond a number of ways, all of which are supported by messages
from this message family. These sets of messages apply for scheduling of
drop ship appointments only.

Delivery Content messages provide the:

-   Ability to create, update, and cancel stand-alone content that can
    be used by a business partner with a DeliveryAppointmentCreate or
    update Request

-   Ability to create, update, and cancel contents for one-time and
    recurring appointments

-   Ability to distinguish eVS parcels and submit the associated eFile
    Number for which they were manifested

-   Support for new container types and handling units

-   Support for sibling containers

-   Ability for schedulers to query for content created by other mail
    owners/mail preparers

-   Ability to provide the Intelligent Mail Container Barcodes(IMCB)
    associated to the appointment

-   Ability to add, update, or cancel a container to an appointment by a
    Scheduler

**Delivery Content Messages**

DeliveryContentCreateRequest / DeliveryContentCreateResponse

DeliveryContentUpdateRequest / DeliveryContentUpdateResponse

DeliveryContentCancelRequest / DeliveryContentCancelResponse

DeliveryContentQueryRequest / DeliveryContentQueryResponse

#### Appointment Shell Messages {#appointment-shell-messages-1 .unnumbered}

This family of Mail.XML transportation related messages enables mailers
to create appointment shells (appointments with no associated content).
Mail owners and mail preparers can use the Delivery Content Messages to
create and associate content to appointment shells. This family of
messages allows for joint scheduling between schedulers and mail owners
and mail preparers. Appointment Shell messages will provide the:

-   Ability to create, update, and cancel recurring appointment shells

-   Ability to create, update, and cancel one-time appointments shells

-   Ability to update the logistics information of an appointment by
    utilizing the appointment shell update message

**Appointment Shell Messages**

DeliveryApptShellCreateRequest / DeliveryApptShellCreateResponse

DeliveryApptShellUpdateRequest / DeliveryApptShellUpdateResponse

DeliveryApptShellCancelRequest / DeliveryApptShellCancelResponse

#### Recurring Appointment Query Messages {#recurring-appointment-query-messages-1 .unnumbered}

This family of Mail.XML transportation related messages allows mailers
to query for active and pending recurring appointments. Recurring
Appointment query messages will provide the:

-   Ability to query for active and pending drop ship recurring
    appointments

-   Ability to query for active First-Class DMU/BMEU verified customer
    transported appointments

**Recurring Appointment Query Messages**

RecurringApptQueryRequest / RecurringApptQueryResponse

#### Appointment Closeout Messages {#appointment-closeout-messages-1 .unnumbered}

This series of messages is pushed from the Consignee to the Shipper
closeout an appointment. Closeout Messages will provide the:

-   Ability to send closeout information for First-Class DMU/BMEU
    verified customer transported appointments

-   Ability to send closeout information for drop ship appointments

-   Ability to communicate closeout irregularities

-   Ability to communicate arrival date/time, unload start date/time,
    unload end date/time, and actual pallet counts

-   Ability to indicate if IMCB Pallet Placard scan occurred

-   Ability to communicate if a drop ship appointment will be excluded
    from rating

-   Provide closeout information for customer transported origin entry
    appointments (all mail classes).

**Appointment Closeout Messages**

AllDeliveryAppointmentCloseoutRequest

AllAppointmentCloseoutResponse

ConsigneeGoodsReceipt

UnscheduledConsigneeGoodsReceipt

#### Partner Appointment Query Messages {#partner-appointment-query-messages .unnumbered}

This family of Mail.XML transportation related messages allows mailers
to query appointment and content information on behalf of partner
mailers:

-   Partner Appointment Query Request

-   Partner Appointment Query Response

Partner Appointment Query Messages

PartnerApptQueryRequest

PartnerApptQueryResponse

#### Customer Supplier Agreement Messages {#customer-supplier-agreement-messages .unnumbered}

This will allow Web Services capable mailers to query for their
associated customer supplier agreements via CRID or CSA IDs (if known).
These messages include:

-   Customer Supplier Agreement Query Request

-   Customer Supplier Agreement Query Response

CSA Messages

CustomerSupplierAgreementQueryRequest

CustomerSupplierAgreementQueryResponse

## Additional Rules/Constraints

The following section outlines the specific rules and constraints for
USPS implementation. For additional details regarding the calculations
used for Appointment Rating, online supported functionality vs. Web
Services supported functionality, etc., please refer to the *FAST User
Guide*.

-   A mailer must submit an appointment using the facility's local time
    (taking time zone and daylight savings into consideration) and FAST
    will respond using the same logic.

-   The following outlines the list of possible values for Appointment
    Types, Mail Classes, Processing Categories, Presort Levels, and Rate
    Types for the Delivery Appointment Query Request, Delivery
    Appointment Create Request and Delivery Appointment Update Request.
    Also included in the Presort list is a breakdown of whether the
    content tied to that Presort will be treated as Working or Cross
    Dock for volume availability calculations.

Table 2‑3. Appointment Type Values

  ---------------- -------------------------------------- --------------------
  Appointment Type                                        
  (apptTypeType)                                          

  Code             Description                            Supported?

  1                Pallet                                 Yes

  2                DropAndPick                            Yes

  3                Speedline                              Yes

  4                Bedload                                Yes
  ---------------- -------------------------------------- --------------------

Table 2‑4. Mail Class Values

  -------------------------------------------------------------------------------
  Mail Class                                                  
  (mailClassType)                                             
  ----------------- ----------------------------------------- -------------------
  Code              Description                               Supported?

  1                 First-Class Mail                          Yes

  2                 Periodicals                               Yes

  3                 Standard Mail                             Yes

  4                 Packaged Services                         Yes

  6                 Standard/Periodicals Co-Mailings          Yes\*
  -------------------------------------------------------------------------------

**\* NOTE**: Standard Mail/Periodicals Co-Mailings content will be
processed by FAST as Standard Mail content. Currently, the *PostalOne!*
system does not support Co-Mailing Class "6" due to postage
implications. As a result, the *PostalOne!* system will not populate
Mail Class "6" from Mail.dat files into the Mail.XML specification
because files with that mail class fail validation.

Table 2‑5. Processing Category Values

  -------------------------- ---------------------------------------- --------------------
  Processing Category                                                 
  (processingCategoryType)                                            

  Code                       Description                              Supported?

  LT                         Letter                                   Yes

  FL                         Flat                                     Yes

  CD                         Card                                     Yes\*

  PF                         Parcel, First-Class Mail                 Yes

  MP                         Machinable Parcel                        Yes

  IR                         Irregular Parcel                         Yes

  OS                         Outside Parcel                           Yes

  CM                         Custom Mail                              No

  NA                         Not Flat-Machinable \< 6oz               Yes

  NB                         Not Flat-Machinable \>= 6oz              Yes

  NP                         Non Machinable Parcels                   Yes
  -------------------------- ---------------------------------------- --------------------

**NOTE**: Processing Category of "CD" ("Card") is translated to "LT"
("Letter") for volume availability.

Table 2‑6. Presort Type Values

  --------------------------------------------------------------------------------------
  Presort Types                                                          
  (containerLevelType)                                                   
  ---------------------- ------------------------------- --------------- ---------------
  Code                   Description                     Supported?      Type

  A                      CR-Direct                       Yes             Cross Dock

  B                      Mixed CR in 5 Digit             Yes             Cross Dock

  C                      Mixed CR in 3 Digit             Yes             Working

  D                      CR -- 5D Scheme                 Yes             Cross Dock

  E                      DPC/3D Scheme                   No              N/A

  F                      RDC/Scheme                      No              N/A

  G                      5 Digit (Auto/Presort)          Yes             Working

  H                      5 Digit (Merged)                Yes             Working

  I                      5 Digit (Presort Only)          Yes             Working

  J                      5 Digit (Barcode Only)          Yes             Working

  K                      Metro Scheme                    Yes             Working

  L                      Mixed RDC                       No              N/A

  M                      5D Scheme (Presort)             Yes             Cross Dock

  N                      5D Scheme (Auto/Presort)        Yes             Cross Dock

  P                      5D Scheme (Barcode)             Yes             Cross Dock

  Q                      5D Scheme (Merged)              Yes             Cross Dock

  R                      3 Digit (Auto/Presort)          Yes             Working

  S                      3 Digit (Barcode)               Yes             Working

  T                      3 Digit (Presort)               Yes             Working

  U                      3 Digit (CR/Auto/Presort)       Yes             Working

  V                      3 Digit Scheme                  Yes             Working

  W                      Unique 3 Digit                  Yes             Working

  X                      SCF                             Yes             Working

  Y                      Protected SCF                   Yes             Working

  Z                      ADC                             Yes             Working

  AA                     AADC                            Yes             Working

  AB                     Mixed ADC                       Yes             Working

  AC                     Mixed AADC                      Yes             Working

  AD                     ASF                             Yes             Working

  AE                     BMC                             Yes             Working

  AF                     Protected BMC                   Yes             Working

  AG                     Mixed BMC                       Yes             Working

  AJ                     Single Piece                    No              Working

  BA                     Urban Direct                    No              N/A

  BB                     Rural Direct                    No              N/A

  BC                     Station                         No              N/A

  BD                     City                            No              N/A

  BE                     FSA                             No              N/A

  BF                     DCF                             No              N/A

  BG                     FCP                             No              N/A

  BH                     Province                        No              N/A

  BI                     Residual                        No              N/A

  BJ                     Foreign                         No              N/A

  BK                     Country                         No              N/A

  BL                     Mixed Country                   No              N/A

  BM                     M Bags                          No              N/A
  --------------------------------------------------------------------------------------

Table 2‑7. Rate Type Values

  ------------------------------------------------------------------------------
  Rate Type                                                 
  (rateTypeType)                                            
  ---------------- ---------------------------------------- --------------------
  Code             Description                              Supported?

  B                Bound Printed Matter                     Yes

  D                Parcel Select                            Yes

  F                Media                                    Yes

  L                Library                                  Yes

  P                Parcel Post                              No
  ------------------------------------------------------------------------------

**NOTE**: The mailClassType, processingCategoryType, containerLevelType,
and RateType fields are all contained in the USPS Summarization block.
Each Delivery Appointment Query Request, Delivery Appointment Create
Request, Delivery Appointment Update Request, Delivery Content Create
Request and Delivery Content Update Request can contain more than one
USPS Summary block. If a single USPS Summary block within these messages
contains an unsupported type for any of these fields, the entire message
will be rejected. In addition, a Return Code/Description will be
returned for each violation.

-   Only the following fields will be populated with new data in the
    response messages. All other information will simply be populated
    based on what was originally sent in the request message.

### Delivery Appointment Query Response {#delivery-appointment-query-response .unnumbered}

-   All available appointment(s) are populated in a one to many
    Available Appt elements in the ApptBlock block.

-   ReturnInfo block containing CIN Warnings if any have occurred.

-   If no Appointment matches are found, the ReturnInfo block containing
    one to many return code/description combinations is populated.

#### Delivery Appointment Acceptance Response {#delivery-appointment-acceptance-response .unnumbered}

-   The ScheduledAppt element in the ApptBlock block is populated.

-   The ConsigneeApptID in the ResponseMsgHeaderInfo block is populated.

-   The ConsigneeMultiStopID in the ResponseMsgHeaderInfo block is
    populated if the Appointment is tied to a Multistop.

-   ReturnInfo block containing CIN Warnings if any have occurred.

#### Delivery Appointment Rejection Response {#delivery-appointment-rejection-response .unnumbered}

ReturnInfo block containing one to many return code/description
combinations is populated.

#### Delivery Appointment Update Acceptance Response {#delivery-appointment-update-acceptance-response .unnumbered}

-   The ScheduledAppt element in the ApptBlock block is populated.

-   ReturnInfo block containing CIN Warnings if any have occurred.

#### Delivery Appointment Update Rejection Response {#delivery-appointment-update-rejection-response .unnumbered}

ReturnInfo block containing one to many return code/description
combinations is populated.

#### Delivery Appointment Cancel Response {#delivery-appointment-cancel-response .unnumbered}

The CancelConfirmID element is populated if the Appointment was canceled
successfully. Otherwise, a ReturnInfo block containing one to many
return code/description combinations is populated.

#### Delivery Content Accept Response {#delivery-content-accept-response .unnumbered}

-   The ConsigneeContentID in the ContentUSPSSummaryUpdate block is
    populated.

-   ReturnInfo block containing CIN Warnings if any have occurred.

#### Delivery Content Reject Response {#delivery-content-reject-response .unnumbered}

The ReturnInfo block containing one to many return code/description
combinations is populated.

#### Delivery Content Cancel Response {#delivery-content-cancel-response .unnumbered}

-   A CancelConfirmID is populated if the content is cancelled.

-   If the content cannot be cancelled, the ReturnInfo block containing
    one to many return code/description combinations is populated.

#### Delivery Appointment Shell Accept Response {#delivery-appointment-shell-accept-response .unnumbered}

-   The PreferredAppt element in the ApptBlock block is populated with
    the actual appointment date/time of the Scheduled appointment.

-   The ConsigneeApptID in the ResponseMsgHeaderInfo block is populated.

-   9-digit numeric ID will be returned for one-time appointment

-   5-digit numeric ID followed by the "R" character will be returned
    for recurring sequences

-   The OptionalAppt field is not returned in the response message.

#### Delivery Appointment Shell Reject Response {#delivery-appointment-shell-reject-response .unnumbered}

ReturnInfo block is populated with one or more return code/description
combinations.

#### Delivery Appointment Shell Cancel Response {#delivery-appointment-shell-cancel-response .unnumbered}

-   A CancelConfirmID is populated if the appointment shell is
    cancelled.

-   If the appointment cannot be cancelled, the ReturnInfo block is
    populated with one or more return code/description combinations.

#### Delivery Content Query Response {#delivery-content-query-response .unnumbered}

-   A USPSSummary block for each active content is populated.

-   If no Appointment matches are found, the ReturnInfo block containing
    one to many return code/description combinations is populated.

-   5-digit Scheduler IDs will be returned in place of full Scheduler
    IDs for all mail preparers and mail owners. A full Scheduler ID will
    be returned if the Scheduler ID is the same as the requestor's
    Scheduler ID or the creator's Scheduler ID.

#### Recurring Appointment Query Response {#recurring-appointment-query-response .unnumbered}

-   A RecurringApptBlk block is populated for each active or pending
    recurring sequence.

-   A USPSSummary block is populated for each active content.

-   If no Recurring Appointment matches are found, the ReturnInfo block
    is populated with one or more return code/description combinations.

-   Five-digit Scheduler IDs will be returned instead of full Scheduler
    IDs for all mail preparers and mail owners. A full Scheduler ID will
    be returned if the Scheduler ID is the same as the requestor's
    Scheduler ID or the creator's Scheduler ID.

-   The IDEAlliance specification allows for an unlimited number of USPS
    Summary blocks to be supplied in the Detail Information block.
    However, the maximum number of USPS Summary blocks allowed in any
    given message is 100.

-   The IDEAlliance specification allows a Pallets block within a given
    USPSSummary block to contain both presort counts and non-presort
    counts. For the USPS implementation, all non-presort counts must be
    added together and summarized into a single Pallets block. For
    example:

The IDEAlliance spec allows for the following:

Pallets Block 1: pallet count = 17

        Presort 1: 5 digit, Count = 4

        Presort 2: 3 digit, Count = 7

The USPS implementation requires the pallets to be broken into two
Pallets blocks:

Pallets Block 1: Count = 11

        Presort 1: 5 digit, Count = 4

        Presort 2: 3 digit, Count = 7

Pallets Block 2: Count = 6; No presort records

**NOTE**: If the total presort counts do not equal the pallet block
count for a pallet block, an error message will be returned.

-   The IDEAlliance specification allows actual piece count to be
    provided for presort and non-presort counts. FAST will only use the
    actual piece count for volume if it is provided for all presorts and
    non-presorts for a given USPSSummary block.

FAST will use the Actual Piece count for the following USPSSummary block
scenario:

Pallets Block 1: Count = 10

        Presort 1: 5 digit, Count = 5, Actual Piece Count = 100

        Presort 2: 3 digit, Count = 5, Actual Piece Count = 100

FAST will NOT use the Actual Piece count for the following USPSSummary
block scenario:

Pallets Block 1: Count = 10

        Presort 1: 5 digit, Count = 5, Actual Piece Count = 100

        Presort 2: 3 digit, Count = 5, Actual Piece Count Not Provided

FAST will NOT use the Actual Piece count for the following USPSSummary
block scenario:

Pallets Block 1: Count = 5, Actual Piece Count = 100

Pallets Block 2: Count = 5, Actual Piece Count Not Provided

-   The IDEAlliance specification allows multiple UniqueContainerBarcode
    elements to be included in a single USPS Summary block. The USPS
    implementation will store all UniqueContainerBarcode elements and
    will validate for uniqueness. Uniqueness is validated based on a
    45-day timeframe. UniqueContainerBarcodes associated to an
    appointment scheduled for 45 days in the past or for an appointment
    that has been cancelled or rejected are considered valid for re-use.
    If an appointment is no-showed, all associated
    UniqueContainerBarcodes are valid again after 12 days (288 hours).

-   The IDEAlliance specification allows multiple SiblingBarcode
    elements to be included in a single USPS Summary block. The USPS
    implementation will store all SiblingBarcode elements and will
    validate for uniqueness. Uniqueness is validated based on a 45-day
    timeframe.

-   The IDEAlliance specification allows for the SiblingBarcode and the
    UniqueContainerBarcode to be between 1 and 24 characters. FAST
    requires that the SiblingBarcode and the UniqueContainerBarcode be
    21 characters and begin with "99M".

-   The IDEAlliance specification allows multiple OptionalAppt elements
    to be included in a single Appointment block. The USPS
    implementation will only use the first OptionalAppt element; all
    others will be ignored. In addition, the OptionalAppt element will
    only be supported for the Delivery Appointment Query Request
    message.

-   The Facility Number should be populated with the facility Locale Key
    (characters 2-7 of the drop site key).

-   The VerificationZip4 element in the Mail.dat Summarization block is
    not required in the IDEAlliance specification. However, it is a
    required element for the USPS implementation when using the Mail.dat
    Summarization block because the VerificationZip4 element must be
    provided in order to retrieve the actual Mail.dat data.

-   Before any message is sent that requires the *PostalOne!* system to
    populate information from Mail.dat data, the Shipper must ensure the
    Mail.dat data that corresponds to the Appointment is up to date in
    the *PostalOne!* system prior to sending a Web Services request*.*

-   The Perishable element is a required field in the USPSSummary block.
    It does not exist in the Mail.dat. The *PostalOne!* system will set
    the Perishable element value to 'No' when the *PostalOne!* system
    populates an USPSSummary block with Mail.dat data.

-   For the Customer Registration Process, the user belonging to a
    Shipper must identify and verify his/her company's correct corporate
    headquarters (HQ) location ZIP (e.g., 22202-6761-000). The
    *PostalOne!* system will generate a 12-byte field for that nine
    digit Scheduler Corporate ZIP+4, e.g., 222026761000. The last three
    digits of a Scheduler Corporate ID will always be 000 (three zeros).
    This 'SchedulerCorporateID' will be provided by the *PostalOne!*
    system to all shippers via e-mail and it will be sent to the
    *PostalOne!* system with every Web Services transaction by the
    shipper. Each User must also be assigned a 'SchedulerID' by the
    *PostalOne!* system, which will be used to uniquely identify the
    scheduler entity. The 'SchedulerID' will be generated in the
    background and shown to the user on the screen.

The Scheduler ID will also be e-mailed to the user/Scheduler/Shipper, so
Shipper can always ensure the correct 'SchedulerID' is always part of
every Web Services message that is sent to USPS for identification
purposes. The Scheduler entity can be an internal business role within a
Shipper's organization, and will be tied to the Shipper's corporate
headquarters for FAST to rate the Shipper's corporation. The format of
the Scheduler ID will be location ZIP+4 format plus three bytes
(201486791001). A unique Scheduler ID will be generated in the ZIP+4
format with appended sequence numbers (always three digits and these
three digits will never be three zeros) and communicated to the user via
e-mail each time for a given Scheduler entity.

For example, the *PostalOne!* system will use the following example
format to identify Corp HQ and Scheduler Locations:

-   222021234000 - Corporate HQ (saved without the hyphen). Shipper MUST
    [not]{.underline} use a hyphen (-) when sending the SchedulerCorpID
    to USPS. The first nine digits will be the Corporate HQ ZIP+4 and
    the last three digits will be sequence numbers and will always be
    three zeros (000).

-   222021234100 - SchedulerID or Scheduler Entity ID (business role) at
    a given Shipper location (saved without the hyphen). Shipper MUST
    [not]{.underline} use a hyphen (-) when sending the SchedulerID to
    USPS. The last three digits will be sequence numbers and will never
    be three zeros.

```{=html}
<!-- -->
```
-   Do not send the same request repeatedly in succession if you did not
    receive an immediate response.  Sending the message repeatedly with
    the same ShipperApptRequestID for a given SchedulerID will result in
    an error. If you received a Tracking ID from the *PostalOne!*
    system, use that Tracking ID in the first response to retrieve your
    message.

-   The DeliveryContent messages can be used by Schedulers, Mail Owners
    and Mail Preparers to add, update, or cancel:

```{=html}
<!-- -->
```
-   Stand-alone content. FAST shall treat the content as stand-alone
    content if the ConsigneeApptID is not provided in the request
    message.

-   One-time content for an existing appointment. FAST shall treat the
    content as one-time content if the ConsigneeApptID provided in the
    request message is a nine-digit appointment ID.

-   Recurring content for an existing recurring sequence. FAST shall
    treat the content as recurring content if the ConsigneeApptID
    provided in the request message is a 5-digit recurring sequence ID
    followed by the character "R".

-   Add/update/remove a specific content for an appointment created by
    the Scheduler.

```{=html}
<!-- -->
```
-   The DeliveryContentUpdateRequest and DeliveryContentCancelRequest
    messages may only be used to update or cancel content that was
    created using the DeliveryApptContentCreateRequest message.

-   The DeliveryApptShellUpdateRequest may be used to update one-time
    and recurring appointment-level detail for an appointment with
    associated content; however, it may not be used to update the
    Facility of an appointment if the appointment has associated
    content. The DeliveryApptShellUpdateRequest may only be used to
    update the facility for one-time and recurring appointments with no
    associated content.

-   The DeliveryApptShellCancelRequest may only be used to cancel
    one-time appointment shells that have no associated content. The
    DeliveryApptCancelRequest should be used for any appointments that
    have associated content.

-   • The DeliveryApptShellCancelRequest may be used to cancel any
    recurring appointment that was previously created via Web Services.

-   An appointment created using Mail.XML Version 4.0 may be updated
    using Mail.XML Version 6.0. An appointment created using Mail.XML
    Version 6.0 may not be updated using Mail.XML Version 4.0.

-   Content created using Mail.XML Version 4.0 may be updated using
    Mail.XML Version 6.0. Content created using Mail.XML Version 6.0 may
    not be updated using Mail.XML Version 4.0. Content using Mail.XML
    Version 4.0 may not be added to an appointment that was last updated
    using Mail.XML Version 6.0.

-   The IDEAlliance specification allows multiple AdvanceMailingID
    elements to be included in a single USPSSummary block. FAST will
    only use the first AdvanceMailingID element and others will be
    ignored.

-   The SchedulerContentID in the DeliveryContentCreate,
    DeliveryContentUpdate and DeliveryContentCancel messages is an ID
    generated by the Scheduler and should be numeric with no alphabet
    characters.

-   The SchedulerContentID may be populated by the customer with a 12
    digit (or less) numeric value. If SchedulerContentID is not
    populated in a MailDatSummary block, the *PostalOne!* system will
    populate SchedulerContentID in both the MailDatSummary block and the
    corresponding USPS Summary block with a *PostalOne!*-generated
    alphanumeric field consisting of P followed by a sequence of 11
    digits or less. The SchedulerContentID will be populated in response
    messages with this value.

-   The FullContentReplacement field in the header of the
    DeliveryContentUpdateRequest may only be "Yes" if a ConsigneeApptID
    is provided. If the FullContentReplacement field is "Yes," FAST will
    cancel all content in an appointment created by the SchedulerID
    provided. If a ConsigneeContentID is provided in the
    DeliveryContentUpdateRequest, then the content will be updated and
    not canceled.

-   The PickupOrDelivery element is required in the
    RequestMsgHeaderInfo, ResponseMsgHeaderInfo and
    ResponseApptUpdateMsgHeaderInfo. FAST will only support requests
    messages with "Delivery" as a value for PickupOrDelivery. FAST will
    ignore "Pickup" as a value for PickupOrDelivery and always treat it
    as "Delivery".

-   The IDEAlliance specification allows MixedLengthTrays to be a valid
    palletHandlingUnitType for First-Class Mail. FAST shall convert all
    MixedLengthTrays to 2' Trays for First-Class mail.

-   The ConsigneeApptID, ScheduledInductionDate, LogisticsSchedulerID
    and LogisticSchedulerCorpID are not required in the
    DeliveryContentCreateRequest and DeliveryContentUpdateRequest
    messages. FAST requires either the ConsigneeApptID or all of the
    following fields be populated: ScheduledInductionDate,
    LogisticsSchedulerID and LogisticSchedulerCorpID.

-   FAST will be supporting First-Class as a MailClass in the
    DeliveryApptCreateRequest, DeliveryApptUpdateRequest and
    DeliveryApptQueryRequest. However FAST will not support a mix of
    both First-Class and drop ship contents on the same appointment.

-   The IDEAlliance specification allows for all enumerations of
    palletType regardless of the MailClass. FAST requires that the
    Standard, Package Services, Periodicals and Standard/Periodicals
    Co-Mailings contents have a palletType of "Pallet". All enumerations
    of palletType will be accepted for First-Class Mail contents.

### Detail Info Block {#detail-info-block .unnumbered}

![](media/image1.wmf)

Figure 2‑1. DetailInfo Block

## Multistop Support

The following is a breakdown of what is supported in the initial release
from a Multistop perspective:

### FAST Online Application {#fast-online-application .unnumbered}

-   Create a new Appointment and associate it to a new Multistop.

-   Create a new Appointment and associate it to an existing Multistop.

-   Disassociate an existing Appointment from a Multistop (the
    Appointment is still active but it is no longer associated with a
    Multistop).

-   Cancel the entire Multistop and therefore cancel all Appointments
    associated with that Multistop.

### Web Services {#web-services .unnumbered}

-   Create a new Appointment and associate it to a new Multistop.

-   Create a new Appointment and associate it to an existing Multistop.

**NOTES**:

-   An Appointment tied to a Multistop cannot be directly disassociated
    from that Multistop by the Web Services. The Appointment will have
    to be canceled and rescheduled without the Multistop information OR
    the Appointment can be disassociated online.

-   An existing Appointment cannot be added to an existing or new
    Multistop through online or Web Services. In both cases, the
    Appointment will have to be canceled and rescheduled with the
    Multistop information.

-   Note that anytime an Appointment is canceled, the overall Corporate
    rating may be impacted. Please see Mailer/Appointment Rating section
    of the *FAST User Guide* for more details on the rating calculation.

## Error Codes/Return Values

The IDEAlliance *TM-Spec-(version)Faults* specification outlines a set
of possible Return Code Values for that Mail.XML Spec version. The
IDEAlliance specification also allows implementation-specific Return
Code Values to be defined. For the IDEAlliance return codes supported in
the initial version of the USPS implementation, see Table 2-8. The USPS
implementation-specific Return Code Values are listed in Table 2-9.

Table 2‑8. IDEAlliance Return Codes

  ------------------------------------------------------------------------------------
  IDEAlliance                                                          
  Return Code                                                          
  Values                                                               
  ------------- ------------------------------------------------------ ---------------
  Code          Description                                            Supported?

  1000          Invalid Scheduler ID for Scheduler Corp ID             Yes

  1001          Invalid Scheduler Corp ID                              Yes

  1002          Unrecognized Facility                                  Yes\*

  1003          Appt Type not supported by the facility                No

  1004          Invalid ConsigneeApptID                                Yes

  1005          Invalid Multistop ID                                   Yes

  1006          Duplicate Unique Container IDs                         Yes

  1007          Appt Type not supported by Consignee                   No\*\*\*\*

  1008          Appt Type not supported by facility                    No

  1009          No slots available for that time / type -- dock limit  Yes

  1010          The volume requested for the following mail shape      Yes\*
                exceeded the maximum volume: \<Mail Shape\>            

  1011          Web Services/Online Appointments must be scheduled at  Yes\*
                least 1 hour in advance                                

  1012          Appointments may only be scheduled up to 14 days in    Yes\*
                advance                                                

  1013          Appt type limits exceeded                              No

  1014          Outside consignee defined timeframes for update/cancel No\*\*

  1015          Update/cancel refused -- appointment closed/canceled   Yes

  1016          Unrecognized Appointment -- field combinations do not  No
                match consignee data (generic)                         

  1017          Customer and Consignee Appointment ID do not           Yes\*
                correspond                                             

  1018          Requested appt date/time is past                       Yes

  1019          Update/Cancel not allowed, past consignee editable     No\*\*
                time threshold                                         

  1100          Mail.dat User License Code not supported by receiver   Yes

  1101          Mail.dat Job ID not in consignee database              Yes

  1102          Mail.dat DatabaseContainerID not in consignee database Yes

  1103          Mail.dat Verification Zip+4 not in consignee database  Yes

  1200          News content is only valid when Mail Class is          Yes\*
                Periodicals                                            

  1201          Perishable content is only valid when Mail Class is    Yes\*
                Package Services                                       

  1202          Invalid Mail Shape/ Handling Unit combination          Yes

  1203          In Home Start Date must be earlier than the In Home    Yes\*
                End Date                                               

  1300          Mail Class not supported by Consignee                  Yes

  1301          Processing Category not supported by Consignee         Yes

  1302          Presort Level not supported by Consignee               Yes

  1303          Mail Class not supported by Facility                   No

  1304          Processing Category not supported by Facility          No

  1305          Presort Level not supported by Facility                No

  1306          Rate Type and Postal class are inconsistent.           Yes

  1307          RateType Not Supported by Consignee                    Yes \*\*\*\*

  1400          Generic Update                                         No\*\*\*

  1401          Content Property Update                                No\*\*\*

  1402          Content Change                                         No\*\*\*

  1403          ETA Update                                             No\*\*\*

  1404          Action Requested by Consignee                          No\*\*\*

  1405          Delivery Appt Cancelled per request of consignee       Yes

  1406          Product combined into another existing appointment     Yes

  1407          Major change in expected delivery window               Yes

  1408          Product not available                                  Yes

  1409          Appt made in error -- human error                      Yes

  1500          Invalid Tracking ID                                    Yes

  1501          Tracking ID does not Match with Shipper                Yes

  1502          Come Back Later                                        Yes\*\*\*\*\*

  1503          InvalidRequestorSchedulerID for                        Yes
                RequestorSchedulerCorpID                               

  1504          InvalidRequestorSchedulerCorpID                        Yes

  1505          Appointment Closeout information unavailable           Yes
  ------------------------------------------------------------------------------------

\* - Indicates that the description listed is a more specific USPS
description than what is outlined in the IDEAlliance specification.

\*\* - Indicates that this specific code will not be returned but that
either the 1011, 1012 or 3010 code will be returned instead, depending
on what timeframe rule was violated.

\*\*\* - These codes will not be stored or used to implement any
business logic in the current USPS implementation.

\*\*\*\* - This specific code will not specifically be supported because
the USPS Implementation supports all Appointment types outlined in the
IDEAlliance specification. Therefore, if a request is received that
contains an invalid Appointment type it will simply fail XSD validation
and a Fault block will be returned.

\*\*\*\* - Indicates that this code will be returned if Package Services
is sent in. The Rate Type Package Services will be supported by FAST in
the future.

\*\*\*\*\* - This indicates Mailer need to come back again to get the
response for the Tracking ID request. This code is returned for TM
Specification 1.3 XSD and above.

**NOTE**: Error Codes 1405-1409 may be provided in the ReturnInfo block
of a DeliveryApptCancelRequest, DeliveryApptShellCancelRequest or
DeliveryApptContentCancelRequest to indicate the cancellation reason.

Table 2‑9. USPS Return Codes

+-----+----------------------------------------------------------------+
| *Po |                                                                |
| sta |                                                                |
| lOn |                                                                |
| e!* |                                                                |
| --  |                                                                |
| F   |                                                                |
| AST |                                                                |
| Ret |                                                                |
| urn |                                                                |
| C   |                                                                |
| ode |                                                                |
| Val |                                                                |
| ues |                                                                |
+=====+================================================================+
| C   | Description                                                    |
| ode |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Scheduler ID is not valid                                      |
| 000 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Scheduled Appointment time must be scheduled on the hour       |
| 001 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Customer and Consignee Multistop ID do not correspond          |
| 002 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Perishable content is only valid when Processing Category      |
| 003 | (Mail Shape) is Machinable Parcel, Outside Parcel              |
|     | (Non-Machinable Parcel), or Irregular Parcel                   |
+-----+----------------------------------------------------------------+
| 3   | Optional Appointment Start Time must be before the Optional    |
| 004 | End Time                                                       |
+-----+----------------------------------------------------------------+
| 3   | Optional Appointment Start Time must be within 8 hours of the  |
| 005 | Optional End Time                                              |
+-----+----------------------------------------------------------------+
| 3   | The time difference between the first and last appointment of  |
| 006 | a multi-stop must be within 24 hours                           |
+-----+----------------------------------------------------------------+
| 3   | Appointment date/time must be earlier than In Home Start Date  |
| 007 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Number of USPSSummary blocks exceeded maximum limit of 100     |
| 008 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | A Speedline Appointment cannot have more than 6 pallet         |
| 009 | positions                                                      |
+-----+----------------------------------------------------------------+
| 3   | Appointments must be updated at least 1 hour in advance        |
| 010 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Facility does not accept drop shipments.                       |
| 011 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | An appointment with this Scheduler ID and Scheduler            |
| 012 | Appointment Request ID already exists                          |
+-----+----------------------------------------------------------------+
| 3   | Valid content count must be present for each USPS Summary      |
| 013 | block                                                          |
+-----+----------------------------------------------------------------+
| 3   | You have experienced an error with the application. Please     |
| 014 | contact your FAST or Web Services system administrator for     |
|     | help                                                           |
+-----+----------------------------------------------------------------+
| 3   | A Pallet Appointment must have a Count of Pallets Containing   |
| 015 | Trays, Sacks, Bundles or Parcels                               |
+-----+----------------------------------------------------------------+
| 3   | Bedload and Drop and Pick Appointments may not have a Count of |
| 016 | Pallets Containing Sacks, Trays, Bundles, or Parcels           |
+-----+----------------------------------------------------------------+
| 3   | A Speedline Appointment may not have a Bedloaded Tray, Sack,   |
| 017 | Bundle or Parcel Count                                         |
+-----+----------------------------------------------------------------+
| 3   | Default Facility:                                              |
| 018 |                                                                |
|     | Error Message Format:                                          |
|     |                                                                |
|     | \<CIN Group\> are not accepted at this facility. Please create |
|     | an appointment at \<NASS Code -- Facility Name\>.              |
|     |                                                                |
|     | Error Message Example:                                         |
|     |                                                                |
|     | Standard/Flats are not accepted at this facility. Please       |
|     | create an appointment at 100 -- New York.                      |
|     |                                                                |
|     | Non-default Facility:                                          |
|     |                                                                |
|     | Error Message Format:                                          |
|     |                                                                |
|     | \<CIN Group\> are not accepted at this facility. Please refer  |
|     | to the Mail Direction Search Report or Drop Ship Product for   |
|     | the correct accepting facility.                                |
|     |                                                                |
|     | Error Message Example:                                         |
|     |                                                                |
|     | Standard/Flats are not accepted at this facility. Please refer |
|     | to the Mail Direction Search Report or Drop Ship Product for   |
|     | the correct accepting facility.                                |
+-----+----------------------------------------------------------------+
| 3   | A Speedline Appointment cannot have more than 24 total pallets |
| 019 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Application cannot get response for the given tracking ID (    |
| 020 | Refer Notes below)                                             |
+-----+----------------------------------------------------------------+
| 3   | A USPSSummary type was not provided in any of the DetailInfo   |
| 021 | blocks (See Notes below)                                       |
+-----+----------------------------------------------------------------+
| 3   | Invalid Mail Preparer ID                                       |
| 022 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Mail Owner ID                                          |
| 023 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Publication ID                                         |
| 024 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Update/cancel refused -- content does not exist                |
| 027 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Mail Class for Appointment                             |
| 028 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | No update to Content made                                      |
| 029 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Publications only valid when Mail Class is Periodicals         |
| 030 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid TM Spec Version                                        |
| 031 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Content may not be cancelled -- appointment must have at least |
| 032 | one content                                                    |
+-----+----------------------------------------------------------------+
| 3   | Invalid ConsigneeContentID                                     |
| 033 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Scheduler ID does not correspond to Scheduler ID for content   |
| 034 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Scheduler ID and Appointment ID do not correspond              |
| 035 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Facility ID and Appointment ID do not correspond               |
| 036 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Appointment may not be cancelled -- appointment has associated |
| 037 | content -- please use the DeliveryApptCancelRequest message to |
|     | cancel this appointment                                        |
+-----+----------------------------------------------------------------+
| 3   | Invalid ConsigneeApptID -- Appointment is not a Web Services   |
| 038 | appointment                                                    |
+-----+----------------------------------------------------------------+
| 3   | RecurringAppt block not supported by Consignee                 |
| 039 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Update refused -- may not change facility for this appointment |
| 040 | -- this appointment has associated content                     |
+-----+----------------------------------------------------------------+
| 3   | Web Services appointments/contents may not be cancelled        |
| 041 | greater than 24 hours past the appointment date/time           |
+-----+----------------------------------------------------------------+
| 3   | Invalid TM Spec Version -- Mailer not certified for TM Spec    |
| 042 | Version                                                        |
+-----+----------------------------------------------------------------+
| 3   | Content update/cancel refused -- content was not created by a  |
| 043 | DeliveryApptContentCreateRequest message                       |
+-----+----------------------------------------------------------------+
| 3   | Invalid TM Spec Version -- Appointment has been previously     |
| 044 | updated with a higher version                                  |
+-----+----------------------------------------------------------------+
| 3   | Pallet Presort Level Counts must equal Pallet Level Counts     |
| 045 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Incorrect WSDL used to send TM2.0 Appointment Message          |
| 046 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | A Drop and Pick Appointment Type may not be a Multi-Stop       |
| 047 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid cancellation reason                                    |
| 048 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Scheduler for appointment must use the DeliveryApptUpdate      |
| 049 | message to add/update content(s)                               |
+-----+----------------------------------------------------------------+
| 3   | Invalid Unique Container ID -- Container ID must be 21-digits  |
| 050 | and begin with 99M                                             |
+-----+----------------------------------------------------------------+
| 3   | No content associated to appointment                           |
| 051 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Mailer must provide FAST content ID on update using a          |
| 052 | DeliveryApptContentUpdateRequest or a                          |
|     | DeliveryContentUpdateRequest Message                           |
+-----+----------------------------------------------------------------+
| 3   | BMC discount for Periodicals is only valid for cross-docked    |
| 053 | pallets                                                        |
+-----+----------------------------------------------------------------+
| 3   | Truck lengths \<range\> \<truck length\> ft are not accepted   |
| 055 | at \<NASS Code - Facility Name\>. Please refer to the Mail     |
|     | Direction Search Report or Drop Ship Product for the correct   |
|     | accepting facility.                                            |
+-----+----------------------------------------------------------------+
| 3   | Truck lengths \<range\> \<truck length\> ft are not accepted   |
| 056 | at \<NASS Code - Facility Name\>. Please refer to the Mail     |
|     | Direction Search Report or Drop Ship Product for the correct   |
|     | accepting facility.                                            |
+-----+----------------------------------------------------------------+
| 3   | No slots available for the requested time/type due to tiering  |
| 057 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Number of Pallet Positions must be specified when Appointment  |
| 058 | Type is Speedline                                              |
+-----+----------------------------------------------------------------+
| 3   | Facility cannot be modified for recurring appointment          |
| 059 | instances.                                                     |
+-----+----------------------------------------------------------------+
| 3   | Effective Start Date must be 14 days in the future             |
| 060 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Effective Start Date must be before the Effective End Date     |
| 061 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Day Frequency/Week Frequency Combination. A Day        |
| 062 | Frequency of Daily must have a Week Frequency of Weekly        |
+-----+----------------------------------------------------------------+
| 3   | eVS Indicator is only valid when Processing Category (Mail     |
| 063 | Shape) is Machinable Parcel, Outside Parcel (Non-Machinable    |
|     | Parcel), or Irregular Parcels                                  |
+-----+----------------------------------------------------------------+
| 3   | eVS Indicator is only valid when Mail Class is Standard,       |
| 064 | Package Services or First-Class                                |
+-----+----------------------------------------------------------------+
| 3   | eFile Number is only valid when eVS Indicator is Yes           |
| 065 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | The eFile Number must be 22 digits                             |
| 066 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Priority Mail Indicator is only valid when Mail Class is       |
| 067 | First-Class                                                    |
+-----+----------------------------------------------------------------+
| 3   | \<Pallet Type\> is only valid when the Mail Class is           |
| 068 | First-Class                                                    |
+-----+----------------------------------------------------------------+
| 3   | Either the appointment ID or all of the following fields are   |
| 069 | required: scheduled induction date, logistic scheduler ID and  |
|     | logistic scheduler Corp ID                                     |
+-----+----------------------------------------------------------------+
| 3   | Scheduled Induction Date cannot be in the past                 |
| 070 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Logistic Scheduler ID                                  |
| 071 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Requestor Scheduler ID                                 |
| 072 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Requestor Scheduler Corp ID                            |
| 073 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Requestor Scheduler ID for Requestor Scheduler Corp ID |
| 074 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid TM Spec Version - Content has been previously updated  |
| 075 | with a higher version                                          |
+-----+----------------------------------------------------------------+
| 3   | Invalid Creator Scheduler ID for Creator Scheduler Corp ID     |
| 076 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Creator Scheduler Corporate ID                         |
| 077 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Creator Scheduler ID is not valid                              |
| 078 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Facility Locale Key is required for this message               |
| 079 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid SchedulerContentID/ConsigneeContentID combination      |
| 080 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | ConsigneeApptID is required to update associated content       |
| 082 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Content has been previously associated to an appointment       |
| 083 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid SchedulerID -- Scheduler ID provided is not the        |
| 084 | Logistic Scheduler                                             |
+-----+----------------------------------------------------------------+
| 3   | No more than 100 Contents may be associated to a single        |
| 085 | appointment                                                    |
+-----+----------------------------------------------------------------+
| 3   | The total volume of Bedload contents may not exceed 9999       |
| 086 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | The total volume of Pallet, Hamper, APC/ERMC and Wire          |
| 087 | Container contents may not exceed 9999                         |
+-----+----------------------------------------------------------------+
| 3   | Invalid SchedulerContentID                                     |
| 088 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Appointment Time not within Facility hours of operation        |
| 089 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | The only valid handling units for a First-Class Appointment    |
| 090 | are 1\' Tray, 2\' Tray, EMM Tray, Flat Tub, Parcels and Sacks  |
+-----+----------------------------------------------------------------+
| 3   | Consignee does not accept First-Class appointments at this     |
| 091 | facility                                                       |
+-----+----------------------------------------------------------------+
| 3   | Unable to associate stand-alone content (ConsigneeContentID    |
| 092 | \<Content ID\>) - content cancelled                            |
+-----+----------------------------------------------------------------+
| 3   | Your search did not return any result                          |
| 093 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | A recurring appointment with this Scheduler ID and Shipper     |
| 094 | Appointment Request ID already exists.                         |
+-----+----------------------------------------------------------------+
| 3   | Effective End Date must not be greater than 12/31/2999         |
| 095 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Recurring Frequency                                    |
| 096 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | The Priority Mail indicator is only valid on First-Class       |
| 098 | Contents                                                       |
+-----+----------------------------------------------------------------+
| 3   | At least 1 Pallet/Bedload count must be provided               |
| 099 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | A one day In-Home Date Range may not be on a Sunday            |
| 102 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Logistic Scheduler Corp ID                             |
| 103 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Invalid Logistic Scheduler ID for Logistic Scheduler Corp ID   |
| 104 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Full content replacement is only valid when the Consignee      |
| 105 | Appointment ID is provided                                     |
+-----+----------------------------------------------------------------+
| 3   | Consignee does not support \<Mail Class\> for this message     |
| 106 | type.                                                          |
+-----+----------------------------------------------------------------+
| 3   | Update/Cancel Refused -- Content is Closed/Cancelled           |
| 107 |                                                                |
+-----+----------------------------------------------------------------+
| 3   | Appointment can not contain both drop ship and First-Class     |
| 108 | contents                                                       |
+-----+----------------------------------------------------------------+

**NOTE**:

-   Return code 3018 refers to the Appointment Scheduling and Management
    Drop Ship Product Validation Process. The new functionality will
    provide online validation to verify if the selected facility can
    accept the mail contents on the requested appointment. FAST will
    utilize the drop ship product ZIP/CIN file. If an appointment passes
    the CIN group (mail class/mail shape combinations) validation,
    normal processing will continue as it does today; however, if it
    fails the CIN group validation, an error message or warning message
    will be displayed. The error message will notify the user of the
    type of content(s) that cannot be accepted at the specified facility
    and which facility those contents should be redirected to for
    processing. The warning message will notify the user that potential
    redirections may exist and provides additional facility information
    for the user to reference. In both cases, the user is provided a
    hyperlink to the 'facility profile -- additional information' page
    to view specific redirections.

-   Return code 3020 is used to indicate the application cannot get a
    response for this 'TrackingID'. The reason could be the Mailer is
    using the 'TrackingID' for which they have already obtained a
    response. This code is supported TM Specification XSD 1.3 and above.
    This is related to another code, 1502, which indicates the response
    is not available now and the Mailer needs to come back again later
    to get a response.

-   Return code 3021 is used to indicate that the XML message does not
    contain any USPSSummary blocks in any of the DetailInfo blocks.
    USPSSummary blocks provide content information, and appointment
    create, update, and query messages cannot be processed without
    content information. Thus, at least one USPSSummary block must be
    present in at least one DetailInfo block.

-   Error Codes 3022 and 3023 are used to validate that the Mail
    Preparer ID and any Mail Owner IDs are valid FAST Scheduler IDs.

-   Error Codes 3025 and 3026 are not included because they are used for
    Mail.dat Recurring Content Notifications as Error Codes specific to
    this message type that FAST sends to the *PostalOne!* system that
    are.

-   Error Code 3031 would be returned in a Fault Response.

-   Error Code 3028 indicates whether the mail class for content is
    accepted for the appointment. When an appointment shell is created,
    the Scheduler indicates which Mail Classes are accepted for that
    appointment. When a DeliveryApptRequest or DeliveryApptUpdateRequest
    is made, only contents with the same mail class as existing contents
    for that appointment may be added using the DeliveryApptContent
    message request and update types.

-   Error Code 3034 is used if a Scheduler who is not associated to the
    same corporation as the Scheduler who created the content attempts
    to update or cancel the content.

-   Error Codes 3035 and 3036 are used to validate that the Scheduler ID
    and Facility ID match the Appointment ID given in a Delivery Content
    Query message.

-   Error Code 3037 is returned if a DeliveryApptShellCancelRequest is
    sent to cancel an appointment that has associated content. The
    DeliveryApptCancelRequest should be used in this scenario.

-   Error Code 3046 Mailers will receive this error messages if they
    used incorrect WSDL to send TM V2.0 Appointment messages.

## CIN Warning Codes and Descriptions

The following CIN Warnings are returned in the ReturnInfo block of
accept messages where they occur. This applies to the following message
types:

-   DeliveryApptCreateAcceptResponse

-   DeliveryApptUpdateAcceptResponse

-   DeliveryApptQueryResponse

-   DeliveryApptContentCreateAcceptResponse

-   DeliveryApptContentUpdateAcceptResponse

Table 2‑10. CIN Warnings Supported

  ----------------------------------------------------------------------------------
  *PostalOne!* --                                   
  FAST CIN                                          
  Warnings                                          
  Supported for                                     
  Mail.XML                                          
  Version 4.0 and                                   
  6.0                                               
  --------------- --------------------------------- --------------------------------
  Code            Warning Description Text          Warning Explanation

  [4000]{.mark}   Some \< cin group \> are accepted If scheduling at a default
                  at this Facility. Please refer to facility that has a complete
                  the Mail Direction Search Report  redirection, but not all
                  or Drop Ship Product for the      discounts or ZIP Codes (in the
                  correct accepting facility.       case of Delivery Units) are
                                                    redirected.

  [4001]{.mark}   Some \< cin group \> are          If scheduling at a redirect
                  redirected to \< redirect         facility that has a complete
                  facility \>. Please refer to the  redirection, but not all
                  Mail Direction Search Report or   discounts or ZIP Codes (in the
                  Drop Ship Product for the correct case of Delivery Units) are
                  accepting facility.               redirected.

  [4002]{.mark}   \< CIN Group \> are being         If scheduling at a default
                  redirected to \< redirect         facility that has a complete
                  facility \>. The grace period     redirection, but the default
                  ends \<grace date\>.              grace date of this redirection
                                                    has not yet expired.

  [4003]{.mark}   \< cin group \> processing will   If scheduling at a redirect
                  no longer be performed at this    facility that has an expired
                  facility. Please refer to the     complete redirection from a
                  Mail Direction Search or Drop     default, but that redirection is
                  Ship Product for the correct      still in the grace period.
                  accepting facility. The grace     
                  period ends \<grace date\>.       

  [4004]{.mark}   This facility currently accepts   [If scheduling at a default
                  \<CIN Group\>, however, on        facility that currently has no
                  \<redirection start date\>; \<CIN complete redirections, but a new
                  Group\> will be redirected to     redirection will become active
                  \<redirect facility\>. Please     in 75 days or less]{.mark}
                  adjust your appointments          
                  accordingly.                      

  [4005]{.mark}   Some \< cin group \> redirections [If scheduling at a redirect
                  to this facility expire before \< facility that currently has at
                  date redirection expires \>.      least one redirection to it, but
                  Please refer to the Mail          at least one of those
                  Direction Search Report or Drop   redirections will expire in 75
                  Ship Product for the correct      days or less]{.mark}
                  accepting facility.               

  [4006]{.mark}   Truck lengths \<range\> \<truck   [If scheduling at a default
                  length\> ft are not accepted at   facility with a truck length
                  \<NASS Code -- Facility Name\>.   that falls within the truck
                  If your truck length is \<range\> length redirection]{.mark} and
                  \<truck length\> ft, please       the default grace date that has
                  create an appointment at \<NASS   not yet expired.
                  Code -- Facility Name\>.          

  [4007]{.mark}   Truck lengths \<range\> \<truck   An appointment is scheduled at a
                  length\> ft are not accepted at   default facility where a
                  \<NASS Code -- Facility Name\>.   truck-length redirection exists,
                  If your truck length is \<range\> and is not within the grace
                  \<truck length\> ft, please       period and/or no truck length is
                  create an appointment at \<NASS   provided for the appointment.
                  Code -- Facility Name\>.          

  [4008]{.mark}   Truck lengths \<range\> \<truck   An appointment is scheduled at a
                  length\> ft are not accepted at   redirect facility where a truck
                  \<NASS Code -- Facility Name\>.   length redirection exists and it
                  If your truck length is \<range\> is within the grace period.
                  \<truck length\> ft, please refer 
                  to the Mail Direction Search      
                  Report or Drop Ship Product for   
                  the correct accepting facility.   

  [4009]{.mark}   Truck lengths \<range\> \<truck   An appointment is scheduled at a
                  length\>ft are not accepted at    redirect facility where a truck
                  \<NASS Code -- Facility Name\>.   length redirection exists, and
                  If your truck length is \<range\> it is not within the grace
                  \<truck length\> ft, please refer period and no truck length is
                  to the Mail Direction Search      provided for the appointment.
                  Report or Drop Ship Product for   
                  the correct accepting facility.   

  [4010]{.mark}   BMC discount for Periodicals is   An appointment is scheduled for
                  only valid for cross-docked       Palletized Periodicals for BMC
                  pallets.                          discount.

  [4011]{.mark}   \< cin group \> processing will   An appointment is scheduled at a
                  no longer be performed at this    default facility where the
                  facility. Please refer to the     effective end date has expired,
                  Mail Direction Search or Drop     but is still in the grace
                  Ship Product for the correct      period.
                  accepting facility. The grace     
                  period ends \<grace date\>.       

  [4012]{.mark}   The Bill of Lading Number,        A leg of a multi-stop
                  Shipper Name and Vehicle ID will  appointment has been created or
                  be updated for the following open updated, and the Bill of Lading
                  appointments that are associated  Number, Shipper Name or Vehicle
                  to multi-stop ID \<multi-stop     ID is different from the
                  id\>: \<appointment ID list\>.    existing corresponding fields
                                                    for the multi-stop appointment.

  4013            Your recurring appointment        If a recurring appointment
                  request has been successfully     sequence is updated in such a
                  created. An email notification of way that a pending request is
                  the request has been sent to the  created (e.g. content or
                  facility for review. After        logistics updated on a recurring
                  review, an email response will be appointment sequence which is
                  sent to you                       not pure Periodicals.)

  4014            Your recurring appointment has    If a recurring appointment
                  been successfully updated. An     sequence is updated and
                  informational email notification  auto-approved (e.g. content or
                  of the approved request has been  logistics updated on a recurring
                  sent to the facility and the      appointment sequence, which is
                  scheduler                         pure Periodicals.)

  4015            This recurring sequence is        If a pending recurring
                  pending facility approval         appointment sequence request is
                                                    returned in a
                                                    RecurringApptQueryResponse.

  4017            Your recurring appointment has    If a recurring appointment
                  been successfully created. Your   sequence is created or updated
                  recurring appointment currently   and there is no associated
                  has no contents. Appointments     content.
                  will not be generated for this    
                  Recurring Appointment while there 
                  are no contents.                  

  4018            The requested appointment date,   If standard content has an
                  time, and in-home date are not    in-home date range of one day
                  synchronized with USPS service    and is being scheduled at a
                  standards. A shipment with a      facility that accepts BMC
                  one-day in-home date claiming a   Standard mail.
                  BMC discount must be scheduled to 
                  arrive by 16:00, five (5) days    
                  prior to the specified in-home    
                  date.                             

  4019            The requested appointment date    If standard content has an
                  and time and in-home date are not in-home date range of one day
                  in sync with USPS service         and is being scheduled at a
                  standards. A shipment with a one  facility that accepts SCF
                  day in-home date claiming a SCF   Standard mail.
                  discount must be scheduled to     
                  arrive by 16:00, three (3) days   
                  prior to the specified in-home    
                  date                              

  4020            The requested appointment date    If standard content has an
                  and time and in-home dates are    in-home date range of more than
                  not in sync with USPS service     one day and is being scheduled
                  standards. A shipment with an     at a facility that accepts BMC
                  in-home date range claiming a BMC Standard mail.
                  discount must be scheduled to     
                  arrive by 16:00, five (5) days    
                  prior to the second day of the    
                  in-home date range.               

  4021            The requested appointment date    If standard content has an
                  and time and in-home dates are    in-home date range of more than
                  not in sync with USPS service     one day and is being scheduled
                  standards. A shipment with an     at a facility that accepts SCF
                  in-home date range claiming a SCF Standard mail.
                  discount must be scheduled to     
                  arrive by 16:00, three (3) days   
                  prior to the second day of the    
                  in-home date range.               
  ----------------------------------------------------------------------------------

Please note that any error or warning messages listed above will be
limited to the acceptable field lengths provided in the Mail.XML
Specification. This could cause a message to be truncated if it exceeds
the acceptable field length.

## Fault Codes

In addition to the above return codes, the IDEAlliance
*TM-Spec-v0Faults* specification also defines a set of possible faults
that are used to convey system or operational information. Unlike return
codes, faults codes are only three-digit long and they are communicated
using the Fault element within the detail section of the SOAP fault. The
Mail.XML specification further mandates that the following codes must be
understood by all receivers:

Table 2‑11. Fault Codes

  ----------- -----------------------------------------------------------
  Faults      Description

  320         Incompatible SOAP Protocol Version

  400         Generic Request Error

  401         Incomplete/Cannot Parse

  402         Not Well Formed XML

  403         Validation Failure

  404         This Error Intentionally Left Blank

  405         Unrecognized Sender

  407         Unrecognized Operation

  408\*       Unrecognized Operation Arguments

  410         Not Found

  412         Unauthorized

  413         Forbidden

  430         Not Confirmed

  431         Failure Fetching External Data

  440         Sorry

  500         Generic Internal Responder Error

  501         Temporary Responder Problem

  503         Not Implemented
  ----------- -----------------------------------------------------------

\* - The fault description will contain additional info about the
offending operation argument.

## Web Service Additional Constraints

In addition to conforming to everything stated in the WSDL file, all XML
inputs to the Appointment Services operations must qualify the XML
elements and attributes with their associated namespace. As an example,
following is a good ApptResponseRetrieval input message to the operation
RetrieveAppointmentResponse:

## Message Response Retrieval Request Processing

The *PostalOne!* system will generate the response to a
MessageResponseRetrievalRequest based on the Mail.XML specification
version of the Request message.

The *PostalOne!* system will provide the Web Services Users with the
capability to re-request the message responses using the generated
TrackingIDs multiple times with a MRRR within 30 days of initial
response receipt from FAST. The *PostalOne!* system will provide the
users with the latest response from FAST in case where there are
multiple appointment responses for the same TrackingID.

## *PostalOne!* WSDL Information

To support IDEAlliance Mail.XML Specification changes and the newly
added Appointment messages types, the *PostalOne!* system will create a
new WSDL.  Mailers are encouraged to use the new WSDL even if they plan
to continue sending and receiving web services requests using previous
version of IDEAlliance TM and Mail.XML Appointment requests.

The WSDLs for Release 1 are available in an appendix of this document
and on RIBBS.

Mailers can access and download the currently supported versions of the
*PostalOne!* WSDL from the following location:
<http://www.usps.com/postalone/autodropshipschedule.htm>.

## SchedulerContent ID

The *PostalOne!* system (Mail.XML Web Services) will generate
SchedulerContent ID only if the mailer has set the
'IncludeInSummarizationblock' to 'No'. Mail.XML Web Services will
generate the USPS Summary Block and reference Scheduler Content ID. The
Scheduler Content ID will be an alphanumeric of the format P###\... (=
P & up to 11 digit sequence number). The prefixing is used to inform
FAST that this Scheduler Content ID has been generated by Mail.XML Web
Services.  Customer will be informed to use up to 12-digit number if
they are populating this information in the appointment message. 

## Closeout Messages

FAST will generate a single closeout message for each appointment. The
Mail.XML Spec version used to generate the message will be determined as
follows:

Closeout messages will be generated by FAST using the latest version of
Mail.XML Specification used to create or update the appointment. If the
latest version of the Mail.XML Specification used to create or update
the appointment is no longer supported, the latest supported version for
which the scheduler is approved will be used for the closeout message.
By the release of the Full-service program, the latest supported version
of Mail.XML is Mail.XML 6.0. For example, if an appointment was created
using Mail.XML Version 4.0, then updated using Mail.XML Version 6.0, the
ConsigneeGoodsReceipt will be generated using Mail.XML Version 6.0. If
an appointment is created/updated using Mail.XML version 4.0 and never
updated using Mail.XML Version 6.0, the ConsigneeGoodsReceipt will be
generated using Mail.XML Version 4.0.

Closeout messages for Unscheduled appointments will be generated using
the latest supported version of Mail.XML for which the scheduler has
completed testing. For example, if the scheduler has completed testing
for Mail.XML 4.0, the UnscheduledConsigneeGoodsReceipt will be generated
using Mail.XML 4.0. If the scheduler has completed testing for Mail.XML
6.0, the UnscheduledConsigneeGoodsReceipt will be generated using
Mail.XML 6.0. If the scheduler has completed testing for both Mail.XML
4.0 and Mail.XML 6.0, the UnscheduledConsigneeGoodsReceipt will be
generated using Mail.XML 6.0.

The *PostalOne!* system will generate the Closeout Response using the
same Mail.XML version as the one used to generate the Closeout Request.
A customer who has appointments for both Mail.XML 4.0 and Mail.XML 6.0
will need to send a separate Closeout Request to retrieve closed
appointments for Mail.XML 4.0 and Mail.XML 6.0.

The total number of 'consignee goods receipt' and 'unscheduled consignee
good receipts' included in the closeout response is currently set to a
maximum of 200 messages per response.

## Appointment Shell Cancellation Messages

FAST will support the cancellation of Appointment Shells using both the
Delivery Appointment Shell Cancel Request message and Delivery
Appointment Cancellation Request Message; however, Appointment with
contents can be cancelled using the Delivery Appointment Cancellation
Request Message. Recurring appointment shells can only be cancelled
using the Delivery Appointment Shell Cancel request.

# PostalOne! -- eDoc Mail.XML Messages 

## Overview

This section will discuss the technical information related to the
*PostalOne!*-Mail.XML Web Services messages that support all eDoc and
miscellaneous functionality related mailer interaction with the
*PostalOne!* system in managing, updating and querying mail contents and
to supplement the Mail.dat functionality such as postage payment,
qualification and content reports, container updates, container status
checking for eDropShip, Cast of Characters and co-palletization
messages. The *PostalOne!* system will support the new and enhanced
version of these messages as described in the external timeline made
available to the MTAC 122 work group.

## eDoc and Miscellaneous Messages

Messages that will be supported by the *PostalOne!* system Full-Service
Release 2 using Mail.XML 6.0

As part of *PostalOne!* support to Full-service program, Mail.XML 6.0
Web Services messages will provide an alternative to and replace the
current Wizard Web Services (WWS) in the *PostalOne!* system. Mail.XML
will be the overall umbrella specification that will contain all of the
current WWS functionality, along with existing Transportation and
appointment management as well as extra eDoc messages to support
Full-service such as piece detail, piece range, Periodicals reports and
postage statements and combined mailing data.

Mail.XML eDOC Web Service Messages will allow business customers to
submit and receive postal documents electronically via Web Services.
Mail.XML is an alternative to the Mail.dat flat file specification that
works as the whole database of information unlike Mail.XML, which is
used for business specific communication.

The following messages are supported in Release 2 of *PostalOne!*
Full-Service:

Table 3‑12. Mail.XML Messages Supported in Full-service Release 2.0

  ----------------------------------------------------------------------------------------
  Mail.XML v6.0 Errata-A Full-Service Release 2   
  Messages                                        
  ----------------------------------------------- ----------------------------------------
  OpenMailingGroupRequest                         PostageAdjustmentCreateRequest

  OpenMailingGroupResponse                        PostageAdjustmentCreateResponse

  MailingGroupQueryRequest                        EndCombinedMailingRequest

  MailingGroupQueryResponse                       EndCombinedMailingResponse

  CloseMailingGroupRequest                        BeginCombinedMailingRequest

  CloseMailingGroupResponse                       BeginCombinedMailingResponse

  QualificationReportCreateRequest                PaymentMessageQueryRequest

  QualificationReportCreateResponse               PaymentMessageQueryResponse

  QualificationReportQueryRequest                 ReconciliationReportQueryRequest

  QualificationReportQueryResponse                ReconciliationReportQueryResponse

  PostageStatementCancelRequest                   ByForConflictDelivery

  PostageStatementCancelResponse                  ByForConflictNotification

  PostageStatementCreateRequest                   ByForConflictQueryRequest

  PostageStatementCreateResponse                  ByForConflictQueryResponse

  MailPieceCancelRequest                          MailDatContainerUpdateRequest

  MailPieceCancelResponse                         MailDatContainerUpdateResponse

  MailPieceCreateRequest                          SibilingContainerCancelRequest

  MailPieceCreateResponse                         SiblingContainerCancelResponse

  MailPieceUpdateRequest                          SibilingContainerCreateRequest

  MailPieceUpdateResponse                         SiblingContainerCreateResponse

  BundleDetailCreateRequest                       OriginalContainerLinkageCancelRequest

  BundleDetailCreateResponse                      OriginalContainerLinkageCancelResponse

  ContainerBundleReportCreateRequest              OriginalContainerLinkageCreateRequest

  ContainerBundleReportCreateResponse             OriginalContainerLinkageCreateResponse

  PeriodicalStatementCancelRequest                USPSCRIDCreateRequest

  PeriodicalStatementCancelResponse               USPSCRIDCreateResponse

  PeriodicalStatementCreateRequest                USPSCRIDQueryRequest

  PeriodicalStatementCreateResponse               USPSCRIDQueryResponse

  PeriodicalStatementQueryRequest                 USPSMIDCreateRequest

  PeriodicalStatementQueryResponse                USPSMIDCreateResponse

  PostageStatementQueryRequest                    USPSMIDQueryRequest

  PostageStatementQueryResponse                   USPSMIDQueryResponse

  PostageStatementStatusQueryRequest              SystemVersionQueryRequest

  PostageStatementStatusQueryResponse             SystemVersionQueryResponse

  ConsolidatedPeriodicalStatementCreateRequest    MessageResponseRetrievalRequest

  ConsolidatedPeriodicalStatementCreateResponse   MessageResponseRetrievalResponse

  Miscellaneous Messages in Release 1             

  MailingGroupQueryRequest                        

  MailingGroupQueryResponse                       

  PaymentMessageQueryRequest                      

  PaymentMessageQueryResponse                     

  ReconciliationReportQueryRequest                

  ReconciliationReportQueryResponse               

  ContainerStatusQueryRequest                     

  ContainerStatusQueryResponse                    
  ----------------------------------------------------------------------------------------

Table 3‑13. Mail.XML Messages Not Supported in Full-service Release 1.0
or 2.0

  -----------------------------------------------------------------------
  Messages NOT Supported for eDoc by the USPS in Full-Service Release 1
  or Release 2
  -----------------------------------------------------------------------
  ContainerBundleReportCancelRequest

  ContainerBundleReportCancelResponse

  ContainerBundleReportUpdateRequest

  ContainerBundleReportUpdateResponse

  BundleDetailCancelRequest

  BundleDetailCancelResponse
  -----------------------------------------------------------------------

All eDoc messages have a submitting Party and submitting software.

### Submitting Party {#submitting-party .unnumbered}

Table 3‑14. Submitting Party Attributes

  -----------------------------------------------------------------------------
  Field                Format and    Required or Not
                       Values        
  -------------------- ------------- ------------------------------------------
  MailerID6            Numeric       Optional -- Either CRID or MID is required
                       String 6      for Data Distribution messages

  MailerID9            Numeric       Optional -- Either CRID or MID is required
                       String 9      for Data Distribution messages

  CRID                 String 10     Optional -- Either CRID or MID is required
                                     for Data Distribution messages

  SchedulerID          String 12     Optional -- Must be used for FAST specific
                                     messages

  MaildatUserLicense   String 4      Optional -- The USPS will use this field
                                     for messages that end in the word
                                     'Notification' or 'Delivery' which are
                                     PUSH messages and will have a value of
                                     'USPS' in this field for the Push messages
                                     from the USPS to the customer.
  -----------------------------------------------------------------------------

### Submitting Software {#submitting-software .unnumbered}

Table 3‑15. Submitting Software Attributes

  ------------------------------------------------------------------------
  Field           Format and    Required or Not
                  Values        
  --------------- ------------- ------------------------------------------
  SoftwareName    String        Required

  Vendor          String        Required

  Version         String        Required

  ApprovalDate    Date Time     Optional -- USPS will require this date

  ApprovalKey     String        Optional -- USPS will require this key
                                given out by the USPS help desk to the
                                software vendor/IT shops to verify the
                                approval process
  ------------------------------------------------------------------------

## Mail.XML-Specific Message Details

### Mailing Group Messages {#mailing-group-messages .unnumbered}

In Mail.XML, a Job is called a 'Mailing Group' or a Customer group. A
Customer Group is an ID created by the customer for a Job and the
Mailing Group ID is the confirmation ID created by the USPS for that
Job.

-   First, the customer's application sends an OpenMailGroupRequest
    passing in the necessary parameters including the customer assigned
    CustomerGroupID.

-   The customer's application will then be returned a MailingGroupID
    from the OpenMailingGroupResponse, assuming the
    OpenMailingGroupRequest was successful.

-   Then, the customer's application sends a
    QualificationReportCreateRequest passing in the values, and the
    CustomerGroupID and MailingGroupID from the
    OpenMailingGroupResponse.

-   Customers' application will then be returned success/failure from
    the QualificationReportCreateResponse and use Tracking ID for
    tracking purposes for that Qualification report.

-   If there is Periodicals Outside county mail, the customer's
    application then can send the ContainerBundle report.

-   Then if there is co-palletized mail, the customer's application will
    send the message linking the consolidated containers to the original
    containers.

-   The customer's application shall send the Piece data if the
    containers were marked as Full-service or Mixed Service Containers.

-   Then, customers' application sends a PostageStatementCreateRequest
    or a PeriodicalStatementCreateRequest passing in the values, and the
    CustomerGroupID and MailingGroupID from the OpenMailingGroupResponse
    for the containers that are marked for postage statement creation
    from within the Mail.dat Job.

-   Customers' application will then receive a success/failure response
    from PostageStatementCreateResponse or
    PeriodicalStatementCreateResponse, a StatementID created by the USPS
    for tracking, and a UserPostageStatementID created and managed by
    the customer.

-   There is no Need to Close the mailing group. The mailing group is
    ONLY Closed if customer wants to delete the WHOLE JOB and all
    associated reports/postage.

-   After opening a mailing group, the customer can send the rest of the
    eDoc messages tied to that mailing group, send updates, or cancel
    requests for existing mailing Groups.

#### Open Mailing Group Request and Response {#open-mailing-group-request-and-response .unnumbered}

This message set allows the customer to provide the basic information
about the mailer, including Permit or Publication Number information as
well as the mailing acceptance office ZIP Code and the type of presort
used in the mailing. There are several required and many optional fields
in the Request. The submitter's CRID is required.

The Response message provides a MailingGroupID that can be used from
this point onwards to identify and link eDoc data to this job.

For more details on required vs. optional fields and blocks as well as
the data types, please review the Mail.XML Transaction Message Protocol
Messaging Specification.

#### Mailing Group Query Request and Response {#mailing-group-query-request-and-response .unnumbered}

The Mailing Group Query Request and Response messages allow the customer
to provide a Customer Group ID to open a mailing group and in response
the USPS *PostalOne!* system sends back all the basic information about
the mailer, including Permit or Publication Number information as well
as the mailing acceptance office ZIP Code and the type of presort used
in the mailing while assigning a MailingGroupID.

For more details on required vs. optional fields and blocks as well as
the data types, please review the Mail.XML Transaction Message Protocol
Messaging Specification.

#### Close Mailing Group Request and Response {#close-mailing-group-request-and-response .unnumbered}

The Close Mailing Group Query Request and Response messages allow the
customer to provide a Customer Group ID and a MailingGroupID and close a
group created previously. The USPS closes all reports and postage
statements in that Mailing group and considers the Mailing Group in a
DELETED state. The USPS provides confirmation ID called CloseConfirmID
back to the customer as a response.

For more details on required vs. optional fields and blocks as well as
the data types, please review the Mail.XML Messaging Specification

### Qualification Report Messages {#qualification-report-messages .unnumbered}

#### Qualification Report Create Request and Response {#qualification-report-create-request-and-response .unnumbered}

The Qualification Report Create Request allows the customer to provide a
Qualification Report. The USPS does not allow any updates to a
qualification report. If any thing changes the customer needs to Close
the mailing group and open a new group to provide a new Qualification
Report. The qualification report conforms to standardized documentation
described in the Domestic Mail Manual DMM 708.1.

The Qualification Query Request requires the Mailing Facility
(customer's plant location), the Destination Facility Zip Code as well
as the Customer Group IDs and Mailing group IDs.

The following fields are available in the
QualificationReportCreateRequest.

Table 3‑16. QualificationReportCreateRequest Fields

  -------------------------------------------------------------------------------------------------------
  Field                                Format and Values                 Required or Not
  ------------------------------------ --------------------------------- --------------------------------
  QualificationReport                  Complex                           Required

  DMMSection                           String 12                         Optional, displayed on header

  BatchManifestIndicator               Boolean                           Required, true for batch
                                                                         manifest

  ContainerInfoData                    Complex                           Optional, if used provide one
                                                                         for each container

  PhysicalPostalCodeEntryPoint in      String 6                          Required, the ZIP Code for the
  ContainerInfoData in                                                   postal service location where
  ContainerInfoData                                                      the container is entered.

  DeliveryLocaleKeyEntryPoint in       String 6                          Required, the Locale Key for the
  ContainerInfoData                                                      postal service location where
                                                                         the container is entered.

  ContainerShipDate in                 date                              Required, *PostalOne!* displays
  ContainerInfoData                                                      this date.

  CSADispatchNumber in                 Non Negative Integer              Optional
  ContainerInfoData                                                      

  CSDID in ContainerInfoData           Numeric String 10                 Optional

  CSADispatchTime in ContainerInfoData Time                              Optional

  CarrierRouteNumber in                String 4                          Optional
  ContainerInfoData                                                      

  CinCode in ContainerInfoData         String 3                          Optional

  ContainerBarcode in                  String 50                         Optional
  ContainerInfoData                                                      

  mailxml:ContainerDetailData in       Complex                           Optional, required for
  ContainerInfoData                                                      particular mail preparations per
                                                                         the DMM 708.

  CarrierRouteNumber in Container      String 4                          Optional
  DetailData                                                             

  CumulativePostage in                 Double                            Required
  ContainerDetailData                                                    

  DestinationZip in                    String                            Required
  ContainerDetailData                  [\[0-9\]{3}\|\[0-9\]{3}]{.mark}   

  EntryDiscountType in Container       See Table\                        Required
  DetailData                           "Qualification Report Entry       
                                       Discount Values"                  

  MailEndSeqNo in Container DetailData String 50                         Optional, used for consolidated
                                                                         statement.

  MailStartSeqNo in Container          String 50                         Optional, used for consolidated
  DetailData                                                             statement.

  Postage in Container DetailData      Double                            Required

  RateLevel in Container DetailData    See Table "Qualification Report   Required, determines postage in
                                       Rate Level Values"                the *PostalOne!* system.

  TotalCopies in Container DetailData  Non Negative Integer              Required, determines postage in
                                                                         the *PostalOne!* system.

  TotalPieces in Container DetailData  Non Negative Integer              Required, determines postage in
                                                                         the *PostalOne!* system.

  Zone in Container DetailData         See Table "Qualification Report   Optional, required for
                                       Zone Values"                      Periodicals and Package
                                                                         Services, determines postage in
                                                                         the *PostalOne!* system.

  VersionID in Container DetailData    String 10                         Optional

  ZipThreeFive in Container DetailData String                            Optional, required if a
                                       [\[0-9\]{3}\|\[0-9\]{3}]{.mark}   different ZIP Three Five from
                                                                         ContainerInfoData

  InOutCountyIndicator in Container    See Table\                        Optional, required for
  DetailData                           "In-County, Outside-County        Periodicals, valid values for
                                       Indicator Values"                 Periodicals are N Outside County
                                                                         and I In-County. F is obsolete
                                                                         and will result in an error
                                                                         message. O is not applicable and
                                                                         intended for other classes of
                                                                         mail.

  RateLevelIndicator in Container      See Table "Rate Category Values"  Optional, required if a
  DetailData                                                             different Rate Level from
                                                                         ContainerInfoData

  IncludedInOtherDoc in Container      Yes No                            Optional, required for
  DetailData                                                             copalletization.

  ContainerChargeContainerLevel in     See Table "Container Level        Optional, required for
  Container DetailData                 Values"                           Periodicals

  ActualPieces in Container DetailData Non Negative Integer              Required, *PostalOne!* uses
                                                                         total pieces not actual pieces

  ServiceLevelIndicator in Container   See Table "Full Service Indicator Required, displayed on
  DetailData                           Values"                           qualification report

  ContainerDisplayName in              String 50                         Optional, if provided displayed
  ContainerInfoData                                                      on qualification report

  ContainerType in ContainerInfoData   See Table\                        Required, displayed on
                                       "Container Type Values"           qualification report

  CustomerContainerID in               String 50                         Required, displayed on
  ContainerInfoData                                                      qualification report

  DestinationZip in ContainerInfoData  String                            Required, displayed on
                                       [\[0-9\]{3}\|\[0-9\]{3}]{.mark}   qualification report

  EntryPointFacilityType in            See Table "Entry Facility Type    Required, displayed on
  ContainerInfoData                    Values"                           qualification report

  EntryPointZip in ContainerInfoData   String                            Required, displayed on
                                       [\[0-9\]{3}\|\[0-9\]{3}]{.mark}   qualification report

  EntryLocaleKey in ContainerInfoData  String 9                          Optional

  ParentContainerID in                 String 50                         Optional, required if there is a
  ContainerInfoData                                                      parent container

  ProcessingCategory in                See Table "Processing Category    Required, displayed in the
  ContainerInfoData                    Values"                           qualification report

  SortationLevel in ContainerInfoData  See Domestic Mail Manual DMM      Required, displayed in the
                                       708.1.4 Sortation Levels          qualification report

  OverflowIndicator in                 Yes No                            Required, displayed in the
  ContainerInfoData                                                      qualification report if yes.

  CoPalletizationIndicator in          Yes No                            Optional, *PostalOne!* does not
  ContainerInfoData                                                      use this field

  CoPalletizationCustomerContainerID   String 50                         Optional, *PostalOne!* does not
  in ContainerInfoData                                                   use this field

  ScheduledInducationDate in           Date                              Required, *PostalOne!* does not
  ContainerInfoData                                                      use this field.

  ScheduledInducationTime in           Time                              Required, *PostalOne!* does not
  ContainerInfoData                                                      use this field.

  USPSPickup in ContainerInfoData      Yes No                            Required

  MailOwnerCRID in ContainerInfoData   String 10                         Required

  MailOwner in ContainerInfoData       Complex                           Optional, will be moved to
                                                                         ContainerDetailData

  PermitNumber in MailOwner in         String 8                          Required, if choose permit
  ContainerInfoData                                                      number

  PermitType in MailOwner in           See Table "Permit Type Values"    Optional, if choose permit
  ContainerInfoData                                                      number

  PermitZip4 in MailOwner in           String 9                          Required, if choose permit
  ContainerInfoData                                                      number

  PublicationNumber in MailOwner in    String 9                          Required, if choose Publication
  ContainerInfoData                                                      Number

  MailXMLContentID in                  String 9                          Optional
  ContainerInfoData                                                      

  MailXMLApptID in ContainerInfoData   String 9                          Optional

  PostageStatementMailingDate in       Date                              Required, not used by PostalOne
  ContainerInfoData                                                      

  PostageStatementMailingTime in       Time                              Required, not used by PostalOne
  ContainerInfoData                                                      

  ContainerAcceptanceDate in           Date                              Optional, not used by PostalOne
  ContainerInfoData                                                      

  ContainerAcceptanceTime in           Time                              Optional, not used by PostalOne
  ContainerInfoData                                                      

  CarrierID in ContainerInfoData       String 15                         Optional, not used by PostalOne

  TruckAndDispatchNumber in            String 10                         Optional, not used by PostalOne
  ContainerInfoData                                                      

  TotalWeightOfContainer in            String 5                          Optional, not used by PostalOne
  ContainerInfoData                                                      

  CustomerGroupID                      String 25                         Required, must be same as in
                                                                         attributes

  CustomerQualificationReportID        String 66                         Optional

  FormType                             See Table "Form Type Values"      Required, indicates class of
                                                                         mail

  MailingGroupID                       Non negative Integer              Required, must be same as in
                                                                         attributes

  PostOfficeOfMailingZip               String 5                          Required, must be same as in
                                                                         Mailing Group

  MailingFacility                      String 10                         Optional

  PreparedDate                         Date Time                         Required, displayed in
                                                                         qualification report

  Preparer                             Complex                           

  PermitNumber in Preparer             String 8                          Required, if choose permit
                                                                         number

  PermitType in Preparer               See Table "Permit Type Values"    Optional, if choose permit
                                                                         number

  PermitZip4 in Preparer               String 9                          Required, if choose permit
                                                                         number

  PublicationNumber in Preparer        String 9                          Required, if choose Publication
                                                                         Number

  PresortSWCompany                     String 50                         Optional, displayed in
                                                                         qualification report

  PresortSWProduct                     String 50                         Optional, displayed in
                                                                         qualification report

  PresortSWVersion                     String 20                         Optional, displayed in
                                                                         qualification report

  DocumentVersionData                  Complex                           Optional, as an alternative to
                                                                         providing version number in
                                                                         container detail data, provide
                                                                         the version report directly
                                                                         using DocumentVersionData

  VersionID in DocumentVersionData     String 10                         Required

  DocumentName in DocumentVersionData  String 12                         Required

  DocumentDescription in               String 30                         Optional
  DocumentVersionData                                                    

  PieceWeight in DocumentVersionData   Double                            Optional

  AdPercent in DocumentVersionData     Percentage -- total digits 5,     Optional
                                       fraction digits 2, max value      
                                       100.00.                           

  RateAffixed in DocumentVersionData   Double                            Optional

  PermitPublicationData in             Complex                           Optional
  DocumentVersionData                                                    

  PermitNumber in                      String 8                          Required, if choose permit
  PermitPublicationData                                                  number

  PermitType in PermitPublicationData  See Table "Permit Type Values"    Optional, if choose permit
                                                                         number

  PermitZip4 in PermitPublicationData  String 9                          Required, if choose permit
                                                                         number

  PublicationNumber in                 String 9                          Required, if choose Publication
  PermitPublicationData                                                  Number

  TotalCopies in DocumentVersionData   Non negative integer              Required

  TotalPieces in DocumentVersionData   Non negative integer              Required
  -------------------------------------------------------------------------------------------------------

#### Qualification Report Query Response {#qualification-report-query-response .unnumbered}

The USPS in response either accepts or rejects the Qualification Report
and in case of acceptance provides a Tracking ID and an optional
CustomerQualificationReportID. In the Response Accept block, the USPS
responds back to the customer with the full Qualification report data it
has on file, initially filed by the customer.

For more details on required vs. optional fields and blocks as well as
the data types, please review the *Mail.XML Transaction Message Protocol
Messaging Specification*.

#### Container Bundle Report Create Request and Response {#container-bundle-report-create-request-and-response .unnumbered}

The Container Bundle Report Create Request is used to state the
Periodicals Outside County chargeable bundles and containers.

Table 3‑17. ContainerBundleReportCreateRequest Fields

  ---------------------------------------------------------------------------------
  Field                            Format and      Required or Not
                                   Values          
  -------------------------------- --------------- --------------------------------
  Customer Group ID                String 25       Required Attribute, must match
                                                   customer group ID in Mailing
                                                   Group ID

  Mailing Group ID                 Non negative    Required Attribute, must match
                                   integer         Mailing Group ID.

  Submitting Party                 Complex         Required

  ContainerBundleMPURequest        Complex         Optional, may use
                                                   ContainerBundleRequest instead

  sackTrayContainerMPURecordType   Complex         Optional, use for sack and tray
                                                   charges.

  MPUItem in                       Complex         Required
  sackTrayContainerMPURecordType                   

  SegmentID in MPUItem in          String 4        Required, choose MPU ID, MPU
  sackTrayContainerMPURecordType                   Name and MPU Description, or
                                                   choose Version ID and Version
                                                   Name

  MPUIDType in MPUItem in          Non Negative    Required, *PostalOne!* will
  sackTrayContainerMPURecordType   Integer         display first five. This should
                                                   be defined as String 5.

  MPU Description in MPUItem in    String 30       Required, should be optional
  sackTrayContainerMPURecordType                   

  VersionID in MPUItem in          String 10       Required
  sackTrayContainerMPURecordType                   

  VersionName in MPUItem in        String 12       Required
  sackTrayContainerMPURecordType                   

  PublicationNumber in             String 9        Required
  SackTrayContainerMPURecord                       

  PublicationTitle in              String 60       Required
  SackTrayContainerMPURecord                       

  PostageStatementLineNumber in    Enumerated Part Optional, *PostalOne!* uses the
  SackTrayContainerMPURecord       E lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table       Required
  SackTrayContainerMPURecord       "Container      
                                   Level Values"   

  ChargeableEntryLevel in          See Table       Required
  sackTrayContainerMPURecordType   "Container      
                                   Charge Entry    
                                   Facility Type   
                                   Values"         

  Containers in                    Double          Required
  sackTrayContainerMPURecordType                   

  IssueDate in                     Date            Required
  sackTrayContainerMPURecordType                   

  IssueNumber in                   String 6        Optional
  sackTrayContainerMPURecordType                   

  VolumeNumber in                  String 6        Optional
  sackTrayContainerMPURecordType                   

  PalletContainerMPURecordType     Complex         Optional, use for Pallet Charges

  MPUItem in                       Complex         Required
  PalletContainerMPURecordType                     

  SegmentID in MPUItem in          String 4        Required, choose MPU ID, MPU
  PalletContainerMPURecordType                     Name and MPU Description, or
                                                   choose Version ID and Version
                                                   Name

  MPUIDType in MPUItem in          Non Negative    Required, *PostalOne!* will
  PalletContainerMPURecordType     Integer         display first five. This should
                                                   be defined as String 5.

  MPU Description in MPUItem in    String 30       Required by USPS validation.
  PalletContainerMPURecordType                     

  VersionID in MPUItem in          String 10       Required
  PalletContainerMPURecordType                     

  VersionName in MPUItem in        String 12       Required
  PalletContainerMPURecordType                     

  PublicationNumber in             String 9        Required
  PalletContainerMPURecord                         

  PublicationTitle in              String 60       Required
  PalletContainerMPURecord                         

  PostageStatementLineNumber in    Enumerated Part Optional. *PostalOne!* uses the
  PalletContainerMPURecord         E lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table       Required
  PalletContainerMPURecordType     "Container      
                                   Level Values"   

  ChargeableEntryLevel in          See Table       Required
  PalletContainerMPURecordType     "Container      
                                   Charge Entry    
                                   Facility Type   
                                   Values"         

  Containers in                    Double          Required
  PalletContainerMPURecordType                     

  IssueDate in                     Date            Required
  PalletContainerMPURecordType                     

  IssueNumber in                   String 6        Optional
  PalletContainerMPURecordType                     

  VolumeNumber in                  String 6        Optional
  PalletContainerMPURecordType                     

  BundleMPURecord                  Complex         Optional, use for Bundle Charges

  MPUItem in BundleMPURecord       Complex         Required, if no MPU Item use
                                                   BundleRecord

  SegmentID in MPUItem in          String 4        Required, choose MPU ID, MPU
  BundleMPURecord                                  Name and MPU Description, or
                                                   choose Version ID and Version
                                                   Name

  MPUIDType in MPUItem in          Non Negative    Required, *PostalOne!* will
  BundleMPURecord                  Integer         display first five. This should
                                                   be defined as String 5.

  MPU Description in MPUItem in    String 30       Required, should be optional
  BundleMPURecord                                  

  VersionID in MPUItem in          String 10       Required
  BundleMPURecord                                  

  VersionName in MPUItem in        String 12       Required
  BundleMPURecord                                  

  PublicationNumber in             String 9        Required
  BundleMPURecord                                  

  PublicationTitle in              String 60       Required
  BundleMPURecord                                  

  PostageStatementLineNumber in    Enumerated Part Optional, *PostalOne!* uses the
  BundleMPURecord                  E lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table       Required
  BundleMPURecord                  "Container      
                                   Level Values"   

  ChargeableBundleLevel in         See Table\      Required
  BundleMPURecord                  "Bundle Level   
                                   Values"         

  Bundles in BundleMPURecord       Double          Required

  IssueDate in BundleMPURecord     Date            Required

  IssueNumber in BundleMPURecord   String 6        Optional

  VolumeNumber in BundleMPURecord  String 6        Optional

  ContainerBundleSummaryRecords    Complex         Required or
                                                   ContainerBundleMPURecords

  PublicationNumber in             String 9        Required
  SackTrayContainerRecord                          

  PublicationTitle in              String 60       Required
  SackTrayContainerRecord                          

  PostageStatementLineNumber in    Enumerated Part Optional, *PostalOne!* uses the
  SackTrayContainerRecord          E lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table\      Required
  sackTrayContainerRecord          "Container      
                                   Level Values"   

  ChargeableEntryLevel in          See Table       Required
  sackTrayContainerRecord          "Container      
                                   Charge Entry    
                                   Facility Type   
                                   Values"         

  Containers in                    Double          Required
  sackTrayContainerRecord                          

  IssueDate in                     Date            Required
  sackTrayContainerRecord                          

  IssueNumber in                   String 6        Optional
  sackTrayContainerRecord                          

  VolumeNumber in                  String 6        Optional
  sackTrayContainerRecordType                      

  PalletContainerRecord            Complex         Optional, use for Pallet Charges

  PublicationNumber in             String 9        Required
  PalletContainerRecord                            

  PublicationTitle in              String 60       Required
  PalletContainerRecord                            

  PostageStatementLineNumber in    Enumerated Part Optional, *PostalOne!* uses the
  PalletContainerRecord            E lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table\      Required
  PalletContainerRecord            "Container      
                                   Level Values"   

  ChargeableEntryLevel in          See Table       Required
  PalletContainerRecord            "Container      
                                   Charge Entry    
                                   Facility Type   
                                   Values"         

  Containers in                    Double          Required
  PalletContainerRecord                            

  IssueDate in                     Date            Required
  PalletContainerRecord                            

  IssueNumber in                   String 6        Optional
  PalletContainerRecord                            

  VolumeNumber in                  String 6        Optional
  PalletContainerRecord                            

  BundleRecord                     Complex         Optional, use for Bundle Charges

  PublicationNumber in             String 9        Required
  BundleRecord                                     

  PublicationTitle in BundleRecord String 60       Required

  PostageStatementLineNumber in    Enumerated Part Optional, *PostalOne!* uses the
  BundleRecord                     D lines         Container Level and the Entry
                                                   Level to find the line number.

  ChargeableContainerLevel in      See Table\      Required
  BundleRecord                     "Container      
                                   Level Values"   

  ChargeableBundleLevel in         See Table\      Required
  BundleRecord                     "Bundle Level   
                                   Values"         

  Bundles in BundleRecord          Double          Required

  IssueDate in BundleRecord        Date            Required

  IssueNumber in BundleRecord      String 6        Optional

  VolumeNumber in BundleRecord     String 6        Optional
  ---------------------------------------------------------------------------------

#### Container Bundle Report Create Response {#container-bundle-report-create-response .unnumbered}

ContainerBundleReportCreateResponse returns a
ContainerBundleReportCreateAccept message or a
ContainerBundleReportCreateReject message in the usual format. The
Accept message includes the ContainerBundleReportID and the TrackingID.
*PostalOne!* does not support canceling a container or bundle in the
ContainerBundleReport (the field ContainerBundleStatus).

#### Container Bundle Report Query Request and Response  {#container-bundle-report-query-request-and-response .unnumbered}

The ContainerBundleReportQueryRequest and
ContainerBundleReportQueryResponse are not supported in *PostalOne!*
because the information is not changed from the
ContainerBundleCreateRequest.

#### Container Bundle Report Update Request and Response  {#container-bundle-report-update-request-and-response .unnumbered}

*PostalOne!* will not support the ContainerBundleUpdateRequest or the
ContainerBundleUpdateResponse. If a container is cancelled, the
Container Bundle report will be cancelled. If the qualification report
is cancelled, the Container Bundle report will be cancelled.

#### Container Bundle Report Cancel Request and Response  {#container-bundle-report-cancel-request-and-response .unnumbered}

*PostalOne!* will not support the ContainerBundleCancelRequest or the
ContainerBundleCancelResponse. If a container is cancelled, the
Container Bundle report will be cancelled. If the qualification report
is cancelled, the Container Bundle report will be cancelled.

### Bundle Detail Messages {#bundle-detail-messages .unnumbered}

#### Bundle Detail Create Request and Response  {#bundle-detail-create-request-and-response .unnumbered}

The BundleDetailCreateRequest sends the bundle detail associated with a
qualification report. Send this message after sending a successful
QualificationReportCreateRequest for the requested containers.

Table 3‑18. BundleDetailCreateRequest Fields

  --------------------------------------------------------------------------------
  Field                          Format and Values      Required or Not
  ------------------------------ ---------------------- --------------------------
  SubmittingParty                Complex                Required

  SubmittingSoftware             Complex                Required

  UserLicenseCode                String 4               Optional

  MaildatJobID                   String 8               Optional

  ContainerID                    String 25              Required, or
                                                        CustomerContainerID

  CustomerContainerID            String 6               Required or ContainerID
                                                        (if CustomerContainerID is
                                                        not unique there may be an
                                                        error.)

  CustomerBundleID               String 6               Optional

  TotalPieces                    Non negative integer   Required

  TotalCopies                    Non negative integer   Required

  BundleZip                      String 6               Required

  BundleCarrierRoute             String 4               Optional

  DestinationEntry               See Table              Optional
                                 "Qualification Report  
                                 Entry Discount Values" 

  Zone                           See Table              Optional
                                 "Qualification Report  
                                 Zone Values"           

  DestinationZIP                 Three or five digit    Optional

  OutsideCountyBundleIndicator   See Table "In-County,  Optional, required for
                                 Outside-County         Periodicals
                                 Indicator Values       

  SortationLevel                 See Table              Optional
                                 "Qualification Report  
                                 Sortation Level        
                                 Values"                

  BundleLevel                    See Table "Bundle      Optional
                                 Detail Levels"         

  ParentBundleID                 String 6               Optional, Not used by
                                                        PostalOne

  BundleBarcode                  String 20              Optional, Not used by
                                                        PostalOne

  BundleStatus                   Blank or C             Optional, Not used by
                                                        PostalOne

  BundleRecordStatus             O, D, I, U             Optional, *PostalOne!*
                                                        supports O Original and U
                                                        Update.

  BundleVersion                  Complex                Optional, displayed on
                                                        Qualification Report
                                                        Bundle Detail

  Version ID in BundleVersion    String 10              Required, displayed on
                                                        Qualification Report
                                                        Bundle Detail

  Version Name in BundleVersion  String 12              Required, displayed on
                                                        Qualification Report
                                                        Bundle Detail
  --------------------------------------------------------------------------------

#### Bundle Detail Create Response {#bundle-detail-create-response .unnumbered}

The BundleDetailCreateResponse returns a BundleDetailCreateAccept block
or a BundleDetailCreateReject block. The BundleDetailCreateAccept block
includes a BundleConfirmID assigned by the *PostalOne!* system.

#### Bundle Detail Cancel Request and Response {#bundle-detail-cancel-request-and-response .unnumbered}

*PostalOne!* does not support the BundleDetailCancelRequest or the
BundleDetailCancelResponse. Use the Mail.dat Container Update Request to
cancel a container or cancel the qualification report and re-create the
qualification report.

### Mail Piece Messages {#mail-piece-messages .unnumbered}

The Mail piece messages provide the capability of creating portions of
piece detail data blocks or piece range blocks so they can be
efficiently sent to the *PostalOne!* system.

#### Mail Piece Create Request and Response {#mail-piece-create-request-and-response .unnumbered}

The Mail Piece Create request provides a choice to the customer to
either provide a Mail.dat Job based piece detail or range information,
tying the data to an existing Mail.dat Job or to provide the piece
detail or range information tied an existing Mail.XML Mailing Group ID.

The optional element of WastedPieceIndicator allows the customer to file
for postage adjustments for Spoilage or Shortage.

The MailPieceCreateRequest contains the following fields.

Table 3‑19. MailPieceCreateRequest Fields

  -----------------------------------------------------------------------------------
  Field                         Format and Values Required or Not
  ----------------------------- ----------------- -----------------------------------
  SubmittingParty               Complex           Required

  SubmittingSoftware            Complex           Required

  UserLicenseCode               String 4          Optional, required for Mail.dat job

  MaildatJobID                  String 8          Optional, required for Mail.dat job

  TransmittedCount              Non negative      Optional
                                integer           

  PDRMailPieceBlock             Complex           Optional, use PDRMailPieceBlock or
                                                  PDRRangePieceBlock for
                                                  Full-service.

  PackageID in                  String 6          Required
  PDRMailPieceBlock                               

  CQTDatabaseID in              Non negative      Required
  PDRMailPieceBlock             integer length 8  

  MailPieceBlockType in         Complex           Required
  PDRMailPieceBlock                               

  ServiceLevelIndicator         See Table         Required
                                "Service Level    
                                Indicators"       

  LOTSequenceDirection in       String 1          If Carrier Route LOT, use either
  MailPieceBlock                                  LOTSequenceDirection and
                                                  LOTSequenceNumber or
                                                  WalkSequenceNumber

  LOTSequenceNumber in          Numeric String 4  See note for LOTSequenceDirection
  MailPieceBlock                                  

  WalkSequenceNumber in         Numeric String 5  See note for LOTSequenceDirection
  MailPieceBlock                                  

  IMB                           Complex           Optional, Required for Full-service

  BarcodeID in IMB in           Numeric string 2  Optional
  MailPieceBlock                                  

  ServiceTypeCode in IMB in     Numeric string 3  Optional
  MailPieceBlock                                  

  MailerID6 in IMB in           Numeric String 6  If Full-service, either MailerID6
  MailPieceBlock                                  and SerialNumber9 are required or
                                                  MailerID9 and SerialNumber6 are
                                                  required.

  SerialNumber9 in IMB in       Numeric String 9  See Note in MailerID6
  MailPieceBlock                                  

  MailerID9 in IMB in           Numeric String 9  See Note in MailerID6
  MailPieceBlock                                  

  SerialNumber6 in IMB in       Numeric String 6  See Note in MailerID6
  MailPieceBlock                                  

  DeliveryPointZIP in IMB in    String 0-11       Optional, if Full-service, 11
  MailPieceBlock                                  digits required

  PlanetCode in MailPieceBlock  String 11-13      Optional, use PlanetCode and
                                                  DeliveryPointZIP in place of IMB
                                                  block.

  DeliveryPointZIP in           String 0-11       Optional, use PlanetCode and
  MailPieceBlock                                  DeliveryPointZIP in place of IMB
                                                  block.

  DeliveryContainerID           Numeric String 22 Optional, use DeliveryContainerID
                                                  and DeliveryPointZIP in place of
                                                  IMB block.

  DeliveryPointZIP in           String 0-11       Optional, use DeliveryContainerID
  MailPieceBlock                                  and DeliveryPointZIP in place of
                                                  IMB block.

  PieceID in MailPieceBlock     String 22         Required

  WastedPieceIndicator in       Yes or No         Optional
  MailPieceBlock                                  

  MLOCRrateANDpostage in        String 7          Optional, see the Mail.dat
  MailPieceBlock                                  specification for the description
                                                  of this field in the PDR file.

  MoveComplianceUpdateMethod in See Table "Move   Optional, use blank for none.
  MailPieceBlock                Update Values"    

  MailOwner in MailPieceBlock   Complex           Optional

  BarCodeApplicator in          Complex           Optional
  MailPieceBlock                                  

  MachineID in MailPieceBlock   String 4          Optional

  CustomerBundleID in           String 12         Optional
  MailPieceBlock                                  

  PDRRangePieceBlock            Complex           Optional, use PDRMailPieceBlock or
                                                  PDRRangePieceBlock for
                                                  Full-service.

  DatabaseContainerID in        Non negative      Required, must match Container ID
  PDRRangePieceBlock            integer 6         in the Mail.dat CSM file.

  PieceRangeBlock in            Complex           Required
  PDRRangePieceBlock                              

  IMBarcodeLowerSerialization   Complex           Required, MailerID6 and
  in PieceRangeBlock                              SerialNumber9 or MailerID9 and
                                                  SerialNumber6

  IMBarcodeUpperSerialization   Complex           Required, MailerID6 and
  in PieceRangeBlock                              SerialNumber9 or MailerID9 and
                                                  SerialNumber6

  MailPreparer in               Complex           Optional
  PieceRangeBlock                                 

  MailOwner in PieceRangeBlock  Complex           Optional

  ServiceTypeCode in            Numeric string 3  ServiceTypeCode or MailClass is
  PieceRangeBlock                                 required, use Service Type Codes
                                                  assigned by the Postal Service.

  MailClassType in              See Table         ServiceTypeCode or MailClass are
  PieceRangeBlock               MailClassType in  required; classes 1, 2, 3 and 4 are
                                the FAST Section  valid for mail pieces.

  ServiceLevelIndicator in      See Table Service Required
  PieceRangeBlock               Level Indicator   
                                Values            

  CustomerGroupID               String 25         Optional, required for Mail XML
                                                  job, must match CustomerGroupID in
                                                  attributes

  MailingGroupID                Non negative      Optional, required for Mail XML
                                integer           job, must match MailingGroupID in
                                                  attributes

  TransmittedCount              Non negative      Optional
                                integer           

  MailPieceBlock                Complex           Either the MailPieceBlock or the
                                                  PieceRangeBlock is required. See
                                                  MailPieceBlock above.

  ContainerID                   String 24         Required, container barcode

  RangePieceCount               Non negative      Required
                                integer           

  PieceRangeBlock               Complex           Either the MailPieceBlock or the
                                                  PieceRangeBlock is required. See
                                                  PieceRangeBlock above.
  -----------------------------------------------------------------------------------

The MailPieceCreateResponse has a MailPieceCreateAccept block and a
MailPieceCreateReject block. The MailPieceAccept has a
MailPieceConfirmID block and a ReturnInfo block. The
MailPieceCreateReject has a ReturnInfo block.

#### Mail Piece Update Request and Response {#mail-piece-update-request-and-response .unnumbered}

The Mail Piece messages provide the capability of update existing piece
detail or range data and send the transaction in manageable chunks. The
Mail Piece Update request is identical to the Create request and allows
the customer to only send those records that they want to update within
the *PostalOne!* system. The update request provides a choice to the
customer: update Mail.dat-based piece detail or range information (tying
the data to an existing Mail.dat job), or update the piece detail or
range information tied to an existing Mail.XML Mailing Group ID. The
optional element of WastedPieceIndicator allows the customer to file for
postage adjustments for Spoilage or Shortage.

In response the *PostalOne!* system will either accept or reject the
transaction.

#### Mail Piece Cancel Request and Response {#mail-piece-cancel-request-and-response .unnumbered}

The Mail Piece messages provide the capability of canceling one or more
records previously sent to the *PostalOne!* system by the customer. The
Mail Piece Cancel request is identical to the create and update
requests, and allows the customer to only send those records that they
want to cancel within the *PostalOne!* system. The update request
provides a choice to the customer to update Mail.dat-based piece detail
or range information (tying the data to an existing Mail.dat job), or to
update the piece detail or range information tied to an existing
Mail.XML Mailing Group ID. The optional element of WastedPieceIndicator
allows the customer to file for postage adjustments for Spoilage or
Shortage and the customer is not allowed to cancel an existing Postage
adjustment transaction where he/she asked for the USPS to adjust postage
for specific pieces. In this case, the customer will need to go through
a reversal of postage manual process.

In response the *PostalOne!* system will either accept or reject the
transaction.

In response, the customer responds with the return code of acceptance or
rejection. Return Codes and their descriptions will be available on the
date defined in the External Timeline for IM implementation document. In
response, the customer must use the Delivery Response message to let the
USPS know of the acceptance or rejection of the message set. If the
customer has registered to receive the By/For Conflict Notification
message that tells the customers that there is a conflict available,
please query and request the USSP to get more details, then the USPS
will push the By Fore Conflict Notification message to the customer. In
response, the customer must respond with the Notification response
message.

#### Co-palletization Container Linkage Messages {#co-palletization-container-linkage-messages .unnumbered}

These messages (or their Mail.dat equivalent) are required for
co-palletized mail to qualify for Full-service. This family of messages
allows the consolidator to link the original containers sent for
copalletization to the new co-palletized container and provides the
following capabilities:

-   Ability to create a linkage between original container(s) at the
    origin site with the new identity of containers from the
    consolidator site

-   Ability to cancel co-palletization linkage between original and new
    or linked containers

The Co-palletization Container Linkage messages include:

OriginalContainerLinkageCreateRequest

OriginalContainerLinkageCreateResponse

OriginalContainerLinkageCancelRequest

OriginalContainerLinkageCancelResponse

The OriginalContainerLinkageCreateRequest includes the following fields.

Table 3‑20. OriginalContainerLinkageCreateRequest Fields

  ----------------------------------------------------------------------------
  Field                 Format and       Required or not
                        Values           
  --------------------- ---------------- -------------------------------------
  Customer Group ID     String 25        Required Attribute, must match
                                         customer group ID in Mailing Group ID

  Mailing Group ID      Non negative     Required Attribute, must match
                        integer          Mailing Group ID.

  Submitting Party      Complex          Optional

  Submitting Software   String 8         Attributes

  MailDat Container in  Complex          Required if MailXML Container block
  OriginalContainer                      is not used.

  Maildat User License  String 4         Required
  Code in MailDat                        
  Container in                           
  OriginalContainer                      

  Maildat Job ID in     String 8         Required
  MailDat Container in                   
  OriginalContainer                      

  Database Container ID Non negative     Required
  in MailDat Container  integer 6        
  in OriginalContainer                   

  Unique Container      String 24        Optional
  Barcode in MailDat                     
  Container in                           
  OriginalContainer                      

  MailXML Container in  Complex          Required if MailDat Container block
  OriginalContainer                      is not used.

  MailingGroupID in     Non negative     Or CustomerGroupID required
  MailXMLContainer in   Integer          
  OriginalContainer                      

  CustomerGroupID in    String 25        Or MailingGroupID required
  MailXMLContainer in                    
  OriginalContainer                      

  MailXMLJobID in       String 8         Required
  MailXMLContainer                       
  OriginalContainer                      

  CustomerContainerID   String 50        Required if ContainerID is not used.
  in MailXMLContainer                    Can be submitted in conjunction with
  in OriginalContainer                   ContainerID.

  ContainerID in        String 50        Or CustomerContainerID or both,
  MailXMLContainer in                    *PostalOne!* requires ContainerID.
  OriginalContainer                      

  ContainerBarcode in   String 24        Required
  OriginalContainer                      

  MailDat Container in  Complex          Required if MailXML Container block
  LinkedContainer                        is not used.

  Maildat User License  String 4         Required
  Code in MailDat                        
  Container in                           
  LinkedContainer                        

  Maildat Job ID in     String 8         Required
  MailDat Container in                   
  LinkedContainer                        

  Database Container ID Non negative     Required
  in MailDat Container  integer 6        
  in LinkedContainer                     

  Unique Container      String 24        Optional
  Barcode in MailDat                     
  Container in                           
  LinkedContainer                        

  MailXML Container in  Complex          Required if MailDat Container block
  LinkedContainer                        is not used.

  MailingGroupID in     Non negative     Required if CustomerGroupID is not
  MailXMLContainer in   Integer          used.
  LinkedContainer                        

  CustomerGroupID in    String 25        Required if MailingGroupID is not
  MailXMLContainer in                    used.
  LinkedContainer                        

  MailXMLJobID in       String 8         Required
  MailXMLContainer in                    
  LinkedContainer                        

  CustomerContainerID   String 50        Required if ContainerID is not used.
  in MailXMLContainer                    Can be submitted in conjunction with
  in LinkedContainer                     ContainerID.

  ContainerID in        String 50        Required if ContainerID is not used.
  MailXMLContainer in                    Can be submitted in conjunction with
  LinkedContainer                        ContainerID. *PostalOne!* validation
                                         requires ContainerID.

  ContainerBarcode in   String 24        Required
  LinkedContainer                        
  ----------------------------------------------------------------------------

### Postage Statement (non-Periodicals) Messages {#postage-statement-non-periodicals-messages .unnumbered}

#### Begin Combined Mailing Request and End Combined Mailing Request {#begin-combined-mailing-request-and-end-combined-mailing-request .unnumbered}

The BeginCombinedMailingRequest method is used only for combined mailing
for the non-Periodicals mailing classes. This method sends the combined
mailing ID information and starts the combined mailing. This method must
precede the postage statements included in the combined mailing and the
EndCombinedMailingRequest method. The EndCombinedMailingRequest method
is used only in combined mailings for the non-Periodicals mailing
classes. The EndCombinedMailingRequest method ends a combined mailing,
and must be used after BeginCombinedMailingRequest and all postage
statements are submitted that are to be included in the non-Periodicals
mailing.

#### Postage Statement Create Request and Response {#postage-statement-create-request-and-response .unnumbered}

The attributes for the PostageStatementCreateRequest includes the
Customer Group ID and the Mailing Group ID. You must obtain a Customer
Group ID and a Mailing Group ID before entering a Postage Statement.

The Submitting Party and the Submitting Software are required.

The PostageStatementCreateRequest message includes the following fields.

Table 3‑21. PostageStatementCreateResponse Fields

  ------------------------------------------------------------------------
  Field             Format and Values     Required or Not
  ----------------- --------------------- --------------------------------
  Agency Cost Code  Simple                Not Required, *PostalOne!*
                                          requires for OMAS permit

  Automation        Date Time             Not Required, Required for
  Address Match                           Automation mailing. *PostalOne!*
  Date                                    uses only date.

  Customer          Simple                Not Required, *PostalOne!* uses
  Reference ID                            to populate customer reference
                                          ID field on the Postage
                                          Statement

  User Postage      Simple 1-10 (May be   Not Required, *PostalOne!* uses
  Statement ID      lengthened in a       to populate User Postage
                    future release.)      Statement ID

  Carrier Route     Date Time             Not Required, Required for
  Address Match                           automation carrier route mail.
  Date                                    *PostalOne!* uses only date.

  Carrier Route     Date Time             Not Required, required for
  Sequencing Date                         carrier route sequenced mail.
                                          *PostalOne!* uses only date.

  Certification     Contact Name and      Required, this is the party that
  Data              Phone Number          signs the certification
                                          statement on the postage
                                          statement

  Container count   Complex               Required, Non negative integer
                                          for each of Other type, Pallets,
                                          Sacks, Trays 1mm, Trays 2emm,
                                          Trays 2mm, Trays Flat

  Enclosed by       Simple                Not Required

  DAL Pieces        Non negative integer  Not Required, required for
                                          Detached Address Labels

  Extended Form     Boolean (Extended     Required, Indicates if using
                    Form will be removed  Line Item Summary Data and Extra
                    when the Mail XML     Service Summary Data (0) or Line
                    structure is          Item Data and Extra Service Data
                    corrected.)           (1)

  Form Type         See Table "Form Type  Required
                    Values"               

  Fob ID            Simple 1-8            Not Required -- Postal Service
                                          does not use this

  Barcode Rate in   See Table\            Required
  Line Item Summary "Parcel Barcode Rate" 
  Data                                    

  Entry Discount in See Table\            Required
  Line Item Summary "Entry Discount       
  Data              Values"               

  Line Label in     Simple, 1-80          Optional, *PostalOne!*
  Line Item Summary                       determines the correct line
  Data                                    label

  Line Number in    Simple, 1-3           Optional, *PostalOne!*
  Line Item Summary                       determines the correct line
  Data                                    number

  Piece Postage in  Double                Optional, Required for piece
  Line Item Summary                       postage summary line where price
  Data                                    is not known.

  Piece Rate in     Double                Optional, Required for piece
  Line Item Summary                       postage summary line where price
  Data                                    is not known

  Postage Amount in Double                Required
  Line Item Summary                       
  Data                                    

  Pound Postage in  Double                Optional, Required for pound
  Line Item Summary                       postage line.
  Data                                    

  Pound Rate in     Double                Optional, Required for pound
  Line Item Summary                       postage line where price is not
  Data                                    known.

  Prepared as SM in Boolean               Required, Yes (1), No (0)
  Line Item Summary                       
  Data                                    

  Rate Category in  See Table\            Optional, Required on lines that
  Line Item Summary "Rate Category        require rate category
  Data              Values"               

  Section in Line   Simple 0-1            Optional
  Item Summary Data                       

  Surcharge Type in See Table\            Required
  Line Item Summary "Surcharge Type       
  Data              Values"               

  Total Pieces in   Non negative integer  Required
  Line Item Summary                       
  Data                                    

  Total Weight in   Double                Optional, Required for pound
  Line Item Summary                       postage summary lines
  Data                                    

  Weight Break Type See Table\            Optional, Required for pound
  in Line Item      "Weight Break         postage summary lines
  Summary Data      Indicator Values"     

  Zone in Line Item See Table "Zone       Optional, Required for pound
  Summary Data      Values"               postage for packages and
                                          Periodicals.

  Flat Rate         See Table\            Optional, relevant to Priority
  Indicator in Line "Flat Rate Indicator  Mail.
  Item Summary Data Values"               

  Barcode Rate in   See Table\            Required
  Postage Statement "Parcel Barcode Rate" 
  Line Item Data                          

  Container Display Simple 1-50           Optional, *PostalOne!* does not
  Name in Postage                         process this field
  Statement Line                          
  Item Data                               

  Customer          Simple 1-50           Optional, *PostalOne!* does not
  Container ID in                         process this field
  Postage Statement                       
  Line Item Data                          

  Entry Discount in See Table\            Required
  Postage Statement "Entry Discount       
  Line Item Data    Values"               

  Entry Facility    See Table\            Optional, but needed for postage
  Type in Postage   "Entry Facility Type  statement register information
  Statement Line    Values"               
  Item Data                               

  Entry ZIP in      Simple                Optional, but needed for postage
  Postage Statement                       statement register information
  Line Item Data                          

  Heavy Letter in   Boolean               Required, 0 for non-letters, 0
  Postage Statement                       for letters 0.2063 pounds or
  Line Item Data                          less and 1 for letters over
                                          0.2063 pounds.

  Line Label in     Simple, 1-80          Optional, *PostalOne!*
  Postage Statement                       determines the correct line
  Line Item Data                          label

  Line Number in    Simple, 1-3           Optional, *PostalOne!*
  Postage Statement                       determines the correct line
  Line Item Data                          number

  Piece Rate in     Double                Optional, Required for piece
  Postage Statement                       postage summary line where price
  Line Item Data                          is not known

  Postage Amount in Double                Required
  Postage Statement                       
  Line Item Data                          

  Pound Rate in     Double                Optional, Required for pound
  Postage Statement                       postage line where price is not
  Line Item Data                          known.

  Prepared as SM in Boolean               Required, Yes (1), No (0)
  Postage Statement                       
  Line Item Data                          

  Rate Category in  See Table\            Optional, Required on lines that
  Postage Statement "Rate Category        require rate category
  Line Item Data    Values"               

  Section in        Simple 0-1            Optional
  Postage Statement                       
  Line Item Data                          

  Single Piece      Double                Required
  Weight in Postage                       
  Statement Line                          
  Item Data                               

  Surcharge Type in See Table\            Required
  Postage Statement "Surcharge Type       
  Line Item Data    Values"               

  Total Pieces in   Non negative integer  Required
  Postage Statement                       
  Line Item Data                          

  Total Weight in   Double                Optional, *PostalOne!* uses
  Postage Statement                       Single Piece Weight and
  Line Item Data                          calculates

  Zone in Postage   See Table "Zone       Optional, Required for pound
  Statement Line    Values"               postage for packages and
  Item Data                               Periodicals.

  Version ID in     Simple 1-10           Optional, Required for version
  Postage Statement                       report and postage statement
  Line Item Data                          register information

  Container Type in See Table\            Optional, *PostalOne!* does not
  Postage Statement "Container Type       process this field
  Line Item Data    Values"               

  Flat Rate         See Table\            Optional, relevant to Priority
  Indicator in      "Flat Rate Indicator  Mail
  Postage Statement Values"               
  Line Item Data                          

  Single Piece      Double                Required, fill with zero except
  Dimensional                             when doing Dimensional Pricing
  Weight in Postage                       and then follow the rules for
  Statement Line                          determining the weight.
  Item Data                               

  Mailing Date      DateTime              Required, *PostalOne!* uses only
                                          the date not the time. This is
                                          the mailing date on the postage
                                          statements.

  Mailing Group ID  Non negative integer  Required, *PostalOne!* requires
                                          the mailing group ID is
                                          established before sending a
                                          postage statement

  Packaging Method  See Table\            Optional
                    "Packaging Basis      
                    Values"               

  Post Office of    Simple 5              Optional, *PostalOne!* will
  Mailing ZIP                             display the post office of
                                          mailing ZIP assigned to the post
                                          office in PostalOne

  Postage Affixed   Double                Required, fill with zero for no
  Amount                                  postage affixed

  Postage Payment   See Table\            Required
  Method            "Postage Payment      
                    Method Values"        

  Processing        See Table\            Optional, required by PostalOne
  Category          "Processing Category  
                    Values"               

  Rate Type         See Table "Rate Type  Optional
                    Values" for the       
                    appropriate postage   
                    statement             

  Register of       Boolean               Required
  Mailing                                 

  Sacking Basis     See Table\            Optional
                    "Sacking Basis        
                    Values"               

  Single Piece      Double                Required, fill with 0 if not
  Weight                                  applicable on a consolidated
                                          statement

  Extra Service     Complex               Optional, required for detailed
  Data                                    postage lines if using extra
                                          services

  Service Code in   See Table\            Required, if using Extra Service
  Extra Service     "Special Service Code Data
  Data              Values"               

  Service Rate in   Double                Optional, *PostalOne!* does not
  Extra Service                           use this field
  Data                                    

  Service Sub Code  See Table "Special    Required, if using Extra Service
  in Extra Service  Service Subcode       Data
  Data              Values"               

  Total Amount in   Double                Optional, *PostalOne!* does not
  Extra Service                           use this field
  Data                                    

  Total Pieces in   Non negative integer  Required, if using Extra Service
  Extra Service                           Data
  Data                                    

  Extra Service     Complex               Required if using Postage
  Summary Data                            Statement Summary Lines

  Line Label in     Simple 1-80           Optional, *PostalOne!* does not
  Extra Service                           use this field
  Summary Data                            

  Line Number in    Simple 1-3            Optional, *PostalOne!* does not
  Extra Service                           use this field
  Summary Data                            

  Section in Extra  Simple 1              Optional, *PostalOne!* does not
  Service Summary                         use this field
  Data                                    

  Service Code in   See Table\            Required, if using Extra Service
  Extra Service     "Special Service Code Summary Data
  Summary Data      Values"               

  Total Amount in   Double                Required, if using Extra Service
  Extra Service                           Summary Data. Fill with zero if
  Summary Data                            no extra services.

  Total Pieces in   Non negative integer  Required, if using Extra Service
  Extra Service                           Summary Data. Fill with zero if
  Summary Data                            no extra services.

  Statement         Simple                Optional, *PostalOne!* displays
  Sequence Number                         this data on the postage
                                          statement

  Repositionable    Boolean               Required (1) Yes (0) No
  Notes Indicator                         

  Document Version  Complex               Optional, required for version
  Data                                    report

  Version ID in     Simple 1-10           Required
  Document Version                        
  Data                                    

  Version Name in   Simple 1-12           Required
  Document Version                        
  Data                                    

  Description in    Simple 1-30           Optional
  Document Version                        
  Data                                    

  Piece Weight in   Double                Required
  Document Version                        
  Data                                    

  Ad Percent in     Percentage -- total   Optional, Required for
  Document Version  digits 5, fraction    Periodicals version report, set
  Data              digits 2, max value   as string 5 so put in digits
                    100.00.               needed assuming two decimal
                                          places

  Rate Affixed in   Double                Required
  Document Version                        
  Data                                    

  Metered Affixed   See Table\            Optional, required for Metered
  Method            "Metered Affixed      Affixed postage
                    Method Indicator      
                    Values"               

  Combined Mailing  Non negative integer  Optional, only applicable to a
  ID                                      combined mailing from more than
                                          one payee or permit holder

  Single Piece      Double                Optional, fill with zero for
  Dimensional                             consolidated postage statement
  Weight                                  

  Enclosing Volume  Simple 1-5 (should be Optional, used to indicate
  Number            6)                    Volume Number of Periodicals for
                                          a non-incidental enclosure of
                                          Standard Mail or First Class
                                          Mail

  Enclosing Issue   Simple 1-6            Optional, used to indicate Issue
  Number                                  Number of Periodicals for a
                                          non-incidental enclosure of
                                          Standard Mail or First Class
                                          Mail

  Enclosing Issue   Date Time             Optional, used to indicate issue
  Date                                    date of Periodicals for a
                                          non-incidental enclosure of
                                          Standard Mail or First Class
                                          Mail. *PostalOne!* uses only
                                          date.

  Price Type        Retail, discount      Optional, used to establish
                                          price for Priority Mail

  Move Update       See Table "Move       Optional
                    Update Values"        

  Permit Holder     Complex               Required
  Data                                    

  MID in Permit     Complex               Optional, choose MID6 or MID9 if
  Holder Data                             used.

  MID6 or MID9 in   String                Required, must choose MID6 or
  MID in Permit                           MID9. If MID6 must have six
  Holder Data                             digits; if MID 9 must have nine
                                          digits. Must include leading
                                          zeros.

  Contact Name in   String 60             Required, *PostalOne!* does not
  Permit Holder                           use this field. Contact name is
  Data                                    from permit data.

  Permit            Complex               The Publication Number or Permit
  Publication Data                        Number data is Required
  in Permit Holder                        
  Data                                    

  Permit Number in  String 1-8            Required, if Permit Number
  Permit Holder                           chosen. Must match the Permit
  Data                                    number in the *PostalOne!*
                                          system.

  Permit Type in    See Table\            Optional, Required for unique
  Permit Holder     "Permit Type Values"  match to a permit in the
  Data                                    *PostalOne!* system.

  Permit ZIP 4 in   String 9              ZIP+4 for the Permit
  Permit Holder                           
  Data                                    

  Publication       String 9              Required if Publication Number
  Number in Permit                        is chosen. Validation will
  Holder Data                             reject Publication Number in
                                          this Postage Statement message.
                                          Use the Periodicals Postage
                                          Statement.

  Mailing Owner     Complex               Optional, *PostalOne!* requires
  Data                                    this data if there is an agent
                                          mailing for a mail owner.
                                          Otherwise the Permit holder is
                                          the mail owner.

  MID in Mailing    Complex               Optional, choose MID6 or MID9 if
  Owner Data                              used.

  MID6 or MID9 in   String                Required, must choose MID6 or
  MID in Mailing                          MID9. If MID6 must have six
  Owner Data                              digits; if MID 9 must have nine
                                          digits. Must include leading
                                          zeros.

  Contact Name in   String 60             Required, *PostalOne!* does not
  Mailing Owner                           use this field. Contact name is
  Data                                    from permit data.

  Permit            Complex               The Publication Number or Permit
  Publication Data                        Number data is Required
  in Mailing Owner                        
  Data                                    

  Permit Number in  String 1-8            Required, if Permit Number
  Mailing Owner                           chosen. Must match the Permit
  Data                                    number in PostalOne

  Permit Type in    See Table\            Optional, Required for unique
  Mailing Owner     "Permit Type Values"  match to a permit in PostalOne
  Data                                    

  Permit ZIP 4 in   String 9              ZIP+4 for the Permit
  Mailing Owner                           
  Data                                    

  Publication       String 9              Required if Publication Number
  Number in Mailing                       is Chosen. *PostalOne!* will
  Owner Data                              reject Publication Number in
                                          this Postage Statement message.
                                          Use the Periodicals Postage
                                          Statement.

  Mailing Agent     Complex               Optional, *PostalOne!* requires
  Data                                    this data if there is an agent
                                          mailing for the mail owner.

  MID in Mailing    Complex               Optional, choose MID6 or MID9 if
  Agent Data                              used.

  MID6 or MID9 in   String                Required, must choose MID6 or
  MID in Mailing                          MID9. If MID6 must have six
  Agent Data                              digits; if MID 9 must have nine
                                          digits. Must include leading
                                          zeros.

  Contact Name in   String 60             Required, *PostalOne!* does not
  Mailing Agent                           use this field. Contact name is
  Data                                    from permit data.

  Permit            Complex               The Publication Number or Permit
  Publication Data                        Number data is Required
  in Mailing Agent                        
  Data                                    

  Permit Number in  String 1-8            Required, if Permit Number
  Mailing Agent                           chosen. Must match the Permit
  Data                                    number in PostalOne

  Permit Type in    See Table\            Optional, Required for unique
  Mailing Agent     "Permit Type Values"  match to a permit in PostalOne
  Data                                    

  Permit ZIP 4 in   String 9              ZIP+4 for the Permit
  Mailing Agent                           
  Data                                    

  Publication       String 9              Required if Publication Number
  Number in Mailing                       is Chosen. *PostalOne!* will
  Agent Data                              reject Publication Number in
                                          this Postage Statement message.
                                          Use the Periodicals Postage
                                          Statement.

  Permit Holder for Complex               Optional, *PostalOne!* uses this
  AP Data                                 data to bill additional postage
                                          to a different party than the
                                          permit holder.

  MID in Permit     Complex               Optional, choose MID6 or MID9 if
  Holder for AP                           used.
  Data                                    

  MID6 or MID9 in   String                Required, must choose MID6 or
  MID in Permit                           MID9. If MID6 must have six
  Holder for AP                           digits; if MID 9 must have nine
  Data                                    digits. Must include leading
                                          zeros.

  Contact Name in   String 60             Required, *PostalOne!* does not
  Permit Holder for                       use this field. Contact name is
  AP Data                                 from permit data.

  Permit            Complex               The Publication Number or Permit
  Publication Data                        Number data is Required
  in Permit Holder                        
  for AP Data                             

  Permit Number in  String 1-8            Required, if Permit Number
  Permit Holder for                       chosen. Must match the Permit
  AP Data                                 number in PostalOne

  Permit Type in    See Table\            Optional, Required for unique
  Permit Holder for "Permit Type Values"  match to a permit in PostalOne
  AP Data                                 

  Permit ZIP 4 in   String 9              ZIP+4 for the Permit
  Permit Holder for                       
  AP Data                                 

  Publication       String 9              Required if Publication Number
  Number in Permit                        is Chosen. *PostalOne!* will
  Holder for AP                           reject Publication Number in
  Data                                    this Postage Statement message.
                                          Use the Periodicals Postage
                                          Statement.
  ------------------------------------------------------------------------

#### Postage Statement Create Response {#postage-statement-create-response .unnumbered}

The PostageStatementCreateResponse includes the
PostageStatementCreateAccept and PostageStatementCreateReject blocks.
The PostageStatementCreateAccept includes the *PostalOne!* assigned
StatementID, TrackingID and calculated TotalPostage and TotalPostageDue.
The PostageStatementCreateAccept includes the UserPostageStatementID if
provided. Both blocks include ReturnInfo.

#### Postage Statement Cancel Request and Response {#postage-statement-cancel-request-and-response .unnumbered}

The PostageStatementCancelRequest includes the attributes
CustomerGroupID and MailingGroupID. The SubmittingParty and
SubmittingSoftware are required. The StatementID is optional. If there
is no StatementID all the postage statements in the MailingGroupID will
be cancelled. Finalized postage statements cannot be cancelled.

The PostageStatementCancelResponse includes the
PostageStatementCancelAccept and the PostageStatementCancelReject
messages. The PostageStatementCancelAccept includes the *PostalOne!*
assigned CancelConfirm ID and StatementID, The
PostageStatementCancelAccept includes the UserPostageStatementID if
provided.

#### Postage Statement Status Query Request and Response {#postage-statement-status-query-request-and-response .unnumbered}

The PostageStatementStatusQueryRequest requires the attributes
CustomerGroupID and MailingGroupID. The
PostageStatementStatusQueryRequest also requires SubmittingParty,
SubmittingSoftware, StatementID, and MailingFacility. Other optional
fields are available.

The PostageStatementStatusQueryResponse includes a QueryResults message
and a QueryError message. The QueryResults provides the
USPSPostageStatementSequenceID, the UserPostageStatementID if provided
and the postage statement status. Both QueryResults and QueryError
include ReturnInfo.

### Periodicals Postage Statement Messages {#periodicals-postage-statement-messages .unnumbered}

#### Periodical Statement Create Request and Response {#periodical-statement-create-request-and-response .unnumbered}

Use the Periodical Statement Create Request or the Consolidated
Periodical Statement Create Request to create a PS Form 3541.
Periodicals pending application are not supported. Use Mail.dat or
Postal Wizard for these. Choose the Form Type appropriate for the
postage statement you want to create. Choose the Rate Type appropriate
for the postage statement. Next choose the Extended Form Type to use
either the summary data postage lines and extra services or the detailed
postage lines and extra services. The detailed lines allow for entry
point information. The postage statement must have a permit holder. If
the permit holder is not the mail owner, the postage statement must have
a mailing agent and a mail owner. Insert the version information if
desired.

The PeriodicalStatementCreateRequest message (used for Single Edition)
describes the postage statement for one copy weight and one advertising
percentage.

Table 3‑22. PeriodicalStatementCreateRequest Fields

  -----------------------------------------------------------------------
  Field               Format and Values      Required or Not
  ------------------- ---------------------- ----------------------------
  Advertising         Percentage -- total    Required
  Percentage          digits 5, fraction     
                      digits 2, max value    
                      100.00.                

  Automation Address  Date Time              Not Required, Required for
  Match Date                                 Automation mailing.
                                             *PostalOne!* uses only date.

  Customer Reference  Simple 1-40            Not Required, *PostalOne!*
  ID                                         uses to populate customer
                                             reference ID field on the
                                             Postage Statement

  User Postage        Simple 1-10 (May be    Not Required, *PostalOne!*
  Statement ID        lengthened in a future uses to populate User
                      release.)              Postage Statement ID

  Carrier Route       Date Time              Not Required, Required for
  Address Matching                           automation carrier route
  Date                                       mail. *PostalOne!* uses only
                                             date.

  Carrier Route       Date Time              Not Required, required for
  Sequencing Date                            carrier route sequenced
                                             mail. *PostalOne!* uses only
                                             date.

  Certification Data  Contact Name (simple   Required, this is the party
                      1-40) and Phone Number that signs the certification
                      3,4,4                  statement on the postage
                                             statement

  Container count     Complex                Required, Non negative
                                             integer for each of Other
                                             type, Pallets, Sacks, Trays
                                             1mm, Trays 2emm, Trays 2mm,
                                             Trays Flat

  Copy Weight         Double                 Optional, Required for
                                             *PostalOne!* postage
                                             calculation

  Edition Code        Simple 1-20            Optional, if provided will
                                             print on postage statement

  First Issue Date    Date Time              Optional, not used by the
                                             *PostalOne!* system.

  Form Type           Must be PE             Required,

  Issue Date          Date Time              Required, *PostalOne!* uses
                                             only date

  Issue Frequency     String 1-20            Optional, not used by the
                                             *PostalOne!* system,
                                             frequency on postage
                                             statement comes from
                                             Publication data.

  Issues in Month     Non negative integer   Optional, not used by the
                                             *PostalOne!* system.

  Mail XML Job ID     Simple, 1-8            Optional, *PostalOne!*
                                             displays this on the
                                             dashboard?

  Last Issue Date     Date Time              Optional, not used by the
                                             *PostalOne!* system.

  Mailing Date        Date Time              Required, *PostalOne!* uses
                                             this date to determine
                                             prices and display on the
                                             postage statement.
                                             *PostalOne!* does not use
                                             the time.

  Mailing Group ID    Non negative integer   Required, \[redundant with
                                             header\]?

  Over 10             Boolean                Required (0) No subscribers
                                             or requesters over the 10%
                                             rule (1) subscribers or
                                             requesters over the 10%
                                             rule.

  Limited Circulation Yes No                 Required
  Discount Claimed                           

  Periodical Line     Complex                Required
  Item Data                                  

  Copies in           Non negative integer   Optional, total copies for
  Periodical Line                            pound postage lines.
  Item Data                                  *PostalOne!* calculates from
                                             Subreq copies and Non
                                             Copies.

  Discount Quantity   Double                 Optional, Required for
  in Periodical Line                         Discount type 1 to indicate
  Item Data                                  In County number of
                                             addressed pieces at DDU
                                             prices

  Discount Type in    See Table "Surcharge   Discount Type 1 is used for
  Periodical Line     Discount Type Values"  input all others are used
  Item Data                                  for output on the receipt.

  In Out County       See Table "In-County,  Required
  Indicator in        Outside-County         
  Periodical Line     Indicator Values"      
  Item Data                                  

  Line Label in       Simple, 1-80           Optional, *PostalOne!*
  Periodical Line                            determines the correct line
  Item Data                                  label

  Line Number in      Simple, 1-3            Optional, *PostalOne!*
  Periodical Line                            determines the correct line
  Item Data                                  number

  Non Copies in       Non negative integer   Optional, required for non
  Periodical Line                            subscriber copies or non
  Item Data                                  requester copies for pound
                                             postage lines

  Advertising         Percentage -- total    Optional, not used by the
  Percentage in       digits 5, fraction     *PostalOne!* system.
  Periodical Line     digits 2, max value    
  Item Data           100.00.                

  Piece Rate in       Double                 Optional, not used by the
  Periodical Line                            *PostalOne!* system.
  Item Data                                  

  Pieces in           Non negative Integer   Optional, required for piece
  Periodical Line                            postage lines.
  Item Data                                  

  Postage Amount in   Double                 Optional, not used by
  Periodical Line                            PostalOne
  Item Data                                  

  Pound Rate in       Double                 Optional, Not used by
  Periodical Line                            PostalOne
  Item Data                                  

  Rate Category in    Must use Rate Category Optional, Required on lines
  Periodical Line     by Form Type PE        that require rate category
  Item Data                                  

  Section in          Simple 0-1             Optional, *PostalOne!* does
  Periodicals Line                           not use this field.
  Item Data                                  

  SubReq Copies in    Non negative integer   Optional, Required if needed
  Periodicals Line                           on pound postage statement
  Item Data                                  lines

  Zone in Periodicals See Table "Zone        Optional, required in pound
  Line Item Data      Values"                postage statement lines.

  Container Type in   See Table\             Optional, Required for
  Periodical Line     "Container Charge      Outside County Container
  Item Data           Container Type Values" charge lines. Can only be
                                             'P' or 'S'

  Chargeable          See Table\             Optional, Required for
  Container Level in  "Container Level       Outside County container and
  Periodical Line     Values"                bundle charge lines.
  Item Data                                  

  Chargeable Bundle   See Table\             Optional, Required for
  Level in Periodical "Bundle Level Values"  Outside County bundle charge
  Line Item Data                             lines.

  Bundles in          Double                 Optional, Required for
  Periodical Line                            Outside County bundle charge
  Item Data                                  lines. *PostalOne!* rounds
                                             to four decimal places on
                                             each line.

  Chargeable Entry    See Table "Container   Optional, Required for
  Level in Periodical Charge Entry Facility  Outside County container and
  Line Item Data      Type Values"           bundle charge lines.

  Containers in       Double                 Optional, Required for
  Periodical Line                            Outside County container
  Item Data                                  charge lines. *PostalOne!*
                                             rounds to four decimal
                                             places on each line.

  Machinable Flag in  Yes No                 Optional, Required for piece
  Periodical Line                            postage lines.
  Item Data                                  

  Periodical          Must be N              Required
  Statement Type                             

  Post Office of      String 5               Required, *PostalOne!* will
  Mailing ZIP                                display the post office of
                                             mailing ZIP assigned to the
                                             post office in PostalOne

  Processing Category See Table\             Optional, required by
                      "Processing Category   PostalOne
                      Values"                

  Publication Title   String 60              Optional, *PostalOne!* gets
                                             the title from the
                                             Publication Number record

  Rate Type           See Table "Rate Type   Optional
                      Values" for the        
                      appropriate postage    
                      statement              

  Sheet Weight        Double                 Optional, not used by
                                             PostalOne

  Single Ride Along   Double                 Required, fill with 0 if not
  Weight                                     applicable

  Statement Sequence  String 1-20            Optional, if provided
  Number                                     *PostalOne!* will display
                                             this on the postage
                                             statement.

  Statement Sequence  Simple                 Optional, *PostalOne!*
  Number                                     displays this data on the
                                             postage statement

  Entry Facility Type See Table\             Optional, Required for
                      "Entry Facility Type   discounts based on dropping
                      Values"                to entry facility type.

  Entry ZIP           Simple 5               Optional, if provided will
                                             be displayed on the postage
                                             statement register.

  Agency cost code    Must be numeric, can   Optional, required if a
                      start with leading     government publication.
                      zeros and can be 5 or  
                      6 digits long          

  Periodical Combined Complex                Optional, required if a
  Mailing Data                               combined mailing.

  Combined Mailing ID Non negative integer   Required for Periodicals
  in Periodical                              combined mailing. This must
  Combined Mailing                           be the same value for every
  Data                                       record of a combined
                                             mailing.

  First Periodical    Boolean                Required The first combined
  Combined Mailing in                        mailing statement must have
  Periodical Combined                        firstCombinedMailing set to
  Mailing Data                               True and the total number of
                                             statements in the combined
                                             mailing. The *PostalOne!*
                                             system starts the combined
                                             Mailing process and saves
                                             the statement in "COM" stage
                                             once the first statement has
                                             been received. All
                                             statements in the mailing
                                             except the first should have
                                             firstCombinedMailing set to
                                             False.

  Last Periodical     Boolean                Required The last combined
  Combined Mailing in                        mailing statement must have
  Periodical Combined                        lastCombinedMailing set to
  Mailing Data                               True. All statements in the
                                             mailing except the last
                                             should have
                                             lastCombinedMailing set to
                                             False. The *PostalOne!*
                                             system completes the
                                             combined mailing, processes
                                             the statements and changes
                                             the stage of those
                                             statements from "COM" to
                                             "UPD" upon receiving the
                                             LastCombinedMailing flagged
                                             Statement.

  Max Statements in   Integer                Required, The number of
  Periodical Combined                        statements in the combined
  Mailing Data                               mailing cannot be changed
                                             after submitting the first
                                             combined mailing statement.
                                             The *PostalOne!* system
                                             discards any change in the
                                             number of statements after
                                             the combined mailing's first
                                             statement.

  Repositionable      Required               Boolean (1) if
  Notes Indicator                            repositionable notes (0) if
                                             no repositionable notes.

  Document Version    Complex                Optional, required for
  Data                                       version report

  Version ID in       Simple 1-10            Required
  Document Version                           
  Data                                       

  Version Name in     Simple 1-12            Required
  Document Version                           
  Data                                       

  Description in      Simple 1-30            Optional
  Document Version                           
  Data                                       

  Piece Weight in     Double                 Required
  Document Version                           
  Data                                       

  Ad Percent in       Percentage -- total    Optional, Required for
  Document Version    digits 5, fraction     Periodicals version report,
  Data                digits 2, max value    set as string 5 so put in
                      100.00.                digits needed assuming two
                                             decimal places

  Rate Affixed in     Double                 Required, fill with zero for
  Document Version                           Periodicals.
  Data                                       

  For Consolidation   Boolean                Optional, required if (1) to
                                             have this postage statement
                                             consolidated together with
                                             other postage statements

  Move Update         See Table "Move Update Optional, *PostalOne!* will
                      Values"                not use this field. Move
                                             Update does not apply to
                                             Periodicals.

  Mailing Agent Data  Complex                Optional, *PostalOne!*
                                             requires this data if there
                                             is an agent mailing for the
                                             mail owner.

  MID in Mailing      Complex                Optional, choose MID6 or
  Agent Data                                 MID9 if used.

  MID6 or MID9 in MID String                 Required, must choose MID6
  in Mailing Agent                           or MID9. If MID6 must have
  Data                                       six digits; if MID 9 must
                                             have nine digits. Must
                                             include leading zeros.

  Contact Name in     String 60              Required, *PostalOne!* does
  Mailing Agent Data                         not use this field. Contact
                                             name is from permit data.

  Permit Publication  Complex                The Publication Number or
  Data in Mailing                            Permit Number data is
  Agent Data                                 Required

  Permit Number in    String 1-8             Required, if Permit Number
  Mailing Agent Data                         chosen. Must match the
                                             Permit number in PostalOne

  Permit Type in      See Table\             Optional, Required for
  Mailing Agent Data  "Permit Type Values"   unique match to a permit in
                                             PostalOne

  Permit ZIP 4 in     String 9               ZIP+4 for the Permit
  Mailing Agent Data                         

  Publication Number  String 9               Required if Publication
  in Mailing Agent                           Number is Chosen.
  Data                                       

  Publisher Data      Complex                Required, *PostalOne!* uses
                                             this data to bill the
                                             postage statement.

  MID in Publisher    Complex                Optional, choose MID6 or
  Data                                       MID9 if used.

  MID6 or MID9 in MID String                 Required, must choose MID6
  in Publisher Data                          or MID9. If MID6 must have
                                             six digits; if MID 9 must
                                             have nine digits. Must
                                             include leading zeros.

  Permit Publication  Complex                The Publication Number or
  Data in Publisher                          Permit Number data is
  Data in Publisher                          Required
  Data                                       

  Permit Number in    String 1-8             Required, if Permit Number
  Permit Publication                         chosen. Must match the
  Data in Publisher                          Permit number in The
  Data                                       *PostalOne!* system. A 3541
                                             may only have bundle and
                                             container postage for a non
                                             Peroidicals permit number.
                                             Pending Periodicals are not
                                             supported.

  Permit Type in      See Table\             Optional, required by
  Permit Publication  "Permit Type Values"   *PostalOne!* to uniquely
  Data in Publisher                          identify permit number,
  Data                                       except for permit type PE
                                             for Periodicals.

  Permit ZIP 4 in     String 9               ZIP+4 for the Permit
  Permit Publication                         
  Data in Publisher                          
  Data                                       

  Publication Number  String 9               Required for Periodical
  in Permit                                  Statement.
  Publication Data in                        
  Publisher Data                             
  -----------------------------------------------------------------------

#### Expanded Definition of Publisher Data {#expanded-definition-of-publisher-data .unnumbered}

This is used in response messages.

Table 3‑23. Expanded Definition Fields

  -----------------------------------------------------------------------
  Field               Format            Required or Not
  ------------------- ----------------- ---------------------------------
  Publisher Data      Complex           Required, *PostalOne!* uses this
                                        data to bill the postage
                                        statement.

  Address 1 in        String 1-64       Required, Address comes from
  Publisher Data                        Publication Number Data

  Address 2 in        String 1-64       Optional, Address comes from
  Publisher Data                        Publication Number Data

  City in Publisher   String 1-45       Optional, Address comes from
  Data                                  Publication Number Data

  Country in          String 1-45       Optional, Address comes from
  Publisher Data                        Publication Number Data

  DUNS Number in      String 1-20       Optional, if provided will print
  Publisher Data                        as an alternate customer number
                                        on the Postage Statement

  Email in Publisher  String            Optional, Email comes from
  Data                                  Publication Number Data

  MID in Publisher    Complex           Optional, choose MID6 or MID9 if
  Data                                  used.

  MID6 or MID9 in MID String            Required, must choose MID6 or
  in Publisher Data                     MID9. If MID6 must have six
                                        digits; if MID 9 must have nine
                                        digits. Must include leading
                                        zeros.

  CRID in Publisher   String 1-10       Optional, if provided will print
  Data                                  as customer number on the Postage
                                        Statement

  Contact Name in     String 1-60       Required, Contact name is from
  Publisher Data                        permit data.

  Permit Publication  Complex           The Publication Number or Permit
  Data in Publisher                     Number data is Required
  Data in Publisher                     
  Data                                  

  Permit Number in    String 1-8        Required, if Permit Number
  Permit Publication                    chosen. Must match the Permit
  Data in Publisher                     number in the *PostalOne!*
  Data                                  system. A 3541 may only have
                                        bundle and container postage for
                                        a non Periodicals permit number.
                                        Pending Periodicals are not
                                        supported.

  Permit Type in      See Table\        Optional, required by
  Permit Publication  "Permit Type      *PostalOne!* to uniquely identify
  Data in Publisher   Values"           permit number, except for permit
  Data                                  type PE for Periodicals.

  Permit ZIP 4 in     String 9          ZIP+4 for the Permit
  Permit Publication                    
  Data in Publisher                     
  Data                                  

  Publication Number  String 9          Required for Periodical
  in Permit                             Statement.
  Publication Data in                   
  Publisher Data                        

  Phone Area Code     String 3          Required, Phone data comes from
                                        Publication Number data

  Phone Extension     String 5          Optional, Phone data comes from
                                        Publication Number data

  Phone Last 4        String 4          Required, Phone data comes from
                                        Publication Number data

  Phone Prefix        String 3          Required, Phone data comes from
                                        Publication Number data

  State               String            Optional, State comes from Permit
                                        Number Data
  -----------------------------------------------------------------------

#### Periodical Statement Create Response {#periodical-statement-create-response .unnumbered}

The PeriodicalStatementCreateResponse includes a
PeriodicalStatementCreateAccept message and a
PeriodicalStatementCreateReject message. The StatementID includes
*PostalOne!* assigned fields StatementID, Tracking ID and calculated
TotalPostageDue.

#### Periodical Statement Cancel Request {#periodical-statement-cancel-request .unnumbered}

The PeriodicalStatementCancelRequest requires attributes CustomerGroupID
and MailingGroupID. It requires SubmittingParty and SubmittingSoftware.
The StatementID is optional. If the StatementID is not provided, all
statements in the MailingGroupID will be cancelled. If the StatementID
is provided and the postage statement is part of a combined mailing, an
error message will be generated. Finalized postage statements cannot be
cancelled.

#### Periodical Statement Cancel Response {#periodical-statement-cancel-response .unnumbered}

The PeriodicalStatementCancelResponse includes the
PeriodicalStatementCancelAccept and the PeriodicalStatementCancelReject
messages. The PeriodicalStatementCancelAccept includes the
CancelConfirmID and the StatementID if provided.

#### Periodical Statement Query Request {#periodical-statement-query-request .unnumbered}

The PeriodicalStatementQueryRequest requires attributes CustomerGroupID
and MailingGroupID. It requires SubmittingParty and SubmittingSoftware.
StatementID(s) and TrackingIDs are required.

#### Periodical Statement Query Response {#periodical-statement-query-response .unnumbered}

The PeriodicalStatementQueryResponse returns QueryResults or QueryError
messages. The QueryResults message includes PeriodicalStatementData and
ReturnInfo. The QueryError message has ReturnInfo.

#### Consolidated Periodicals Statement Create Request and Response {#consolidated-periodicals-statement-create-request-and-response .unnumbered}

A consolidated Periodicals statement contains one or more Periodicals
postage statements, each of which has a different version number and/or
entry point. Consolidated statements must include both pound and piece
postage amounts. This message consolidates the multiple postage
statements together into one postage statement. This message also states
the postage for the total bundles and containers for all the individual
statements.

Table 3‑24. ConsolidatedPeriodicalStatementCreateRequest Fields

  -----------------------------------------------------------------------
  Field              Format and Values Required or Not
  ------------------ ----------------- ----------------------------------
  Periodical         Complex see       Required. Use Periodical Statement
  Statement          Create Periodical to describe each line in the
                     Statement         individual pound and piece postage
                                       statements for each version and/or
                                       entry point.

  First Statement    String 30         Required, optional in the
  Sequence Number                      *PostalOne!* system. If provided
                                       will be printed on the Postage
                                       Statement

  Last Statement     String 30         Required, optional in the
  Sequence Number                      *PostalOne!* system. If provided
                                       will be printed on the Postage
                                       Statement

  Limited            Yes No            Required
  Circulation                          
  Discount                             

  Publisher Data     Complex           Required, *PostalOne!* uses this
                                       data to bill the postage
                                       statement.

  MID in Publisher   Complex           Optional, choose MID6 or MID9 if
  Data                                 used.

  MID6 or MID9 in    String            Required, must choose MID6 or
  MID in Publisher                     MID9. If MID6 must have six
  Data                                 digits; if MID 9 must have nine
                                       digits. Must include leading
                                       zeros.

  Permit Publication Complex           The Publication Number or Permit
  Data in Publisher                    Number data is Required
  Data in Publisher                    
  Data                                 

  Permit Number in   String 1-8        Required, if Permit Number chosen.
  Permit Publication                   Must match the Permit number in
  Data in Publisher                    the *PostalOne!* system. A 3541
  Data                                 may only have bundle and container
                                       postage for a non Peroidicals
                                       permit number. Pending Periodicals
                                       are not supported.

  Permit Type in     See Table\        Optional, required by *PostalOne!*
  Permit Publication "Permit Type      to uniquely identify permit
  Data in Publisher  Values"           number, except for permit type PE
  Data                                 for Periodicals.

  Permit ZIP 4 in    String 9          ZIP+4 for the Permit
  Permit Publication                   
  Data in Publisher                    
  Data                                 

  Publication Number String 9          Required for Periodical Statement.
  in Permit                            
  Publication Data                     
  in Publisher Data                    

  Mailing Agent Data Complex           Optional, *PostalOne!* requires
                                       this data if there is an agent
                                       mailing for the mail owner.

  MID in Mailing     Complex           Optional, choose MID6 or MID9 if
  Agent Data                           used.

  MID6 or MID9 in    String            Required, must choose MID6 or
  MID in Mailing                       MID9. If MID6 must have six
  Agent Data                           digits; if MID 9 must have nine
                                       digits. Must include leading
                                       zeros.

  Contact Name in    String 60         Required, *PostalOne!* does not
  Mailing Agent Data                   use this field. Contact name is
                                       from permit data.

  Permit Publication Complex           The Publication Number or Permit
  Data in Mailing                      Number data is Required
  Agent Data                           

  Permit Number in   String 1-8        Required, if Permit Number chosen.
  Mailing Agent Data                   Must match the Permit number in
                                       PostalOne

  Permit Type in     See Table\        Optional, Required for unique
  Mailing Agent Data "Permit Type      match to a permit in PostalOne
                     Values"           

  Permit ZIP 4 in    String 9          ZIP+4 for the Permit
  Mailing Agent Data                   

  Publication Number String 9          Required if Publication Number is
  in Mailing Agent                     Chosen.
  Data                                 

  Container Count    Complex           Required, Non negative integer for
                                       each of Other type, Pallets,
                                       Sacks, Trays 1mm, Trays 2emm,
                                       Trays 2mm, Trays Flat

  Periodical Line    Complex           Optional. See description above.
  Item Data                            Required for Outside County
                                       Chargeable Containers and Bundles.
  -----------------------------------------------------------------------

#### Consolidated Periodical Statement Create Response {#consolidated-periodical-statement-create-response .unnumbered}

The ConsolidatedPeriodicalStatementCreateResponse has a
ConsolidatedPeriodicalStatementCreateAccept message and a
ConsolidatedPeriodicalStatementCreateReject message. The
ConsolidatedPeriodicalStatementCreateAccept includes the *PostalOne!*
assigned TrackingID, Statement ID and the calculated TotalPostage. These
response messages include the ReturnInfo with a ReturnCode and
ReturnDescription.

### Payment Messeges {#payment-messeges .unnumbered}

#### PaymentMessageQueryRequest {#paymentmessagequeryrequest .unnumbered}

After paying for postage, send the PaymentMessageQueryRequest. The
request requires the Statement ID, tracking ID, mailing and Customer
group ID besides the submitting party and submitting software.

#### PaymentMessageQueryResponse {#paymentmessagequeryresponse .unnumbered}

PaymentMessageQueryResponse includes a QueryResponse and a QueryError
block. The QueryResponse includes Postage statement data blocks for
postage statement(s). Each Postage statement data block includes
PostageStatementTransactionNumber, CustomerReferenceTransactionNumber,
MailingFacility, PostageAmountPaid, DateOfTransaction, and
TimeOfTransaction. Both messages include ReturnInfo.

### Miscellaneous Messages {#miscellaneous-messages .unnumbered}

These messages are available for customer convenience, but are not
required to participate in Full-service.

#### By For Conflict Query Request and Response {#by-for-conflict-query-request-and-response .unnumbered}

The customer provides the submitting party and software information with
mandatory Job information, either the Mail.dat job info or the Mail.XML
mailing group info to request conflict data for the job. In response,
the USPS responds with the full conflict and conflict reason code and
description on owner and preparer if there is a conflict as responds
with a return code of No data found if there are no conflicts for the
job. Return Codes and their descriptions will be available by the
documented date in the External Timeline document for IM implementation.

#### Postage Adjustment Create Request and Response {#postage-adjustment-create-request-and-response .unnumbered}

The USPS allows the customer to file for postage adjustments in case of
spoilage or shortage. The adjustments can only occur against the
un-finalized postage statements and against the statements with the
latest mailing date. The postage Adjustments messages in Mail.XML 6.0
seem to support adjustments for both Mail.dat jobs and Mail.XML jobs but
in reality only support the postage statements filed through the
Mail.XML process. An errata has been filed to fix that in Errata A
version.

In the Postage Adjustment Create Request, the customer provides the
submitting party and software information with mandatory Job
information, either the Mail.dat job info or the Mail.XML mailing group
info to request potage adjustments. The customer is also required to
provide the StatementID and UserPostageStatementID. In the
PostageAdjustmentCreateResponse message the USPS responds with the
mailing group and either PostageAdjustmentAccept block or reject block.
With the Accept block, the *PostalOne!* system responds with a user ID
of the adjuster ands the confirmation ID for the adjustment. The USPS
can also respond with Return codes and descriptions, optionally as part
of the Accept response. For the reject response, the USPS responds with
one or more return codes and descriptions.

#### Reconciliation Report Query Request and Response  {#reconciliation-report-query-request-and-response .unnumbered}

The customer is not allowed to update the Qualification report once
filed. After the customer goes through the process of printing and
delivering the mail to the USPS, the USPS creates a reconciliation
report that shows how much mail was planned and how much was mailed.
Such reports are called reconciliation reports.

In the ReconciliationReportQueryRequest, the customer is required to
provide the mailing group ID and Customer group ID besides the mandatory
elements of Submitting party and Submitting software. In the
ReconciliationReportQueryResponse message the *PostalOne!* system
responds back with a reconciliation report for every qualification
report with in the Job/mailing group. The USPS responds back with one
Mailing Group Summary and one or more Reconciliation Summary reports.
The message also includes an optional Return Code and description. If
there are issues, the USPS responds back with the Query Error block and
provides one or more Return codes and descriptions to explain the
errors.

#### Mail.dat Container Update Messages {#mail.dat-container-update-messages .unnumbered}

This family of Mail.XML messages allows the update of the Mail.dat
Container Summary records. The key process flow for this message set,
besides an electronic data sender updating his own data, is that a List
provider or mail owner may send his/her Mail.dat to the *PostalOne!*
system, identifying the Printer by providing the MailFacilityID (CRID)
and Zip+4 of the Printer in the segment. The authorization mechanism
used by the USPS today requires that the user account reading or
updating the data must have the same MailingFacilityZip+4 and/or
MailFacilityID (CRID) toed to his/her account which is in the electronic
data found ion the Mail.dat segment file. With this message, after the
List provider/Mail Owner sends the Mail.dat to the USPS *PostalOne!*
system and identifies the printer in the Segment file, the Printer shall
be able to send a container update message to update IM Container
barcodes, to trigger postage statement and transportation updates for
containers in the Segment identified as his/her plant.

The *PostalOne!* system will receive certain container data elements
from the Mail.dat Container Update message that will have the
functionality to individually update fields on the Mail.dat Container
Summary Record (CSM).

-   Ability to update container information sent via Mail.dat

-   Ability to add sibling containers through the sibling messages

The Mail.dat Container Update messages include:

Mail.dat Container Update Request

Mail.dat Container Update Response

#### Sibling Container Messages {#sibling-container-messages .unnumbered}

This family of messages provides the capability to create sibling
containers that share the same detail information, despite being unique
and carrying separate IDs, and supports the Create/Cancel Sibling
Containers messages. When Sibling containers are added through this
message set, the USPS triggers FAST and eDropShip processes as
necessary. This message set cannot be used by the MLOCR mailer to update
a Mail.dat MLOCR job because of very specific MLOCR business rules. The
Sibling container messages include:

Sibling Container Create Request

Sibling Container Create Response

Sibling Container Cancel Request

Sibling Container Cancel Response

#### Container Status Messages {#container-status-messages .unnumbered}

The container status message set allows a mailer, mail owner or
consolidator to provide container key information and find out if the
container has any eDropShip-related or any other issues prior to
shipping the container to the USPS. The eDropShip issues that can
prevent the creation of an electronic 8125 are:

-   invalid barcode (meaning the barcode data format is not valid)

-   payment not finalized (clerk has not yet finalized payment)

-   payment not yet processed (meaning the electronic data has not been
    updated by the mailer to make the container in a ready to pay
    status)

-   entry point payment discount error (meaning the entry point discount
    filed vs. the physical facility where mail is scheduled through FAST
    for delivery does not support the discount type)

In all of these cases, unless the issues are resolved electronically
through an update of data or through the clerk finalizing the postage,
the containers' e8125 will not be generated and sent to the SV devices
for induction. When that container shows up without an e8125 at the
plant, the container can be stopped and its processing can get delayed
or it can be returned to the shipper.

This message set includes:

Container Status Query Request

Container Status Query Response

#### Customer Identification Messages {#customer-identification-messages .unnumbered}

These messages are used by mailers to get their own Mailer IDs and their
customer's Mailer IDs, after they have provided a Mail Owner signed
agreement to the USPS. The CRID messages can be used to get receive
their own CRIDs. The USPS is currently working on a legal process to be
able to give out CRIDs to mailers that belong to mailers customers.

USPS MID Create Request

USPS MID Create Response

USPS MID Query Request

USPS CRID Create Request

USPS CRID Create Response

USPS CRID Query Request

USPS CRID Query Response

#### Fault and Fault Recovery Messages {#fault-and-fault-recovery-messages .unnumbered}

This series of messages is primarily used to support the Asynchronous
communication when the response from the USPS may not be within a 7
second period and the USPS gives out a tracking Id to the customer. The
customer then uses the tracking ID to get his message response back
using the MRRR message set which includes:

Message Response Retrieval Request

Message Response Retrieval Response

#### Software Version of the USPS Messages {#software-version-of-the-usps-messages .unnumbered}

The customer can query the USPS to request the version of the current
PostalOne! software.

#### System Version Query Request and System Version Query Response  {#system-version-query-request-and-system-version-query-response .unnumbered}

The customer is can provide the necessary submitting party and software
information in the request and can receive the Query Results or Query
Error block back from the USPS. The Query Results usually will return
the software status block with an optional return code and description.
IN the Query Errors block, the USPS will respond with Return Codes and
descriptions.

## Additional Rules/Constraints

### Mail.dat Container Update Messages {#mail.dat-container-update-messages-1 .unnumbered}

Through Mail.dat container update request and response messages, the
*PostalOne!* system will allow the customer to change the container's
status, update transportation information (such as entry point, ship
dates, ship times, pick up dates, and pick up times for plant-loaded
mail) and any other elements in the message /other characteristics of a
container such as the barcodes, entry points, weight and any other
element present in the message. Customers may only update information
until postage statement generation.

-   The transportation update will trigger recurring appointment
    processing for FAST and eDropShip, when the sixth byte in the
    appointment is an R and the update was done using a 'T'
    transportation update flag. The *PostalOne!* system will allow
    updating of actual delivery locale key, actual delivery postal Code
    through a T flag after postage has been set to Ready to Pay to
    support Mail Redirection Scenarios.

-   The *PostalOne!* system will not allow updating of Entry Point Entry
    Disc PostalCode, entry disc facility type, actual delivery locale
    key, actual delivery postal Code, if the previous container status
    is an 'R'.

-   The *PostalOne!* system will allow the customer to send a cancel or
    delete status for a container and if the container status was an
    'R', then all postage cancellation processing shall be triggered.

-   The *PostalOne!* system will allow updating of Entry Point Entry
    Disc PostalCode, entry disc facility type, actual delivery locale
    key, actual delivery postal Code, if the previous container status
    is an 'O'.

-   If the customer updates the container status to an R then the
    *PostalOne!* system shall trigger all processes it triggers today
    when a customer sends an R status for a container, such as postage
    statement processing, eDropShip processing, reports generation and
    updates based upon the R status.

### Container Status Messages {#container-status-messages-1 .unnumbered}

The *PostalOne!* system will support status checking through Container
Status Query Request and Response messages. In this release, the
originator of data, the entity identified as the Scheduler or Carrier in
the eDoc, or third parties based upon profile and Cast of Characters
implementation, can check the status of any given container(s) and
ensure when the container is shipped that the induction facility will
not have any issues in accepting the containers.

-   The *PostalOne!* system upon receiving the container status message
    shall go to the container management system of eDropShip to find out
    all validation status of the requested container(s) and respond to
    the customer with the status information.

-   If there are any issues or validation errors for one or more
    containers, then the *PostalOne!* system shall respond back to the
    customer with validation failures for one or more container(s).

## Error Codes/Return Values

Faults, such as a message timeout or invalid XML are to be communicated
using the \<fault element and returned within the detail section of the
SOAP fault. The fault is made up of a tracking ID and one or more fault
codes and optional fault descriptions. The USPS will update this guide
and provide all the return codes, error codes and their descriptions, as
well the WSDLs for Release 2 available to the industry on the dates
documented in the External TimeLine for IM implementation document made
available to the MTAC 122 work group.

## Additional Constraints

TBD

## WSDL Information

WSDL for Release 2 will be made available to the industry on the dates
documented in the External TimeLine for IM implementation document.

# Full-service Data Distribution -- Release 1.0

## Purpose

This section describes the technical implementation and ways in which
customers will be able to receive the Full-service data feedback as part
of the USPS Full-service implementation.

The Full-service program, through the *PostalOne!* System, will provide
Start-the-Clock, Container Visibility, Confirm (Full-service Only),
Address Correction Report, and Nixie Detail data to the customers
identified as recipients of the Full-service feedback.

## Which methods does the *PostalOne!* system support for Full-service data feedback?

The USPS will provide multiple options to receive the Full-service data,
which are as follows:.

Table 4‑25. Full-service Data Feedback Options

  ----------------------------------------------------------------------------
                           Options for                           
                           Data Exchange                         
  ---- ------------------- ------------- ---------- ------------ -------------
  No   Data / Service      Browser based Browser    Mail.XML     Mail.XML Push
                           HTTPS         based      Pull         (USPS Invokes
                           Download      Report     (Customer    Customer Web
                           (Compressed   (over      Invokes USPS Service)
                           Files)        HTTPS)     Web Service) 

  1    Start-the-Clock     No            Yes        Yes          Yes

  2    Container           No            Yes        Yes          Yes
       Visibility/Scan                                           

  3    ACS                 Yes           No         Yes          Yes

  4    Nixie Detail        Yes           No         Yes          Yes
  ----------------------------------------------------------------------------

**FTP** -- File Transfer Protocol method. FTP support is phasing out to
meet USPS Security standards for secured, guaranteed solutions. Any USPS
services that currently provide data through the FTP protocol to its
customers will provide ample time and communication to the USPS
customers and collaborate with the customers to help with transition
before transitioning to the non-FTP protocol data communication 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.

## What do you need to receive your data through the data exchange methods identified?

### Step 1  {#step-1 .unnumbered}

The customers must be registered *PostalOne!* users and must have signed
data exchange agreements in order to send or receive electronic data
from the *PostalOne!* system.

It is as easy as visiting the *PostalOne!* home page at
[www.usps.com/postalone](http://www.usps.com/postalone) and clicking the
**Learn More** button on the right under New Customers. There, you will
find additional information about the program and application process.
If you have questions, call the *PostalOne!* Customer Care Center at
(800) 522-9085.

Once you are a registered user and have the ability to access the
*PostalOne!* system you will have access to the browser based HTTPS
reports and data download options as well, you will have the ability to
perform electronic data exchange with the USPS *PostalOne!* system
through approved methods.

### Step 2  {#step-2 .unnumbered}

The customers interested in automated electronic data exchange currently
have four options available to them for receiving electronic data from
the USPS for Full-service mailings.

Browser based HTTPS Download (Compressed Files) - The first available
data exchange option is secure browser based *[compressed file
download]{.underline}*. No other information for Full-service will be
available through browser based download method, other than Address
Correction, and Nixie Detail data.

Browser based HTTPS Reports - The second option available to customers
is viewable browser based reports. The only data available through
browser based reports in Start-The-Clock and Container Visibility data.

Mail.XML Pull (Customer Invokes USPS Web Services) -- The Mail.XML is an
IDEAlliance specification and does not require any IDEAlliance fee to
use/implement the specification. The latest version of Mail.XML is
version 6.0-A available at the
[http://www.mailxml.org](http://www.mailxml.org/) site. Customers can
pull their information whenever they desire, using Request and Response
methods for StartTheClock, Container Scans, ACS, and Nixie data.

Mail.XML Push (USPS Invokes the Customer's Web Services) -- The Mail.XML
specification also provides Web Services Methods where the customer can
register with *PostalOne!* as a subscriber of detail data (delivery
messages) or as a subscriber of notifications that tell the customer,
your data is ready to be pulled. The customer can register to
automatically receive either the detail data or the notifications as
they pertain to StartTheClock, Container Scans, ACS, and Nixie data.

The Mail.XML specification is a strategic communication method for data
exchange, agreed to by USPS and the mailing industry. It is
bi-directional, near real time and can convert large data transactions
into smaller transactions while providing guaranteed delivery,
verification and near real-time conflict resolution capabilities. The
sender and receiver can validate the data, verify guaranteed delivery
and actually converse intelligently both ways to report any issues with
data transfer or with business issues found within the data.

## How do you implement/use the Mail.XML available for Full-service data distribution?

The specification is available at
[http://www.mailxml.org](http://www.mailxml.org/).

### Why use Mail.XML-based Data Distribution? {#why-use-mail.xml-based-data-distribution .unnumbered}

Mail.XML version 6.0 is created to enhance efficiency and ease of
transmission for the small and large data volume communications. The
message sets are designed with an attribute that allows all large data
volume messages to be broken up in as many unique child transactions as
the USPS and the industry feels will be easily and efficiently supported
by the existing network infrastructure. In other words, a 10 MB file can
be broken up in ten 1MB transactions or twenty 500KB in size
transactions. The Mail.XML allows for verification and thorough
validation of the data, right away, in near real time. More importantly,
with Mail.XML your software can respond back to the USPS *PostalOne!*
system right away to let the USPS know if you successfully received all
the data or not? You can also let the USPS know, right away, if the data
sent by the USPS to you had problems, the data was bad or incomplete or
did not belong to you, etc; so, automatic conflict resolution triggers
can result in immediate action by the USPS.

Other important thing for your business is that unlike Mail.dat, there
are almost no wait times for you to file your postage, qualification,
and container and bundle reports with the USPS since you are filing
final documents.

**Prerequisite:**

All customers who want to receive Full-service data feedback must be
registered *PostalOne!* users. The customer must have gone through the
USPS *PostalOne!* approval and activation process for this business
function and may have profiles setup in *PostalOne!* to provide data
distribution guidance for their data. The Data distribution
authorization is driven by the data provided in the eDoc to the
*PostalOne!* system about the By/For relationship. The profiles defined
below, if setup by the customer, take precedence on authorization rules
over the eDoc data.

## Data Distribution Authorization Profiles

Mailers may set up profiles (static or dynamic) in order to allow other
agents (Mail Preparers and/or third-parties) to gain access to their
mailing data. If a mailer has set up a profile in *PostalOne!* system
(implemented in the MID system), SASP will combine the profile
relationships with the By/For information to determine the correct data
recipients. When setting up a profile in the *PostalOne!* Mailer ID
system, mailers must identify the intended data recipient using the
recipient MID. .

### Static {#static .unnumbered}

Static relationships are created when a mailer desires to engage a
third-party to manage their data for a specific Mailer ID and service.

Four levels of access may be provided in a static relationship:
Delegated, Complete, Partial -- Mail Preparer or Partial -- MID on
Piece.

### Delegated {#delegated .unnumbered}

If the Mailer ID associated with the mailing has created a delegated
profile and given control of their profile to a Mail Preparer or
third-party, SASP will identify the type of profile (if any) created by
the delegated party (Complete, Partial -- Mail Preparer, Partial -- MID
on Piece or Dynamic). If no subsequent profile has been created, SASP
will distribute data to the Delegated Participant.

### Complete {#complete .unnumbered}

If the Mailer ID associated with the mailing has set up a Complete
relationship with a designated recipient, SASP will distribute data to
the designated recipient, regardless of the specific mailing
information.

### Partial -- Mail Preparer {#partial-mail-preparer .unnumbered}

If the Mailer ID associated with the mailing has set up Partial -- Mail
Preparer relationships with several designated recipients, SASP will
identify the type of service and distribute data to the mail preparer
for the mailpieces they prepared.

### Partial -- MID on Piece {#partial-mid-on-piece .unnumbered}

If the Mailer ID associated with the mailing has set up a Partial -- MID
on Piece relationship, SASP will distribute ACS data to the Mailer ID
associated with the mailpiece.

### Dynamic {#dynamic .unnumbered}

Dynamic relationships are created when a mailer desires to engage a
third-party to manage their data for a specific mailing. Creation of a
dynamic relationship serves as a pre-qualification for the designated
party. The mailer must still submit a Cast of Characters message in
order to indicate the intended data recipient. The dynamic data
distribution messages must be sent to the USPS at least 3 hours prior to
the induction of mail.

## Messages Supported in Release 1.0

The following messages are supported in Release 1.0 of *PostalOne!*
Full-Service:

Table 4‑26. Full-service Messages Supported in Release 1.0

  --------------------------------------------- --------------------------------
  FullServiceAddressCorrectionDelivery          StartTheClockDelivery

  FullServiceAddressCorrectionNotification      StartTheClockNotification

  FullServiceAddressCorrectionQueryRequest      StartTheClockQueryRequest

  FullServiceAddressCorrectionQueryResponse     StartTheClockQueryResponse

  FullServiceContainerVisibilityDelivery        CastofCharactersCancelRequest

  FullServiceContainerVisibilityNotification    CastofCharactersCancelResponse

  FullServiceContainerVisibilityQueryRequest    CastofCharactersCreateRequest

  FullServiceContainerVisibilityQueryResponse   CastofCharactersCreateResponse

  FullServiceNixieDetailDelivery                CastofCharactersUpdateRequest

  FullServiceNixieDetailRequest                 CastofCharactersUpdateResponse

  FullServiceNixieDetailResponse                DeliveryResponse

  FullServiceNixieNotification                  NotificationResponse
  --------------------------------------------- --------------------------------

## Messages Not Supported in Release 1 or 2

The following messages will NOT be supported in Full-service Release 1
or Release 2 for eDoc:

-   DeliveryPointValidationNotification

-   DeliveryPointValidationDelivery

-   DeliveryPointValidationRequest

-   DeliveryPointValidationResponse

## Push Messages

If the customer wants to automatically receive the data as soon as it is
ready (Push model), the customer must have registered their Web Services
URL, implemented a WSDL for push (Delivery and Notification) Mail.XML
messages and must have implemented Authentication and Authorization to
authenticate and authorize transactions sent by the *PostalOne!* system
to your server. The WSDLs and XSDs are available at the end of the
document which MUST be used to ensure conformity and standardization of
the data exchange between *PostalOne!* and the customers. Within the
*PostalOne!* system, a user interface is created to allow the customer
to provide the information and indicate which messages he/she wants to
receive as a Push model. The customer must have also checked the type of
data he/she wants to receive as a Push. All push messages end in the
word "Delivery" or in the word "Notification".

The messages that end with the word "Delivery" mean that the message has
all the detail data and the customer is receiving the data because the
customer registered with the USPS *PostalOne!* system to receive the
detail data as it becomes available.

The messages that end with the word "Notification" mean that the message
will only say that the 'data is ready' to be pulled by the customer
through Pull Mail.XML mechanism or other approved method. Notification
messages will 'not' have detail data. The customer will have the option
to choose the push messages that they want the *PostalOne!* System to
use and send the data to the customer. e.g., a customer may decide to
use Pull messages for ACS but may decide to receive continuous feeds of
data for StartTheClock "Delivery" message or Nixie "Delivery" message
and may choose to receive the notifications through the Notification
messages.

## Pull Messages 

If the customer wants to get the data based upon their own need; and
want to Pull the data from the *PostalOne!* system, they will not need
to host their own Web Services URL. They will need the software that can
send a message request to the *PostalOne!* system for any available data
and *PostalOne!* will respond back to your software with the data. You
need to be approved and activated by the USPS to be able to use this
software in production.

## Messages 

The USPS will initially implement the following Mail.XML messages in
support of Full-service Push/Pull methods for Full-Service data
feedback.

### Push Messages Supported in Release 1 of Full-service implementation: {#push-messages-supported-in-release-1-of-full-service-implementation .unnumbered}

1.  Response Messages for Notification and Delivery:

-   NotificationResponse

-   DeliveryResponse

3.  StartTheClock:

-   StartTheClockNotification

-   StartTheClockDelivery

4.  Container Visibility:

-   FullServiceContainerVisibilityNotification

-   FullServiceContainerVisibilityDelivery

5.  ACS:

-   FullServiceAddressCorrectionNotification

-   FullServiceAddressCorrectionDelivery

6.  Nixie:

-   FullServiceNixieDetailNotification

-   FullServiceNixieDetailDelivery

For the above messages, you need to implement the USPS-provided WSDL and
XSD, and to implement on your side as a server solution that can accept
requests from the USPS *PostalOne!* system and also to provide
*PostalOne!* with the proper URL and access information in order for
*PostalOne!* to push the data to your server.

### Pull Messages Supported in Release 1 of Full-service implementation: {#pull-messages-supported-in-release-1-of-full-service-implementation .unnumbered}

1.  StartTheClock:

-   StartTheClockQueryRequest

-   StartTheClockQueryResponse

7.  Container Visibility:

-   FullServiceContainerVisibilityQueryRequest

-   FullServiceContainerVisibilityQueryResponse

8.  ACS:

-   FullServiceAddressCorrectionQueryRequest

-   FullServiceAddressCorrectionQueryResponse

9.  Nixie:

-   FullServiceNixieDetaiQueryRequest

-   FullServiceNixieDetailResponse

### Cast Of Characters Messages for Release 1 of Full-service implementation: {#cast-of-characters-messages-for-release-1-of-full-service-implementation .unnumbered}

**CastOfCharacters:**

-   CastOfCharactersCreateRequest

-   CastOfCharactersCreateResponse

-   CastOfCharactersCancelRequest

-   CastOfCharactersCancelResponse

-   CastOfCharactersUpdateRequest

-   CastOfCharactersUpdateResponse

## Additional Business Rules

### Delivery and Notification Messages: {#delivery-and-notification-messages .unnumbered}

#### Response Messages for Notification and Delivery {#response-messages-for-notification-and-delivery .unnumbered}

-   NotificationResponse

Every time the USPS sends a Push 'Notification' message to the customer,
if the customer has registered for one or more 'Notification' messages,
the USPS *PostalOne!* program expects a 'Notification Response' message
from the customer to let the *PostalOne!* system know if all is ok.

All return codes and their descriptions for the Response messages will
be made available by the USPS for implementation based upon the schedule
made available in the External Timeline for IM implementation document.

-   DeliveryResponse

Every time the USPS sends a Push 'Delivery' message to the customer, if
the customer has registered for one or more 'Delivery' messages, the
USPS *PostalOne!* program expects a 'Delivery Response' message from the
customer to let the *PostalOne!* system know if all is ok.

All return codes and their descriptions for the Response messages will
be made available by the USPS for implementation based upon the schedule
made available in the External Timeline for IM implementation document.

#### StartTheClock: {#starttheclock .unnumbered}

1.  StartTheClockNotification

With each StartTheClockNotification message, if the customer has
registered with the *PostalOne!* system to receive the message, the
*PostalOne!* system will provide a

-   date of notification and

-   job information, either the Mail.dat Job ID and User License Code,
    OR the Customer Group ID and MailingGroupID for Mail.XML to the
    customer, so the customer can use the Job information in his/her
    Query request.

10. StartTheClockDelivery

With each StartTheClockDelivery message, if the customer has registered
with the *PostalOne!* system to receive the message, the *PostalOne!*
system will provide the:

-   Job information, either the Mail.dat Job ID and User License Code,
    OR the Customer Group ID and MailingGroupID for Mail.XML to the
    customer.

-   Zero or more StartTheClockBMEUBlock blocks for the job

-   Zero or more StartTheClockDropShipBlock blocks for the job

-   Zero or more StartTheClockPlantLoadBlock blocks for the job

-   In addition, optional return Info block in case of issues or no data
    found. All return codes and their descriptions for the Response
    messages will be made available by the USPS for implementation based
    upon the schedule made available in the External Timeline for IM
    implementation document.

#### Container Visibility: {#container-visibility .unnumbered}

1.  FullServiceContainerVisibilityNotification

With each FullServiceContainerVisibilityNotification message, if the
customer has registered with the *PostalOne!* system to receive the
message, the *PostalOne!* system will provide a

-   date of notification and

-   will provide the job information, either the Mail.dat Job ID and
    User License Code, OR the Customer Group ID and MailingGroupID for
    Mail.XML to the customer, so the customer can use the Job
    information in his/her Query request.

11. FullServiceContainerVisibilityDelivery

With each FullServiceContainerVisibilityDelivery message, if the
customer has registered with the *PostalOne!* system to receive the
message, the *PostalOne!* system will provide the

-   OPTIONAL LargeTransactionDivideroptionalGroupType. This type is
    created to allow breaking up of any large data into multiple
    transactions, where the sender of the large data is providing
    information about how many total transactions, records to expect and
    what is the current transaction number among the total expected
    transactions etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
a.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

b.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

c.  TransmittedRecordCount -- is count of records in the current message
    transaction.

d.  TotalRecordsAccrossMessages -- This is the total expected record
    count when the receiver for the MessageGroupID has received all
    transactions.

e.  LastMessage -- is a Yes or No indicator confirming for the receiver
    that this transaction is the last transaction of the MessageGroupID
    e.g., MessageGroupID 10.

-   SubmittingParty -- The *PostalOne!* system for all Notification and
    Delivery messages will always put a value of 'USPS' in the
    MaildatUserLicense field.

a.  SubmittingSoftware -- The *PostalOne!* system for all Notification
    and Delivery messages will always put

-   The value of 'PostalOne' in the SoftwareName element

-   The value of 'USPS' in the vendor element

-   The most current version number available, such as 19.0 or 20.0 in
    the Version element

-   The *PostalOne!* system will not fill any values in the ApprovalDate
    and ApprovalKey elements

f.  The CRID element is for industry usage and is optional. For the
    Delivery messages, the *PostalOne!* system will not populate this
    element.

g.  The *PostalOne!* system will provide the job information, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML to the customer. The *PostalOne!* system
    will send one or more FullServiceContainerVisibility blocks.

#### ACS: {#acs .unnumbered}

1.  FullServiceAddressCorrectionNotification

With each FullServiceAddressCorrectionNotification message, if the
customer has registered with the *PostalOne!* system to receive the
message, the *PostalOne!* system will provide the

-   SubmittingParty -- The *PostalOne!* system for all Notification and
    Delivery messages will always put a value of 'USPS' in the
    MaildatUserLicense field.

-   SubmittingSoftware -- The *PostalOne!* system for all Notification
    and Delivery messages will always put

a.  The value of 'PostalOne' in the SoftwareName element

```{=html}
<!-- -->
```
h.  The value of 'USPS' in the vendor element

i.  The most current version number available, such as 19.0 or 20.0 in
    the Version element

j.  The *PostalOne!* system will not fill any values in the ApprovalDate
    and ApprovalKey elements

-   The CRID element is for industry usage and is optional. For the
    Delivery messages, the *PostalOne!* system will not populate this
    element.

-   The *PostalOne!* system will provide the job information, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML to the customer.

-   The *PostalOne!* system will provide the NotificationDate, which is
    the date when the message is transmitted.

12. FullServiceAddressCorrectionDelivery

With each FullServiceAddressCorrectionDelivery message, if the customer
has registered with the *PostalOne!* system to receive the message, the
*PostalOne!* system will provide the:

-   OPTIONAL LargeTransactionDivideroptionalGroupType. This type is
    created to allow breaking up of any large data into multiple
    transactions, where the sender of the large data is providing
    information about how many total transactions and records to expect
    and what is the current transaction number among the total expected
    transactions etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
k.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

l.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

m.  TransmittedRecordCount -- is count of records in the current message
    transaction.

n.  TotalRecordsAccrossMessages -- This is the total expected record
    count when the receiver of the MessageGroupID has received all
    messages.

o.  LastMessage -- is a Yes or No indicator confirming for the receiver
    that this transaction is the last transaction of the MessageGroupID
    e.g., MessageGroupID 10.

-   SubmittingParty -- The *PostalOne!* system for all Notification and
    Delivery messages will always put a value of 'USPS' in the
    MaildatUserLicense field.

-   SubmittingSoftware -- The *PostalOne!* system for all Notification
    and Delivery messages will always put

a.  The value of 'PostalOne' in the SoftwareName element

```{=html}
<!-- -->
```
p.  The value of 'USPS' in the vendor element

q.  The most current version number available, such as 19.0 or 20.0 in
    the Version element

r.  The *PostalOne!* system will not fill any values in the ApprovalDate
    and ApprovalKey elements

-   The CRID element is for industry usage and is optional. For the
    Delivery messages, the *PostalOne!* system will not populate this
    element.

-   The *PostalOne!* system will provide the job information, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML to the customer.

-   The *PostalOne!* system will send one or more
    FullServiceAddressCorrection blocks.

#### Nixie:  {#nixie .unnumbered}

1.  FullServiceNixieDetailNotification

With each FullServiceNixieDetailNotification message, if the customer
has registered with the *PostalOne!* system to receive the message, the
*PostalOne!* system will provide the

-   SubmittingParty -- The *PostalOne!* system for all Notification and
    Delivery messages will always put a value of 'USPS' in the
    MaildatUserLicense field.

-   SubmittingSoftware -- The *PostalOne!* system for all Notification
    and Delivery messages will always put

a.  The value of 'PostalOne' in the SoftwareName element

```{=html}
<!-- -->
```
s.  The value of 'USPS' in the vendor element

t.  The most current version number available, such as 19.0 or 20.0 in
    the Version element

u.  The *PostalOne!* system will not fill any values in the ApprovalDate
    and ApprovalKey elements

-   The CRID element is for industry usage and is optional. For the
    Delivery messages, the *PostalOne!* system will not populate this
    element.

-   The *PostalOne!* system will provide the job information, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML to the customer.

-   The *PostalOne!* system will provide the NotificationDate, which is
    the date when the message is transmitted.

13. FullServiceNixieDetailDelivery

With each FullServiceNixieDetailDelivery message, if the customer has
registered with the *PostalOne!* system to receive the message, the
*PostalOne!* system will provide the:

-   OPTIONAL LargeTransactionDivideroptionalGroupType. This type is
    created to allow breaking up of any large data into multiple
    transactions, where the sender of the large data is providing
    information about how many total transactions and records to expect
    and what is the current transaction number among the total expected
    transactions etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
v.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

w.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

x.  TransmittedRecordCount -- is count of records in the current message
    transaction.

y.  TotalRecordsAccrossMessages -- This is the total expected record
    count when the receiver of the MessageGroupID has received all
    messages.

z.  LastMessage -- is a Yes or No indicator confirming for the receiver
    that this transaction is the last transaction of the MessageGroupID
    e.g., MessageGroupID 10.

-   SubmittingParty -- The *PostalOne!* system for all Notification and
    Delivery messages will always put a value of 'USPS' in the
    MaildatUserLicense field.

-   SubmittingSoftware -- The *PostalOne!* system for all Notification
    and Delivery messages will always put

a.  The value of 'PostalOne' in the SoftwareName element

```{=html}
<!-- -->
```
a.  The value of 'USPS' in the vendor element

b.  The most current version number available, such as 19.0 or 20.0 in
    the Version element

c.  The *PostalOne!* system will not fill any values in the ApprovalDate
    and ApprovalKey elements

-   The CRID element is for industry usage and is optional. For the
    Delivery messages, the *PostalOne!* system will not populate this
    element.

-   The *PostalOne!* system will provide the job information, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML to the customer.

The *PostalOne!* system will send one or more
FullServiceNixieDetailDelivery blocks.

### Request and Response Messages {#request-and-response-messages .unnumbered}

#### StartTheClock: {#starttheclock-1 .unnumbered}

1.  StartTheClockQueryRequest

With each StartTheClockQueryRequest message, the customer needs to
provide information for all required blocks.

-   SubmittingParty -- The *PostalOne!* system for all data distribution
    for Full-service messages, i.e., non-FAST, non-eDoc messages, will
    only accept a MID or a CRID as a valid id.

-   SubmittingSoftware -- The *PostalOne!* system for messages that it
    receives from the customer for the Mail.XML will always require

a.  A valid software name in the SoftwareName element

```{=html}
<!-- -->
```
d.  A valid software vendor company name in the vendor element

e.  The most current version number of the software in the Version
    element

f.  A valid Approval Date and a valid Approval Key in the ApprovalDate
    and ApprovalKey elements. The approval date is the date when the
    USPS approved the software usage in the USPS production environment
    and a valid Approval Key is what the USPS provided to the Software
    Vendor or Mailer (who may have developed their own software) as
    authorization to use in all messages.

-   The FAST appointment ID or the CSA Dispatch ID, created by the FAST
    system, can be provided optionally in the ConsigneeApptID or
    CSADispatchNumber elements respectively.

-   The job information can also be provided optionally, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML by the customer.

-   The customer can also optionally provide the Permit information or
    publication number information to receive the StarttheClock data in
    PermitNumber, PermitType and PermitZip4 elements or in the
    PublicationNumber element.

-   The customer must provide a date range in the LowerDateRange and
    UpperDateRange elements.

14. StartTheClockQueryResponse

The StartTheClockQuery Response has two major choice blocks one is
QueryResults and the other is QueryErrors.

-   In QueryResults,

a.  The job info will be returned by the USPS *PostalOne!* system and
    either the Mail.dat Job info will be returned or Mail.XML job info
    will be returned. The Mail.dat Job ID and User License Code elements
    represent Mail.dat info and the Customer Group ID and MailingGroupID
    represent the Mail.XML info.

```{=html}
<!-- -->
```
g.  The customer will receive one or more ClockStarted blocks. The block
    includes StartTheClockBMEUBlock, StartTheClockPlantLoadBlock, and
    StartTheClockDropShipBlock.

h.  The USPS as part of the QueryResults to communicate any issues can
    return an optional ReturnCode and Description.

-   The QueryError Block provides zero or more return codes and
    descriptions to communicate any issues with the response of the
    query.

#### Container Visibility: {#container-visibility-1 .unnumbered}

1.  FullServiceContainerVisibilityQueryRequest

With each FullServiceContainerVisibilityQueryRequest message, the
customer needs to provide information for all required blocks.

-   SubmittingParty -- The *PostalOne!* system for all data distribution
    for Full-service messages, i.e., non-FAST, non-eDoc messages, will
    only accept a MID or a CRID as a valid id.

-   SubmittingSoftware -- The *PostalOne!* system for messages that it
    receives for the Mail.XML will always require

a.  A valid software name in the SoftwareName element

```{=html}
<!-- -->
```
i.  A valid software vendor company name in the vendor element

j.  The most current version number of the software in the Version
    element

k.  A valid Approval Date and a valid Approval Key in the ApprovalDate
    and ApprovalKey elements. The approval date is the date when the
    USPS approved the software usage in the USPS production environment
    and a valid Approval Key is what the USPS provided to the Software
    Vendor or Mailer (who may have developed their own software) as
    authorization to use in all messages.

-   The job information can also be provided optionally, either the
    Mail.dat Job ID and User License Code, OR the Customer Group ID and
    MailingGroupID for Mail.XML by the customer.

-   The FAST appointment ID or the CSA Dispatch ID, created by the FAST
    system, can be provided optionally in the ConsigneeApptID or
    CSADispatchNumber elements respectively.

-   The customer can also optionally provide the 21 digit Pallet IMB
    barcodes in the UniqueContainerBarcode element tied to the Mail.XML
    job info or Mail.dat Job info and can optionally provide the Locale
    Key of the Induction facility in the USPSInductionFacilityLocaleKey
    element.

-   The customer can also optionally provide the Mail.XML Container ID
    in the CustomerContainerID element tied to the Mail.XML job info or
    can optionally provide the Mail.dat ContainerID in the ContainerID
    element.

15. FullServiceContainerVisibilityQueryResponse

With each FullServiceContainerVisibilityQueryResponse message, the
*PostalOne!* system will provide the

-   Mandatory LargeTransactionDividerGroupType. This type is created to
    allow breaking up of any large data into multiple transactions,
    where the sender of the large data is providing information about
    how many total transactions and records to expect and what is the
    current transaction number among the total expected transactions
    etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
l.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

m.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

n.  TransmittedRecordCount -- is count of records in the current message
    transaction.

o.  TotalRecordsAcrossMessages -- This is the total expected record
    count when the receiver of the MessageGroupID has received all
    messages.

p.  LastMessage -- is an optional Yes or No indicator confirming for the
    receiver that this transaction is the last transaction of the
    MessageGroupID e.g., MessageGroupID 10.

-   The FullServiceContainerVisibilityQueryResponse has two major choice
    blocks one is QueryResults and the other is QueryErrors.

In QueryResults,

a.  The job info will be returned by the USPS *PostalOne!* system and
    either the Mail.dat Job info will be returned or Mail.XML job info
    will be returned. The Mail.dat Job ID and User License Code elements
    represent Mail.dat info and the Customer Group ID and MailingGroupID
    represent the Mail.XML.

```{=html}
<!-- -->
```
q.  The customer will receive zero or more ContainerVisibilityEntry
    blocks with container unload and scan information.

r.  The customer may also optionally receive Return Codes and
    Descriptions as part of the Query Results.

The QueryError Block provides zero or more return codes and descriptions
to communicate any issues with the response of the query.

#### ACS:  {#acs-1 .unnumbered}

1.  FullServiceAddressCorrectionQueryRequest

With each FullServiceAddressCorrectionQueryRequest message, the customer
needs to provide information for all required blocks.

-   SubmittingParty -- The *PostalOne!* system for all data distribution
    for Full-service messages, i.e., non-FAST, non-eDoc messages, will
    only accept a MID or a CRID as a valid id.

-   SubmittingSoftware -- The *PostalOne!* system for messages that it
    receives for the Mail.XML will always require

a.  A valid software name in the SoftwareName element

```{=html}
<!-- -->
```
s.  A valid software vendor company name in the vendor element

t.  The most current version number of the software in the Version
    element

u.  A valid Approval Date and a valid Approval Key in the ApprovalDate
    and ApprovalKey elements. The approval date is the date when the
    USPS approved the software usage in the USPS production environment
    and a valid Approval Key is what the USPS provided to the Software
    Vendor or Mailer (who may have developed their own software) as
    authorization to use in all messages.

-   The OwningParty information can also be provided optionally, if the
    data is requested by third parties based upon existing profiles or
    cast Of characters messages.

-   The customer shall also provide piece information such as optional
    piece ranges and job info, as well as date ranges by providing one
    or more PieceRequest blocks.

16. FullServiceAddressCorrectionQueryResponse

With each FullServiceAddressCorrectionQueryResponse message, the
*PostalOne!* system will provide the

-   Mandatory LargeTransactionDividerGroup. This type is created to
    allow breaking up of any large data into multiple transactions,
    where the sender of the large data is providing information about
    how many total transactions and records to expect and what is the
    current transaction number among the total expected transactions
    etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
v.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

w.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

x.  TransmittedRecordCount -- is count of records in the current message
    transaction.

y.  TotalRecordsAccrossMessages -- This is the total expected record
    count when all transactions have been received by the receiver for
    the MessageGroupID.

z.  LastMessage -- is an optional Yes or No indicator confirming for the
    receiver that this transaction is the last transaction of the
    MessageGroupID e.g., MessageGroupID 10.

-   The FullServiceContainerVisibilityQueryResponse has two major choice
    blocks one is QueryResults and the other is QueryErrors.

In QueryResults,

a.  The customer will receive zero or more FullServiceAddressCorrection
    blocks with job info and address correction information.

```{=html}
<!-- -->
```
a.  The customer may also optionally receive Return Codes and
    Descriptions as part of the Query Results.

The QueryError Block provides zero or more return codes and descriptions
to communicate any issues with the response of the query.

#### Nixie:  {#nixie-1 .unnumbered}

1.  FullServiceNixieDetailQueryRequest

With each FullServiceNixieDetailQueryRequest message, the customer needs
to provide information for all required blocks.

-   SubmittingParty -- The *PostalOne!* system for all data distribution
    for Full-service messages, i.e., non-FAST, non-eDoc messages, will
    only accept a MID or a CRID as a valid ID.

-   SubmittingSoftware -- The *PostalOne!* system for messages that it
    receives for the Mail.XML will always require

a.  A valid software name in the SoftwareName element

```{=html}
<!-- -->
```
b.  A valid software vendor company name in the vendor element

c.  The most current version number of the software in the Version
    element

d.  A valid Approval Date and a valid Approval Key in the ApprovalDate
    and ApprovalKey elements. The approval date is the date when the
    USPS approved the software usage in the USPS production environment
    and a valid Approval Key is what the USPS provided to the Software
    Vendor or Mailer (who may have developed their own software) as
    authorization to use in all messages.

-   The RequestorCRID can be used to identify the requestor through the
    company CRID.

-   The customer can also provide the 6-digit or 9-digit
    OriginalMailerID.

-   The customer shall also provide one or more PieceRequests with piece
    ranges, class, date range and job info.

17. FullServiceNixieDetailResponse

With each FullServiceNixieDetailResponse message, the *PostalOne!*
system will provide the

-   Mandatory LargeTransactionDividerGroupType. This type is created to
    allow breaking up of any large data into multiple transactions,
    where the sender of the large data is providing information about
    how many total transactions and records to expect and what is the
    current transaction number among the total expected transactions
    etc. as part of this one business transaction.

a.  MessageGroupID -- It's a Sequence Number and will remain to be the
    same until all the transactions are completed, e.g., MessageGroupID
    is 10 and until the last transaction is received on this business
    transaction, the MessageGroupID will remain 10 for all transactions,
    so the receiver knows that all the transactions with MessageGroupID
    10 are one business transaction.

```{=html}
<!-- -->
```
e.  TotalMessageCount - This element tells the receiver that for
    MessageGroupID of 10 expect a total of X transactions, the X is a
    positive integer.

f.  MessageSerialNumber -- Is a serial number that will always start
    with 1 for every MessageGroupID, so the receiver always know if this
    is the 1^st^, 2^nd^, 3^rd^ transaction from the TotalMessageCount
    and for the same MessageGroupID.

g.  TransmittedRecordCount -- is count of records in the current message
    transaction.

h.  TotalRecordsAccrossMessages -- This is the total expected record
    count when the receiver of the MessageGroupID has received all
    messages LastMessage -- is an optional Yes or No indicator
    confirming for the receiver that this transaction is the last
    transaction of the MessageGroupID e.g., MessageGroupID 10.

-   The FullServiceNixieDetailResponse has two major choice blocks one
    is QueryResults and the other is QueryErrors.

In QueryResults,

a.  The customer will receive zero or more FullSercviceNixieDetail
    blocks with job info, original MID info and Nixie address
    information.

```{=html}
<!-- -->
```
i.  The customer may also optionally receive Return Codes and
    Descriptions as part of the Query Results.

The QueryError Block provides zero or more return codes and descriptions
to communicate any issues with the response of the query.

### Cast Of Characters Messages for Release 1 of Full-service implementation: {#cast-of-characters-messages-for-release-1-of-full-service-implementation-1 .unnumbered}

#### CastOfCharacters:  {#castofcharacters .unnumbered}

The Cast Of Characters messages are used to distribute data to a third
party by a Mail Preparer or Mail Owner. All of the Full-service data for
StartTheClock, Container Scans, ACS, Nixie, and Confirm can be diverted
to another party, if that third party is pre-identified in the
*PostalOne!* 'Dynamic' profile.

1.  CastOfCharactersCreateRequest

With each CastOfCharactersCreateRequest message, the customer needs to
provide information for all required blocks.

-   The customer must provide an internal tracking ID in the header
    attribute of OriginalSenderMsgID.

-   SubmittingParty -- The *PostalOne!* system for all data distribution
    for Full-service messages, i.e., non-FAST, non-eDoc messages, will
    only accept a MID or a CRID as a valid id.

-   SubmittingSoftware -- The *PostalOne!* system for messages that it
    receives for the Mail.XML will always require

a.  A valid software name in the SoftwareName element

```{=html}
<!-- -->
```
j.  A valid software vendor company name in the vendor element

k.  The most current version number of the software in the Version
    element

l.  A valid Approval Date and a valid Approval Key in the ApprovalDate
    and ApprovalKey elements. The approval date is the date when the
    USPS approved the software usage in the USPS production environment
    and a valid Approval Key is what the USPS provided to the Software
    Vendor or Mailer (who may have developed their own software) as
    authorization to use in all messages.

-   The customer must provide one or more MailPieceGroup blocks or the
    ContainerGroup blocks depending on the type of data that needs to be
    distributed.

-   The customer may provide one or more MailPieceGroup blocks and
    provide either the IMB info, or planet code or LineOfTravel info or
    may provide the IMB lowest or highest ID block information.

-   The customer may provide one or more ContainerBlocks with either a
    Mail.dat container block or a Mail.XML container block or an IMB
    container barcode.

-   The customer must identify the business entity who is to receive the
    data in the Participant block by only using CRID or MID of the
    participant.

-   The customer must identify the role in the Role element type to
    define what type of data needs should be sent to the participant.
    Valid data types are Nixie, ACS subscriber, ACS Data Receiver,
    Confirm Subscriber, Confirm Data Receiver, Tracker CONFIRM-scan,
    Tracker CONFIRM-payer, ACS Receiver, ACS Payer, StartTheClock,
    ContainerVisibility.

-   The customer must identify the date on which the Cast Of Characters
    direction to distribute data to third party becomes active and
    valid.

-   The customer may provide an optional EffectiveEndDate or duration or
    DurationUnitOfMeasure.

18. CastOfCharactersCreateResponse

With each CastOfCharactersCreateResponse message, the *PostalOne!*
system will provide the Mandatory OriginalSenderMsgID and the
ReceiverMessageID.

19. CastOfCharactersCreateAccept or CastOfCharactersReject blocks.

-   In CastOfCharactersCreateAccept block, the customer will receive
    confirmation group IDs for either the MailPieceGroup or for the
    ContainerGroup Blocks, or an Optional Return info block with a
    return code and description. The return codes and descriptions will
    be provided by the USPS, based on the schedule made available in the
    External Timeline for IM implementation document.

-   In CastOfCharactersCreateReject block,

a.  The customer will receive the return Codes and descriptions which
    will be provided by the USPS in the Timeline for IM implementation
    document.

```{=html}
<!-- -->
```
m.  With the return Code and descriptions the USPS may provide the
    details back to the customer on the piece or Container data provided
    to USPS which was rejected.

-   CastOfCharactersCancelRequest

The CastOfCharactersCancelRequest is identical to the Create request
message and can be used to cancel one or more records that the customer
previously sent to the USPS.

-   CastOfCharactersCancelResponse

The CastOfCharactersCancelResponse is identical to the Create response
with Accept and reject response blocks.

-   CastOfCharactersUpdateRequest

The CastOfCharactersUpdateRequest is identical to the Create request
message and can be used to update one or more records that the customer
previously sent to the USPS.

-   CastOfCharactersUpdateResponse

The CastOfCharactersUpdateResponse is identical to the Create response
with Accept and reject response blocks.

## Pull Request/Response-Handling Large Transactions

The following messages can get large transactions as part of response.

-   FullServiceAddressCorrectionQueryResponse

-   FullServiceContainerVisibilityQueryResponse

-   FullServiceNixieDetailQueryResponse

-   Start the Clock Query Response

MailXML spec has defined an element 'LargeTransactionDividerResult' to
support verification, tracking, and pulling of all data that is divided
into multiple transactions. *PostalOne!* will divide the large data
result-set into smaller chunks. In the response messages, *PostalOne!*
 would include TRACKINGID(s) as part of
'LargeTransactionDividerResult'.  Whenever Mailer application sees this
element, they need to send  MessageResponseRetrievalRequest (MRRR) and
use the TrackingID(s) provided to get further responses for the same
data transaction to completely receive all data for that data
transaction.

For example, Mailer sends 'FullServiceNixieDetailQueryRequest' and
*PostalOne!* observes it has to send Large data result set as
response(1000 messages broken down into 200 messages per transaction,
making it a total of 5 transactions) *PostalOne!* will return  response
of first 200 messages and include 5 TrackingID(s) as part of the
'LargeTransactionDividerResult'.

Mailer can send TrackingID requests using the MRRR  message and get the
remaining data for all tracking ids. The other element
'LargeTransactionDividerGroupType' provides more information on what is
included in each data transmission.

# APPENDIX A - WSDLs and XSDs

## WSDL for Release 1

This WSDL will also be available as a downloadable attachment from
RIBBS.

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

[\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>]{.mark}

[\<!\-- Date Comments \--\>]{.mark}

[\<!\-- 11/17/2007 MailXML -POAppointmentServices WSDL Initial version
1.0 \--\>]{.mark}

[]{.mark}

[\<wsdl:definitions xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
xmlns:tns=\"http://www.usps.com/postalone/services/POAppointmentServices20\"
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:soap=\"http://schemas.xmlsoap.org/wsdl/soap/\"
xmlns=\"http://www.usps.com/postalone/services/POAppointmentServices20\"
xmlns:pdd=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
name=\"POAppointmentServices20\"
targetNamespace=\"http://www.usps.com/postalone/services/POAppointmentServices20\"\>]{.mark}

[\<wsdl:documentation
xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"\>Version
1.0.0\</wsdl:documentation\>]{.mark}

[\<wsdl:types\>]{.mark}

[\<xsd:schema
targetNamespace=\"http://www.usps.com/postalone/services/POAppointmentServices20\"
xmlns=\"http://www.usps.com/postalone/services/POAppointmentServices20\"
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:soap=\"http://schemas.xmlsoap.org/wsdl/soap/\"
xmlns:tns=\"http://www.usps.com/postalone/services/POAppointmentServices20\"
xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
schemaLocation=\"UserAuthenticationInfo.xsd\"/\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
schemaLocation=\"PushUserProfileInfo.xsd\"/\>]{.mark}

[\<!\-- Appointment Messages \--\>]{.mark}

[\<xsd:element name=\"apptQuery\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptRequest\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptUpdate\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptCancel\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptCloseout\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptResponseRetrieval\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"recurringApptQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"messageResponseRetrieval\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptCancelCreate\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptStatus\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"result\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fault\" type=\"xsd:string\"/\>]{.mark}

[\<!\-- Appointment Shell Messages \--\>]{.mark}

[\<xsd:element name=\"apptShellUpdate\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptShellCancel\" type=\"xsd:string\"/\>]{.mark}

[\<!\-- Content Messages \--\>]{.mark}

[\<xsd:element name=\"apptContentCreate\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptContentUpdate\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptContentCancel\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"contentQuery\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"apptShell\" type=\"xsd:string\"/\>]{.mark}

[\<!\-- eDoc Messages\--\>]{.mark}

[\<xsd:element name=\"mailingGroupQuery\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"paymentMessageQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"reconciliationReportQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"containerStatusQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"partnerApptQuery\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"customerSupplierAgreementQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<!\-- Data Distribution Service Measurement(Pull
Messages)\--\>]{.mark}

[\<xsd:element name=\"fullServiceAddressCorrectionQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fullServiceContainerVisibilityQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fullServiceNixieDetailQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"startTheClockQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"byForConflictQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"castofCharactersCreate\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"castofCharactersUpdate\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"castofCharactersCancel\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"deliveryPointValidationQuery\"
type=\"xsd:string\"/\>]{.mark}

[\<!\--Push Subscriptions Messages(Data Distribution) \--\>]{.mark}

[\<xsd:element name=\"pushSubscriptionCreate\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"pushSubscriptionUpdate\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"pushSubscriptionCancel\"
type=\"xsd:string\"/\>]{.mark}

[\</xsd:schema\>]{.mark}

[\<xsd:schema xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
schemaLocation=\"PushUserProfileInfo.xsd\"/\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
schemaLocation=\"PushUserProfileInfo.xsd\"/\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
schemaLocation=\"PushUserProfileInfo.xsd\"/\>]{.mark}

[\</xsd:schema\>]{.mark}

[\</wsdl:types\>]{.mark}

[\<wsdl:message name=\"DeliveryApptQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptQuery\" element=\"tns:apptQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptRequest\" element=\"tns:apptRequest\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"AllDeliveryApptCloseoutRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptCloseout\"
element=\"tns:apptCloseout\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptStatusRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptStatus\" element=\"tns:apptStatus\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"RecurringApptQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"recurringApptQuery\"
element=\"tns:recurringApptQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptContentUpdateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptContentUpdate\"
element=\"tns:apptContentUpdate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"ApptResponseRetrieval\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptResponseRetrieval\"
element=\"tns:apptResponseRetrieval\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryContentQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"contentQuery\"
element=\"tns:contentQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptContentCancelRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptContentCancel\"
element=\"tns:apptContentCancel\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptContentCreateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptContentCreate\"
element=\"tns:apptContentCreate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptUpdateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptUpdate\" element=\"tns:apptUpdate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptCancelCreateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptCancelCreate\"
element=\"tns:apptCancelCreate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptCancelRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptCancel\" element=\"tns:apptCancel\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptShellRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptShell\" element=\"tns:apptShell\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"POAppointmentServicesFault\"\>]{.mark}

[\<wsdl:part name=\"fault\" element=\"tns:fault\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptShellUpdateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptShellUpdate\"
element=\"tns:apptShellUpdate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"AppointmentServiceResponse\"\>]{.mark}

[\<wsdl:part name=\"result\" element=\"tns:result\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryApptShellCancelRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"apptShellCancel\"
element=\"tns:apptShellCancel\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"MessageResponseRetrievalRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"messageResponseRetrieval\"
element=\"tns:messageResponseRetrieval\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"MailingGroupQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"mailingGroupQuery\"
element=\"tns:mailingGroupQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"PaymentMessageQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"paymentMessageQuery\"
element=\"tns:paymentMessageQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"ReconciliationReportQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"reconciliationReportQuery\"
element=\"tns:reconciliationReportQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"ContainerStatusQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"containerStatusQuery\"
element=\"tns:containerStatusQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"PartnerApptQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"partnerApptQuery\"
element=\"tns:partnerApptQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"CustomerSupplierAgreementQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"customerSupplierAgreementQuery\"
element=\"tns:customerSupplierAgreementQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message
name=\"FullServiceAddressCorrectionQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"fullServiceAddressCorrectionQuery\"
element=\"tns:fullServiceAddressCorrectionQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message
name=\"FullServiceContainerVisibilityQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"fullServiceContainerVisibilityQuery\"
element=\"tns:fullServiceContainerVisibilityQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"FullServiceNixieDetailQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"fullServiceNixieDetailQuery\"
element=\"tns:fullServiceNixieDetailQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"StartTheClockQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"startTheClockQuery\"
element=\"tns:startTheClockQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"ByForConflictQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"byForConflictQuery\"
element=\"tns:byForConflictQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"CastofCharactersCreateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"castofCharactersCreate\"
element=\"tns:castofCharactersCreate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"CastofCharactersUpdateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"castofCharactersUpdate\"
element=\"tns:castofCharactersUpdate\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"CastofCharactersCancelRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"castofCharactersCancel\"
element=\"tns:castofCharactersCancel\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryPointValidationQueryRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"deliveryPointValidationQuery\"
element=\"tns:deliveryPointValidationQuery\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"PushSubscriptionCreateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"pushSubscriptionCreate\"
element=\"pdd:PushProfile\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"PushSubscriptionUpdateRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"pushSubscriptionUpdate\"
element=\"pdd:PushProfile\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"PushSubscriptionCancelRequest\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"pushSubscriptionCancel\"
element=\"pdd:PushCancel\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:portType name=\"POAppointmentServicesPortType\"\>]{.mark}

[\<wsdl:operation name=\"QueryDeliveryAppt\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptQueryRequest\"
message=\"tns:DeliveryApptQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RequestDeliveryAppt\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptRequest\"
message=\"tns:DeliveryApptRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"UpdateDeliveryAppt\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptUpdateRequest\"
message=\"tns:DeliveryApptUpdateRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptUpdateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptUpdateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CancelDeliveryAppt\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptCancelRequest\"
message=\"tns:DeliveryApptCancelRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptCancelResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptCancelFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"GetDeliveryApptStatus\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptStatusRequest\"
message=\"tns:DeliveryApptStatusRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptStatusResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptStatusFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"GetAllDeliveryApptCloseouts\"\>]{.mark}

[\<wsdl:input name=\"AllDeliveryApptCloseoutRequest\"
message=\"tns:AllDeliveryApptCloseoutRequest\"/\>]{.mark}

[\<wsdl:output name=\"AllDeliveryApptCloseoutResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"AllDeliveryApptCloseoutFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RetrieveAppointmentResponses\"\>]{.mark}

[\<wsdl:input name=\"ApptResponseRetrievalRequest\"
message=\"tns:ApptResponseRetrieval\"/\>]{.mark}

[\<wsdl:output name=\"ApptResponseRetrievalResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"ApptResponseRetrievalFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentCreate\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentCreateRequest\"
message=\"tns:DeliveryApptContentCreateRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentCreateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentCreateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentUpdate\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentUpdateRequest\"
message=\"tns:DeliveryApptContentUpdateRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentUpdateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentUpdateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentCancel\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentCancelRequest\"
message=\"tns:DeliveryApptContentCancelRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentCancelResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentCancelFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryContentQuery\"\>]{.mark}

[\<wsdl:input name=\"DeliveryContentQueryRequest\"
message=\"tns:DeliveryContentQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryContentQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryContentQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShell\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellRequest\"
message=\"tns:DeliveryApptShellRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShellUpdate\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellUpdateRequest\"
message=\"tns:DeliveryApptShellUpdateRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellUpdateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellUpdateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShellCancel\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellCancelRequest\"
message=\"tns:DeliveryApptShellCancelRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellCancelResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellCancelFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptCancelCreate\"\>]{.mark}

[\<wsdl:input name=\"DeliveryApptCancelCreateRequest\"
message=\"tns:DeliveryApptCancelCreateRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryApptCancelCreateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptCancelCreateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RecurringApptQuery\"\>]{.mark}

[\<wsdl:input name=\"RecurringApptQueryRequest\"
message=\"tns:RecurringApptQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"RecurringApptQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"RecurringApptQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"MessageResponseRetrieval\"\>]{.mark}

[\<wsdl:input name=\"MessageResponseRetrievalRequest\"
message=\"tns:MessageResponseRetrievalRequest\"/\>]{.mark}

[\<wsdl:output name=\"MessageResponseRetrievalResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"MessageResponseRetrievalFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"MailingGroupQuery\"\>]{.mark}

[\<wsdl:input name=\"MailingGroupQueryRequest\"
message=\"tns:MailingGroupQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"MailingGroupQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"MailingGroupQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PaymentMessageQuery\"\>]{.mark}

[\<wsdl:input name=\"PaymentMessageQueryRequest\"
message=\"tns:PaymentMessageQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"PaymentMessageQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"PaymentMessageQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ReconciliationReportQuery\"\>]{.mark}

[\<wsdl:input name=\"ReconciliationReportQueryRequest\"
message=\"tns:ReconciliationReportQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"ReconciliationReportQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"ReconciliationReportQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ContainerStatusQuery\"\>]{.mark}

[\<wsdl:input name=\"ContainerStatusQueryRequest\"
message=\"tns:ContainerStatusQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"ContainerStatusQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"ContainerStatusQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PartnerApptQuery\"\>]{.mark}

[\<wsdl:input name=\"PartnerApptQueryRequest\"
message=\"tns:PartnerApptQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"PartnerApptQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"PartnerApptQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CustomerSupplierAgreementQuery\"\>]{.mark}

[\<wsdl:input name=\"CustomerSupplierAgreementQueryRequest\"
message=\"tns:CustomerSupplierAgreementQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"CustomerSupplierAgreementQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"CustomerSupplierAgreementQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceAddressCorrectionQuery\"\>]{.mark}

[\<wsdl:input name=\"FullServiceAddressCorrectionQueryRequest\"
message=\"tns:FullServiceAddressCorrectionQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"FullServiceAddressCorrectionQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"FullServiceAddressCorrectionQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceContainerVisibilityQuery\"\>]{.mark}

[\<wsdl:input name=\"FullServiceContainerVisibilityQueryRequest\"
message=\"tns:FullServiceContainerVisibilityQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"FullServiceContainerVisibilityQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"FullServiceContainerVisibilityQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceNixieDetailQuery\"\>]{.mark}

[\<wsdl:input name=\"FullServiceNixieDetailQueryRequest\"
message=\"tns:FullServiceNixieDetailQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"FullServiceNixieDetailQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"FullServiceNixieDetailQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"StartTheClockQuery\"\>]{.mark}

[\<wsdl:input name=\"StartTheClockQueryRequest\"
message=\"tns:StartTheClockQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"StartTheClockQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"StartTheClockQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ByForConflictQuery\"\>]{.mark}

[\<wsdl:input name=\"ByForConflictQueryRequest\"
message=\"tns:ByForConflictQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"ByForConflictQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"ByForConflictQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersCreate\"\>]{.mark}

[\<wsdl:input name=\"CastofCharactersCreateRequest\"
message=\"tns:CastofCharactersCreateRequest\"/\>]{.mark}

[\<wsdl:output name=\"CastofCharactersCreateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersCreateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersUpdate\"\>]{.mark}

[\<wsdl:input name=\"CastofCharactersUpdateRequest\"
message=\"tns:CastofCharactersUpdateRequest\"/\>]{.mark}

[\<wsdl:output name=\"CastofCharactersUpdateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersUpdateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersCancel\"\>]{.mark}

[\<wsdl:input name=\"CastofCharactersCancelRequest\"
message=\"tns:CastofCharactersCancelRequest\"/\>]{.mark}

[\<wsdl:output name=\"CastofCharactersCancelResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersCancelFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryPointValidationQuery\"\>]{.mark}

[\<wsdl:input name=\"DeliveryPointValidationQueryRequest\"
message=\"tns:DeliveryPointValidationQueryRequest\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryPointValidationQueryResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"DeliveryPointValidationQueryFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionCreate\"\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionCreateRequest\"
message=\"tns:PushSubscriptionCreateRequest\"/\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionCreateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionCreateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionUpdate\"\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionUpdateRequest\"
message=\"tns:PushSubscriptionUpdateRequest\"/\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionUpdateResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionUpdateFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionCancel\"\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionCancelRequest\"
message=\"tns:PushSubscriptionCancelRequest\"/\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionCancelResponse\"
message=\"tns:AppointmentServiceResponse\"/\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionCancelFault\"
message=\"tns:POAppointmentServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\</wsdl:portType\>]{.mark}

[\<wsdl:binding name=\"POAppointmentServicesSoapBinding\"
type=\"tns:POAppointmentServicesPortType\"\>]{.mark}

[\<soap:binding style=\"document\"
transport=\"http://schemas.xmlsoap.org/soap/http\"/\>]{.mark}

[\<wsdl:operation name=\"QueryDeliveryAppt\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/queryDeliveryAppt\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptQueryFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptQueryFault\" use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RequestDeliveryAppt\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/requestDeliveryAppt\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptFault\" use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"UpdateDeliveryAppt\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/updateDeliveryAppt\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptUpdateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptUpdateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptUpdateFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptUpdateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CancelDeliveryAppt\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/cancelDeliveryAppt\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptCancelRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptCancelResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptCancelFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptCancelFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"GetDeliveryApptStatus\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/getDeliveryApptStatus\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptStatusRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptStatusResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptStatusFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptStatusFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"GetAllDeliveryApptCloseouts\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/getAllDeliveryApptCloseouts\"/\>]{.mark}

[\<wsdl:input name=\"AllDeliveryApptCloseoutRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"AllDeliveryApptCloseoutResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"AllDeliveryApptCloseoutFault\"\>]{.mark}

[\<soap:fault name=\"AllDeliveryApptCloseoutFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RetrieveAppointmentResponses\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/retrieveAppointmentResponses\"/\>]{.mark}

[\<wsdl:input name=\"ApptResponseRetrievalRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"ApptResponseRetrievalResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"ApptResponseRetrievalFault\"\>]{.mark}

[\<soap:fault name=\"ApptResponseRetrievalFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentCreate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptContentCreate\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentCreateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentCreateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentCreateFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptContentCreateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentUpdate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptContentUpdate\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentUpdateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentUpdateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentUpdateFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptContentUpdateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptContentCancel\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptContentCancel\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptContentCancelRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptContentCancelResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptContentCancelFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptContentCancelFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryContentQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryContentQuery\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryContentQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryContentQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryContentQueryFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryContentQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShell\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptShell\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptShellFault\" use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShellUpdate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptShellUpdate\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellUpdateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellUpdateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellUpdateFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptShellUpdateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptShellCancel\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptShellCancel\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptShellCancelRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptShellCancelResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptShellCancelFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptShellCancelFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryApptCancelCreate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/DeliveryApptCancelCreate\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryApptCancelCreateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryApptCancelCreateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryApptCancelCreateFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryApptCancelCreateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"RecurringApptQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/RecurringApptQuery\"/\>]{.mark}

[\<wsdl:input name=\"RecurringApptQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"RecurringApptQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"RecurringApptQueryFault\"\>]{.mark}

[\<soap:fault name=\"RecurringApptQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"MessageResponseRetrieval\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/MessageResponseRetrieval\"/\>]{.mark}

[\<wsdl:input name=\"MessageResponseRetrievalRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"MessageResponseRetrievalResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"MessageResponseRetrievalFault\"\>]{.mark}

[\<soap:fault name=\"MessageResponseRetrievalFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"MailingGroupQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/MailingGroupQuery\"/\>]{.mark}

[\<wsdl:input name=\"MailingGroupQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"MailingGroupQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"MailingGroupQueryFault\"\>]{.mark}

[\<soap:fault name=\"MailingGroupQueryFault\" use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PaymentMessageQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/PaymentMessageQuery\"/\>]{.mark}

[\<wsdl:input name=\"PaymentMessageQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"PaymentMessageQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PaymentMessageQueryFault\"\>]{.mark}

[\<soap:fault name=\"PaymentMessageQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ReconciliationReportQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/ReconciliationReportQuery\"/\>]{.mark}

[\<wsdl:input name=\"ReconciliationReportQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"ReconciliationReportQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"ReconciliationReportQueryFault\"\>]{.mark}

[\<soap:fault name=\"ReconciliationReportQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ContainerStatusQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/ContainerStatusQuery\"/\>]{.mark}

[\<wsdl:input name=\"ContainerStatusQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"ContainerStatusQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"ContainerStatusQueryFault\"\>]{.mark}

[\<soap:fault name=\"ContainerStatusQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PartnerApptQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/PartnerApptQuery\"/\>]{.mark}

[\<wsdl:input name=\"PartnerApptQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"PartnerApptQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PartnerApptQueryFault\"\>]{.mark}

[\<soap:fault name=\"PartnerApptQueryFault\" use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CustomerSupplierAgreementQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/AppointmentService/CustomerSupplierAgreementQuery\"/\>]{.mark}

[\<wsdl:input name=\"CustomerSupplierAgreementQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"CustomerSupplierAgreementQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"CustomerSupplierAgreementQueryFault\"\>]{.mark}

[\<soap:fault name=\"CustomerSupplierAgreementQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceAddressCorrectionQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/FullServiceAddressCorrectionQuery\"/\>]{.mark}

[\<wsdl:input
name=\"FullServiceAddressCorrectionQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output
name=\"FullServiceAddressCorrectionQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"FullServiceAddressCorrectionQueryFault\"\>]{.mark}

[\<soap:fault name=\"FullServiceAddressCorrectionQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceContainerVisibilityQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/FullServiceContainerVisibilityQuery\"/\>]{.mark}

[\<wsdl:input
name=\"FullServiceContainerVisibilityQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output
name=\"FullServiceContainerVisibilityQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault
name=\"FullServiceContainerVisibilityQueryFault\"\>]{.mark}

[\<soap:fault name=\"FullServiceContainerVisibilityQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"FullServiceNixieDetailQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/FullServiceNixieDetailQuery\"/\>]{.mark}

[\<wsdl:input name=\"FullServiceNixieDetailQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"FullServiceNixieDetailQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"FullServiceNixieDetailQueryFault\"\>]{.mark}

[\<soap:fault name=\"FullServiceNixieDetailQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"StartTheClockQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/StartTheClockQuery\"/\>]{.mark}

[\<wsdl:input name=\"StartTheClockQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"StartTheClockQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"StartTheClockQueryFault\"\>]{.mark}

[\<soap:fault name=\"StartTheClockQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"ByForConflictQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/ByForConflictQuery\"/\>]{.mark}

[\<wsdl:input name=\"ByForConflictQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"ByForConflictQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"ByForConflictQueryFault\"\>]{.mark}

[\<soap:fault name=\"ByForConflictQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersCreate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/CastofCharactersCreate\"/\>]{.mark}

[\<wsdl:input name=\"CastofCharactersCreateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"CastofCharactersCreateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersCreateFault\"\>]{.mark}

[\<soap:fault name=\"CastofCharactersCreateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersUpdate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/CastofCharactersUpdate\"/\>]{.mark}

[\<wsdl:input name=\"CastofCharactersUpdateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"CastofCharactersUpdateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersUpdateFault\"\>]{.mark}

[\<soap:fault name=\"CastofCharactersUpdateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"CastofCharactersCancel\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/CastofCharactersCancel\"/\>]{.mark}

[\<wsdl:input name=\"CastofCharactersCancelRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"CastofCharactersCancelResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"CastofCharactersCancelFault\"\>]{.mark}

[\<soap:fault name=\"CastofCharactersCancelFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"DeliveryPointValidationQuery\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/DeliveryPointValidationQuery\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryPointValidationQueryRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"DeliveryPointValidationQueryResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"DeliveryPointValidationQueryFault\"\>]{.mark}

[\<soap:fault name=\"DeliveryPointValidationQueryFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionCreate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/PushSubscriptionCreate\"/\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionCreateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionCreateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionCreateFault\"\>]{.mark}

[\<soap:fault name=\"PushSubscriptionCreateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionUpdate\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/PushSubscriptionUpdate\"/\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionUpdateRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionUpdateResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionUpdateFault\"\>]{.mark}

[\<soap:fault name=\"PushSubscriptionUpdateFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushSubscriptionCancel\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/ops/services/PushSubscriptionCancel\"/\>]{.mark}

[\<wsdl:input name=\"PushSubscriptionCancelRequest\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"PushSubscriptionCancelResponse\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushSubscriptionCancelFault\"\>]{.mark}

[\<soap:fault name=\"PushSubscriptionCancelFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\</wsdl:binding\>]{.mark}

[\<wsdl:service name=\"POAppointmentServices\"\>]{.mark}

[\<wsdl:port name=\"POAppointmentServices\"
binding=\"tns:POAppointmentServicesSoapBinding\"\>]{.mark}

[\<soap:address
location=\"https://fast.uspspostalone.com/PFSTIApptWeb/services/POAppointmentServices\"/\>]{.mark}

[\</wsdl:port\>]{.mark}

[\</wsdl:service\>]{.mark}

[\</wsdl:definitions\>]{.mark}

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

## PUSH User Profile XSD

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

[\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>]{.mark}

[\<xsd:schema xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
xmlns:pdd=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
targetNamespace=\"http://www.usps.com/postalone/services/PushUserProfileSchema\"
version=\"1.0.0\"\>]{.mark}

[]{.mark}

[\<xsd:annotation\>]{.mark}

[\<xsd:documentation xml:lang=\"en\"\>PostalOne! User Push
Profile]{.mark}

[\</xsd:documentation\>]{.mark}

[\</xsd:annotation\>]{.mark}

[]{.mark}

[\<xsd:element name=\"PushProfile\"
type=\"pdd:PushProfileType\"/\>]{.mark}

[\<xsd:element name=\"PushCancel\"
type=\"pdd:PushCancelType\"/\>]{.mark}

[\<xsd:complexType name=\"PushProfileType\"\>]{.mark}

[\<xsd:sequence\>]{.mark}

[\<xsd:element name=\"PushMessage\"
type=\"pdd:PushMessageType\"/\>]{.mark}

[\<xsd:element name=\"PushType\" type=\"pdd:PushType\"/\>]{.mark}

[\<xsd:element name=\"PushFrequency\"\>]{.mark}

[\<xsd:simpleType\>]{.mark}

[\<xsd:restriction base=\"xsd:string\"\>]{.mark}

[\<xsd:enumeration value=\"onceaday\"/\>]{.mark}

[\<xsd:enumeration value=\"twiceperday\"/\>]{.mark}

[\<xsd:enumeration value=\"every6hours\"/\>]{.mark}

[\<xsd:enumeration value=\"hourly\"/\>]{.mark}

[\</xsd:restriction\>]{.mark}

[\</xsd:simpleType\>]{.mark}

[\</xsd:element\>]{.mark}

[\</xsd:sequence\>]{.mark}

[\</xsd:complexType\>]{.mark}

[]{.mark}

[\<xsd:complexType name=\"PushCancelType\"\>]{.mark}

[\<xsd:sequence\>]{.mark}

[\<xsd:element name=\"PushMessage\"
type=\"pdd:PushMessageType\"/\>]{.mark}

[\<xsd:element name=\"PushType\" type=\"pdd:PushType\"/\>]{.mark}

[\</xsd:sequence\>]{.mark}

[\</xsd:complexType\>]{.mark}

[]{.mark}

[\<xsd:simpleType name=\"PushMessageType\"\>]{.mark}

[\<xsd:restriction base=\"xsd:string\"\>]{.mark}

[\<xsd:enumeration value=\"StartTheClock\"/\>]{.mark}

[\<xsd:enumeration value=\"FullServiceAddressCorrection\"/\>]{.mark}

[\<xsd:enumeration value=\"FullServiceContainerVisibility\"/\>]{.mark}

[\<xsd:enumeration value=\"FullServiceNixie\"/\>]{.mark}

[\<xsd:enumeration value=\"DeliveryPointVerification\"/\>]{.mark}

[\</xsd:restriction\>]{.mark}

[\</xsd:simpleType\>]{.mark}

[\<xsd:simpleType name=\"PushType\"\>]{.mark}

[\<xsd:restriction base=\"xsd:string\"\>]{.mark}

[\<xsd:enumeration value=\"Push\"/\>]{.mark}

[\<xsd:enumeration value=\"Notify\"/\>]{.mark}

[\</xsd:restriction\>]{.mark}

[\</xsd:simpleType\>]{.mark}

[\</xsd:schema\>]{.mark}

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

## USER Authentication Info XSD

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

[\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>]{.mark}

[\<xsd:schema
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
targetNamespace=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
version=\"0.0.3\"\>]{.mark}

[\<xsd:annotation\>]{.mark}

[\<xsd:documentation xml:lang=\"en\"\>PostalOne! User Authentication
Request\</xsd:documentation\>]{.mark}

[\</xsd:annotation\>]{.mark}

[\<xsd:element name=\"AuthenticationInfo\"
type=\"auth:AuthenticationInfoType\"/\>]{.mark}

[\<xsd:complexType name=\"AuthenticationInfoType\"\>]{.mark}

[\<xsd:sequence\>]{.mark}

[\<xsd:element name=\"UserId\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"UserPassword\" type=\"xsd:string\"/\>]{.mark}

[\</xsd:sequence\>]{.mark}

[\</xsd:complexType\>]{.mark}

[\</xsd:schema\>]{.mark}

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

## WSDL -- PUSH Model

**The customer must implement the PUSH model to receive data from the
*PostalOne!* system**

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

[\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>]{.mark}

[\<!\-- Date Comments \--\>]{.mark}

[\<!\-- 11/17/2008 POCustomerMailXMLServices WSDL Initial version 1.0
\--\>]{.mark}

[\<wsdl:definitions xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
xmlns:tns=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:soap=\"http://schemas.xmlsoap.org/wsdl/soap/\"
xmlns=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"
name=\"POCustomerMailXMLServices\"
targetNamespace=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"\>]{.mark}

[\<wsdl:documentation
xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"\>Version
1.0.0\</wsdl:documentation\>]{.mark}

[\<wsdl:types\>]{.mark}

[\<xsd:schema
targetNamespace=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"
xmlns=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:soap=\"http://schemas.xmlsoap.org/wsdl/soap/\"
xmlns:tns=\"http://www.usps.com/postalone/services/POCustomerMailXMLServices\"
xmlns:wsdl=\"http://schemas.xmlsoap.org/wsdl/\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"\>]{.mark}

[\<xsd:import
namespace=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
schemaLocation=\"UserAuthenticationInfo.xsd\"/\>]{.mark}

[\<xsd:element name=\"fullServiceAddressCorrectionData\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fullServiceContainerVisibilityData\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fullServiceNixieDetailData\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"DeliveryPointVerificationData\"
type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"StartTheClockData\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"acknowledgement\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"fault\" type=\"xsd:string\"/\>]{.mark}

[\</xsd:schema\>]{.mark}

[\</wsdl:types\>]{.mark}

[\<wsdl:message name=\"AddressCorrectionData\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"addressCorrectionData\"
element=\"tns:fullServiceAddressCorrectionData\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"ContainerVisibilityData\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"containerVisibilityData\"
element=\"tns:fullServiceContainerVisibilityData\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"NixieDetailData\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"nixieDetailData\"
element=\"tns:fullServiceNixieDetailData\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"DeliveryPointVerificationData\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"deliveryPointVerificationData\"
element=\"tns:DeliveryPointVerificationData\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"StartTheClockData\"\>]{.mark}

[\<wsdl:part name=\"authInfo\"
element=\"auth:AuthenticationInfo\"/\>]{.mark}

[\<wsdl:part name=\"startTheClockData\"
element=\"tns:StartTheClockData\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"Acknowledgement\"\>]{.mark}

[\<wsdl:part name=\"acknowledgement\"
element=\"tns:acknowledgement\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:message name=\"POCustomerMailXMLServicesFault\"\>]{.mark}

[\<wsdl:part name=\"fault\" element=\"tns:fault\"/\>]{.mark}

[\</wsdl:message\>]{.mark}

[\<wsdl:portType name=\"POCustomerMailXMLServicesPortType\"\>]{.mark}

[\<wsdl:operation name=\"PushAddressCorrectionData\"\>]{.mark}

[\<wsdl:input name=\"AddressCorrectionData\"
message=\"tns:AddressCorrectionData\"/\>]{.mark}

[\<wsdl:output name=\"AddressCorrectionAcknowledgement\"
message=\"tns:Acknowledgement\"/\>]{.mark}

[\<wsdl:fault name=\"PushAddressCorrectionDataFault\"
message=\"tns:POCustomerMailXMLServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushContainerVisibilityData\"\>]{.mark}

[\<wsdl:input name=\"ContainerVisibilityData\"
message=\"tns:ContainerVisibilityData\"/\>]{.mark}

[\<wsdl:output name=\"ContainerVisibilityAcknowledgement\"
message=\"tns:Acknowledgement\"/\>]{.mark}

[\<wsdl:fault name=\"PushContainerVisibilityDataFault\"
message=\"tns:POCustomerMailXMLServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushNixieDetailData\"\>]{.mark}

[\<wsdl:input name=\"NixieDetailData\"
message=\"tns:NixieDetailData\"/\>]{.mark}

[\<wsdl:output name=\"NixieDetailAcknowledgement\"
message=\"tns:Acknowledgement\"/\>]{.mark}

[\<wsdl:fault name=\"PushNixieDetailDataFault\"
message=\"tns:POCustomerMailXMLServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushDeliveryPointVerificationData\"\>]{.mark}

[\<wsdl:input name=\"DeliveryPointVerificationData\"
message=\"tns:DeliveryPointVerificationData\"/\>]{.mark}

[\<wsdl:output name=\"DeliveryPointVerificationAcknowledgement\"
message=\"tns:Acknowledgement\"/\>]{.mark}

[\<wsdl:fault name=\"PushDeliveryPointVerificationDataFault\"
message=\"tns:POCustomerMailXMLServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushStartTheClockData\"\>]{.mark}

[\<wsdl:input name=\"StartTheClockData\"
message=\"tns:StartTheClockData\"/\>]{.mark}

[\<wsdl:output name=\"StartTheClockAcknowledgement\"
message=\"tns:Acknowledgement\"/\>]{.mark}

[\<wsdl:fault name=\"PushStartTheClockDataFault\"
message=\"tns:POCustomerMailXMLServicesFault\"/\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\</wsdl:portType\>]{.mark}

[\<wsdl:binding name=\"POCustomerMailXMLServicesSoapBinding\"
type=\"tns:POCustomerMailXMLServicesPortType\"\>]{.mark}

[\<soap:binding style=\"document\"
transport=\"http://schemas.xmlsoap.org/soap/http\"/\>]{.mark}

[\<wsdl:operation name=\"PushAddressCorrectionData\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/POCustomerMailXMLServices/pushAddressCorrectionData\"/\>]{.mark}

[\<wsdl:input name=\"AddressCorrectionData\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"AddressCorrectionAcknowledgement\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushAddressCorrectionDataFault\"\>]{.mark}

[\<soap:fault name=\"PushAddressCorrectionDataFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushContainerVisibilityData\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/POCustomerMailXMLServices/pushContainerVisibilityData\"/\>]{.mark}

[\<wsdl:input name=\"ContainerVisibilityData\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"ContainerVisibilityAcknowledgement\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushContainerVisibilityDataFault\"\>]{.mark}

[\<soap:fault name=\"PushContainerVisibilityDataFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushNixieDetailData\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/POCustomerMailXMLServices/pushNixieDetailData\"/\>]{.mark}

[\<wsdl:input name=\"NixieDetailData\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"NixieDetailAcknowledgement\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushNixieDetailDataFault\"\>]{.mark}

[\<soap:fault name=\"PushNixieDetailDataFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushDeliveryPointVerificationData\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/POCustomerMailXMLServices/pushDeliveryPointVerificationData\"/\>]{.mark}

[\<wsdl:input name=\"DeliveryPointVerificationData\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output
name=\"DeliveryPointVerificationAcknowledgement\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushDeliveryPointVerificationDataFault\"\>]{.mark}

[\<soap:fault name=\"PushDeliveryPointVerificationDataFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\<wsdl:operation name=\"PushStartTheClockData\"\>]{.mark}

[\<soap:operation
soapAction=\"https://www.uspspostalone.com/POCustomerMailXMLServices/pushStartTheClockData\"/\>]{.mark}

[\<wsdl:input name=\"StartTheClockData\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:input\>]{.mark}

[\<wsdl:output name=\"StartTheClockAcknowledgement\"\>]{.mark}

[\<soap:body use=\"literal\"/\>]{.mark}

[\</wsdl:output\>]{.mark}

[\<wsdl:fault name=\"PushStartTheClockDataFault\"\>]{.mark}

[\<soap:fault name=\"PushStartTheClockDataFault\"
use=\"literal\"/\>]{.mark}

[\</wsdl:fault\>]{.mark}

[\</wsdl:operation\>]{.mark}

[\</wsdl:binding\>]{.mark}

[\<wsdl:service name=\"POCustomerMailXMLServices\"\>]{.mark}

[\<wsdl:port name=\"POCustomerMailXMLServices\"
binding=\"tns:POCustomerMailXMLServicesSoapBinding\"\>]{.mark}

[\<soap:address
location=\"http://localhost/Customer/services/POCustomerMailXMLServices\"/\>]{.mark}

[\</wsdl:port\>]{.mark}

[\</wsdl:service\>]{.mark}

[\</wsdl:definitions\>]{.mark}

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

## USER Authentication XSD 

**The customer must implement to allow the *PostalOne!* system to invoke
customer's Web Services**

**+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

[\<?xml version=\"1.0\" encoding=\"UTF-8\"?\>]{.mark}

[\<xsd:schema
xmlns:auth=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
targetNamespace=\"http://www.usps.com/postalone/services/UserAuthenticationSchema\"
version=\"0.0.3\"\>]{.mark}

[\<xsd:annotation\>]{.mark}

[\<xsd:documentation xml:lang=\"en\"\>PostalOne! User Authentication
Request\</xsd:documentation\>]{.mark}

[\</xsd:annotation\>]{.mark}

[\<xsd:element name=\"AuthenticationInfo\"
type=\"auth:AuthenticationInfoType\"/\>]{.mark}

[\<xsd:complexType name=\"AuthenticationInfoType\"\>]{.mark}

[\<xsd:sequence\>]{.mark}

[\<xsd:element name=\"UserId\" type=\"xsd:string\"/\>]{.mark}

[\<xsd:element name=\"UserPassword\" type=\"xsd:string\"/\>]{.mark}

[\</xsd:sequence\>]{.mark}

[\</xsd:complexType\>]{.mark}

[\</xsd:schema\>]{.mark}

**++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++**

# APPENDIX B -- Message Choreography for Data Distribution

Table B- . Data Distribution Message Choreography

  --------------------------------------------------------------------------------------------------------------------------
  No   Message Name                                  Description                                   Customer   *PostalOne!*
  ---- --------------------------------------------- --------------------------------------------- ---------- --------------
  1    StartTheClockQueryRequest                     The customer requests the Start-the-Clock               
                                                     data by providing appointment and job                    
                                                     information for which Start-the-Clock data is            
                                                     needed. The date range of upper and lower is             
                                                     necessary to receive data from the USPS.                 

  2    StartTheClockQueryResponse                    The USPS responds with the Start-the-Clock               
                                                     data for the job and provides the data for               
                                                     plant loaded mail in the plan loaded XML                 
                                                     block, data for drop Shipped mail in the                 
                                                     dropshipped XML block, and BMEU entered mail             
                                                     data in the BMEU XML block.                              

  3    FullServiceContainerVisibilityQueryRequest    The customer can request container visibility           
                                                     information from the USPS by providing the               
                                                     job information, appointment/trip                        
                                                     information, facility id, and container                  
                                                     information or container barcodes.                       

  4    FullServiceContainerVisibilityQueryResponse   The USPS responds with the Container                     
                                                     Induction detail data by providing scan dates            
                                                     and times as well as any conflicts with the              
                                                     container back to the customer.                          

  5    FullServiceAddressCorrectionQueryRequest      The customer can request address correction             
                                                     information from the USPS by providing the               
                                                     job information and date ranges and optional             
                                                     piece barcode range information.                         

  6    FullServiceAddressCorrectionQueryResponse     The USPS, in response to the requests, sends             
                                                     all the address correction data pertinent to             
                                                     the request.                                             

  7    FullServiceNixieDetaiQueryRequest             The customer can request Nixie information              
                                                     from the USPS by providing the CRID, MID, and            
                                                     by providing the job information, class of               
                                                     mail, date ranges and optional piece barcode             
                                                     range information.                                       

  8    FullServiceNixieDetailResponse                The USPS, in response to the requests, sends             
                                                     all the Nixie detail data by MID and Job                 
                                                     information back to the customer.                        

  10   StartTheClockNotification                     The USPS sends this notification to the                  
                                                     customer and provides the Job information for            
                                                     which the Start-the-Clock data is ready                  

  11   StartTheClockDelivery                         The USPS sends this detail data delivery to              
                                                     the customer with all the data available in              
                                                     the StartTheClockQueryResponse message                   

  12   FullServiceContainerVisibilityNotification    The USPS sends this notification to the                  
                                                     customer and provides the Job information for            
                                                     which the ContainerVisibility data is ready              

  13   FullServiceContainerVisibilityDelivery        The USPS sends this detail data delivery to              
                                                     the customer with all the data available in              
                                                     the                                                      
                                                     FullServiceContainerVisibilityQueryResponse              
                                                     message                                                  

  14   FullServiceAddressCorrectionNotification      The USPS sends this notification to the                  
                                                     customer and provides the Job information for            
                                                     which the Address Correction data is ready               

  15   FullServiceAddressCorrectionDelivery          The USPS sends this detail data delivery to              
                                                     the customer with all the data available in              
                                                     the FullServiceAddressCorrectionQueryResponse            
                                                     message                                                  

  16   FullServiceNixieDetailNotification            The USPS sends this notification to the                  
                                                     customer and provides the Job information for            
                                                     which the Nixie Detail data is ready                     

  17   FullServiceNixieDetailDelivery                The USPS sends this detail data delivery to              
                                                     the customer with all the data available in              
                                                     the FullServiceNixieDetailQueryResponse                  
                                                     message                                                  

  18   NotificationResponse                          This message is used in response to all                 
                                                     messages that end in the word 'Notification'             

  19   DeliveryResponse                              This message is used in response to all                 
                                                     messages that end in the word 'Delivery'                 
  --------------------------------------------------------------------------------------------------------------------------

# Appendix C -- Data Distribution Scenarios

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)

## 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.

## 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.

## 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.

## 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 OneCode ACS data through the By/For
    information in the electronic documentation.

-   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 the *PostalOne!* system, 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 D -- Data Distribution Chart 

Table D- . Data Distribution Scenario Chart

  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  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 E - eDoc Form Values

The chapter lists the values associated with the Qualification Report
and Postage Statement form fields.

## Bundle Detail Levels

These bundle detail levels will display in the qualification report.
Reserve or working will show as blank.

Table E- . Bundle Detail Level Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  A                        Firm

  B                        Carrier Route

  C                        5 Digit

  D                        Unique 3-Digit

  E                        Reserve

  F                        3 Digit

  G                        Reserve

  H                        ADC

  I                        AADC

  J                        Reserve

  K                        Origin MxADC

  L                        MxADC

  M                        MxAADC

  N                        Reserve

  O                        Working

  P                        Reserve

  Q                        Reserve

  R                        Parcel

  S                        Multi pc Parcel

  T                        3-D Scheme

  U                        5-D Scheme

  V                        BMC

  W                        5-Digit Super Scheme
  -----------------------------------------------------------------------

## Bundle Levels

Bundle Levels only apply to PS Form 3541. See Bundle Detail Levels for
all classes of mail.

Table E- . Bundle Level Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  3                        3-Digit / SCF

  5                        5-Digit

  A                        ADC/AADC

  C                        Carrier Route

  F                        Firm

  M                        Mixed ADC/Mixed AADC
  -----------------------------------------------------------------------

## Carrier Route Number 

This is the first character in the Carrier Route description. Other
values are not valid.

Table E- . Carrier Route Number Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  C                        Carrier Route

  R                        Rural Route

  H                        Contract Route

  B                        P.O. Box

  G                        General Delivery
  -----------------------------------------------------------------------

## Container Charge Container Type

Container Charge Container Type only applies to PS Form 3541.

Table E- . Container Charge Container Type Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  P                        Pallet

  S                        Sack/Tray

  V                        Exception to sacking
  -----------------------------------------------------------------------

## Container Charge Entry Facility Type

Container Charge Entry Facility Type only applies to PS Form 3541.

Table E- . Container Charge Entry Facility Type Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  B                        Destination BMC

  C                        Origin SCF

  D                        DDU

  J                        Origin ADC

  K                        Origin BMC

  O                        Origin Post Office/DMU

  R                        Destination ADC

  S                        Destination SCF
  -----------------------------------------------------------------------

## Container Levels

Container Levels only apply to PS Form 3541 and the Container and Bundle
report.

Table E- . Container Level Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  3                        3-Digit/SCF

  5                        5-Digit/Carrier Route

  A                        ADC/AADC

  M                        Mixed ADC/Mixed AADC
  -----------------------------------------------------------------------

## Container Type

Table E- . Container Type Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  1                        #1 Sack

  2                        #2 Sack

  3                        #3 Sack

  4                        01V Sack

  5                        03V Sack

  E                        EMM Tray

  F                        Flat Tub

  L                        Logical Tray

  O                        1' Tray

  P                        Pallet

  S                        Sack (general)

  T                        2' Tray

  V                        Sack (Virtual

  B                        Bedload

  U                        Unit Load Device \*

  Z                        User Pallet

  W                        Walled Unit \*\*

  X                        Other

  Null                     No containers sent with detail submission
  -----------------------------------------------------------------------

\*  Describes a variety of rolling stock or wheeled containers designed
for transporting mail.

\*\*  Describes a pallet with corrugated cardboard walls, commonly
called a "Gaylord".

## Enclosing Class

These enclosing classes apply only to 3541.

Table E- . Enclosing Class Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  SM                       Standard Mail

  BP                       Bound Printed Matter

  PE                       Periodicals

  PP                       Package Services

  ML                       Media/Library Mail
  -----------------------------------------------------------------------

## Entry Discount

Table E- . Entry Discount Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  N                        None

  B                        DBMC

  S                        DSCF

  D                        DDU

  P                        Inter-BMC

  Q                        Intra-BMC

  A                        DADC
  -----------------------------------------------------------------------

## Entry Facility Type

Table E- . Entry Facility Type Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  O                        Origin

  B                        BMC

  S                        SCF

  D                        DDU
  -----------------------------------------------------------------------

## Flat Rate Indicator

Table E- . Flat Rate Indicator Values

  -----------------------------------------------------------------------
  Value                    Description
  ------------------------ ----------------------------------------------
  Blank/Null/Nil           Null

  B                        Box - Priority Mail flat rate only

  E                        Envelope -- Priority Mail flat rate only

  L                        Box -- Large -- Priority Mail flat rate only

  M                        Box -- Large, to military destination --
                           Priority Mail flat rate only
  -----------------------------------------------------------------------

## Form Type

Choose the Form Type appropriate for the postage statement you want to
create. The Postage Statement Create Request allows the USPS customer to
submit a 3600-series postage statement to a mailing group. Use the
Periodical Statement Create Request or the Consolidated Periodical
Statement Create Request to create a PS Form 3541. Periodicals pending
application are not supported. Use Mail.dat files or *PostalOne!* Web
pages to submit Periodicals pending.

Table E- . Form Type Values

  ------------------------------------------------------------------------
  Value                  Description                      Postage
                                                          Statement
  ---------------------- -------------------------------- ----------------
  PM                     Priority Mail                    3600

  FC                     First-Class Mail                 3600

  SM                     Standard Mail                    3602

  BP                     Bound Printed Matter             3605

  PP                     Package Services                 3605

  PE                     Periodicals                      3541

  ML                     Media/Library Mail               3605
  ------------------------------------------------------------------------

## Full-service Indicator

Table E- . Full-service Indicator Values

  ---------------------- ------------------------------------------------
  Value                  Description

  F                      Full Service

  B                      Basic

  P                      PostNet

  O                      Other
  ---------------------- ------------------------------------------------

## In-County, Outside-County Indicator

Table E- . In-County, Outside County Indicator Values

  ------------------------------------------------------------------------
  Value                   Description                   Postage Statement
  ----------------------- ----------------------------- ------------------
  I                       In-County                     3541

  N                       Outside County                3541

  O                       Other                         Not 3541
  ------------------------------------------------------------------------

## Metered Affixed Method

Table E- . Metered Affixed Method Indicator Values

  -----------------------------------------------------------------------
  Value                   Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  C                       Metered - Correct

  L                       Metered - Lowest

  M                       Metered - Neither
  -----------------------------------------------------------------------

## Move Update

Table E- . Move Update Values

  -----------------------------------------------------------------------
  **Mail XML      Description
  Value**         
  --------------- -------------------------------------------------------
  0               None

  1               Address Change Service

  2               NCOALink

  3               FASTforward

  4               Alternative Method

  5               Ancillary Service Endorsement

  6               Multiple Methods

  7               Simplified/Occupant/Exceptional Address (no Move Update
                  Method needed)
  -----------------------------------------------------------------------

## Packaging Basis

Table E- . Packaging Basis Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  0                       Piece Count

  1                       Weight

  2                       Both
  -----------------------------------------------------------------------

## Parcel Barcode Rate

Table E- . Package Barcode Rate Values

  --------------------------------------------------------------------------
  **Value**   Description
  ----------- --------------------------------------------------------------
  Y           Yes (machinable parcels, not-flat machinables, Bound Printed
              Matter flats, and Standard Mail irregular parcels only)

  N           No (parcels, not-flat machinables, Bound Printed Matter flats,
              and Standard Mail letters paid as not-flat machinables only)

  O           Other (all others)
  --------------------------------------------------------------------------

## Periodicals Statement Type

Table E- . Periodicals Statement Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  N                       3541

  -----------------------------------------------------------------------

## Permit Type

Table E- . Permit Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  PI                      Permit Imprint

  MT                      Metered Tape

  PC                      Precanceled Stamps

  BR                      Business Reply

  PE                      Periodicals

  GH                      Ghost

  OI                      Official Imprint

  OM                      Official Metered
  -----------------------------------------------------------------------

## Postage Payment Method

Table E- . Postage Payment Method Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  S                       Precanceled Stamps

  M                       Meter

  P                       Permit
  -----------------------------------------------------------------------

## Postage Statement Stage

Table E- . Postage Statement Stage Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  FIN                     Finalized

  REV                     Reversed

  CAN                     Canceled

  UPD                     USPS Processing Due.

  NAP                     Not Available for Processing -- unsupported.
                          Can cancel.

  CON                     Included in a Consolidated Statement. No
                          operations possible.

  ERR                     Cannot be finalized due to an Error

  EST                     Estimated, not actual postage statement

  REW                     Rework - failed verification.

  COM                     Included in a combined Periodicals mailing
                          statement.
  -----------------------------------------------------------------------

## Processing Category

Table E- . Processing Category Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  LT                      Letters

  FL                      Flats

  CD                      Cards

  NF                      Not Flat Machinable

  MP                      Machinable Parcels

  IR                      Irregular Parcels

  PF                      Parcel, First-Class

  CM                      Custom Market Mail
  -----------------------------------------------------------------------

## Publication Type

Table E- . Publication Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  PE                      Periodicals

  -----------------------------------------------------------------------

## Rate Category

Table E- . Rate Category Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  A                       Saturation ECR

  AF                      Standard Mail Saturation ECR Letter Paid As
                          Flat

  B                       High Density ECR

  BF                      Standard Mail High Density ECR Letter Paid As
                          Flat

  D                       Basic ECR (Carrier Route)

  DF                      Standard Mail Basic ECR Letter Paid As Flat

  E                       5-Digit Automation (5-Digit Barcode)

  FB                      Firm Bundle Outside County

  G                       5-Digit Non Barcode(Auto)

  GF                      5-Digit Non Barcode (Auto) Letter Paid As Flat

  H                       3-Digit Automation (3-Digit Barcode)

  K                       3-Digit Non Barcode(Auto)

  KF                      3-Digit Non Barcode (Auto) Letter Paid As Flat

  L                       Basic Automation (Basic Barcode)

  L1                      AADC Barcode

  L2                      Mixed AADC Barcode

  L3                      ADC Barcode

  L4                      Mixed ADC Barcode

  L5                      ADC Non-Barcode

  L6                      Mixed ADC Non-Barcode

  L7                      AADC Non-Barcode

  L8                      Mixed AADC Non-Barcode

  N                       Basic Nonautomation (Basic Presorted)

  NG                      5-Digit Not Flat Machinable

  NK                      3-Digit Not Flat Machinable

  N5                      ADC/BMC Not Flat Machinable

  N6                      Mixed ADC/BMC Not Flat Machinable

  PI                      5-Digit Parcel 0.2063 pounds or less

  PM                      3-Digit Parcel 0.2063 pounds or less

  P7                      ADC Parcel 0.2063 pounds or less

  P8                      Mixed ADC Parcel 0.2063 pounds or less

  PE                      5-Digit Machinable Parcel over 0.2063 pounds

  PQ                      BMC Machinable Parcel over 0.2063 pounds

  PR                      Mixed BMC Machinable Parcel over 0.2063 pounds

  PG                      5-Digit Irregular Parcel over 0.2063 pounds

  PK                      3-Digit Irregular Parcel over 0.2063 pounds

  P5                      ADC Irregular Parcel over 0.2063 pounds

  P6                      Mixed ADC Irregular Parcel over 0.2063 pounds

  S                       Single Piece

  Z1                      BMC Presort

  Z2                      OBMC Presort
  -----------------------------------------------------------------------

## Rate Level

Table E- . Rate Level Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  SP                      Single-Piece

  5B                      Auto 5-Digit/Scheme

  3B                      Auto 3-Digit/Scheme

  AB                      Auto AADC/ADC

  PSRT                    Presort

  5D                      Presort 5 Digit

  3D                      Presort 3 Digit

  BMC                     BMC Presort

  OBMC                    OBMC Presort

  BP                      Standard Mail BMC

  MP                      Mixed BMC Standard

  AD                      ADC Presort

  MD                      Mixed ADC Presort

  WS                      Carrier Route Saturation

  HD                      Carrier Route High Density

  CR                      Carrier Route Line of Travel

  MB                      Auto Mixed AADC/ADC
  -----------------------------------------------------------------------

## Rate Level Indicator

Rate level indicator is used in conjunction with some rate level values.
For valid rate level values, see Error: Reference source not found.

Table E- . Rate Level Indicator

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  A                       Auto (use with rateLevel 5B, 3B, AB, MB)

  B                       Nonauto (use with rateLevel 5D, 3D, AD, MD)

  C                       ECR (use with rateLevel WS, HD, CR)

  M                       Machinable (use with rateLevel AB, MB)

  N                       Nonmachinable (use with rateLevel 5D, 3D, AD,
                          MD)
  -----------------------------------------------------------------------

## Rate Type

Choose the rate type appropriate for the postage statement you want to
create.

Table E- . Rate Type Values

  -----------------------------------------------------------------------------
  **Value**    Description                Applicable Postage Statement
  ------------ -------------------------- -------------------------------------
  R            Regular                    3600, 3602R, 3605, 3541

  N            Nonprofit                  3602N\*, 3541

  C            Classroom                  3541

  S            Science of Agriculture     3541

  T            Priority Mail              3600

  B            Bound Printed Matter       3605

  P            Package Services           3605

  L            Library Mail               3605

  F            Media Mail                 3605

  [A]{.mark}   Alt Delivery               Not Supported

  D            Parcel Select              Not Supported

  X            Other                      Not Supported

  H            Per Ride Along             Not Supported - Use Single Ride Along
                                          Weight

  M            Repositionable Component   Not Supported - Use Repositionable
                                          Notes Indicator

  Z            Included-Part of Host      Not Supported - Add weight (and
               Postage                    advertising percentage) to piece or
                                          copy weight.

  E            Priority Mail Flat Rate    Not Supported -- Use Priority Mail
               Envelope                   Postage Statement 3600

  G            Priority Mail Flat Rate    Not Supported -- Use Priority Mail
               Box                        Postage Statement 3600

  1            UA                         Not Supported -- International

  2            UL                         Not Supported -- International

  3            UM                         Not Supported -- International

  4            UR                         Not Supported -- International

  J            Priority Mail Flat Large   Not Supported -- Use Priority Mail
               Box                        Postage Statement 3600

  K            Priority Mail Flat Large   Not Supported -- Use Priority Mail
               Box APO/FPO                Postage Statement 3600

  W            Science of Agriculture     3541
               Limited Circulation        

  Y            Regular Limited            3541
               Circulation                
  -----------------------------------------------------------------------------

\* If you choose Nonprofit Standard Mail, the Permit Holder Permit or
the Mail Owner Permit must reference a valid Nonprofit Standard Mail
application number or authorization number in the *PostalOne!* system.

## Recipient Type

Table E- . Recipient Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  0                       Not Applicable

  1                       Subscriber

  2                       Requester

  3                       Nonsubscriber/Nonrequester

  4                       Subscriber/Nonsubscriber

  5                       Requester/Nonrequester
  -----------------------------------------------------------------------

## Sacking Basis

Table E- . Sacking Basis Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  0                       Piece Count

  1                       20 lbs.

  2                       125 pieces

  3                       15 lbs.

  4                       Both
  -----------------------------------------------------------------------

## Sortation Level

Table E- . Sortation Level Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  CRD                     Carrier Route

  5DG                     5 Digit

  CR5                     5 Digit Carrier Route

  5DGS                    5 Digit Scheme

  CR5S                    5 Digit Scheme Carrier Route

  M5D                     5 Digit Merged

  M5DS                    5 Digit Merged Scheme

  MET                     5 Digit Metro

  3DG                     3 Digit

  CR3                     3 Digit Carrier Route

  3DGS                    3 Digit Scheme

  ADC                     ADC

  AADC                    AADC

  MADC                    Mixed ADC

  MAAD                    Mixed AADC

  SCF                     SCF

  PSCF                    PSCF

  BMC                     BMC

  PBMC                    PBMC

  MBMC                    Mixed BMC

  ASF                     ASF

  OMX                     Mixed Origin ADC

  PADC                    Protected ADC

  DPC                     DPC/3D Scheme

  RDC                     RDC/Scheme

  MRDC                    Mixed RDC

  SP                      Single Piece
  -----------------------------------------------------------------------

## Special Service Code

Table E- . Special Service Code Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  CM                      Certified Mail

  COD                     Collect on Delivery

  COM                     Certificate of Mailing

  DC                      Delivery Confirmation

  IM                      Insured Mail

  PAL                     Parcel Airlift

  RD                      Restricted Delivery

  RM                      Registered Mail

  RR                      Return Receipt

  RRE                     Return Receipt Electronic

  RRM                     Return Receipt for Merchandise

  SC                      Signature Confirmation

  SH                      Special Handling
  -----------------------------------------------------------------------

## Special Service Subcode

Table E- . Special Service Subcode Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  N                       None or Not Bulk

  E                       Electronic

  R                       Retail or Registered (depending on Service
                          Code)

  T                       Requested at Time of Mailing

  B                       Bulk
  -----------------------------------------------------------------------

## Status 

Table E- . Status Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  1                       Success

  0                       Pending

  -1                      Failed
  -----------------------------------------------------------------------

## Surcharge Discount Type

Surcharge Discount Types only apply to PS Form 3541. The description for
each value includes the relevant line number on PS Form 3541.

Table E- . Surcharge Discount Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  1                       DDU (A17)

  5\*                     Nonadvertising Piece Rate (C30)

  9\*                     Ride-Along (surcharge) (A20, F1)

  C\*                     Nonadvertising Pound Rate -- DDU (B12)

  D\*                     Nonadvertising Pound Rate -- DSCF (B13)

  E\*                     Nonadvertising Pound Rate -- DADC (B14)

  R\*                     Repositionable notes (surcharge) (A21, F2)

  Z\*                     Nonadvertising Pound Rate -- All Others (B15)
  -----------------------------------------------------------------------

\* These values only appear in receipt files generated by the
*PostalOne!* system. Mailers should only send files that claim Surcharge
Discount value "1" if a surcharge applies, and leave the field blank if
no discount applies.

## Surcharge Type

Table E- . Surcharge Type Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  2                       Oversized Surcharge

  A                       First-Class Mail Parcel Surcharge

  D                       Dimensional Rate

  E                       Permit Reply Mail

  L                       Detached Address Label Used

  N                       No surcharge

  P                       Balloon surcharge

  R                       First-Class Mail Nonmachinable Letters (0.0625
                          lbs or less)
  -----------------------------------------------------------------------

## Weight Break Indicator

Table E- . Weight Break Indicator Values

+---------+------------------------------------------------------------+
| **      | Description                                                |
| Value** |                                                            |
+=========+============================================================+
| A       | For Standard Mail non-Letters, piece weight is over 0.2063 |
|         | lbs.                                                       |
|         |                                                            |
|         | For First-Class Mail Permit Reply, piece weight is over    |
|         | 0.0625 lbs.                                                |
+---------+------------------------------------------------------------+
| B       | For Standard Mail, piece weight is 0.2063 lbs or less.     |
|         |                                                            |
|         | For First-Class Mail Permit Reply, piece weight is 0.0625  |
|         | lbs or less.                                               |
+---------+------------------------------------------------------------+
| H       | For Standard Mail Letters, piece weight is over 0.2063     |
|         | lbs.                                                       |
+---------+------------------------------------------------------------+
| N       | None                                                       |
+---------+------------------------------------------------------------+

## Zone (Qualification Report)

Table E- . Zone (Qualification Report) Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  N                       None

  M                       Mixed

  1                       Zone 1 & 2

  3                       Zone 3

  4                       Zone 4

  5                       Zone 5

  6                       Zone 6

  7                       Zone 7

  8                       Zone 8

  ICD                     In County DDU

  IC                      In County Other

  DDU                     Out County DDU

  SCF                     Out County DSCF

  ADC                     Out County DADC
  -----------------------------------------------------------------------

## Zone

Table E- . Zone Values

  -----------------------------------------------------------------------
  **Value**               Description
  ----------------------- -----------------------------------------------
  Blank/Null/Nil          Null

  N                       None

  M                       Mixed

  LC                      Local

  1                       Zone 1 & 2

  3                       Zone 3

  4                       Zone 4

  5                       Zone 5

  6                       Zone 6

  7                       Zone 7

  8                       Zone 8

  D                       DDU

  S                       DSCF

  V                       DADC
  -----------------------------------------------------------------------

# Appendix F -- Postage Statement Values by Form Type

The postage statement values will be validated for each form type as
listed in this appendix.

## Enclosing Class

Table F- . Enclosing Class by Form Type

  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                   Form Types                                                                 

                   Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                   Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                   Matter                                                            (PP)     
                   (BP)                                                                       

  Enclosing                                                                              
  Class                                                                                       

              BP                                                                             

              ML                                                                             

              PE                                                                             

              PP                                                                             

              SM                                                                             
  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Entry Discount

Table F- . Entry Discount by Form Type

  ---------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  Entry      N                                                                           
  Discount                                                                                   

             B                                                                             

             S                                                                             

             D                                                                             

             P                                                                              

             Q                                                                              

             A                                                                              
  ---------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Entry Facility Type

Table F- . Entry Facility by Form Type

  ---------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  Entry      O                                          \*                             
  Facility                                                                                   
  Type                                                                                       

             B                                          \*                             

             S                                          \*                             

             D                                          \*                             
  ---------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

\* Applies to consolidated statements only.

## Flat Rate Indicator

Table F- . Flat Rate Indicator by Form Type

  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  Flat Rate                                                                             
  Indicator                                                                                  

              B                                                                             

              E                                                                             

              L                                                                             

              M                                                                             
  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Nonsub/Nonreq 10% Limit

See field name Over 10.

Table F- . Nonsubscriber / Nonrequester Over 10% Limit by Form Type

  -------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
               Form Types                                                                 

               Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
               Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
               Matter                                                            (PP)     
               (BP)                                                                       

  Nonsub / Y                                                                             
  Nonreq                                                                                  
  10%                                                                                     
  Limit                                                                                   

           N                                                                             
  -------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Inside-County, Outside-County Indicators

Table F- . Inside-County, Outside-County Indicators by Form Type

  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  In/Out      I                                                                             
  County                                                                                     
  Indicator                                                                                  

              N                                                                             
  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Mailer Role

Table F- . Mailer Roles

  --------------------------------------------------------------------------
  Mailer Role       **Abbreviation**   **Postage          **Periodicals
                                       Statement**        Statement\*\***
  ----------------- ------------------ ------------------ ------------------
  Additional        AP                 Required.\*        N/A
  Postage                                                 

  Permit Holder     PH                 Required.          N/A

  Publisher         PU                 N/A                Required.

  Mailing Agent     MA                 Required.          Required.
  (Preparer)                                              

  Mail Owner        MO                 Optional.          N/A
  (Prepared For)                                          
  --------------------------------------------------------------------------

The abbreviations provided are for the Table "Mailer Roles by Form
Type."

\*Required only for Postage Affixed postage statements.

\*\*Pending Periodicals (permit type PP are not supported).

Table F- . Mailer Role by Form Type

  -------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                Form Types                                                                 

                Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                Matter                                                            (PP)     
                (BP)                                                                       

  Mailer   AP                                                                          
  Role                                                                                     

           PH                                                                         

           MA                                                                        

           MO                                                                        

           PU                                                                             
  -------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Metered Affixed Method

Table F- . Metered Affixed Method by Form Type

  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                Form Types                                                                 

                Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                Matter                                                            (PP)     
                (BP)                                                                       

  Metered                                                                             
  Affixed                                                                                  
  Method                                                                                   

            C                                                                         

            L                                                                         

            M                                                                         
  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Move Update

Table F- . Move Update Abbreviations Key

  ----------------------------------------------------------------------------
  **Abbreviation**   Description
  ------------------ ---------------------------------------------------------
  ACE                Ancillary Service Endorsement

  ACS                Address Change Service

  ALT                Alternative Method

  FAST               FASTforward

  MULT               Multiple Methods

  NCOA               NCOALink
  ----------------------------------------------------------------------------

Table F- . Move Update by Form Type

  -------- ------ --------- ------------- --------------- ------------- ---------- -------- ----------
                  Form                                                                      
                  Types                                                                     

                  Bound     First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed   Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                           (PP)     
                  (BP)                                                                      

  Move     ACE                                                                            
  Update                                                                                    

           ACS                                                                            

           ALT                                                                            

           FAST                                                                           

           MULT                                                                           

           NCOA                                                                           
  -------- ------ --------- ------------- --------------- ------------- ---------- -------- ----------

## Packaging Basis

Table F- . Packaging Basis by Form Type

  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  Packaging                                                                             
  Basis                                                                                      

              0                                                                           

              1                                                                            

              2                                                                            
  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Parcel Barcode Rate

Table F- . Parcel Barcode Rate by Form Type

  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                Form Types                                                                 

                Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                Matter                                                            (PP)     
                (BP)                                                                       

  Parcel    Y                                                                           
  Barcode                                                                                  
  Rate                                                                                     

            N                                                                         

            O                                                                            
  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Permit Type

Table F- . Permit Holder Type by Form Type

  ---------------------------------------------------------------------------------------------------
                Form Types                                                                 
  -------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                Matter                                                            (PP)     
                (BP)                                                                       

  Permit   PI                                                                         
  Type                                                                                     

           MT                                                                           

           PC                                                                            

           PE                                                                             

           GH                                                                              

           OI                                                                         

           OM                                                                         
  ---------------------------------------------------------------------------------------------------

## Periodicals Statement Type

Table F- . Periodicals Statement Type by Form Type

  ------------- ----- --------- ------------- --------------- ------------- ---------- -------- ----------
                      Form                                                                      
                      Types                                                                     

                      Bound     First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                      Printed   Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                      Matter                                                           (PP)     
                      (BP)                                                                      

  Periodicals   N                                                                              
  Statement                                                                                     
  Type                                                                                          
  ------------- ----- --------- ------------- --------------- ------------- ---------- -------- ----------

## Postage Payment Method

Table F- . Postage Payment Method by Form Type

  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                Form Types                                                                 

                Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                Matter                                                            (PP)     
                (BP)                                                                       

  Postage   S                                                                           
  Payment                                                                                  
  Method                                                                                   

            M                                                                          

            P                                                                        
  --------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Postage Statement Stage

Table F- . Postage Statement Stage by Form Type

  ----------- ----------- --------- ------------- --------------- ------------- ---------- -------- ----------
                          Form                                                                      
                          Types                                                                     

                          Bound     First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                          Printed   Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                          Matter                                                           (PP)     
                          (BP)                                                                      

  Postage     FIN                                                                             
  Statement                                                                                         
  Stage                                                                                             

              REV                                                                             

              CAN                                                                             

              UPD                                                                             

              NAP\*                                                                           

              CON\*\*                                                                              

              COM\*\*\*                                                                            

              ERR                                                                             

              EST                                                                             

              REW                                                                             
  ----------- ----------- --------- ------------- --------------- ------------- ---------- -------- ----------

\* Unsupported. Only cancellations possible.

\*\* Only allowed for child PS Form 3541 statements within a
consolidated Periodicals statement. If billable postage statements have
this stage, it is a system error and the statement is not billed, it
must be re-entered.

\*\*\* Only allowed for combined PS Form 3541 mailings.

## Prepared as Standard Mail

Table F- . Prepared as Standard Mail by Form Type

  ---------- ----- --------- ------------- --------------- ------------- ---------- -------- ----------
                   Form                                                                      
                   Types                                                                     

                   Bound     First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                   Printed   Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                   Matter                                                           (PP)     
                   (BP)                                                                      

  Prepared   Yes                                                                           
  As SM                                                                                      

             No                                                                         
  ---------- ----- --------- ------------- --------------- ------------- ---------- -------- ----------

## Price Type

Table F- . Price Type by Form Type

  ------- ---------- ---------- ------------- --------------- ------------- ---------- -------- ----------
                     Form Types                                                                 

                     Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                     Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                     Matter                                                            (PP)     
                     (BP)                                                                       

  Price   DISCOUNT                                                                             
  Type                                                                                          

          RETAIL                                                                               
  ------- ---------- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Processing Category

Table F- . Processing Category by Form Type

  ------------ ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                    Form Types                                                                 

                    Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                    Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                    Matter                                                            (PP)     
                    (BP)                                                                       

  Processing   LT                                                                           
  Category                                                                                     

               FL                                                                          

               CD                                                                             

               MP                                                                           

               IR                                                                          

               PF                                                                            

               CM                                                                              

               NF                                                                              
  ------------ ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Rate Category

Table F- . Rate Category by Form Type

  -----------------------------------------------------------------------------------------------
            Form Types                                                                 
  ---- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
            Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
            Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
            Matter                                                            (PP)     
            (BP)                                                                       

       A                                                                              

       AF                                                                             

       B                                                                              

       BF                                                                             

       D                                                                             

       DF                                                                             

       E                                                                             

       FB                                                                             

       G                                                                            

       GF                                                                             

       H                                                                             

       K                                                                             

       KF                                                                             

       L                                                                              

       L1                                                                            

       L2                                                                            

       L3                                                                            

       L4                                                                            

       L5                                                                             

       L6                                                                             

       L7                                                                             

       L8                                                                             

       N                                                                           

       NG                                                                              

       NK                                                                              

       N5                                                                              

       N6                                                                              

       P5                                                                              

       P6                                                                              

       P7                                                                              

       P8                                                                              

       PE                                                                              

       PG                                                                              

       PI                                                                              

       PK                                                                              

       PM                                                                              

       PR                                                                              

       PQ                                                                              

       S                                                                          

       Z1                                                                             

       Z2                                                                             
  -----------------------------------------------------------------------------------------------

## Rate Type

Table F- . Rate Type by Form Type

  -------------------------------------------------------------------------------------------------
              Form Types                                                                 
  ------ ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
              Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
              Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
              Matter                                                            (PP)     
              (BP)                                                                       

  Rate   R                                                                             
  Type                                                                                   

         N                                                                              

         C                                                                              

         S                                                                              

         T                                                                              

         B                                                                              

         P                                                                              

         L                                                                              

         F                                                                              

         W                                                                              

         Y                                                                              
  -------------------------------------------------------------------------------------------------

## Recipient Type

Table F- . Recipient Type by Form Type

  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                   Form Types                                                                 

                   Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                   Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                   Matter                                                            (PP)     
                   (BP)                                                                       

  Recipient   0                                                                              
  Type                                                                                        

              1                                                                              

              2                                                                              

              3                                                                              

              4                                                                              

              5                                                                              
  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Sacking Basis

Table F- . Sacking Basis by Form Type

  --------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                 Form Types                                                                 

                 Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                 Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                 Matter                                                            (PP)     
                 (BP)                                                                       

  Sacking                                                                              
  Basis                                                                                     

            0                                                                             

            1                                                                             

            2                                                                              

            3                                                                              

            4                                                                              
  --------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Special Service Code

Table F- . Special Service Code by Form Type

  --------------------------------------------------------------------------------------------------------
                     Form Types                                                                 
  --------- -------- ---------- ------------- --------------- ------------- ---------- -------- ----------
                     Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                     Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                     Matter                                                            (PP)     
                     (BP)                                                                       

  Special   CM                                                                                
  Service                                                                                       
  Code                                                                                          

            COD                                                                            

            COM                                                                            

            DC\*                                                                            

            IM                                                                             

            PAL                                                                              

            RD                                                                             

            RM                                                                                

            RR                                                                             

            RRE                                                                            

            RRM                                                                             

            SC\*\*                                                                          

            SH                                                                             
  --------------------------------------------------------------------------------------------------------

\* DC is allowed by BP, ML, PP and SM because they support processing
categories of MP, IR or PF

\*\* SC is allowed by BP, ML and PP because they support processing
categories of MP, IR or PF and are not explicitly excluded.

## Special Service Subcode

Table F- . Special Service Subcode by Special Service Code

  --------- ---- --------- ----- ----- ---- ----- ----- ---- ----- ---- ----- ----- ---- ----
                 Special                                                                 
                 Service                                                                 
                 Code                                                                    

                 CM        COD   COM   DC   IM    PAL   RD   RM    RR   RRE   RRM   SC   SH

  Special   N                                                                    
  Service                                                                                
  Subcode                                                                                

            E                                                                         

            R                                                                         

            T                                                                           

            B                                                                           
  --------- ---- --------- ----- ----- ---- ----- ----- ---- ----- ---- ----- ----- ---- ----

## Surcharge

Table F- . Surcharge by Form Type

  ------------------------------------------------------------------------------------------------------
                   Form Types                                                                 
  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                   Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                   Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                   Matter                                                            (PP)     
                   (BP)                                                                       

  Surcharge   2                                                                              
  Type                                                                                        

              A                                                                              

              D                                                                              

              E                                                                             

              L                                                                               

              N                                                                          

              P                                                                              

              R                                                                              
  ------------------------------------------------------------------------------------------------------

## Surcharge Discount Type

Table F- . Surcharge Discount Type by Form Type

  ------------------------------------------------------------------------------------------------------
                   Form Types                                                                 
  ----------- ---- ---------- ------------- --------------- ------------- ---------- -------- ----------
                   Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                   Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                   Matter                                                            (PP)     
                   (BP)                                                                       

  Surcharge                                                                                  
  Discount                                                                                    
  Type                                                                                        

              1                                                                              

              5                                                                              

              9                                                                              

              C                                                                              

              D                                                                              

              E                                                                              

              R                                                                              

              Z                                                                              
  ------------------------------------------------------------------------------------------------------

## Weight Break Indicator

Table F- . Weight Break Indicator by Form Type

  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------
                  Form Types                                                                 

                  Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
                  Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
                  Matter                                                            (PP)     
                  (BP)                                                                       

  Weight      N                                                                         
  Break                                                                                      
  Indicator                                                                                  

              B                                                                             

              A                                                                             

              H                                                                              
  ----------- --- ---------- ------------- --------------- ------------- ---------- -------- ----------

## Zone

Table F- . Zone by Form Type

  --------------------------------------------------------------------------------------------------
               Form Types                                                                 
  ------ ----- ---------- ------------- --------------- ------------- ---------- -------- ----------
               Bound      First-Class   Media/Library   Periodicals   Priority   Parcel   Standard
               Printed    Mail (FC)     Mail (ML)       (PE)          Mail (PM)  Post     Mail (SM)
               Matter                                                            (PP)     
               (BP)                                                                       

  Zone                                                                                   

         N                                                                          

         LC                                                                              

         1                                                                            

         3                                                                             

         4                                                                            

         5                                                                            

         6                                                                            

         7                                                                            

         8                                                                            

         D                                                                               

         S                                                                               

         V                                                                               
  --------------------------------------------------------------------------------------------------