Common use of ODUF Pack Rejection Clause in Contracts

ODUF Pack Rejection. 6.4.1 Vertex will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Vertex will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Vertex by BellSouth.

ODUF Pack Rejection. 6.4.1 Vertex Momentum will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Vertex Momentum will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Vertex Momentum by BellSouth.

ODUF Pack Rejection. 6.4.1 Vertex Momentum will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Vertex Momentum will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Vertex Momentum by BellSouthXxxxXxxxx.