1.Itinerary push for Travel Requests depends on configurations such as the TMC. When a push error occurs, delivery and operations teams need to repeatedly compare historical push data with current configurations to identify the cause, making troubleshooting difficult and communication inefficient. This update introduces “Simulated Itinerary Push”, allowing users to identify potential configuration adjustments based on historical itinerary push data or simulate a push using the current configuration to quickly verify whether the configuration is correct. 2.After a vendor updates their bank account, payments to the old account via the bank-enterprise direct link may fail. Currently, for the same AP document, employees must locate payment records for the same payee one by one and update each record individually. This repetitive process is time-consuming and prone to missed updates. This update allows users to update the payee's bank account once in unsettled business details, automatically updating payment lines associated with the same document, vendor, and account to keep payment data consistent. 3.A single business trip may span multiple cities and dates, and different daily travel allowance amounts may apply on different dates. Employees may also receive complimentary meals on certain days and need to record the applicable deduction items for each date. This update allows enterprises to enable “daily entry” in the relevant travel allowance settings. Employees can select applicable deduction items in the itinerary details for each date. The system calculates the allowance for each day based on the applicable daily amount and aggregates the results, making the allowance amount more accurately reflect actual circumstances. 4.For international invoices and receipts, enterprises may configure multiple rules to identify suspected duplicate invoices, with different risk levels assigned to different rules. If all rules enforce blocking, legitimate expense claims may be affected; if all rules only trigger reminders, high-risk duplicate documents may not be prevented. This update allows the control level to be configured separately for each enabled rule. High-risk rules can block expense claims, while rules requiring manual judgment can issue reminders and allow the process to continue. 5.Approval to-dos and approval or rejection notifications often need to include dynamic information from the document so employees can quickly identify the relevant business matter. If notification bodies can only contain fixed text or predefined fields, users may need to open the document to check key details. This update allows users to insert formula-based dynamic text into the bodies of relevant approval messages in the Message Center, so notification content can be generated based on document data.

1.Currently, when employees select a region rather than a specific city when submitting a Travel Request, budget standards for flights, trains, hotels, ride services, meals, and other expenses cannot be properly retrieved. In actual business scenarios, companies often want to designate a representative city for each region and use the standards of that city to generate budgets or push itineraries. This update supports configuring a default city for each region and using the standards of that city when generating budgets and pushing itineraries. 2.In business scenarios involving tax deducted at source (TDS), such as in India, the amount of the company's prepayment available for offsetting differs from the actual amount paid to the vendor through the bank: one portion is paid to the vendor, while the other is withheld and subsequently paid to the tax authority. This update supports displaying the withholding tax amount and the actual amount paid to the vendor. When offsetting the prepayment subsequently, the system will calculate the offset amount based on the sum of the actual amount paid to the vendor and the withholding tax amount, ensuring that the business transaction is accurately and completely reflected. 3.Currently, when the total expense amount of Expense Claims associated with a Request exceeds the request control limit, the system recursively searches for all interrelated Requests and Expense Claims and combines their expenses for validation. This update supports prioritizing the validation of the total amount against the request control limit based on the expenses of the current document and the amount of the Request directly associated with the current document. 4.Some companies manage Helios hotel expenses through a monthly fixed limit, with different limits assigned to different employees. The limit is deducted based on the actual month in which the expense is incurred. However, employees may book hotels across months. If the limit for the following month has not yet been issued at the time of booking, the system may fail the limit validation and prevent the employee from completing the booking. This update allows the limit to be made available in advance, enabling employees to use their assigned limit earlier while complying with the company's policies. 5.In enterprise budget management, the department responsible for budget preparation may differ from the department that actually handles the business. For example, HR may centrally prepare the budget for employee team-building expenses, while individual business departments actually submit reimbursement requests. If queries can only be viewed by the handling department, it is difficult for finance users to analyze data from the responsible department perspective. This update adds the Responsible Department dimension to budget balance queries, helping finance users view balances and details from the perspective of the responsible department.

1.For certain catering businesses, employees are only allowed to travel within designated regions (e.g., Department A can only select Cities A, B, and C, while Department B can only select Cities B, C, and D.). Previously, the city selector did not support such restrictions. This update introduces support for configuring city controls to allow selection only from specified city groups, thereby restricting employees' travel destinations. 2.When processing prepayment refunds, some enterprises encounter scenarios where the actual refund distribution ratios across multiple associated allocation items differ from the original allocation. This update enables users to directly enter allocation details when creating prepayment refunds. 3.Although workflow approvals currently support withdrawal, some enterprises require that documents cannot be withdrawn after specific operations, by certain users, or after reaching designated workflow nodes. This update introduces validation rules for document withdrawal and deletion. When users attempt to withdraw or delete a document, the system will evaluate the configured rules and either issue warnings or prevent the operation. 4.Currently, reversal vouchers can only be generated based on existing original vouchers and must be triggered through workflow processes. This update enables system administrators to generate reversal vouchers directly from the Voucher Monitor without requiring workflow execution. 5.Some documents require designated header field values, such as Cost Center, Department, or Project Task, to be automatically populated into corresponding allocation line fields after the document header is saved, reducing manual maintenance effort. This update supports automatic propagation of configured header field values to all allocation lines upon saving the document header.

1.For some enterprises, private vehicle usage often occurs alongside business trips. They want the same control as for travel—meaning private car usage must be pre-approved. This update now supports private car claims only after a travel request involving private vehicle usage has been approved. 2.Some enterprises prepay travel expenses by legal entity, which are then used by various business divisions (subsidiaries). After usage, subsidiaries write off the corresponding amount prepaid by the legal entity. Currently, Accounts Payable documents only support cross-company prepayment write-offs within the same set of books, which may result in a wide range of write-off companies. This update adds support for cross-company prepayment write-offs under the same legal entity. 3.Currently, the system determines whether E-invoice (General VAT) and Electronic General VAT Invoices are deductible based solely on whether the invoice line item is for passenger transportation services. However, according to the latest deduction policy, only passenger transportation service invoices that list passenger information are deductible. To address this policy change, this update optimizes the system's deduction logic by adding passenger information verification. 4.During budget approval, the detailed data can be scattered. This update introduces a summary mode that lets users view data aggregated by department or cost center. 5.In some group companies with many subsidiaries and diverse business operations, employees can easily get confused. To address this, the system now supports setting a different logo for each company — logos can be configured at the company level.

1.For some enterprises, private vehicle usage often occurs alongside business trips. They want the same control as for travel—meaning private car usage must be pre-approved. This update now supports private car claims only after a travel request involving private vehicle usage has been approved. 2.Some enterprises prepay travel expenses by legal entity, which are then used by various business divisions (subsidiaries). After usage, subsidiaries write off the corresponding amount prepaid by the legal entity. Currently, Accounts Payable documents only support cross-company prepayment write-offs within the same set of books, which may result in a wide range of write-off companies. This update adds support for cross-company prepayment write-offs under the same legal entity. 3.Currently, the system determines whether E-invoice (General VAT) and Electronic General VAT Invoices are deductible based solely on whether the invoice line item is for passenger transportation services. However, according to the latest deduction policy, only passenger transportation service invoices that list passenger information are deductible. To address this policy change, this update optimizes the system's deduction logic by adding passenger information verification. 4.During budget approval, the detailed data can be scattered. This update introduces a summary mode that lets users view data aggregated by department or cost center. 5.In some group companies with many subsidiaries and diverse business operations, employees can easily get confused. To address this, the system now supports setting a different logo for each company — logos can be configured at the company level.

1.For some enterprises, private vehicle usage often occurs alongside business trips. They want the same control as for travel—meaning private car usage must be pre-approved. This update now supports private car claims only after a travel request involving private vehicle usage has been approved. 2.Some enterprises prepay travel expenses by legal entity, which are then used by various business divisions (subsidiaries). After usage, subsidiaries write off the corresponding amount prepaid by the legal entity. Currently, Accounts Payable documents only support cross-company prepayment write-offs within the same set of books, which may result in a wide range of write-off companies. This update adds support for cross-company prepayment write-offs under the same legal entity. 3.Currently, the system determines whether E-invoice (General VAT) and Electronic General VAT Invoices are deductible based solely on whether the invoice line item is for passenger transportation services. However, according to the latest deduction policy, only passenger transportation service invoices that list passenger information are deductible. To address this policy change, this update optimizes the system's deduction logic by adding passenger information verification. 4.During budget approval, the detailed data can be scattered. This update introduces a summary mode that lets users view data aggregated by department or cost center. 5.In some group companies with many subsidiaries and diverse business operations, employees can easily get confused. To address this, the system now supports setting a different logo for each company — logos can be configured at the company level.

1.For some enterprises, private vehicle usage often occurs alongside business trips. They want the same control as for travel—meaning private car usage must be pre-approved. This update now supports private car claims only after a travel request involving private vehicle usage has been approved. 2.Some enterprises prepay travel expenses by legal entity, which are then used by various business divisions (subsidiaries). After usage, subsidiaries write off the corresponding amount prepaid by the legal entity. Currently, Accounts Payable documents only support cross-company prepayment write-offs within the same set of books, which may result in a wide range of write-off companies. This update adds support for cross-company prepayment write-offs under the same legal entity. 3.Currently, the system determines whether E-invoice (General VAT) and Electronic General VAT Invoices are deductible based solely on whether the invoice line item is for passenger transportation services. However, according to the latest deduction policy, only passenger transportation service invoices that list passenger information are deductible. To address this policy change, this update optimizes the system's deduction logic by adding passenger information verification. 4.During budget approval, the detailed data can be scattered. This update introduces a summary mode that lets users view data aggregated by department or cost center. 5.In some group companies with many subsidiaries and diverse business operations, employees can easily get confused. To address this, the system now supports setting a different logo for each company — logos can be configured at the company level.

1.Some companies handle downstream payable settlements through invoice payment lines in Accounts Payable. Previously, the system did not support offsetting prepayments when these payable records were created; actual payments were initiated using the "Previous Invoice Payment" function. This update now supports offsetting prepayment directly on the previous invoice payment line. 2.For companies involved in European operations, cross-border transactions within Europe may be subject to reverse charge mechanisms. This release introduces a "Reverse Charge Flag" on international invoices. Additionally, the OCR service now supports the recognition of this flag, along with the corresponding reverse charge rate and amount. 3.Some clients requested that the same approver should not be notified multiple times for a single document during its approval process. This release introduces configurable duplicate notification rules, allowing the system to filter out repetitive notifications to the same person based on defined criteria. 4.For the overseas subsidiaries of some corporations, different countries require different payment submission file templates and formats. This release now supports setting the applicable organizational level for these offer files, enabling control so that different cashiers can only select templates specific to their country or ledger. Furthermore, the template field structure is now customizable, supporting the configuration of header, line, and footer fields to meet the requirements of various overseas banks. 5.When integrating with external master data systems, duplicate department names at the same hierarchy level could cause transmission failures to the Helios system. This update now supports configuring the system to allow duplicate department names to prevent these failures.

1.Some companies handle downstream payable settlements through invoice payment lines in Accounts Payable. Previously, the system did not support offsetting prepayments when these payable records were created; actual payments were initiated using the "Previous Invoice Payment" function. This update now supports offsetting prepayment directly on the previous invoice payment line. 2.For companies involved in European operations, cross-border transactions within Europe may be subject to reverse charge mechanisms. This release introduces a "Reverse Charge Flag" on international invoices. Additionally, the OCR service now supports the recognition of this flag, along with the corresponding reverse charge rate and amount. 3.Some clients requested that the same approver should not be notified multiple times for a single document during its approval process. This release introduces configurable duplicate notification rules, allowing the system to filter out repetitive notifications to the same person based on defined criteria. 4.For the overseas subsidiaries of some corporations, different countries require different payment submission file templates and formats. This release now supports setting the applicable organizational level for these offer files, enabling control so that different cashiers can only select templates specific to their country or ledger. Furthermore, the template field structure is now customizable, supporting the configuration of header, line, and footer fields to meet the requirements of various overseas banks. 5.When integrating with external master data systems, duplicate department names at the same hierarchy level could cause transmission failures to the Helios system. This update now supports configuring the system to allow duplicate department names to prevent these failures.

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.