What's New
In addition to general editorial changes and corrections, this release of the documentation contains the following main changes included in the release of 2026.R1:
- Users can now view the SAP authorization objects currently configured for the service user directly in Financial Organization Structure. They can use the report to validate whether the service user has been configured properly for operation with Nakisa products.
- In Module Management, 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 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.
- 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.
- 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.
- To support integration of Nakisa Accounts Payable Automation with Nakisa Lease Accounting Suite and/or Nakisa Portfolio Management, the following changes have been made:
- The setting "AP Offset Account" has been added to the System Configuration > Company Financial Settings page to configure the GL account for offset journal entries in Nakisa Accounts Payable Automation.
- In the Document Type Determination table, the value "Invoice" has been added to Posting Document Type. There must be one mapping from Invoice to a Document Type (from SAP) per company code.
- If Module Management has Nakisa Accounts Payable Automation enabled, the new Vendor Profiles page appears in the Security section of the main menu. On the Users Profiles page, you can then assign a Vendor Profile that restrict a user's access to certain vendors in Nakisa Accounts Payable Automation.
- The table Expense Account Determination has been added to specify which expense GL account should be used when AP invoices require direct expense posting.
Note: Refer to Configuration for Nakisa Accounts Payable Automation Integration for more information.
|
Financial Organization Structure 2026.R1 © 2026
|
Nakisa Inc. All rights reserved worldwide. |