Common use of Pack Rejection Clause in Contracts

Pack Rejection. 6.4.1 API 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API by BellSouth.

Pack Rejection. 6.4.1 API MPOWER 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API MPOWER will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API MPOWER by BellSouth.

Pack Rejection. 6.4.1 API IDS 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API IDS will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API IDS by BellSouth.

Pack Rejection. 6.4.1 API Max-Tel 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Max-Tel will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Max-Tel by BellSouth.

Pack Rejection. 6.4.1 API ICG 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API ICG will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API ICG by BellSouth.

Pack Rejection. 6.4.1 API BTI 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API BTI will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API BTI by BellSouth.

Pack Rejection. 6.4.1 API Arrow 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Arrow will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Arrow by BellSouth.

Pack Rejection. 6.4.1 API Advantel 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Advantel will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Advantel by BellSouth.

Pack Rejection. 6.4.1 API Navigator 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Navigator will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Navigator by BellSouth.

Pack Rejection. 6.4.1 API SBCT 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API SBCT will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API SBCT by BellSouth.

Pack Rejection. 6.4.1 API Access One 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Access One will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Access One by BellSouth.

Pack Rejection. 6.4.1 API New Access 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API New Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API New Access by BellSouth.

Pack Rejection. 6.4.1 API Pointecom 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API Pointecom will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API Pointecom by BellSouth.

Pack Rejection. 6.4.1 API 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API TrustedNet will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API TrustedNet by BellSouth.

Pack Rejection. 6.4.1 API ACCESS Integrated 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 (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. API ACCESS Integrated will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to API ACCESS Integrated by BellSouth.