1.In certain cases, the counterparty in a contract differs from the company that ultimately issues the invoice and receives payment. Previously, the system could not associate contracts from different vendors during corporate payment. This update introduces the ability to configure associated vendors for the current vendor, thereby expanding the scope of associable contracts. 2.Drafting electronic contracts involves both internal staff and external counterparties. Previously, contracts had to be finalized internally before being sent offline to the other party, resulting in a cumbersome process. This update enables direct online collaboration by allowing external parties to be invited to participate in contract drafting in real time. 3.Some companies require expense claims to be filed from company-managed computers, which often automatically encrypt PDF attachments for security. This encryption previously interfered with invoice recognition. This update adds support for decrypting uploaded PDF attachments via configured callbacks before initiating invoice recognition. 4.For companies that use a shared center to assign review tasks, there is now an option to configure working hours. Task assignments will only occur within these defined hours; the system will not assign tasks outside of the configured schedule. This update enables the shared task pool to reference a working calendar and assign tasks accordingly. 5.In cases where employees receive cash advances and later submit invoices for reimbursement, some companies need to perform expense accruals for those advances. This update introduces automatic accrual settings for Cash Advance  to support this requirement.

1.Some companies have a secondary approval process for booking flights, hotels, and trains that exceed the standard, which requires high timeliness. In this update, the system supports sending SMS messages to approvers, who can directly operate to approve or reject based on the SMS prompts. 2.In scenarios where a company's employees advance funds to pay deposits to vendors (serving as guarantees for the vendor platform), with such deposits later refunded to the company's corporate bank account, this update now supports enabling the employee advance payment function for corporate prepayments and allows modifying the prepayment recipient account to an employee's personal bank account. 3.When the amount an employee books for a hotel is less than the company's standard, some companies will reward employees for the difference, which is known as the reward scenario. Previously, all reward scenarios required secondary development for calculation. In this update, the product now supports simple strategy reward calculations. 4.Some companies control budgets by department groups, with corresponding leaders managing different department groups. The current budget balance query scheme is set according to department groups, but it requires setting up many query schemes. Moreover, if the department groups change later, adjustments are also needed, and the maintenance adjustment workload is relatively large. In this update, you can now set roles for department groups and authorize budget balance query schemes based on these roles.

1.The current contract drafting feature only supports online editing. Some companies have fixed contract templates. This update allows creating contracts using predefined templates and enables collaborative editing. 2.For multinational conglomerates, domestic and international business travel allowances follow different reimbursement policies. This update supports configuring the cross-border criteria in the allowance rules. 3.To streamline invoice entry, this release introduces a "Scan-to-Invoice" feature via Helios QR codes. The system will automatically populate reimbursement company title and recipient emails from scanned invoices, while syncing them to personal invoice folders. 4.Currently, the approval-related messages in the system can only be configured with fixed fields as the message content. This update supports extending the message content configuration to include other fields on the document.

1.The current contract drafting feature only supports online editing. Some companies have fixed contract templates. This update allows creating contracts using predefined templates and enables collaborative editing. 2.For multinational conglomerates, domestic and international business travel allowances follow different reimbursement policies. This update supports configuring the cross-border criteria in the allowance rules. 3.To streamline invoice entry, this release introduces a "Scan-to-Invoice" feature via Helios QR codes. The system will automatically populate reimbursement company title and recipient emails from scanned invoices, while syncing them to personal invoice folders. 4.Currently, the approval-related messages in the system can only be configured with fixed fields as the message content. This update supports extending the message content configuration to include other fields on the document.

1.The current contract drafting feature only supports online editing. Some companies have fixed contract templates. This update allows creating contracts using predefined templates and enables collaborative editing. 2.For multinational conglomerates, domestic and international business travel allowances follow different reimbursement policies. This update supports configuring the cross-border criteria in the allowance rules. 3.To streamline invoice entry, this release introduces a "Scan-to-Invoice" feature via Helios QR codes. The system will automatically populate reimbursement company title and recipient emails from scanned invoices, while syncing them to personal invoice folders. 4.Currently, the approval-related messages in the system can only be configured with fixed fields as the message content. This update supports extending the message content configuration to include other fields on the document.

1.Currently, Accounts Payable only validate unfully cleared prepayments at the invoice payment line level. In this update introduces document-level validation for more flexible open prepayment checks. 2.Some companies require approval workflows to be triggered upon Request closure, with the document closing only after approval is granted. In this update, supports configuring approval workflows for the 'closure' scenario, enabling manual closure triggers. 3.The current system calculates service remuneration tax monthly per external employee. However, if an employee serves multiple entities under one tenant, single-entity tax calculations may be inaccurate. This release enables cumulative tax calculation by company or legal entity. 4.Finance teams require urgent mobile review capabilities without full desktop functionality. This update addresses this by enabling core operations - document viewing and approve/reject actions - on mobile devices. 5.Multinational corporations often deal with vendors requiring invoice information in local languages (e.g., Thai for Thailand, English for the US). This update allows switching between language versions on both PC and mobile for viewing and copying.

1.Currently, Accounts Payable only validate unfully cleared prepayments at the invoice payment line level. In this update introduces document-level validation for more flexible open prepayment checks. 2.Some companies require approval workflows to be triggered upon Request closure, with the document closing only after approval is granted. In this update, supports configuring approval workflows for the 'closure' scenario, enabling manual closure triggers. 3.The current system calculates service remuneration tax monthly per external employee. However, if an employee serves multiple entities under one tenant, single-entity tax calculations may be inaccurate. This release enables cumulative tax calculation by company or legal entity. 4.Finance teams require urgent mobile review capabilities without full desktop functionality. This update addresses this by enabling core operations - document viewing and approve/reject actions - on mobile devices. 5.Multinational corporations often deal with vendors requiring invoice information in local languages (e.g., Thai for Thailand, English for the US). This update allows switching between language versions on both PC and mobile for viewing and copying.

1.Multinational companies with multiple set of books often involve scenarios of unified procurement and unified market activity management. In this update, we support the association of Accounts Payable across set of books with AP Request for amount control and budget check. 2.Some companies focus on the travel application experience for employees, hoping that they only need to fill in the travel time and destination to make reservations. In this update, we support one-screen Travel Request without detailed expense itineraries. 3.Some companies have employees submit toll invoices to a designated person for reimbursement, but the volume of invoices is too large to enter at once. In this update, we support selecting toll invoices and quota invoices from the invoice pool to generate aggregated invoices separately. 4.After the budget document is rechecked and approved, if a budget entry error is found, currently, the only option is to manually submit a reverse budget journal entry. In this update, we support for reversing budget entries directly after the budget recheck. 5.Currently, the system's condition-based employee group addition requires backend task calculations, and all tenants in the environment are queued together for computation, which sometimes results in longer effective times. In this update, we support manual update calculations after adding conditions to reduce backend computation time and achieve quicker availability.

1.When performing “Claimed amount vs. associated request amount" controls on reimbursements, certain business scenarios only require validation at the specified cost center's aggregate level. This update extends support to request-associated Expense Claims, enabling amount controls based on the aggregated allocation items within the cost centers specified in the Request. 2.Enterprises may have certain special expenses where they prefer not to update the expense amount when uploading invoices. However, for regular expenses, updating the amount based on the invoice is still necessary for ease of entry. Therefore, this update supports configuring whether to update the expense amount upon invoice upload based on the expense type dimension. 3.Some enterprises want to control travel standards based on the mileage distance between business trip locations. For example, if the distance is less than 800 km, only high-speed rail is allowed, while flights are permitted for distances exceeding 800 km. This update supports mileage-based travel standard control. 4.After users submit an Accrual Request, the subsequent process involves submitting an Accounts Payable form to offset the accrual. This update supports initiating AP payments directly from the accrual request, closing the loop and simplifying operations. 5.For certain table viewing interfaces in the system, users want the system to automatically summarize amounts. This update supports advanced table styling by adding calculation methods (such as sum, average, maximum, and minimum) to the current page's data.

1.When performing “Claimed amount vs. associated request amount" controls on reimbursements, certain business scenarios only require validation at the specified cost center's aggregate level. This update extends support to request-associated Expense Claims, enabling amount controls based on the aggregated allocation items within the cost centers specified in the Request. 2.Enterprises may have certain special expenses where they prefer not to update the expense amount when uploading invoices. However, for regular expenses, updating the amount based on the invoice is still necessary for ease of entry. Therefore, this update supports configuring whether to update the expense amount upon invoice upload based on the expense type dimension. 3.Some enterprises want to control travel standards based on the mileage distance between business trip locations. For example, if the distance is less than 800 km, only high-speed rail is allowed, while flights are permitted for distances exceeding 800 km. This update supports mileage-based travel standard control. 4.After users submit an Accrual Request, the subsequent process involves submitting an Accounts Payable form to offset the accrual. This update supports initiating AP payments directly from the accrual request, closing the loop and simplifying operations. 5.For certain table viewing interfaces in the system, users want the system to automatically summarize amounts. This update supports advanced table styling by adding calculation methods (such as sum, average, maximum, and minimum) to the current page's data.

1.Some companies have scenarios where labor dispatch personnel take cash advances from the company as specific project managers. When making subsequent payments to the labor dispatch company, these cash advances need to be offset. This update allows the Accounts Payable to offset cash advances that were not applied for by the applicant 2.For value-added tax (VAT) special invoices issued on projects that have already enjoyed preferential policies, companies do not claim input tax credits for the related expenses. In this update, it is now possible to configure that the specific cost center of the expense document does not enable price-tax separation. 3.Some companies wish to control employees' train travel standards based on the duration of high-speed rail travel between two locations. For example, if the travel time exceeds 4 hours, business class seats may be taken. This update supports controlling train travel standards based on high-speed rail travel time. 4.For Expense Claims and Accounts Payable documents where expense lines are amortized and accruals are made at the end of each month, accruals are currently based on the amortized amount, which leads to the accrual of data for future amortization periods and results in inaccurate accrual amounts. In this update, the system now supports accrual batches to only accrue the amortized expenses for the current period. 5.Multinational groups have vendors with multiple bank accounts, divided into domestic and foreign accounts. The accounts used for transactions with each company within the group may vary. The system should control which vendor bank accounts can be selected for different companies and businesses. This update supports maintaining "company permissions" and "applicable currencies" for vendor bank accounts.

1.In certain industries, there are business scenarios involving recharge-based spending or payments to agents. In such cases, prepayments may be made to Vendor A, but invoices are issued by other vendors. This update now supports cross-vendor write-off of prepayments. 2.During budget control, some companies may have specific budget items that they prefer to keep from all employees. This update now supports permission-based access to budget execution details based on budget items. 3.The system currently supports cross-company document allocation line permissions, which may lead to the creation of vouchers for multiple companies. This update supports restricting voucher information for different companies based on the company permissions in the document allocation line, allowing finance personnel to only see voucher information for companies they have permission for. 4.Some enterprises and institutions require a system signature function during review. This update supports signing during the review process. 5.The formula editor in Form Settings is widely used, but many complex expressions required in practice are difficult to write using existing functions. This update introduces an advanced mode for the formula editor, enabling the use of JS syntax to write expressions.

1.Overseas companies frequently encounter payment scenarios involving international vendors, each with a designated payment channel. This update facilitates maintaining a default payment method within the vendor master data and automatically applies this default when processing payments to vendors. 2.Some businesses close their accounts earlier at the end of the month. When a business consistently settles its accounts 1 or 2 days before the official month-end, it is necessary to make accruals on the second-to-last or third-to-last day of each month. The current update allows for the configuration of a time offset in accrual batch settings, enabling the generation of accrual batches based on this time offset. 3.Certain accounts not linked to online direct banks and the majority of overseas payment transactions require offline or file-based payment processing. These operations may result in returned payment scenarios. In this update, a new "Returned Payment" feature is introduced in the offline and file-based payment types in Helios, enabling users to upload bank return screenshots or documents when handling returned payments. 4.Some enterprises aim to notify the relevant responsible person when the budget reaches a specific usage threshold, ensuring they are informed of the budget status in advance. This update supports configuring message reminders regarding budget usage for roles or specified personnel within a cost center or cost center group.

1.Overseas companies frequently encounter payment scenarios involving international vendors, each with a designated payment channel. This update facilitates maintaining a default payment method within the vendor master data and automatically applies this default when processing payments to vendors. 2.Some businesses close their accounts earlier at the end of the month. When a business consistently settles its accounts 1 or 2 days before the official month-end, it is necessary to make accruals on the second-to-last or third-to-last day of each month. The current update allows for the configuration of a time offset in accrual batch settings, enabling the generation of accrual batches based on this time offset. 3.Certain accounts not linked to online direct banks and the majority of overseas payment transactions require offline or file-based payment processing. These operations may result in returned payment scenarios. In this update, a new "Returned Payment" feature is introduced in the offline and file-based payment types in Helios, enabling users to upload bank return screenshots or documents when handling returned payments. 4.Some enterprises aim to notify the relevant responsible person when the budget reaches a specific usage threshold, ensuring they are informed of the budget status in advance. This update supports configuring message reminders regarding budget usage for roles or specified personnel within a cost center or cost center group.

1.Overseas companies frequently encounter payment scenarios involving international vendors, each with a designated payment channel. This update facilitates maintaining a default payment method within the vendor master data and automatically applies this default when processing payments to vendors. 2.Some businesses close their accounts earlier at the end of the month. When a business consistently settles its accounts 1 or 2 days before the official month-end, it is necessary to make accruals on the second-to-last or third-to-last day of each month. The current update allows for the configuration of a time offset in accrual batch settings, enabling the generation of accrual batches based on this time offset. 3.Certain accounts not linked to online direct banks and the majority of overseas payment transactions require offline or file-based payment processing. These operations may result in returned payment scenarios. In this update, a new "Returned Payment" feature is introduced in the offline and file-based payment types in Helios, enabling users to upload bank return screenshots or documents when handling returned payments. 4.Some enterprises aim to notify the relevant responsible person when the budget reaches a specific usage threshold, ensuring they are informed of the budget status in advance. This update supports configuring message reminders regarding budget usage for roles or specified personnel within a cost center or cost center group.

1.Accounts Payable now supports batch authorization and custom buttons, with options to restrict cash advance types for offset. 2.Enhanced the user experience of expense report details and attachments. 3. Significantly optimized approval interactions, improving workflow efficiency. 4.Added a reminder feature for contracts to expedite the approval process. 5.Proxy issuance of service remuneration invoices now allows for income tax calculation based on amounts excluding tax. 6.New expenses in the Expense List can be restricted by job position and department. 7.Travel Request now includes a nearby airport recommendation feature. 8.Optimized performance and stability for personal cars used for business purposes.

1.In actual business operations, the finance department often confirms the actual expense amount multiple times through Unfinished Business Details portal. Since accurate allocation information may not be available when documents are first submitted, this update now allows for the entry of new allocation details during later expense confirmations. 2.In some countries/regions, invoices may involve withholding tax scenarios with different withholding taxes on a single invoice. Therefore, users need to maintain detailed withholding tax information during reimbursement. This update introduces support for maintaining withholding tax detail line information, allowing users to bring out tax types and rates based on configured tax code information, and also supports manual maintenance of withholding tax amounts. 3.Some enterprises use large language models for intelligent review. For certain attachment files deemed sensitive by the enterprise, they should not be processed by the large language model. This update supports enterprises in first determining whether a file is sensitive, and then allowing the large language model to access the file based on the determination. 4.Some enterprises wish to push approval tasks to be concentrated at a fixed time, uniformly sending pending approval tasks to high-level leaders. This update supports configuring scenarios where approval tasks are temporarily held and subsequently aggregated for reminders. 5.Enterprises adopting AI intelligent recognition to enhance form-filling processes hope to make them increasingly intelligent over time. This update supports extracting information from attachment files using AI recognition technology and intelligently filling it into documents, reducing manual entry.

1.In actual business operations, the finance department often confirms the actual expense amount multiple times through Unfinished Business Details portal. Since accurate allocation information may not be available when documents are first submitted, this update now allows for the entry of new allocation details during later expense confirmations. 2.In some countries/regions, invoices may involve withholding tax scenarios with different withholding taxes on a single invoice. Therefore, users need to maintain detailed withholding tax information during reimbursement. This update introduces support for maintaining withholding tax detail line information, allowing users to bring out tax types and rates based on configured tax code information, and also supports manual maintenance of withholding tax amounts. 3.Some enterprises use large language models for intelligent review. For certain attachment files deemed sensitive by the enterprise, they should not be processed by the large language model. This update supports enterprises in first determining whether a file is sensitive, and then allowing the large language model to access the file based on the determination. 4.Some enterprises wish to push approval tasks to be concentrated at a fixed time, uniformly sending pending approval tasks to high-level leaders. This update supports configuring scenarios where approval tasks are temporarily held and subsequently aggregated for reminders. 5.Enterprises adopting AI intelligent recognition to enhance form-filling processes hope to make them increasingly intelligent over time. This update supports extracting information from attachment files using AI recognition technology and intelligently filling it into documents, reducing manual entry.

1.When a company generates accounts payable through the import of Request details, the requested fees are estimated amounts. Therefore, there can be partial payment reimbursements. In this release, Helios now supports marking the remaining amount of the Request as non-payable during the import of Request fees. Once the Accounts Payable is paid, the corresponding Request detail lines will be automatically closed. 2.Some companies have business trips lasting half a day, but the current system only supports full-day amount limit control for such trips. This update extends support for half-day business trip management scenarios. 3.Currently, overseas invoices/receipts are uploaded through a single entry point for invoice attachment recognition. Different countries have different recognition fields, resulting in low recognition accuracy. This update supports a separate entry point for Japanese invoices, utilizing a dedicated recognition model service to improve accuracy. 4.Employees may have business activities in multiple cities, with corporate accommodation and office locations in each city. This includes regional sales managers and department supervisors with cross-city responsibilities. This update supports the configuration of multiple bases for employees, facilitating the management of travel standards and other controls. 5.Based on the needs for various approval list-related functionalities and user experience, this update includes a reconstruction of the approval lists.

1.When a company generates accounts payable through the import of Request details, the requested fees are estimated amounts. Therefore, there can be partial payment reimbursements. In this release, Helios now supports marking the remaining amount of the Request as non-payable during the import of Request fees. Once the Accounts Payable is paid, the corresponding Request detail lines will be automatically closed. 2.Some companies have business trips lasting half a day, but the current system only supports full-day amount limit control for such trips. This update extends support for half-day business trip management scenarios. 3.Currently, overseas invoices/receipts are uploaded through a single entry point for invoice attachment recognition. Different countries have different recognition fields, resulting in low recognition accuracy. This update supports a separate entry point for Japanese invoices, utilizing a dedicated recognition model service to improve accuracy. 4.Employees may have business activities in multiple cities, with corporate accommodation and office locations in each city. This includes regional sales managers and department supervisors with cross-city responsibilities. This update supports the configuration of multiple bases for employees, facilitating the management of travel standards and other controls. 5.Based on the needs for various approval list-related functionalities and user experience, this update includes a reconstruction of the approval lists.

1.For companies with numerous scenarios involving previous invoice payments, the system currently only allows adding previous invoice payment lines one by one. This update supports the bulk import and creation of previous invoice payment lines. 2.This update supports the automatic population of the expected payment date for the selected contract payment line when making vendor payments. Additionally, a new configuration has been added to restrict the modification of the expected payment date, preventing employees from making early payments that are not in accordance with the contract. 3.For electronic toll invoices, some companies prefer to deduct these invoices only when reimbursing toll fees. This update adds an expense type configuration item in the "Invoice Price and Tax Separation" settings, allowing certain invoices to be deductible only under specific expense types. 4.For cross-year requests, some companies wish to release budget reserves in the original period of previous years, without affecting the current budget. This update supports the configuration of document types that allow cross-year budget releases to remain in the original period. 5.Currently, some TMCs support travel policies and can manage multiple categories in a bundled manner. When submitting requests via Helios, there is a need to push the travel policies of the employees to TMCs for travel booking control. This update allows maintaining employee travel policies within the expense policies and pushing them to TMCs.

1.For companies with numerous scenarios involving previous invoice payments, the system currently only allows adding previous invoice payment lines one by one. This update supports the bulk import and creation of previous invoice payment lines. 2.This update supports the automatic population of the expected payment date for the selected contract payment line when making vendor payments. Additionally, a new configuration has been added to restrict the modification of the expected payment date, preventing employees from making early payments that are not in accordance with the contract. 3.For electronic toll invoices, some companies prefer to deduct these invoices only when reimbursing toll fees. This update adds an expense type configuration item in the "Invoice Price and Tax Separation" settings, allowing certain invoices to be deductible only under specific expense types. 4.For cross-year requests, some companies wish to release budget reserves in the original period of previous years, without affecting the current budget. This update supports the configuration of document types that allow cross-year budget releases to remain in the original period. 5.Currently, some TMCs support travel policies and can manage multiple categories in a bundled manner. When submitting requests via Helios, there is a need to push the travel policies of the employees to TMCs for travel booking control. This update allows maintaining employee travel policies within the expense policies and pushing them to TMCs.

1.In cases where companies do not confirm expenses upon receipt of invoices and instead require financial verification of actual expense amounts through multiple actions in the unfinished business detail entry, this update introduces support for employees to manage expense confirmation directly and initiate expense confirmation approval workflows. 2.In scenarios involving reimbursement of invoices with multiple tax rates, the system currently only supports automatic splitting of invoices with different tax rates. In this release, support is added for users to manually select invoice lines for reimbursement across all invoice types. 3.In cases where companies prefer that budgets are not allocated when documents are submitted but rather after approval by business leaders, this update supports triggering budget allocation at the document approval node. 4.For cases involving the import of a large volume of expense and allocation data into the system, the current process involves batch importing expense data first, followed by importing allocation data for each expense separately, which is cumbersome. This release supports simultaneous import of expense and allocation data. 5.In cases where companies have strict requirements when submitting Expense Claims, demanding that each payment transaction corresponds to one expense, not allowing multiple expense types to match a single payment transaction. This release adds support for summarizing payment receipt lines in Expense Claims based on "Expense Type + Payee" dimensions.

1.In cases where companies do not confirm expenses upon receipt of invoices and instead require financial verification of actual expense amounts through multiple actions in the unfinished business detail entry, this update introduces support for employees to manage expense confirmation directly and initiate expense confirmation approval workflows. 2.In scenarios involving reimbursement of invoices with multiple tax rates, the system currently only supports automatic splitting of invoices with different tax rates. In this release, support is added for users to manually select invoice lines for reimbursement across all invoice types. 3.In cases where companies prefer that budgets are not allocated when documents are submitted but rather after approval by business leaders, this update supports triggering budget allocation at the document approval node. 4.For cases involving the import of a large volume of expense and allocation data into the system, the current process involves batch importing expense data first, followed by importing allocation data for each expense separately, which is cumbersome. This release supports simultaneous import of expense and allocation data. 5.In cases where companies have strict requirements when submitting Expense Claims, demanding that each payment transaction corresponds to one expense, not allowing multiple expense types to match a single payment transaction. This release adds support for summarizing payment receipt lines in Expense Claims based on "Expense Type + Payee" dimensions.

1.In cases where companies do not confirm expenses upon receipt of invoices and instead require financial verification of actual expense amounts through multiple actions in the unfinished business detail entry, this update introduces support for employees to manage expense confirmation directly and initiate expense confirmation approval workflows. 2.In scenarios involving reimbursement of invoices with multiple tax rates, the system currently only supports automatic splitting of invoices with different tax rates. In this release, support is added for users to manually select invoice lines for reimbursement across all invoice types. 3.In cases where companies prefer that budgets are not allocated when documents are submitted but rather after approval by business leaders, this update supports triggering budget allocation at the document approval node. 4.For cases involving the import of a large volume of expense and allocation data into the system, the current process involves batch importing expense data first, followed by importing allocation data for each expense separately, which is cumbersome. This release supports simultaneous import of expense and allocation data. 5.In cases where companies have strict requirements when submitting Expense Claims, demanding that each payment transaction corresponds to one expense, not allowing multiple expense types to match a single payment transaction. This release adds support for summarizing payment receipt lines in Expense Claims based on "Expense Type + Payee" dimensions.