License Reporting Clause Samples
The License Reporting clause requires a licensee to provide regular updates or reports to the licensor regarding the use, distribution, or sales of licensed materials. Typically, this involves submitting periodic statements detailing quantities sold, revenues generated, or other relevant metrics, often accompanied by supporting documentation. This clause ensures transparency and accountability, enabling the licensor to monitor compliance with the license terms and accurately calculate royalties or other payments owed.
License Reporting. Government Integrator shall deliver to MS report information, via the format attached hereto as Exhibit B ("Report Format"), or such other format as MS shall specify from time to time in the future. Report information shall be itemized for each Program and shall be itemized for each Participating Agency under the Program. Such Report is due no later than the fifteenth (15th) day of each calendar month. Each such Report shall be sent to the following addresses: Microsoft Corporation Microsoft Corporation Dept. 551, One Microsoft Way 5335 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇-▇▇▇▇ Suite 600 Attn: Special Agreement Accounting Attn: [*] Federal Contracts Manager Following receipt of each such Report, MS shall invoice Government Integrator and Government Integrator shall be obligated to pay MS the fees set forth in the relevant Program Agreement for each unit indicated on the Report. The Government Integrator's invoice address is identified in each Program Agreement.
License Reporting. No later than on the fifth (5th) Business Day following the end of each quarter of the Term agreed in the Purchase Order, the Licensee shall submit to the Licensor via email to ▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ any changes to licensing (peers, orders, CAs), Organizations (MSPIDs), list of End Users, Nodes consumption, in case of any changes the actual costs will be prorated on the basis of the rates stated below and invoiced accordingly. Such change in usage (change in Organizations (MSPIDs) and Nodes across all environments running on Software can be extracted from each deployed instance of the Software by following the guidelines in the following Link.
License Reporting. No later than on the fifth (5th) Business Day following the end of each quarter of the Term agreed in the Purchase Order, the Licensee shall submit to the Licensor via email to ▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ any changes to licensing (nodes consumption) in case of any changes the actual costs will be prorated on the basis of the rates stated below and invoiced accordingly.
License Reporting. Within 30 days of the end of each Fiscal Year, commencing with the Fiscal Year ending December 31, 2025, a list of all licenses of Holdings and its Subsidiaries as of the last day of such Fiscal Year required (i) to transact with a Sanctioned Person or in a Sanctioned Jurisdiction, or (ii) under applicable export laws (with copies thereof to be delivered upon the request of the Administrative Agent).
License Reporting. Contractor shall provide the State with the following information regarding the State’s Oracle software licenses and other State-paid software licenses installed on the HSEP on a quarterly, or more frequent basis as agreed upon by the parties, as part of Reporting for M&O Services specified in this section:
1. An Inventory of all of State’s software licenses installed in all environments managed within the scope of this Contract.
2. The Inventory shall include:
a. the product name, version, number of licenses and vendor contact information.
b. A list of installed product components.
c. Specification of the characteristics of the physical and/or virtual server on which the licensed software is running including the number of physical or virtual CPU cores and other server characteristics as available to determine or enable a license count that helps satisfy the State’s software license reporting requirements.
d. List of license keys to be sent to State via mutually agreed secure process. Table C – Transition Deliverables includes: (1) the Deliverable Identifier (“Req”) Number, (2) the Requirement Name, and (3) Due Date. • Transition Deliverables are non-Key Deliverables that do require Acceptance by the State. • Transition Deliverables are tied to Core M&O services monthly fee as specified in Attachment B.
3. T01 Lessons Learned document 30 days prior to Contract termination 3.T02 M&O Plan 90 days prior to Contract termination 3.T03 Project Management Plan 90 days prior to Contract termination
License Reporting. For Armory Services that are self-hosted you agree to allow Armory to collect telemetry data for the purposes of identifying the licenses being used. If telemetry data is unavailable, at Armory’s request, but in no case more than once per quarter, You agree to provide detail on the number of Users interacting with the Services and Armory may, at its discretion, require Customer to reduce its usage to its agreed to number of Users or, if Customer’s usage cannot be reduced to the licensed number of Users, charge Customer for any overage at the then market rate, unless a different rate is agreed to by the parties. Any licenses added pursuant to this section shall be coterminous with the remainder of Customer’s licenses and shall be billed on a pro-rata basis. Third party providers. Armory may use Stripe, Inc. and its affiliates as a third party service provider for payment services (e.g., card acceptance, merchant settlement, and related services) (a “Payment Processor”). By making or accepting any payments via the Services, you agree to be bound by Stripe’s Privacy Policy (currently accessible at ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/us/ privacy) and its Terms of Service (currently accessible at ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/ us/terms) and hereby consent and authorize Armory and Stripe to share any information and payment instructions you provide with one or more third parties to the minimum extent required to complete your transactions. By making payments on our Website, you also agree to be bound by Stripe’s services agreement at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/us/legal/ and Stripe’s connect agreement at: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/connect-account/legal. Account and Environment Security Customer Data Your Responsibilities: You are solely responsible for your Customer Data. By importing, storing, or processing Customer Data with the Armory Services, You affirm, represent, and warrant that:
License Reporting. Contractor shall provide the State with the following information regarding the State’s Oracle software licenses and other State-paid software licenses installed on the HSEP on a quarterly, or more frequent basis as agreed upon by the parties, as part of Reporting for M&O Services specified in this section:
1. An Inventory of all of State’s software licenses installed in all environments managed within the scope of this Contract.
2. The Inventory shall include:
a. The product name, version, number of licenses and vendor contact information;
b. A list of installed product components;
c. Oracle Extended Support dates for each component;
d. Specification of the characteristics of the physical and/or virtual server where the licensed software is running, including the number of physical or virtual CPU cores and other server characteristics as available to determine or enable a license count that helps satisfy the State’s software license reporting requirements; and
e. List of license keys to be sent to State via mutually agreed secure process.