The Infor On-Premises Software Terms and Conditions are the exhibit under which Infor licenses software that the customer installs and runs itself. The exhibit says that the Agreement “applies to On Premises Software, with modifications as described in this Exhibit”. It also states that Infor does not provide Cloud Services for on-premises software, and that the Service Level Agreement does not apply to it.[1] The current versions are dated November 2023. Infor publishes them for the Americas (AMER), Asia Pacific Japan (APJ), several EMEA countries and Latin America, in local languages as well as English.[3] This article follows the AMER English text and notes where the EMEA English text differs.[2]
Older Infor products were sold under a Software License and Support Agreement (SLSA). Infor’s LN documentation still points readers to the SLSA to find out how an application is licensed.[7] A licence position therefore starts with the customer’s own signed documents, and the terms below are what Infor offers for new on-premises Order Forms.
Editions
The exhibit has no editions. It applies to every product listed as On Premises Software in an Order Form. The Order Form carries the commercial detail: products, locations, user restrictions and any source code grant.[1] The regional versions differ in wording more than in substance. The main differences in the English texts are these:
| Topic | AMER (November 2023) | EMEA (November 2023) |
|---|---|---|
| Copies | Use right “consists of (exhaustive) the right to make a reasonable number of copies”[1] | Licence is “to make a reasonable number of copies of” the Documentation and software[2] |
| Change of location | “upon written notice to Infor”[1] | “upon notice to Infor”[2] |
| Third-party access | Needs “Infor’s prior written consent”[1] | Needs “Infor’s consent”[2] |
| Moral rights in Modifications | Assigned or waived[1] | Not mentioned[2] |
Metrics
The exhibit does not define a metric. It grants use “subject to applicable user restrictions stated in the Order Form”.[1] In practice, Infor’s audit turns usage data into “counts of named or concurrent users”.[4] The products enforce their own licence types: Named User License, Concurrent User License, Server License and others in Solution License Manager.[7] These are explained in Infor LN, M3 and SyteLine user licensing.
Counting / floors
Grant. The licence is “perpetual (subject to right of termination due to breach not cured after 30 day notice), non-exclusive, non-transferable … (without the right to sublease or sublicense)”. It is solely for the internal operations of the customer and its Affiliates.[1] Catalog proof: On-premises licence is perpetual, non-exclusive and non-transferable.
Who may use it. The employees of the customer and its Affiliates are the “Authorized Users”, and the customer is liable for their non-compliance. “Third parties are not permitted access to the On Premises Software or Documentation without Infor’s prior written consent.” This affects outsourcers and consultants.[1] Catalog proof: Third parties need Infor consent to access on-premises software.
User maximum and keys. A security program or code may stop the software from running on another configuration, or “for more than the maximum number of users specified in an Order Form”.[1] M3, for example, validates its licence key at startup and monitors logged-on users continuously. Its default key is valid for ten users.[8] Infor’s FAQ warns that keys are “not adequate in all situations”: it has found cases where users or servers “was not restricted as intended”.[4] Catalog proof: Security code may enforce the Equipment and user maximum; M3 Foundation validates logged-on users against the licence key; Licence keys are not adequate assurance of compliance.
Source code. Where an Order Form grants source code, the customer may make Modifications. However, Infor “will own all Intellectual Property Rights, title and interest in and to the Source Code and all Modifications, even if created without assistance or input from Infor”.[1] Infor also has no Support obligation for software modified other than by Infor through Support.[1] Catalog proof: Infor owns source code Modifications made by the customer.
Adding users. The one-year warranty applies only while the customer is active on Support. It “shall not restart” for Updates or for licensed software whose user restrictions change, “e.g., without limitation, adding users”.[1] Catalog proof: Software warranty does not restart when users are added.
End of the licence. When an Order Form expires or is terminated, the customer must return or destroy all copies and certify this in writing.[1] Catalog proof: Return or destroy software and certify at termination.
Virtualization & partitioning
Use is limited to “Equipment”: customer or Affiliate equipment on which the software can be expected to run, based on the configuration in Infor’s then-current Platform Support Guide or Hardware Recommendation Guide, at the locations in the Order Form.[1] Infor has no Support obligation for software installed on anything other than the Equipment.[1] The exhibit has no processor, core or virtual machine rule. Server-bound products are counted per named server in Solution License Manager.[7] Catalog proof: On-premises use is limited to the Equipment and the Order Form locations.
Cloud / BYOL
The exhibit grants no right to run on-premises software in a hosted or public cloud. A third-party hosting provider would be a third party needing Infor’s consent.[1] When a customer moves to an Infor cloud subscription, Infor may offer Transitional Support for the existing licence for “no longer than 18 months” for a reduced fee. This must be documented in a written agreement, and it does not include upgrades or enhancements.[6] Catalog proof: Transitional Support lasts no more than 18 months.
Programs
Support
Support covers the support helpline, Updates “when and if generally available”, and reasonable efforts to correct deviations from the Documentation. It excludes configuration, installation and implementation.[1] The term begins on the Order Form Date, lasts 12 months, and renews for 12-month periods. It renews unless either party gives written notice of non-renewal “at least 90 days prior” to renewal. Infor notifies the customer of the renewal and the next fee at least 30 days before that notice period. The term “cannot be terminated prior to its expiration date” except as the Agreement says. After 30 business days’ notice, Infor may suspend Support for past-due undisputed fees.[1] If Support lapses, it can be reinstated only with Infor’s written consent and payment of “all Support fees that would have been due during such lapsed period of Support plus a reinstatement charge”.[5] Catalog proof: On-premises Support renews annually unless cancelled 90 days ahead; Support cannot be ended early and may be suspended for unpaid fees; Lapsed Support is reinstated only with back fees and a reinstatement charge.
Maintenance lifecycle
The General Product Lifecycle Policy describes three stages for each on-premises release.[6]
| Stage | Fixes | Price |
|---|---|---|
| Mainstream Maintenance | Priority 1 and 2 fixes, updates, regulatory enhancements; Support Portal and staff | Standard Maintenance pricing |
| Extended Maintenance | Priority 1 only; no regulatory enhancements | Standard pricing “plus 20% premium unless otherwise determined by Infor” |
| Sustaining Maintenance | “Access to pre-existing fixes only” | Standard pricing unless Infor determines otherwise |
Infor typically gives one year’s notice of the end of Mainstream Maintenance. Extended Maintenance premiums are added on top of normal annual adjustments and are non-refundable.[6] The policy says it is not “a contractual document or commitment of any kind”. It does not cover subscription products, and product-specific lifecycle policies prevail over it.[6] Catalog proof: Extended Maintenance costs a 20% premium over standard pricing; Sustaining Maintenance gives access to pre-existing fixes only; Lifecycle Policy excludes subscription products.
Licence audits
Contract right. “Infor may audit the records and systems of Customer to ensure compliance with this Order Form”, under the Agreement’s confidentiality terms. Infor must give at least 10 business days’ written notice. The audit takes place during regular business hours, and Infor may audit “no more than once in any 6 month period”. If the customer is beyond the scope of the licence, it pays “the underpaid license fees therefore and associated fees for Support”. The price is any valid price option in the Order Form for additional usage or, if there is none, “Infor’s then current rates”.[1] The EMEA text is the same.[2] Catalog proof: Infor may audit on 10 business days notice, at most every 6 months; Audit shortfalls are paid at the Order Form price option or current rates.
Process. Infor’s FAQ describes the audit in practice.[4]
- Infor and its licensors and consultants have audited Infor licences since 2001 and have carried out more than 20,000 licence reviews.
- The right to audit “is not related to the continuance of support”, so customers whose Support has expired must still take part.
- The customer completes a License Review Questionnaire of fewer than 20 questions, with input from IT, the business or legal.
- Infor’s audit software logs on to target servers, reports which Infor products it finds, and asks permission to proceed. For most products it then runs for six weeks; for some, only a few hours.
- The data collected “normally includes the products, the user by ID, and the workstation by ID”. From it Infor produces named or concurrent user counts.
- Infor provides the audit at no cost beyond the customer’s help with downloading and installing the software.
Catalog proof: Audit rights continue after Support expires; Audit collects products, users and workstations and produces user counts; Audit software usually runs for six weeks.
Commentary. Read together, the documents mean that the audit measures users by ID and workstation over a period of weeks, while the contract measures against the Order Form’s user restrictions. Before an audit, a licence manager would reconcile active user IDs, shared or generic logins, and Affiliate and third-party users against the Order Form, because third-party access needs Infor’s consent.[1][4] See also software licence audit.
Out of scope
This page does not cover the liability caps in section 8, which limit liability for software to two times the fees paid for it. It does not cover the Agreement’s general terms, which are not published, or product-specific lifecycle dates. Licence terms in Order Forms or SLSAs signed before November 2023 may differ from those described here.