Email Verification Process

As part of our commitment to security and preparation for the upcoming rollout of Multi-Factor

Authentication (MFA), we are introducing a new Email Verification process. This ensures every

user has a unique, verified email address associated with their account.

• Admin Controls: Administrators can manually trigger verification for one or more users

  from the Personnel record, setting their status to Scheduled. Saving any changes to a

  user's email address will also automatically trigger the verification process.

• New Filters: To easily manage verifications, Admins can now filter the Personnel record

  by Role, Active/Inactive status, and Email Verification Status.

• User Experience: When a user with a scheduled verification logs in, they will be

  prompted via an on-screen banner to verify their email. Users can also proactively

  initiate this from their User Settings.

• Automated Emails: Triggered users will receive a secure link from The Aqilla Team that

  is valid for 15 minutes.

Expanded Entity Selection in Mapping Rules

We have expanded the capabilities of the Mapping Rules UI. Previously, users could only select

a concrete ledger account within a mapping rule. You can now define specific entities across

other ledger associations, including Project, Fixed Asset, Item, Department, and Analysis 1,

2, & 3. This enhancement allows for greater flexibility, such as conditionally posting or

automatically defaulting a specific Project for all journals of a given type.

Enhanced System Auditability

We have expanded our internal audit logging to track deeper backend configuration changes

(such as attribute or bandcell updates). To keep your Entity Settings view clean and relevant,

these backend logs will not be visible in standard user exports, but they will be securely tracked

and accessible by Aqilla Support and Consulting teams to better assist you with system

configurations.

Bug Fixes & Resolutions

• Workflow Line Item Approvals: Resolved an issue where approval limits on individual document lines were not being strictly enforced. Approvers (e.g., in Timesheets or Expenses) will no longer be able to transition docuent lines that exceed their specific monetary approval limit from Released to Approval.

• Purchase Invoice Matching (PIM) Descriptions: Fixed a bug where the description

  field on manually added lines within PIMs incorrectly became read-only after saving.

  Moving forward, only lines automatically created from a Purchase Order will be

  read-only, allowing you to freely edit your manual entries.

• Fixed Assets Depreciation Runs: Addressed an issue that blocked users from

  completing depreciation runs if the final period of the financial year was set as an

  adjustment period. The system now correctly recognizes the adjustment period and

  allows the depreciation journal to post successfully up to the last standard period.

Security & Maintenance

• General Security Fixes: Deployed routine background security enhancements to maintain the integrity and safety of the Aqilla platform.

Known Issues in this Release

Our team is aware of minor visual bugs related to the new Email Verification process that will be addressed in an upcoming patch:

• The blue email verification reminder banner may disappear quickly without being dismissed by the user.

• In some instances, the option to verify an email only shows once, and the UI temporarily lacks a clear indicator of whether the email was successfully verified.