Common use of Functional Acknowledgement and Response Document Clause in Contracts

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPW, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPWAgreement, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW included Trading Partner Information Sheet(s) a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPWAgreement, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW Exhibit(s) a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPW, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW Exhibit(s)TPW a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPW, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s 's records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s 's records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPWAgreement, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the Exhibit(s) TPW a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPWAgreement, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW Exhibit(s)TPW a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.

Functional Acknowledgement and Response Document. 2.3.1 For the purposes of this Agreement and the TPWAgreement, a "Functional Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document has been received and whether all required portions of the Document are syntactically correct or not, but which does not confirm the substantive content(s) of the related Document. 2.3.2 If the Functional Acknowledgment indicates an error, neither party shall rely on the Document. The sending party shall attempt to correct the error and promptly retransmit the Document or otherwise contact the receiving party. If the Functional Acknowledgment does not indicate any error, the Functional Acknowledgment shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.3 If there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Functional Acknowledgement, the sending party’s records of the contents of the Document shall control, unless the sending party has retransmitted a Document pursuant to Section 2.3.7. 2.3.4 By mutual agreement, the parties may designate in the TPW Exhibit(s) EDI Worksheet(s) a "Response Document" Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document confirms that a Document has been received, and whether all required portions of the Document are syntactically correct, and contains data sent by the receiving party to the sending party in response to the substantive content of the related Document. 2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a Document has been received in syntactically correct form. 2.3.6 If the parties have mutually agreed to the use of a Response Document, and if there has been proper receipt pursuant to Section 2.1, verification and successful decryption pursuant to Section 2.2, and if the receiving party nevertheless fails to transmit a Response Document, the sending party’s records of the contents of the Document shall control unless the sending party has retransmitted a Document pursuant to Section 2.3.7.