I always recommend and it is frequently implemented to put the SoldTo.DisplayName in the Notice field when defining a license model. This way the application can read this data from the license and use it in for example a help/about screen. Example syntax for a license model Notice field for this would be: Sold To {SoldTo.DisplayName} Other common Pre-Defined substitution variables include: Serial Number = {EntitlementLineItem.activationId} (if not already using this for other reason) Also {Entitlement.id} If you are using FlexNet Publisher TS activation including the {Fulfillment.id} can be helpful. Issuer = Hard code company name that is issuing the entitlement and license.   Additional Note: the OP asked about a "comment" for a license file. There is a way to specify  hard coded text to appear at the top of an FNP license file by building it into the VCG, but it does not use the substitution variables. Second additional Note: the OP asked about custom attributes to be added to a license. FNO does allow the creation of custom license attributes that essentially become substitution variables (they're just not pre-defined) that can be used in VENDOR_STRING, NOTICE, etc. See online help section title "Custom Attributes in License Strings". ... View more