Invoice Aging Clause Samples

POPULAR SAMPLE Copied 2 times
Invoice Aging. No BTC Recipient will be required to pay any invoices issued by State Street or any third party more than three (3) months after the month on which the fees owed thereunder have accrued. Notwithstanding the foregoing, for any Services provided by any Subcontractor that is not an Affiliate of State Street, such three-month period shall not begin until State Street receives the invoice from the applicable Subcontractor, but in no event will a BTC Recipient be required to pay any invoices issued by State Street or any third party for such Subcontractor services more than fifteen (15) months after the month on which the fees accrued.
View SourceView Similar (10)
Invoice Aging. No BFA Recipient (nor BFA, on behalf of any BFA Recipient), will be required to pay any invoices issued by Provider or any third party more than three (3) months after the month on which the fees owed thereunder have accrued. Notwithstanding the foregoing, for any Services provided by any Subcontractor that is not an Affiliate of Provider, such three-month period shall not begin until Provider receives the invoice from the applicable Subcontractor, but in no event will a BFA Recipient (or BFA, on behalf of a BFA Recipient), be required to pay any invoices issued by Provider or any third party for such Subcontractor services more than fifteen (15) months after the month on which the fees accrued.
View SourceView Similar (7)
Invoice Aging. No BFA Recipient nor BFA, on behalf of any BFA Recipient, will be required to pay any invoices issued by State Street or any third party more than three (3) months after the month on which the fees owed thereunder have accrued. Notwithstanding the foregoing, for any Services provided by any Subcontractor that is not an Affiliate of State Street, such three-month period shall not begin until State Street receives the invoice from the applicable Subcontractor, but in no event will a BFA Recipient or BFA, on behalf of a BFA Recipient, be required to pay any invoices issued by State Street or any third party for such Subcontractor services more than fifteen (15) months after the month on which the fees accrued.
View SourceView Similar (3)
Invoice Aging. BTC will not be required to pay any invoices issued by Provider or any third party more than three (3) months after the month on which the fees owed thereunder have accrued.
View SourceView Similar (3)
Invoice Aging. No BGI Recipient will be required to pay any invoices issued by State Street or any third party more than three (3) months after the month on which the fees Master Services Agreement 20 BGI | State Street CONFIDENTIAL Portions of this agreement have been omitted pursuant to a request for confidential treatment request by BlackRock Institutional Trust Company, N.A. and have been filed separately with the Securities Exchange Commission. owed thereunder have accrued. Notwithstanding the foregoing, for any Services provided by any Subcontractor that is not an Affiliate of State Street, such three-month period shall not begin until State Street receives the invoice from the applicable Subcontractor, but in no event will a BGI Recipient be required to pay any invoices issued by State Street or any third party for such Subcontractor services more than fifteen (15) months after the month on which the fees accrued.
View Source

Related to Invoice Aging

  • Invoice Detail All charges for services rendered or for reimbursement of expenses authorized by Department pursuant to the Grant Work Plan shall be submitted to Department in sufficient detail for a proper pre-audit and post-audit to be performed. The Grantee shall only invoice Department for deliverables that are completed in accordance with the Grant Work Plan.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s ▇▇▇▇ from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth ▇▇▇▇ ▇▇▇▇ identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.

  • Invoice The original and duplicate invoices covering each and every shipment made against this order showing Contract number, Vendor number, and other essential particulars, must be forwarded promptly to the ordering agency concerned by the Vendor to whom the order is issued. Delays in receiving invoice and also errors and omissions on statements will be considered just cause for withholding settlement without losing discount privileges. All accounts are to be carried in the name of the agency or institution receiving the goods, and not in the name of the Division of Purchases.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).