Invoice and Payment Process Sample Clauses
Invoice and Payment Process. (a) As soon as practicable after the end of each Showing Month, Seller will render to Buyer an invoice for the payment obligations, if any, incurred hereunder with respect to such Showing Month.
(b) Buyer will pay Seller all undisputed invoice amounts on or before the later of (i) the twentieth (20th) day of each month, or (ii) the tenth (10th) day after receipt of Seller’s invoice and Demonstrated Capacity or, if such day is not a Business Day, then on the next Business Day.
(c) Each Party will make payments by electronic funds transfer, or by other mutually agreeable method(s), to the account designated by the other Party. Any amounts not paid by the due date will be deemed delinquent and will accrue interest at the Cash Interest Rate, such interest to be calculated from and including the due date to but excluding the date the delinquent amount is paid in full.
(d) Buyer may offset against any future payments by any amount(s) that were previously overpaid.
(e) Either Party may, in good faith, dispute the correctness of any invoice, bill, charge, or any adjustment to an invoice, rendered under this Agreement, or adjust any invoice for any arithmetic or computational error within twelve (12) months of the date the invoice, bill, charge, or adjustment to an invoice, was rendered. Disputes are subject to the provisions of Article 10 below. In the event an invoice or portion thereof, or any other claim or adjustment arising hereunder, is disputed, payment of the undisputed portion of the invoice shall be required to be made when due, with Notice of the objection given to the other Party. Any invoice dispute or invoice adjustment shall be in writing and shall state the basis for the dispute or adjustment. Payment of the disputed amount shall not be required until the dispute is resolved. Upon resolution of the dispute, any required payment shall be made within ten (10) Business Days of such resolution.
(f) Buyer may deduct any amounts that would otherwise be due to Seller under this Agreement from any amounts owing and unpaid by Seller to Buyer under this Agreement.
(g) With respect to any Joint Resource, if Seller and any third party both submit claims to Buyer for payment with respect to such Joint Resource which, when added together, exceed the total capacity of the Joint Resource, Buyer shall not be obligated to make payment to Seller in respect of such Joint Resource until Seller reconciles the error with such third party and Seller re-submits the correct...
Invoice and Payment Process. If the RC Customer is a Balancing Authority, or if it is a Transmissions Operator who elects to be billed directly in exchange for the RC Services provided by this Agreement, said RC Customer will be invoiced for RC Services in accordance with Section X.X19.7 of the CAISO Tariff and will have the right to dispute the RC Services invoiced amount in accordance with Section X.XSections 19.7 and 19.10 of the CAISO Tariff. If the RC Customer is a Transmission Operator and does not elect to be billed directly, the costs for its RC Services will be borne by its Balancing Authority. If the RC Customer is within the CAISO Balancing Authority Area, the Transmission Operator will be billed in accordance with Section X.X11.20.9 of the CAISO Tariff. For billing purposes in accordance with this Section, the RC Customer represents that it is either a (check the box that applies):
(a) Balancing Authority ☐
(b) Transmission Operator (direct billing elected) ☐
(c) Transmission Operator (billed to Balancing Authority) ☐
(d) Transmission Operator within the CAISO BAA ☐
Invoice and Payment Process. If the RC Customer is a Balancing Authority, or if it is a Transmissions Operator who elects to be billed directly in exchange for the RC Services provided by this Agreement, said RC Customer will be invoiced for RC Services in accordance with Section 19.7 of the CAISO Tariff and will have the right to dispute the RC Services invoiced amount in accordance with Sections 19.7 and 19.10 of the CAISO Tariff. If the RC Customer is a Transmission Operator and does not elect to be billed directly, the costs for its RC Services will be borne by its Balancing Authority. If the RC Customer is within the CAISO Balancing Authority Area, the Transmission Operator will be billed in accordance with Section 11.20.9
Invoice and Payment Process. Upon completion of the Project and approval by the City, Community Transit will submit a reimbursement request to the City for the full purchase cost, excluding installation, of the bicycle storage and bicycle locks. The reimbursement request shall, at a minimum, include the invoice(s) and any required documents in reference to the total purchase cost. The reimbursement request shall be sent to the City of Lynnwood, Accounts Payable, ▇▇▇▇▇ ▇▇▇▇ ▇▇▇ ▇▇▇▇, ▇▇▇▇▇▇▇, WA 98036. DocuSign Envelope ID: 8D40084F-41A6-4A63-A635-84D811C1D0BE
Invoice and Payment Process. If the RC Customer is a Balancing Authority, or if it is a Transmissions Operator who elects to be billed directly in exchange for the RC Services provided by this Agreement, said RC Customer will be invoiced for RC Services in accordance with Section 19.7 of the CAISO Tariff and will have the right to dispute the RC Services invoiced amount in accordance with Sections 19.7 and 19.10 of the CAISO Tariff. If the RC Customer is a Transmission Operator and does not elect to be billed directly, the costs for its RC Services will be borne invoiced ▇▇▇▇ its Balancing Authority as identified in its Schedule 1 and confirmed in the Schedule 1 submitted by the identified Balancing Authority. If the RC Customer is within the CAISO Balancing Authority Area, the Transmission Operator will be billed in accordance with Section 11.20.9 of the CAISO Tariff. For billing purposes in accordance with this Section, the RC Customer represents that it is either a (check the box that applies):
(a) Balancing Authority ☐
(b) Transmission Operator (direct billing elected) ☐
(c) Transmission Operator (billed to Balancing Authority) ☐
(d) Transmission Operator within the CAISO BAA ☐
Invoice and Payment Process. If the RC Customer is a Balancing Authority, or if it is a Transmissions Operator who elects to be billed directly in exchange for the RC Services provided by this Agreement, said RC Customer will be invoiced for RC Services in accordance with Section 19.7 of the CAISO Tariff and will have the right to dispute the RC Services invoiced amount in accordance with Sections 19.7 and 19.10 of the CAISO Tariff. If the RC Customer is a Transmission Operator and does not elect to be billed directly, the costs for its RC Services will be borne by its Balancing Authority. If the RC Customer is within the CAISO Balancing Authority Area, the Transmission Operator will be billed in accordance with Section 11.20.9 of the CAISO Tariff. For billing purposes in accordance with this Section, the RC Customer represents that it is either a (check the box that applies):
(a) Balancing Authority
(b) Transmission Operator (direct billing elected) □
(c) Transmission Operator (billed to Balancing Authority) □
(d) Transmission Operator within the CAISO BAA □ DocuSign Envelope ID: B20E0236-CE45-41E6-AECF-EF776923E86E California ISO Rel iabil it y Coo r d in at o r Ser v ic es Ag r eemen t The invoice and payment process for the HANA services will be in accordance with Section 19.8 of the CAISO Tariff. The invoice and payment process for other supplemental services will be in accordance with Section 19.9 of the CAISO Tariff.
Invoice and Payment Process. Contractor shall be paid for all Work, Materials, Pass-Through Costs, Fees, Company Taxes and ▇▇▇▇-ups rendered pursuant to this Agreement as follows. In no event shall Contractor commence Work on a Site in the absence of a PO authorizing such Work; and in no event shall Contractor proceed with additional Work on a Site not covered by the original PO for the Site absent written authorization from Company.
(i) By the Effective Date, Contractor shall provide an initial draft of the Rolling Cash Flow Projection (defined below) and supporting assumptions used to arrive at the amounts shown in such draft of the Rolling Cash Flow Projection. Within ten (10) Business Days after the Effective Date, Company will wire an initial payment to Contractor in an amount based on the forecast of compensation to be earned as described below in Sections 12.1(viii) through (xiii) and the factors described in Section 12.4 for the then current month (Month 0) and an Advance Payment (defined below) for the ensuing two months (Months 1 and 2).
(ii) Following the payment of the initial Advance Payment, the process for invoicing and payments described in Sections 12.1 (iii) through (vii) shall be followed by both Parties for the remainder of the Term.
(iii) Commencing on the 15th day of the first calendar month after the Effective Date, and by the 15th day of each month thereafter, the Parties shall hold a meeting (“Compensation Projection Meeting”) attended by Authorized Representatives of the Parties to review and agree upon the projected compensation to be earned by Contractor for each of the ensuing 18 months (“Months 1 – 18”, with the month containing the Compensation Projection Meeting designated as Month 0 in each monthly revision). The projected compensation (“Rolling Cash Flow Projection”) will be based on the then-current Throughput Model and forecast compensation to be earned as described below in Sections 12.1(viii) through (xiii) and the factors described in Section 12.4. If the Rolling Cash Flow Projection forecasts no compensation for the Construction Start Payment Milestone (as defined in Exhibit F) occurring in Months 0 through 2, the amount of the Advance Payment payable by Company to Contractor by the end of Month 0 shall be equal to the projected Contractor’s compensation for Month 2. If the Rolling Cash Flow Projection for the first time forecasts compensation for the Construction Start Payment Milestone (as defined in Exhibit F) occurring in Months 0 through 2,...
Invoice and Payment Process. An invoice from a related incident can be automatically generated.