A TPA defines how trading partners interact in transportation, document exchange and business protocol. A TPA contains the terms and conditions of the contract, the roles of participant (buyer, seller), communication and security protocols and business processes (valid actions, sequencing rules, etc.). All access and data exchange relationships must be governed by agreements that respect the legal and programmatic obligations of partners to exchange data. The Commercial Contract (TPA) is intended to document and formalize business processes and contractual aspects related to data exchange through the Exchange network. It allows parties to explain that they have a personal interest and commitment to making the relationship and data exchange work, and provides a tool to define contact points within their organizations responsible for managing a successful exchange of information. papiNet offers a TPA (Trading Partner Agreement) model for your use in developing your own TPA when you start exchanging electronic documents between B2B partners. It is important to understand that these agreements must be verified by your company before being used to ensure that all items applicable to your particular environment are included (or excluded). In some cases, the necessary elements of a TPA can already be filled out by programmatic documents and, in this case, a reference to the existing voice storage location in these documents can be used to satisfy the TPAs. If other agreements cover only a portion of the necessary elements, an “Umbrella” TPA could be implemented to identify and aggregate relevant control documents, as well as the inclusion of missing components under a single reference source. In all cases, existing documents, a hybrid or a newly developed TPA must be in place within six months of the launch of the data exchange. In the context of papiNet, the TPA thus defines a specific implementation of the papiNet standard between two parties.