What's New in Nakisa Lease Accounting Suite

This section outlines the new features and fixes included in Nakisa Lease Accounting Suite 2026.R1.

General

Nakisa Decision Intelligence (NDI) for Nakisa Lease Accounting Suite is a next-generation agentic AI platform that lets you securely access decision-ready insights and simulate future outcomes instantly without relying on dashboards, analytics teams, or traditional BI tools. Fully integrated into Nakisa products, NDI is available to users with the appropriate roles and permissions.
General user experience enhancements have been made throughout the application, such as:
- The lease component Unit Distribution table has been simplified, requiring fewer steps to update the information.
- To improve clarity in financial schedules, calculated amounts that result in zero (e.g., after currency conversion) are now presented as N/A instead of 0.00.
- To help users better identify configured master data, many places now show the ID and the name of the data from Financial Organization Structure (such as the ERP system ID with Company ID and Name, and Country Code).
- Landing pages and their filters have been enhanced for improved usability and consistency, such as date filters displaying months (instead of specific dates), and a new supported field called "Number of Assets in LC".
In this release, Nakisa has introduced updates to the analytics platform's technology stack to enhance overall stability and performance. As a result, some custom dashboards and reports may be impacted, particularly pivot tables and reports that include calculated fields.

Contract Operation and Lease Events

A new Bulk Asset option has been added to the lease component Definition tab. When enabled, multiple identical leased assets can be recorded as a single unit, with financial amounts representing the total value of all units in the bulk asset.
- The columns "Bulk Asset" and "Bulk Asset Quantity" have also been added to the Asset Roll Forward report.
Document Date and Posting Date fields have been added to the activation group Definition tab, allowing users to set them before activation if they are going to be different from the ROU Start Date. These dates are used to determine the exchange rate for company currency conversion for the Asset Transition schedule, with validation and schedule updates applied at activation if needed.
An auto-close feature has been implemented that allows parent objects to be closed automatically when all their child objects are closed, reducing manual effort and improving workflow efficiency for users.

Mass Operations

Intercompany Transfers have been enhanced to support more flexible transfer scenarios and improved control over processing and reversal.
- System-to-system transfers: Contracts can now be transferred between different ERP systems, and to different master agreements.
- Separate Transfer, Posting, and Document Dates: The Transfer Date is now independent from the Posting Date and Document Date. Posting and document dates can be defined at the job level and adjusted per object in the Excel file.
- Enhanced job reverting: Users can now revert one or more transferred contracts within a job, instead of reverting the entire job.
- Enhanced Excel template: The template now includes additional fields such as New Contract Name, New ERP System, and New Master Agreement, along with a Contract Partners sheet for one-to-one partner mapping.
- Improved job reporting: Reports now include additional details such as new object references, processing duration, and revert status, with direct links to transferred contracts.
- Skip objects with open drafts: A new option allows users to skip contracts with open drafts or delete drafts automatically during transfer.
- Increased batch size limit: The number of contracts that can be processed in a single job has increased from 10 to 50.
- Additionally, Mass Workflow Transition jobs now have an "Include Transferred" checkbox to include the terminated source objects, allowing users to easily manage the closing of these objects once the transfers have been verified.
The job scheduler for mass operations and reports has been enhanced to support more reliable and flexible recurring jobs, and for an overall improved user experience.
- Updated job Date Input fields allow for more granular flexibility in the job setup.
- Users can now easily select the last day of the month.
- The new Upcoming Executions area clearly lists when the next five jobs will be run.

Dashboards and Reports

The following Disclosure Reports have been renamed for clarity:
- "Non Lease Charges Expense" is now called "Expense - Charges"
- "Expense" is now "Expense - Lease"
- "Maturity Analysis" is now "Maturity Analysis - Calendar Year (Lease)"
The following Disclosure Reports have been added:
- Maturity Analysis - Rolling (Lease): Users can now generate the Maturity Analysis report on a yearly rolling basis instead of per calendar year with the existing report.
- Maturity Analysis - Calendar Year (Non Lease): Users can now generate the Maturity Analysis report per calendar year for non-lease amounts.
In the Disclosure Report job, the following changes have been made:
- In Additional Filters, a new currency option has been added called "Currency Definition Type" (which also appears in the header section of the generated report). This allows users to generate the report for multiple company currencies, rather than for a single currency. Note that in this case, the report will not include a Summary table as there cannot be aggregations across multiple currencies.
- The job Date Input fields have been updated to allow for more granular flexibility in the job setup.
The following enhancements have been made for Consolidated Transaction Reports in Nakisa General Ledger to improve usability and clarity:
- In the header section in generated reports, the first column now shows "Profile Inputs" or "Object List Inputs", based on the Filter Type used to generate the report.
- The Environment is now included in the Report Information part of the header section in generated reports. Users will be able to track where the report was generated and avoid confusion when comparing reports across environments.
- Profile fields that have no impact on the generated Consolidated Transaction Reports (e.g., Calendar Type, Fiscal Variant) are no longer displayed in the Profile table in the job pop-up or header section in the generated reports.
- To simplify the view of the Consolidated Transaction Report for users, the report now shows or hides application-specific columns based on which applications are enabled and integrated in Module Management in Financial Organization Structure.
The following columns have been added to the Consolidated Transaction Report:
- To improve clarity, the "Vendor" column has been replaced by "Partner Name" and "Partner ID".
- The column "Migrated" has been added. Along with the "Source" column, users can easily view directly in the report which transactions were migrated or not.
- Specifically for Nakisa Portfolio Management:
  - Location ID
  - Premises ID
  - Contract ID
The following enhancements have been made for GL Balance Reports in Nakisa General Ledger to improve usability and clarity:
- In the job pop-up form, the field "Vendor Filter Type" has also been renamed to "Partner Filter Type". In the header section in the generated report, the "Vendor" field has been renamed as "Partner".
- Because the GL Balance Report is a period-based report, the following changes have been made:
  - The "Date Range Type" field was removed from the job input fields.
  - The read-only "Calendar Type" field that previously distinguished between Regular Calendar and 360 convention has been removed as it does not affect the generated report.
- The Date Inputs section of the GL Balance Report job pop-up, the fields are now simply "From Year" and "To Year", and "From Posting Period" and "To Posting Period" to align with how the data is presented in the generated report.

Configuration and Administration

Form Management in Nakisa Lease Accounting Suite has been enhanced to provide greater control over form configuration and improve usability. Administrators can now manage field visibility and update field captions for out of the box fields, and benefit from improved UI behavior and consistency.
In Module Management in Financial Organization Structure, the field "Integrated to General Ledger" has been renamed to "Document Enrichment" for clarity.
The following improvements have been made to the master data tables in Financial Organization Structure:
- In the Exchange Rate Type table, if the Target Currency is configured for an entry, the application will not reset it to empty following an SAP sync, Excel import, or API calls.
- For REPORTING_CURRENCY entries in the Exchange Rate Type table, the Target Currency field is now mandatory.
- In the Relations section of the Company table, users can only attach one SECOND_LOCAL_CURRENCY, one THIRD_LOCAL_CURRENCY, and one MONTH_END_CURRENCY.
  Note: If there are already more than one of each of these entries assigned to a company code, they will not be removed. Users should review their own configuration to ensure that the Company table is correctly configured.
- In the GL Account table, the "General Ledger Account Category" is now mandatory for both standalone systems and SAP connected systems.
- The Accounting Standard table now supports an “Off-Balance Sheet” type, enabling leases to be classified so that no right-of-use asset or lease liability is recognized on the balance sheet. This can be configured as an alternative accounting standard at the Company Code level, with system behaviors aligned to off-balance sheet treatment for compliance and reporting.
In the Transaction Type Determination table, transaction types can now be determined based on GL account rather than just account type, enabling finer control for those who require more granular reporting.
On both the System Configuration > Company Financial Settings and System Financial Settings pages, the setting "Disable External Posting Requirement" has been added. If it is enabled, then Lease End and Close workflow transitions can be completed on activation groups even if external postings have not been successfully processed.
In the Security section of Financial Organization Structure, the following enhancements have been made:
- To simplify the selection of all Company Codes belonging to an ERP system on the Security > Profiles page, the ERP system has been added to the Company Code drop-down field. Users can simply search and filter based on ERP system, and click the new "Select All" checkbox.
- "First Name" and "Last Name" have been added to the User Profiles table.

Nakisa General Ledger

When an account has Open Item Management enabled in Financial Organization Structure, the icon is now displayed next to the account name in the transaction entries.
The Financial Close Connector has been introduced to generate structured files for financial close and reconciliation processes. Users can now configure scheduled jobs to extract lease accounting data, define file formats, and automate file generation.
Note: This is a licensed feature. To enable access, please contact your Customer Success Manager for more information.

Integration

In ERP Field Mapping in Nakisa SAP Posting Bot, a new "Scripting" option has been added, allowing users to enter custom JavaScript to transform field values and create advanced field mappings to send in documents to SAP.
In Nakisa SAP Posting Bot, the Settings pages have been updated:
- The page "General ERP Settings" is now "Default BAPI Settings".
- The page "ERP System BAPI Settings" is now "ERP System Settings"
- The General Settings page has been added, where currently there is one setting "Duplicate Consistency Start Date" that specifies the date when the SAP T-code was enabled and set to NAKISA in the SAP system. The Duplicate Consistency Check will only verify documents from this date on.
Directly in Financial Organization Structure, users can now view the SAP authorization objects currently configured for the service user. They can use the report to validate whether the service user has been configured properly for operation with Nakisa products.
In Nakisa SAP Sync Bot, the Sync Report has been enhanced to not only show the Failed Count, but also the error details in a separate Sync Failure Report (which can also be downloaded as an Excel file). Additionally, the "diff" column has been renamed to "Process Time (Seconds)" for clarity.
In Nakisa SAP Sync Bot, the Configuration Settings page has been added to control how Cost Center and Partner tables are synced with SAP ERP. Users can now choose between a full load and an incremental (delta) sync based on changes since the last synchronization.
Note: Users must ensure that their SAP system is configured to track all changes related to cost centers and partners.