Configuration Data
This section defines the Configuration data required to establish your LeaseAccelerator environment. The tabs are found on the LeaseAccelerator Client Information Workbook (CIW).
Download a PDF version of the Client Implementation guide.
Special Considerations:
-
There are 5 tabs that are considered Core. These 5 tabs MUST initially be populated. The 5 tabs are:
Companies
Addresses
People
Geo
Reporting Area.
Once the import has been completed, any non-required field can only be added via the UI.
Several fields on the Configuration tabs contain drop-down boxes to select valid values for these fields. LeaseAccelerator (LA) will reject the imported data file if the values entered are not in the drop-down. Please consult your LAS Implementation Project Manager, or Client Success Manager, if additional values pertain to your organization.
An import is failed when you receive RED errors. These must be fixed to continue the import process. YELLOW errors will not stop the import; however, these must be reviewed to ensure there are no issues downstream.
Companies Tab
The Companies tab defines those companies that are a part of your leasing program. Each company, however, may perform a different role or function. Examples include:
Lessees – the legal party to the agreement leasing the equipment or renting the real estate
Funders – also referred to as lessors: they provide the cash to finance the equipment purchase through a lease agreement
Entity: Organization you consider to be the Lessee (may be different than actual Lessee). An Entity must have a functional currency selected. Entity is the out-of-the-box company role that Functional Currency is tied to. It is possible to use Lessee with a request to Support.
Business Units (BU) – an internal reporting group
Vendors – various other parties such as the equipment manufacturer or supplier, an assignee, or an organization to whom you pay an initial direct cost to or receive a lease incentive from
It is required that data be input into tabs in a top-down manner by order of generality. In other words, if a company is listed as a Parent, it should appear in the tab above, according to the hierarchy.
Company Name |
Parent Name |
Ledger Code |
---|---|---|
Company A |
#### |
|
Company B |
Company A |
#### |
Business Unit A |
Company B |
#### |
Note: State/Province entry field is only allowed for the following Countries: Australia, Brazil, Canada, China, India, Ireland, Italy, Japan, Mexico, and the US. For the US, please use the standard 2-character abbreviation. Click here to view the list of acceptable provinces.
You will see that the worksheet asks for an address for each of these companies. We know that companies have many locations, therefore this address should be the primary mailing location.
The Functional Currency field should be populated for any Entity. You may only have one Functional Currency for a single Entity.
Tips:
In Column I, Country, the US is the first listed Country in the drop-down. Entering anything other than the US will cause an error.
If you enter address information on the Companies tab, the minimum required fields for system import are City and Country.
If one of your Company Role Types (Lessee, Entity, BU, etc.) is a part of your General Ledger String, therefore one of the segments, then an associated Ledger Code in column N is required for accurate reporting. You only need to populate this field for those participants that are part of your GL String. A Company may only have one Ledger Code associated with it, so if it listed multiple times because of multiple Company Role Types, ensure it has the same Ledger Code each time.
While Addresses and Contact information are not required fields for system import, we do recommend that you provide this detail, particularly for your Funders and Vendors, as this will allow you to easily access this information as needed for communication with Funders and Vendors regarding your leases with them.
A Company can only have one parent and it must be the same for every mention or line item that is used for that Company.
A Company can also only have one address listed so if that company is listed more than once with different role types, ensure that the address used (if any) is identical each time the company is listed.
Tab: |
Companies |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Company Role Type |
This is a description of the function that this company plays within your leasing program. |
See Data Validation List |
Drop-down |
Y |
Y |
B |
Company Name |
Name of the entity which you want to use within the system. This may or may not be the official legal name of the entity. This may be a subsidiary of a larger organization. |
Alphanumeric (1000) |
Y |
Y |
|
C |
Parent Company Name |
The highest organization within a company’s legal structure. |
Alphanumeric (1000) |
N |
N |
|
D |
URL |
Website Address |
Must be in standard format |
Alphanumeric (1000) |
N |
N |
E |
Address Line 1 |
Street Address |
Alphanumeric (1000) |
N |
N |
|
F |
Address Line 2 |
Additional address information such as floor or suite. |
Alphanumeric (1000) |
N |
N |
|
G |
City |
City used by postal service. This may not be the more common name used in conversation. |
Alphanumeric (1000) |
N |
N |
|
H |
State Province |
Postal Abbreviation for acceptable Countries. See Country Province List in Valid Values Glossary. |
See Data Validation List |
Alphanumeric (1000) |
N |
N |
I |
Country |
Name |
See Data Validation List |
Drop-down |
N |
N |
J |
Postal Code |
Zip Code or other Postal code |
Alphanumeric (1000) |
N |
N |
|
K |
Contact Name |
First Name, Last Name of Primary Contact |
Alphanumeric (1000) |
N |
N |
|
L |
Phone |
Telephone number |
Valid Format |
Numeric (1000) |
N |
N |
M |
Email address for POC |
Valid Format contains @xxx |
Alphanumeric (1000) |
N |
N |
|
N |
Ledger Code |
The code or “value” per Chart of Accounts or accounting system associated with the participant company, if appropriate. |
Alphanumeric (1000) |
N |
Y |
|
O |
Functional Currency |
Functional Currency is the currency which is used for accounting purposes. This currency is common for all contracts for the specified company role. The functional currency causes a remeasurement of accounting transactions from the local or transaction currency so that all contracts are accounted for using the same currency. Each Entity may only have 1 Functional Currency. Note: When configuring an Entity with Functional Currency, you must enter and save at least one Foreign Exchange rate for that currency to ensure proper reporting. |
See Data Validation List |
Drop-down |
N |
Y |
Addresses Tab
Addresses are specific workplaces in your organization where employees work and/or equipment may be physically located or shipped to. This would also include the physical location of any leased Real Estate. They are typically associated with a Lessee, Entity, or Business Unit. (There may be a 1: n relationship because companies may have multiple teams “sitting” at a single location.) Please see notes above regarding specific validation reminders pertaining to the address fields.
Please note that if clients want to utilize the Facility Code field on the PIW, they must ensure that an associated Facility Code is entered on this tab when importing the ShipTo addresses. If each address has an associated Facility Code, those Facility Codes may be used on the PIW in lieu of the ShipTo Address fields.
Tab: |
Addresses |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Address Role Type |
The function that this location plays within your leasing program. |
See Data Validation List below |
Drop-down |
Y |
Y |
B |
Company Name |
Name of the location used as reference within your company where assets are located. |
Alphanumeric (1000) |
Y |
Y |
|
C |
Address Line 1 |
Street Address |
Alphanumeric (1000) |
N |
N |
|
D |
Address Line 2 |
Additional address information such as floor or suite. |
Alphanumeric (1000) |
N |
N |
|
E |
City |
City used by postal service. This may not be the more common name used in conversation. |
Alphanumeric (1000) |
Y |
N |
|
F |
State Province |
Postal Abbreviation for acceptable Countries. See Country Province List in Valid Values Glossary. |
See Data Validation List |
Alphanumeric (1000) |
N |
N |
G |
Country |
Postal Abbreviation |
See Data Validation List |
Drop-down |
Y |
N |
H |
Postal Code |
Zip Code or other Postal code |
Alphanumeric (1000) |
N |
N |
|
I |
Facility Code |
Facility Code (ShipTo Key) is a client code associated with a specific ShipTo Address. Using a Facility Code on the PIW eliminates the need to enter any values in the ShipTo Address fields in the PIW only. |
Unique value, code cannot exist in the system already. |
Alphanumeric (100) |
N |
N |
J |
Ledger Code |
The “value” used by your accounting system to identify the work location. Typically, this is one of many portions of an overall General Ledger string |
Alphanumeric (1000) |
N |
Y |
People Tab
Many people participate in your leasing program and have different roles. These people may or may not be users of the system. LeaseAccelerator captures these people so that they can receive notifications or other information important to their function. Examples of the roles that people may play and therefore need to be configured in the system are:
Asset Owners – employees who have fiduciary responsibility for the maintenance and use of the assets. These employees are typically management level and are financially responsible for the equipment.
Asset Users – employees who have custodial responsibility for the leased assets. These employees may be management or staff level. These employees’ work locations are typically at the equipment’s physical location or in the same area.
Order Administrators – employees who have “procurement” responsibility for the leased assets, shepherding the administrative process in your organization to finance the acquisition of equipment and securing its delivery to the asset user.
Analysts – employees responsible for generating the Lease vs. Buy.
Treasury Approvers – employees typically responsible for approving the lease transaction and may be the responsible party signing the lease documents. These employees are typically management or executive level and are an escalation step for notifications regarding End-of-Term.
Sourcing contacts – employees responsible for initiating and creating an RFP, reviewing the Proposals and awarding to a Funder/Lessor.
Accounting Analysts – staff accountant typically responsible for compiling and verifying accounting data associated with a lease, recording journal entries, analyzing monthly results and preparing reconciliations.
Accounting Approvers – supervisors or managers typically responsible for reviewing and approving accounting data associated with a lease and approving results.
Note: that a person may be listed multiple times if their role types are different, but the company and address information for that person must be identical. Do not list a person multiple times with the same role type and different companies. This tab is used to create a record for that person and as such they can only have one Company associated with them, along with one address.
CORRECT | INCORRECT |
|||||
---|---|---|---|---|---|---|
Full Name |
Person Role Type |
Company Name |
Full Name |
Person Role Type |
Company Name |
|
John Smith |
Analyst |
Acme, Inc. |
John Smith |
Analyst |
Acme, Inc. |
|
John Smith |
Asset Owner |
Acme, Inc. |
John Smith |
Analyst |
Acme International |
|
Gloria Sanchez |
Asset Owner |
Acme, Inc. |
Gloria Sanchez |
Asset Owner |
Acme, Inc. |
Tab: |
People |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Full Name |
First name, Last name |
Alphanumeric (1000) |
Y |
N |
|
B |
Person Role Type |
The function that a person plays within your leasing program. |
See Data Validation List |
Drop-down |
Y |
N |
C |
Company Name |
Employee’s Entity or Business Unit (typically governed by your company’s internal method to commonly reference the organization that an employee is part of). |
Must exactly match a value on Companies Tab where Company Role Type = Lessee, Entity, Funder, Vendor, or BU. |
Alphanumeric (1000) |
Y |
N |
D |
Address Line 1 |
Street Address |
If blank, data from corresponding Company Name on Companies Tab will be applied. |
Alphanumeric (1000) |
N |
N |
E |
Address Line 2 |
Additional address information such as floor or suite. |
If blank, data from corresponding Company Name on Companies Tab will be applied. |
Alphanumeric (1000) |
N |
N |
F |
City |
City used by postal service. This may not be the more common name used in conversation. |
If blank, data from corresponding Company Name on Companies Tab will be applied. Required for LeaseAccelerator Users. Defined on LA Users Tab. |
Alphanumeric (1000) |
Y |
N |
G |
State Province |
Postal Abbreviation for acceptable Countries. See Country Province List in Valid Values Glossary. |
If blank, data from corresponding Company Name on Companies Tab will be applied. |
Alphanumeric (1000) |
N |
N |
H |
Country |
Postal Abbreviation |
If blank, data from corresponding Company Name on Companies Tab will be applied. Required for LeaseAccelerator Users. Defined on LA Users Tab. |
Drop-down |
Y |
N |
I |
Postal Code |
Zip Code or other Postal code |
If blank, data from corresponding Company Name on Companies Tab will be applied. |
Alphanumeric (1000) |
N |
N |
J |
Phone |
Telephone number |
Numeric (1000) |
N |
N |
|
K |
Email* |
Email address for POC |
Valid email address format. Must include @xxx. |
Alphanumeric (1000) |
Y |
N |
L |
Is User* |
Field to define whether this person is a defined user within LA. By selecting Yes, this person will be provisioned as a user upon import and their username will be everything before the ‘@’ sign of their email address. |
Yes or No |
Drop-down |
Y |
N |
M |
Is SSO User |
Field to define if user will be created as an SSO user and therefore will not be able to login through LA UI but will be able to access the system through custom application (SSO Console). |
Yes or No |
Drop-down |
N |
N |
N |
External UID |
Unique ID used to authenticate the SSO user. (Typically, the email ID but can be anything.) |
If value of “Is SSO User” field is “Yes”, then this field must be populated. |
Alphanumeric (50) |
N |
N |
* User Ids are automatically created using the email address listed for the person listed on each row in the CIW.
Note: The system creates the User Id equal to the values before the ‘@’ in the email address. These values must be unique. Therefore, if a company is using generic mailboxes distribution lists that have a different email suffix or people, with the same name, but different company email suffix; the automated User Id creation process will fail.
Correct Incorrect
DistroList1@company1.com |
DistroList@company1.com |
DistroList2@company1.com |
DistroList@company2.com |
DistroList3@company2.com |
DistroList@company3.com |
John.James@company1.com |
|
John.James@company2.com |
Geo Tab
Geo is the country that determines the accounting and tax rules that apply to a lease. This is typically the same country as the physical location of the equipment or real estate. However, when various participants and assets are in different countries, this field may not be obvious.
Data is collected using the Geo tab. However, to import the data, please use the Companies tab input where:
Company Role Type = Geo
Company Name = Geo Name
Ledger Code = Ledger Code
Note: Geos cannot have a parent/child relationship within the Geo Role Type; however, Geos can roll up to Reporting Areas. In this case, The Reporting Areas should be listed above the Geos on the Companies tab.
Tab: |
Geos |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Geo Name |
Name of the country that governs the accounting and tax rules for a transaction. |
See Data Validation List below |
Drop-down |
Y |
Y |
B |
Ledger Code |
The “value” used by your accounting system to identify the location or geography. Typically, this is one of many portions of an overall General Ledger string. |
Alphanumeric (1000) |
N |
Y |
Reporting Area Tab
Reporting Area is used for internal management reporting to group various other organizational divisions together. Originally designed to group geographical locations or regions together, it may be used for other purposes such as lines of business. Reporting Areas may have a hierarchical relationship where one Reporting Area rolls into another. It is suggested that data be input into tabs in a top-down manner by order of generality. In other words, the higher the Reporting Area is in the hierarchy, the earlier it should be entered into the import table. Each Reporting Area used as a rollup must also have a unique row on the table with the Reporting Area Rollup Field blank.
Example: You have 4 countries (US, Canada, Argentina, and Brazil), a hierarchy that groups the countries US with Canada in the North America Area and Argentina with Brazil in the South America Area, and a grand total grouping North and South America in the Americas Area. The following rows would be required on the Companies tab:
Company Role Type |
Company Name |
Parent Name |
---|---|---|
Reporting Area |
Americas |
|
Reporting Area |
North America |
Americas |
Reporting Area |
South America |
Americas |
Geo |
US |
North America |
Geo |
Canada |
North America |
Geo |
Argentina |
South America |
Geo |
Brazil |
South America |
Data is collected using the attached Reporting Area tab. However, to import the data, please use the Companies tab input where:
Company Role Type = Reporting Area
Company Name = Reporting Area Name
Parent Company Name = Reporting Area Rollup
Ledger Code = Ledger Code
Tab: |
Reporting Area |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Reporting Area |
Grouping of Geos for aggregated reporting purposes. |
Alphanumeric (1000) |
Y |
Y |
|
B |
Reporting Area Rollup |
A grouping of Reporting Areas for aggregated reporting. |
Alphanumeric (1000) |
N |
N |
|
C |
Ledger Code |
The “value” used by your accounting system to identify the Reporting Area. This may be one of many portions of an overall General Ledger string. |
Alphanumeric (1000) |
N |
Y |
Cost Centers Tab
Cost Centers (CC) are departments within your organization which typically have a budget. Employees, Revenue, Expenses, Assets, Liabilities, and other financial information is recorded in the CC in the General Ledger.
Note: Cost Centers are required when entering a lease. If your organization does not use Cost Centers, then a default of TBD should be used. This Cost Center is automatically created when a new environment is created.
Tab: |
Cost Center |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Cost Center |
The “value” used by your accounting system to identify the cost center. Typically, this is one of many portions of an overall General Ledger (GL) string. |
Alphanumeric (100) |
Y |
Y |
|
B |
Description |
Name used within GL |
Alphanumeric (300) |
N |
N |
Foreign Exchange Rates Tab
FX (or Currency Translation Factors) are published indices used to convert financial data from one currency to another. These factors are critical to accounting, reporting, and marketplace functions so that accurate comparisons can be made between Geos (countries).
Foreign Currency Reporting: This feature enables the ability to report accounting information using either the local transaction, functional or reporting currency. This feature is available to all clients with accounting but requires client configuration actions.
There are three potential currencies involved in the accounting flow:
Contract (Local) Currency: This is the currency that a contract is denominated in.
Functional Currency: This is the currency for which a business entity creates its accounting records.
Reporting Currency: This is the currency that a parent company reports its financial statements in.
There are two processes typically involved in converting transactions or balances from one currency to another:
Remeasurement: The process of converting a transaction from its local currency to its functional currency. This calculation is done at the transaction level, meaning it is a recalculation that must be done for each individual journal entry. This activity results in a Gain/Loss on Currency Translation, which is part of Net Income.
Translation: The process used for converting the functional currency financial statements of an entity into the reporting currency used by the parent company. This is required to consolidate the financial statements of entities with different functional currencies into a single currency. This activity results in an adjustment to equity which is called Other Comprehensive Income (OIC).
Each of these processes uses the Current Fx Exchange rate (or Current Rate); however, the applicable Current Rate differs, based on the type of a conversion (remeasurement or translation) and the type of account (Balance Sheet or Income Statement).
The lease accounting standard is consistent with the above. ASC842 20-55-10 states that the right of use asset is a non-monetary asset while the lease liability is a monetary liability. Therefore, in accordance with Subtopic 830-10 on foreign currency matters, when accounting for a lease that is denominated in a foreign currency, if remeasurement into the lessee’s functional currency is required, the lease liability is REMEASURED using the current exchange rate (Monetary=spot rate at fiscal month end) while the right of use asset is remeasured using the exchange rate as of the commencement date (Non-Monetary=spot rate at original transaction date).
For the income statement, calculating the weighted average rate may not be practical or may not result in a material difference as compared to using the spot rate at the balance sheet date. Therefore, clients often set an internal practice defining the average rate. This practice impacts a client’s financial statements in all line items, so LeaseAccelerator must be able to mirror those practices for the functional remeasurement and reporting currency translation.
Based on discussions with many clients, we believe the most prevalent methods for calculating the average rate will be:
Current Fiscal Month End Fx Rate
Prior Fiscal Month End Fx Rate
Simple Average Fx Rate
Weighted Avg Month End Fx Rate
LeaseAccelerator determines the Current Month Average Rate from existing client Fx data, EXCEPT, if the client chooses the Weighted Avg Month End Fx Rate method. This method requires information from the client. LeaseAccelerator can’t calculate this value.
As part of the implementation, it is suggested that you import all historical currency translation factors that impact your leases throughout their lives. If a specific rate is not imported, journal entries before the first imported factor will not be reportable or included in amounts reported in functional or reporting currency.
You may update currency translation factors as often as you like using either the bulk import mechanism or the online settings feature. Since factors may change daily, we suggest that you determine the most appropriate frequency for updates with your Accounting and Finance teams.
LeaseAccelerator has two types of rates that can be imported: 1) Spot and 2) Weighted Average. The Weighted Average Month End rate is set through one of four calculations based on a configuration setting:
Spot rate for the last day of the prior fiscal period.
Spot rate for the last day of the current fiscal period.
Spot rate for the last day of the prior fiscal period plus Spot rate for the last day of the current fiscal period divided by 2.
Weighted Average rate for the last day of the fiscal period.
The Fx Rates are for both Balance Sheet and P&L. LeaseAccelerator does not translate from a non-USD to a non-USD rate. All conversions are based on USD to non-USD only. We do support non-USD to non-USD translation by using a 2-step process: 1st non-USD to USD then USD to 2nd non-USD rate.
Note: Some published exchange rates may need to be converted to the standard “From FX to USD” equivalent multiplier by using the inverse of the published index. Please consult with your internal Treasury teams to verify the values provided.
Tab: |
Fx Rates |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Effective Date |
Date which the multiplier is active (as of the beginning of the day). |
MM/DD/YYYY |
Y |
Y |
|
B |
From Currency |
Name of local currency |
See Date List Validation Below |
Drop-down |
Y |
Y |
C |
To Currency |
Name of currency translation for accounting or reporting purposes. |
See Date List Validation Below |
Drop-down |
Y |
Y |
D |
Rate |
Factor to multiply the From Currency against to arrive at the To Currency. Multipliers are published indices. This includes inverse rates calculated by the system. |
Numeric (Total Digits = 19, Precision = 12 to the right of the decimal) |
Y |
Y |
|
E |
Rate Type |
Type of Rate being imported, either Spot or Weighted Average |
Spot or Weighted Average |
Drop-down |
Y |
Y |
F |
Source |
The source of the currency translation factor. |
Alphanumeric (1000) |
N |
N |
For more information on Foreign Currency Reporting features, please refer to the 17R2.1 Concept of Operations - Fx.
LeaseAccelerator Users Tab
This section identifies the employees who will be users of LeaseAccelerator (LA), the access level they will be granted, the role that they will perform, and the entities they will have access to.
Access level within LA determines the way an individual will use the system (i.e. the rights and privileges granted).
Roles (Can Act As) within LA is an identifier that is assigned for To-Do actions (workflow).
Scope of Access and Scope of Ledgers define the data that a user has visibility to. For example, this can be limited to certain Lessees, Business Units, and/or GEOs.
Tab: |
LA Users |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Full Name |
First and last name |
Alphanumeric (1000) |
Y |
N |
|
B |
Company Name |
Employee’s Entity or Business Unit (typically governed by your company’s internal method to commonly reference the organization that an employee is part of). |
Must exactly match value on Companies Tab where Company Role Type = Lessee, Entity, BU |
Alphanumeric (1000) |
Y |
N |
C |
Address Line 1 |
Street Address |
If blank, data from corresponding Company Name on Companies Tab will be applied |
Alphanumeric (1000) |
N |
N |
D |
Address Line 2 |
Additional address information such as floor or suite. |
If blank, data from corresponding Company Name on Companies Tab will be applied |
Alphanumeric (1000) |
N |
N |
E |
City |
City used by postal service. This may not be the more common name used in conversation. |
If blank, data from corresponding Company Name on Companies Tab will be applied |
Alphanumeric (1000) |
Y |
N |
F |
State or Province |
Postal Abbreviation for acceptable Countries. See Country Province List in Valid Values Glossary. |
If blank, data from corresponding Company Name on Companies Tab will be applied |
Alphanumeric (1000) |
N |
N |
G |
Country |
Postal Abbreviation |
See Data Validation List Below |
Drop-down |
Y |
N |
H |
Postal Code |
Zip Code or other Postal code |
If blank, data from corresponding Company Name on Companies Tab will be applied |
Alphanumeric (1000) |
N |
N |
I |
Phone |
Telephone number |
Numeric (1000) |
N |
N |
|
J |
Email address for POC |
Must be standard format |
Alphanumeric (1000) |
Y |
N |
|
K |
Title |
Title |
Alphanumeric (1000) |
N |
N |
|
L |
Access Level |
The grouping which identifies the extent of functionality that a user is given. |
See Data Validation List Below |
Drop-down |
Y |
N |
M |
Role(s) |
The functionality this user will perform within LA. This is a standard list of roles within LA that drives the feature/function and reports which are available. |
See Data Validation List Below |
Drop-down |
Y |
N |
N |
Scope of Access |
Entities or Business Units and Geos which user will have access to. |
List with “,” delimiter. Values must match values on Companies Tab and Geo |
Alphanumeric (50) |
Y |
N |
Notifications Tab
The Notifications tab in the CIW identifies the criteria for each notification configured to drive the automated email notifications on a portfolio level. By using the global notifications tab in Settings, a client can set up notifications to be sent out for every lease schedule entered into the system after configuration by default. If specific notifications are required per lease schedule, clients may override the global notifications by entering schedule notifications either using the PIW or in the UI in Deal Summary once a deal has been booked.
When configuring Notifications, clients may:
Attach documents that exist within LeaseAccelerator to a notification
Specify whether the attachment is sent on ONLY the first notification or ALL subsequent notifications
Specify which User Roles will receive the attachment on the notification
Global Notifications are applicable to schedules after a notification has been configured. They will not apply to any existing leases in the system prior to the configuration of that notification. For more information on Notifications and Templates, please refer to the Product Feature Advisory for Global Notifications Settings.
Tab: |
Notifications |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Number Days |
Number of days prior to a notification due date that an email notification should be sent. |
Number ≥ 0 |
Numeric (6) |
Y |
N |
B |
Timing |
Indicator defining whether the number of days is counted before or after the specified Milestone for when the notification email request should be sent. |
See Data Validation Below |
Drop-down |
Y |
N |
C |
Milestone |
The contractual milestone that drives the notification due date. |
See Data Validation Below |
Drop-down |
Y |
N |
D |
Frequency |
How often the notification should be sent. |
See Data Validation Below |
Drop-down |
Y |
N |
E |
Recurring |
Indicator to determine how often a recurring notification should be sent. Used in conjunction with ‘Units’. |
Number ≥ 0 |
Numeric (6) |
N |
N |
F |
Units |
Unit of measure determining how many times and for how long the recurring notification should be sent. |
See Data Validation Below |
Drop-down |
N |
N |
G |
Until Days |
Number of units that the recurring notification should be sent. This sets an end date for these notifications. |
Number ≥ 0 |
Numeric (6) |
N |
N |
H |
Send To |
This is the Lessee Role that the notification email is sent to. |
See Data Validation Below, may enter multiple roles |
Alphanumeric (1000) |
N |
N |
I |
Template Name |
Name of template to be sent. This is required for any EOT Notification to function. |
Must exactly match Template Name on Configuration Tab: EOT Templates |
Alphanumeric (1000) |
Y |
N |
J |
Action Required Days |
Number of days that user must perform action. |
Number ≥ 0 |
Numeric (6) |
N |
N |
K |
Consequences |
Client-specified information to the recipient of the notification. |
Alphanumeric (1000) |
N |
N |
|
L |
Enqueue |
Workflow event to be added |
See Data Validation Below |
Drop-down |
N |
N |
M |
Enqueue To |
User role that workflow event is set to. |
See Data Validation Below |
Drop-down |
N |
N |
N |
Message |
Detail text to be included in email notifications. |
Alphanumeric (1000) |
N |
N |
|
O |
Enqueue Event Frequency |
Option to create a new to do for every notification sent or create the new to do once regardless of how many notifications are sent |
See Data Validation Below |
Drop-down |
N |
N |
Economic Life Tab
The Economic Life is a critical attribute for each Product Category. This tab defines the key configuration elements associated with each product category, so you will see that it is pre-populated with the list.
For each product category (or for those that your company anticipates leasing) you will need to insert the corresponding factor. The primary factor is the economic life, which is the value assigned to a product category that signifies the useful life of the leased equipment. This value is used in lease classification testing.
Note: LeaseAccelerator may sometimes refer to Product Category by Asset Class or Asset Type in various documents.
Tab: |
Economic Life |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Product Category |
A predefined list of asset categories. No INPUT required. |
Pre-populated List |
Y |
Y |
|
B |
Economic Life (Months) |
The expected useful life of the assets in the category. |
Number >0; Populate the value for the corresponding Economic Life ONLY for those categories that are used by your company. Leave all others BLANK. |
Numeric (6) |
Y |
Y |
C |
Default EOT Treatment |
The end of term option to be used to record a lease in the absence of a defined EOT Recordation. |
See Data Validation List Below |
Drop-down |
Y |
Y |
D |
Ledger Code |
The “value” used by your accounting system to identify the product category. This may be one of many portions of an overall General Ledger string. |
Alphanumeric (1000) |
N |
Y |
|
E |
Lessee |
Indicates companies to which economic life will apply. ‘All’ is a valid response. |
All is an acceptable value. |
Alphanumeric (1000) |
Y |
N |
F |
Country |
Required for use in LvB Analysis |
See Data Validation List Below. You should only indicate countries you’ve configured as Geos. |
Drop-down |
Y |
N |
G |
Default Lease Component Treatment |
Identification of Lease Component or Non-Lease Component for a given product category or asset type. Non-lease Component means product category will have non-lease treatment in LeaseAccelerator. This is required for accounting. |
See Data Validation List Below. |
Drop-down |
Y |
Y |
The process to update Economic Life in the UI is:
Step |
Action |
---|---|
1 |
Go to Settings by clicking the gear icon in the top-right corner and selecting Settings. |
2 |
Select the Asset Types tile. |
3 |
Check the appropriate box, under Product Categories. Once selected, Default Lease Component Treatment, Default EOT Treatment, and Ledger Code are now enabled. |
4 |
Set the Default Lease Component Treatment by Product Category (not by Lessee). You may indicate multiple Product Categories, if needed. Click Update. |
5 |
Next, set the Default EOT Treatment, Ledger Code, Default Economic Life, and Amortization Term, by selecting a single Product Category and applicable Lessees. Best practice is to select the Parent Lessee only (children will inherit the settings of the parent). Click Update. |
6 |
Lastly, check the appropriate Geo or Country, to set the Depreciation Methods. Best practice is to ONLY select countries that you have configured as Geos during the Companies import. Click Update. |
Depreciation Tab
The Depreciation configuration data defines the methodology and useful lives for each type of asset that you may lease. Depreciation drives critical calculations in your lease versus buy analysis. Also, it sets the method to be used in determining the depreciation expense of your leased assets where an automatic transfer of ownership exists.
Note: Each country (Geo) that you do business in must have unique entries on the Depreciation table so that the calculations can be aligned appropriately with the tax rate information entered on the Tax Rate table. It is inappropriate to select all countries when setting your Depreciation Methods. You should only indicate countries you have configured as Geos.
Tab: |
Depreciation |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Product Category |
A predefined list of asset categories. No INPUT required. |
Pre-populated List |
Y |
Y |
|
B |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
Must exactly match value from Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
Y |
C |
Geo |
The country that determines the accounting and tax rules that apply to a transaction. Geo Name corresponding to an entry on the Geo Tab. |
See Data Validation List Below |
Drop-down |
Y |
Y |
D |
Book Depreciation Method (Accounting) |
The accounting methodology used to calculate depreciation expense for financial accounting purposes. |
See Data Validation List Below |
Drop-down |
Y |
Y |
E |
Tax Depreciation Method |
The accounting methodology used to calculate depreciation expense for tax accounting purposes. This is required for Lease versus Buy Analysis. |
See Data Validation List Below |
Drop-down |
Y |
N |
F |
Amortization Term (months) |
The depreciable period for financial accounting purposes if different from the economic life. This term is used to define the depreciable period for when a buyout or change of ownership is expected to occur. |
Number >0 |
Numeric (5) |
N |
N |
Lessee Rates Tab
Lessee Rates include 3 types of rates used for different purposes in LeaseAccelerator.
The IBR represents the interest rate at which your company could borrow additional funds to purchase the leased equipment under the same terms and conditions. It is typically defined by your Treasury and Accounting teams. The IBR is critical in the Lease Classification Process and the detail accounting calculations for valuing the leased asset and associated lease liability in accordance with the standards.
Debt Rate represents the rate at which you could borrow funds through a loan. It may or may not equate to the IBR (as defined by the accounting standard). LeaseAccelerator uses this rate in the lease versus buy analysis.
-
Equity Rate represents the return on investment which could be earned by investing the funds. LeaseAccelerator uses this rate in the lease versus buy analysis.
Note: Rates may be configured for any term but the CIW contains a Drop-down with the most common lease terms. If you have rates for terms not listed in the Drop-down, please let your Implementation Manager or Support know and they can facilitate the configuration. The UI will reflect any terms that a client requests to be configured to enable future maintenance of these terms. Also please note that it is NOT acceptable to put ALL in the Terms field in the CIW. LeaseAccelerator does interpolate rates so if you do not want to provide rates for every possible term, the system will calculate the right term by using the next lowest and highest rate in the interpolation formula. For that reason, it is recommended to have at least a 1-month rate and a rate for the longest lease term in your portfolio.
Tab: |
Lessee Rates |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
This must exactly match value on Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
Y |
B |
Geo |
GEO Name corresponding to an entry on the GEO Table. Companies may have a single IBR or an individual IBR based on the combination of Country, Term, Asset Type, etc. |
See Data Validation List Below |
Drop-down |
Y |
Y |
C |
Term (Months) |
Reference number of months the IBR is typically associated with. Companies may have a single IBR or an individual IBR based on the combination of Country, Term, Asset Type, etc. |
See Data Validation List Below but LA allows any term if not listed in Validation. |
Drop-down/ Freeform for adding a term |
Y |
N |
D |
Rate Type |
Defines the type of rate |
See Data Validation List Below |
Drop-down |
Y |
Y |
E |
Rate |
The value |
Number where rate is expressed as a Percent ##.### (For example, 3.2 not 0.032) Do not include percent sign in field. |
IBR: Numeric (Total Digits = 9, Precision = 6 to the right of the decimal) Debt/Equity: Numberic (Total Digits = 8, Precision = 6 to the right of the decimal) |
Y |
Y |
F |
Effective Date |
Date at which the multiplier is active (as of the beginning of the day). |
MM/DD/YYYY |
Y |
Y |
LvB Settings Tab
The LvB Net Present Value Settings are used when performing a Lease vs. Buy Analysis. These settings are critical for performing a Lease vs. Buy Analysis. Please work with your Implementation Manager to configure these settings. Each Lessee should be listed on the tab with each of the seven items and the Rate Type that should be used in that calculation.
Tab: |
LvB Settings |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
This must exactly match value on Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
Y |
B |
Rate Type |
Specify type of rate used for each Item. |
See Data Validation List Below |
Drop-down |
Y |
Y |
C |
Item |
A predefined list of categories. No INPUT required. |
Numeric (4) |
N |
N |
|
D |
Definition |
A predefined list of categories. No INPUT required. |
See Data Validation List Below |
Drop-down |
Y |
Y |
Salvage Value Tab
Salvage Value is associated with a Product Category. This information is required for the Lease vs. Buy Analysis. To properly configure the Salvage Value, LeaseAccelerator will need to know the associated Lessee, Geo, Term, Percentage, and Effective Date. Salvage Value is used in determining the Depreciable period for the Buy side of the Lease vs Buy. It has no bearing on the Lease side of the analysis. This tab is not importable, and is not needed unless you want default values in the Lease vs Buy Analysis to auto-populate.
Tab: |
Salvage Value |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Product Category |
Asset Type |
See Data Validation List Below |
Drop-down |
Y |
N |
B |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
This must exactly match value on Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
N |
C |
Geo |
GEO Name corresponding to an entry on the GEO Table. Companies may have a single IBR or an individual IBR based on the combination of Country, Term, Asset Type, etc. |
See Data Validation List Below |
Drop-down |
Y |
N |
D |
Term (Months) |
Reference number of months the Salvage Value is typically associated with. The duration of the lease in the Lease vs. Buy Analysis. |
See Data Validation List Below but LA allows any term if not listed in Validation. |
Drop-down |
Y |
N |
E |
Salvage Value |
The estimated resale value of an asset at the end of its useful life. Salvage Value is subtracted from the cost of a fixed asset to determine the amount of the asset cost that will be depreciated. Thus, salvage value is used as a component of the depreciation calculation. |
Number where rate is expressed as a Percent ##.### (For example, 50.00 not 0.5000) Do not include percent sign in field. |
Numeric (Total Digits = 5, Precision = 2 to the right of the decimal) |
Y |
N |
F |
Effective Date |
Date at which the multiplier is active (as of the beginning of the day). |
MM/DD/YYYY |
Y |
N |
Policy Thresholds Tab
The Policy Thresholds are used in the Lease Classification Engine as parameters for specific tests as outlined in the accounting standards. These thresholds are important in that they allow clients to define quantitative metrics to use where the accounting standards allow for judgment, but also require consistency in the actual application of the thresholds through the organization.
The key judgments in the Lease Classification Process are:
What lease term constitutes the majority of the economic life? (ASC 840 prescribes 75%)
What % of the PV of Lease Payments versus FMV constitutes substantially all of the Fair Market Value? (ASC840 prescribes 90%)
What % of the PV of total cash stream of all payments including the Buyout Option defines when a Bargain exists. (ASC840) This is an economic metric to standardize the evaluation across any contract structure for the same type of asset. For example, a contract may have very low recurring payments but a higher balloon payment to Purchase the asset. Another contract may have high recurring payments with a very low buyout payment. Each may constitute a “bargain” to purchase the asset, but a common metric must be used to evaluate the overall economic incentive to buy the asset, not just the nominal buyout price. LeaseAccelerator measures this using the PV of the total payment stream.
What % of the PV of total cash stream of all payments including the Buyout Option defines when it is reasonably certain that the Buyout or Purchase Option will be exercised. (ASC842)
Tab: |
Policy Thresholds |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Product Category |
A predefined list of asset categories. No INPUT required. |
Pre-populated List |
Y |
Y |
|
B |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
Must exactly match value from Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
Y |
C |
Geo |
The country that determines the accounting and tax rules that apply to a transaction. |
See Data Validation List Below |
Drop-down |
N |
N |
D |
Majority Economic Life Threshold |
Cutoff value used in lease classification test. 75% in ASC840. |
Number >0; Enter % as a number xx.xx (for example 82.5 not 0.825) Do not include percent sign. |
Numeric (Total Digits = 10, Precision = 6 to the right of the decimal) |
Y |
Y |
E |
PV Substantially All Threshold |
Cutoff value used in lease classification test. 90% in ASC840. |
Number >0; Enter % as a number xx.xx (for example 82.5 not 0.825) Do not include percent sign. |
Numeric (Total Digits =10, Precision = 6 to the right of the decimal) |
Y |
Y |
F |
Bargain Purchase Option Threshold |
Point at which a client determines that the overall economics of the lease make it reasonably certain that the buyout price is a bargain and will therefore be exercised (this is an ASC840 classification test). |
Number >0; Enter % as a number xx.xx (for example 82.5 not 0.825) Do not include percent sign. |
Numeric (Total Digits = 10, Precision = 6 to the right of the decimal) |
N |
Y |
G |
Likely Purchase Option Threshold |
Point at which a client determines that the overall economics of the lease make it reasonably certain that the buyout option will be exercised. |
Number >0; Enter % as a number xx.xx (for example 82.5 not 0.825) Do not include percent sign. |
Numeric (Total Digits = 10, Precision = 6 to the right of the decimal) |
N |
Y |
H |
Materiality Threshold Basis |
The metric used to determine whether a lease is material or not. |
See Validation List Below |
Drop-down |
N |
Y |
I |
Materiality Threshold Amount |
The cutoff point (or maximum value) of the Materiality Threshold Basis where a schedule would be determined to have a classification of ‘Operating – Materiality’. Leases with a value below the threshold amount are de-scoped from the standard’s accounting rules based on a company’s defined capitalization policy. |
Number >0 |
Numeric (Total Digits = 18, Precision = 2 to the right of the decimal) |
N |
Y |
Lessee Info Tab
The Lessee Info describes information about your company that will be included in your Marketplace RFPs and other key information required to calculate the lease versus buy (LvB) analysis. The Fiscal Year End and Fiscal Year Model data are critical for establishing your accounting functions and must be provided even if you are not using the Marketplace or LvB functionality. This data also facilitates the creation of the Fiscal Calendar in the UI.
Tab: |
Lessee Info |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
Must exactly match value from Companies Tab where Company Role Type = Lessee |
Alphanumeric (1000) |
Y |
Y |
B |
Effective Date |
Date that the related information is to begin to be used. |
MM/DD/YYYY |
Y |
Y |
|
C |
Fiscal Year End |
The last day in your accounting year. |
MM/DD/YYYY |
Y |
Y |
|
D |
Fiscal Year Model |
The standard type of accounting year – Gregorian Calendar or a special recognized pattern such as 4-4-5. |
See Data Validation List Below |
Drop-down |
Y |
Y |
E |
Stock Symbol |
Assuming a public company, the ticker used on the stock market where the Lessee’s (or parent company’s) stock is traded. Key information for Sourcing RFP. |
Alphanumeric (16) |
N |
N |
|
F |
Industry |
Standard categorization of the type of business / product that the company participates in. Key information for Sourcing RFP. |
See Data Validation List Below |
Drop-down |
N |
N |
G |
Business Type |
Is your company a for-profit or non-profit enterprise? Key information for Sourcing RFP. |
See Data Validation List Below |
Drop-down |
N |
N |
H |
Ownership Type |
Legal Structure of the Lessee – Corporation, C-Corp, S-Corp, LLC, Sole Proprietorship, Partnership, etc. Key information for Sourcing RFP. |
See Data Validation List Below |
Drop-down |
N |
N |
I |
Description |
Description of the company’s products and services. Key information for Sourcing RFP. |
Alphanumeric (4000) |
N |
N |
|
J |
Debt Weight |
Percent of Debt to Total Debt + Equity. Key information for Sourcing LvB. |
Numeric (4) |
N |
N |
|
K |
NOL Final Year |
Year when your current Net Operating Loss for tax purposes ends. Key information for Sourcing LvB. |
Date (YYYY) Numeric (4) |
N |
N |
|
L |
Credit Rating |
Credit Rating assigned to the Lessee (or Parent Company, if appropriate). Key information for Sourcing RFP. |
See Data Validation List Below |
Drop-down |
Y |
N |
M |
Credit Rating Source |
Company issuing Credit Rating. Key information for Sourcing RFP. |
Drop-down |
Y |
N |
Tax Rates Tab
The Lessee Tax Rate table provides detailed tax information for income tax rates at the federal and state level. These rates are important factors in accurately calculating your lease versus buy analyses. The system, however, is currently limited to using only one state rate per LvB request.
Tab: |
Tax Rates | |||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Lessee |
Entity or organization that is the legal party to the lease agreement. |
Must exactly match value from Companies Tab where Company Role Type = Lessee |
Drop-down |
Y |
N |
B |
Geo |
The country that determines the accounting and tax rules that apply to a transaction Geo Name corresponding to an entry on the Geo Table. Tax payment calendar configuration exists in LeaseAccelerator for 27 countries. Additional countries can be configured via an enhancement request. |
See Data Validation Lists Below |
Drop-down |
Y |
N |
C |
Federal Tax Rate |
The Federal Income Tax rate to be used in the LvB analysis. The rate is typically the highest marginal rate used in a client’s tax return. Key information for Sourcing LvB. |
Number ≥ 0. Enter as ## |
Numeric (Total Digits = 8, Precision = 6 to the right of the decimal) |
N |
N |
D |
State Tax Rate |
The State Income Tax rate to be used in the LvB analysis. The rate is typically the highest marginal rate used in a client’s tax return. Key information for Sourcing LvB. |
Number ≥ 0. Enter as ## |
Numeric (Total Digits = 8, Precision = 6 to the right of the decimal) |
N |
N |
E |
Effective Date |
Date which the multiplier is active (as of the beginning of the day). |
MM/DD/YYYY |
Y |
N |
Lessee Financials Tab
The Lessee Financials tab provides information about your company that you may want to include in your Marketplace RFPs. You may choose to input as many or as few of these attributes as you like. If you are a PureLease Marketplace client, it is best practice to provide at least three (3) years of financial information for each Lessee that will be releasing RFP’s as this provides proof of financial stability to the Global Lessor Network.
Tab: |
Lessee Financials |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Lessee |
Entity or organization that is the legal party to the lease agreement |
Must exactly match value from Companies Tab where Company Role Type = Lessee. |
Alphanumeric (1000) |
Y |
N |
B |
Source |
Where the data comes from. Examples may be SEC Filing, Annual Report, Press Release. |
See Data Validation List below |
Drop-down |
N |
N |
C |
Period |
The Period that data is reported for. |
See Data Validation List below |
Drop-down |
Y |
N |
D |
Currency |
Currency that financials are reported in. |
Drop-down |
Y |
N |
|
E |
Total Revenues |
Total Revenue as Reported |
Number >0 |
Numeric (22) |
N |
N |
F |
Net Income |
Total Net Income as Reported |
Number. May be greater than, less than, or equal to 0 |
Numeric (22) |
N |
N |
G |
Total Assets |
Total Assets as Reported |
Number >0 |
Numeric (22) |
N |
N |
H |
Net Worth |
Total Assets minus Total Liabilities as Reported (Or Total Equity). |
Number >0 |
Numeric (22) |
N |
N |
I |
Period End Date |
Date configured financials are valid. Must be date prior to current date. |
MM/DD/YYYY |
Y |
N |
|
J |
Show on RFP |
If checked, data will appear on all Request for Proposals (RFP). |
See Data Validation List below |
Drop-down |
Y |
N |
Templates Tab
This tab identifies the types of End of Term Notifications to be received by asset owners and users based on criteria established by your company. The template includes the specific text of the email notification. These messages are standardized by template and will be automatically sent for all lease schedules. For more information on Notifications and Templates, please refer to the Product Feature Advisory for Global Notifications Settings.
Tab: |
Templates |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Template Name |
User-Defined name of template used to generate email. |
Alphanumeric (1000) |
Y |
N |
|
B |
Subject |
Email subject line description |
Alphanumeric (1000) |
Y |
N |
|
C |
Message |
Text of email to be sent to appropriate employees. |
Alphanumeric (1000) |
Y |
N |
Approved Funders Tab
Approved Funders are the companies that your company specifically wishes to participate in the Sourcing process. If an Approved Funder list is provided, ONLY those companies will receive RFPs. Other unspecified Global Leasing Network (GLN) funders will not receive such requests.
Tab: |
Approved Funders |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Company Name |
Name of the entities who are actively used as funders (or lessors) by your company and should be included in the sourcing and RFP process. |
Must exactly match value on Companies Tab where Company Role Type = Funder |
Alphanumeric (1000) |
N |
N |
Restricted Funders Tab
Restricted Funders are the companies that your company does not wish to receive RFP responses from. You may be disinclined to do business with these organizations due to company policy, practice, or other internal reasons. For example, a competitor of yours may have a subsidiary that provides funding to Lessees and you don’t want to provide them with additional revenue. Therefore, you would list them on this sheet as a Restricted Funder. You may only choose to configure Approved Funders OR Restricted Funders but not both. If Approved Funders are provided, RFP’s will ONLY go to those listed. If Restricted Funders are provided, then RFP’s will go to all Global Lessor Network Funders EXCEPT those listed.
Tab: |
Restricted Funders |
|||||
---|---|---|---|---|---|---|
Column |
Field Name |
Description |
Validation / Valid Values |
Format |
Req’d System Import |
Req’d Acctg |
A |
Company Name |
Name of the entities who are NOT actively used as funders (or lessors) by your company. These lessors should be excluded from receiving RFPs in the marketplace process. |
Must exactly match value on Companies Tab where Company Role Type = Funder |
Alphanumeric (1000) |
N |
N |