Release Notes October 2026

First Week Of The Month

New Feature:

Allocation Key Column on the Funds Page

Overview

This release introduces a new Allocation Key column on the Funds page. The enhancement provides users with immediate visibility into each fund's allocation key, eliminating the need to open individual fund records for verification. This streamlines fund management activities and improves overall efficiency.

How It Works

Users can now view the Allocation Key directly from the Funds list, allowing for quicker validation and review of fund configurations without navigating into each fund's details.

Where to Find It

Accounting > Account Management > Funds

To Access It

1. Navigate to the Accounting menu and select Account Management.
2. Open the Funds tab.
3. Locate the new Allocation Key column within the funds grid.

Previous Experience

Previously, the allocation key information was not displayed in the Funds list. Users were required to select Edit for each individual fund to view and validate the allocation key.

What's New

• Added a new Allocation Key column to the Funds page.
• Allocation keys are now visible directly from the funds list.
• Reduced the need to access individual fund records for validation purposes.

Benefits

1. Improved Efficiency
2. Faster Validation Process
3. Enhanced Accuracy and Visibility

Important Notes:

For rental properties, the new column displaying the allocation key is now available in the "Projects" tab.

Improvements

Enhanced Request Closure Management

Overview

This release introduces Enhanced Request Closure Management, designed to improve communication around closed Requests and ensure Requests are properly finalized after a defined period.

Past State

Previously, when a Request was closed, users could continue replying to the ticket indefinitely, either through the application or by email. Replies could reopen the Request regardless of how long it had been closed. Additionally, automatically closed Requests did not notify all participants that the Request had been closed.

What's New

With this release:

• Users and request participants receive an email notification when a Request is automatically closed by the system.

• Closed Requests remain editable and can be reopened for 14 days after closure.

• After 14 days, closed Requests become permanently closed and read-only.

• Permanently closed Requests can no longer be reopened, updated, or replied to.

• Email replies to permanently closed Requests no longer reopen or update the Request.

• Users attempting to reply to a permanently closed Request by email receive an automated notification directing them to create a new Request.

• The Request closure popup has been updated to clearly communicate the 14-day reopening period.

How It Works

Automatic Closure Notifications

When the system automatically closes a Request, an email notification is sent to all participants associated with the Request. The notification informs them that the Request has been closed and advises them to create a new Request if they wish to continue the discussion.

14-Day Reopening Period

After a Request is closed, users can continue to:

• Reopen the Request

• Add replies

• Update information

for a period of 14 days.

Permanent Closure

Once a Request has been closed for more than 14 days:

• The Request becomes read-only.

• Users can still view the Request and its complete history.

• Users can no longer:

  • Add replies

  • Modify information

  • Reopen the Request

This behavior applies to Requests closed either manually by a user or automatically by the system.

Email Replies After Permanent Closure

If a user replies by email to a Request that has been closed for more than 14 days:

• The Request remains closed.

• The email reply is not added to the Request.

• An automated email informs the user that the Request can no longer be updated.

• The notification includes a link directing the user to create a new Request.

Updated Closure Popup

The Request closure confirmation popup now displays a message indicating that closed Requests can only be modified or reopened within 14 days. After that period, they become read-only and can no longer be edited or reopened.

Where to Find It

You can find this feature in: Requests Module

To access it:

1. Open a Request.

2. Close the Request or review an existing closed Request.

3. View the updated closure messaging and closure behavior.

Benefits

• Improves transparency by notifying participants when Requests are automatically closed.

• Prevents outdated Requests from being reopened months after closure.

• Encourages better Request tracking by directing users to create a new Request when a new issue arises.

Important Notes

• Closed Requests remain fully accessible for viewing after permanent closure.

• The 14-day rule applies to both manually closed and automatically closed Requests.

• Email replies to permanently closed Requests will not update the original Request.

Improvements

Restrict Invoice Assignment to Authorized Approvers

Overview

This release introduces approval permission validation for invoice assignments, designed to ensure that invoices can only be assigned to users who have the necessary access rights to approve and process them.

Past State

Previously, invoices could be assigned to any employee regardless of their approval permissions. This occasionally resulted in invoices being assigned to users who could not access or approve them, causing approval bottlenecks, delayed payments, supplier follow-ups, and, in some cases, late payment penalties.

Additionally, when an employee was archived, invoices awaiting approval could remain assigned to that employee without a streamlined reassignment process.

What's New

With this release:

• Invoices can now only be assigned to users who have the required permissions to approve invoices.

• When an employee is archived, the system prompts administrators to reassign all pending invoices.

• Pending invoices can be reassigned in bulk to either:

  • A specific user

  • A user role

These enhancements help ensure that invoices remain within the approval workflow and are not left unattended.

How It Works

Invoice Assignment Validation

When assigning an invoice for approval:

1. The system verifies whether the selected user has invoice approval permissions.

2. If the user does not have the required access, the assignment cannot be completed.

3. Only eligible approvers are allowed to receive invoices for approval.

Employee Archiving Process

When an employee is archived:

1. The system identifies any invoices currently awaiting action from that employee.

2. A reassignment prompt is displayed.

3. Administrators can choose to reassign all pending invoices to:

   • Another employee, or

   • A role responsible for invoice approvals.

4. The reassignment is completed in bulk, ensuring no invoices remain assigned to an inactive employee.

Where to Find It

You can find this feature in: Accounts Payable > Invoice Approval Workflow

To access it:

1. Open an invoice that requires approval.

2. Select an approver or assign the invoice.

3. The system will validate the approver's permissions before completing the assignment.

For invoice reassignment:

1. Navigate to Administration > Employees.

2. Archive an employee.

3. Select the user or role that should receive all pending invoices.

Benefits

• Prevents invoices from being assigned to users who cannot approve them.

• Reduces approval delays and improves payment processing efficiency.

• Ensures pending invoices are automatically addressed when employees leave or become inactive.

Important Notes

• Only users with invoice approval permissions can receive invoices for approval.

• The reassignment prompt appears only when the archived employee has pending invoices.

• Bulk reassignment helps maintain continuity in the approval process and prevents invoices from being overlooked.

Second Week Of The Month

Third Week Of The Month

Last Week Of The Month