Eric Zavala

In the Talent module, when a time-off request is generated with a date that has previously been approved for another permission from the same user, the system allows you to overwrite the previous permission without notifying or warning you.

Example: There is a time-off request for August 20 for the type of absence of illness, and it has already been approved. If a 2nd time-off request is sent dated August 20, but with a vacation leave type, the system will allow the request to be made and approved.

The main idea is that there should be a warning message to the user at the time a 2nd request is sent for an already approved day, letting them know which day already has a prior permission, and asking if they want to overwrite it.

When using bills of exchange, the cancellation process cannot be carried out when the post-dated check has been registered in a previous accounting period that has already been closed. Therefore, the cancellation of a post-dated check in the Issued status is required in the current accounting period and is not sent to the initial registration date of the document.

The process of correction or cancellation of this Bill of Exchange can generally occur because the client decides on another form of payment or because the check presents an error in its record.

When registering a delivery note or customer invoice in Dynamics 365 F&O, additional information must be provided based on the document class ID when the LATAM localization feature is used for Chile and Colombia in order for the documents to be stamped.

• Delivery Note (Chile):

Additional data, such as shipment ports, type of transfer and transportation types, must be specified by default based on the document class ID. This is essential for issuing delivery notes sent to the Chilean government portal. The following additional information must be included:

• Exceptional Transfer Issuer Code
• Type of Transfer Indicator
• Type of Transportation

• Customer Invoice Generation (Chile and Colombia):

The functionality to automatically register invoices through the standard batch job process must be utilized. Specific additional data is required for each country:

• Local customer invoice: Indicate the type of service, if applicable.
• Foreign or export invoice: Indicate the sales modality, Ports of shipment and Ports of destination.
• Credit/debit notes: Indicate the reference code and document type.

Tax Invoice (Chile and Colombia)

The following fields must be manually completed by the user:

• Tax Invoice for Domestic Customer (Chile): If applicable, indicate the type of service for which the sales invoice is generated.
• Credit Note (Chile and Colombia): Indicate the reference of the document being canceled.
• Export Tax Invoice (Chile): Indicate the type of export and, if applicable, any document to be referenced.
• Debit Note (Chile): Indicate the reference of the document being canceled or corrected.

In all the above cases, the document class ID applicable to the transaction must be indicated, which can be done through the customer/vendor set.

If the company fails to issue invoices to customers in compliance with local government regulations, it may face the following additional business impacts:

• Legal Risks: Potential lawsuits or legal action due to non-compliance.
• Regulatory Restrictions: Suspension of operations or inability to transact with government entities.
• Damage to Reputation: Loss of credibility with clients, suppliers, and stakeholders.
• Disrupted Cash Flow: Delayed revenue collection affects financial stability and investments.
• Loss of Market Share: Clients may switch to competitors that can fulfill regulatory requirements.
• Audit Complications: Increased scrutiny during financial audits and potential challenges in justifying operations.
• Operational Bottlenecks: Manual intervention may slow down other critical business processes.
• High Employee Turnover: Frustration from repetitive manual tasks could lead to workforce dissatisfaction and attrition.
• Missed Growth Opportunities: Reduced ability to expand operations in new regions due to compliance gaps.
• Technology Investment Loss: Existing system investments may become underutilized or require costly adjustments.
• Higher Training Costs: Continuous re-education of staff on evolving manual processes.
• Increased Error Rates: Manual processing inherently carries a higher risk of mistakes, resulting in rejected invoices or corrections.
• Delayed Client Deliverables: Invoicing delays may postpone project or product delivery commitments.

In D365 Finance, when the standard Mexican Localization is enabled, the Journal Voucher form displays the required field to specify the UUID value for each line (CFDIUUID_MX). However, when using the Excel Add-In to Read/Write over the LedgerJournalTable this field is not available.

This prevents the UUID field from being modified in bulk and quickly through the corresponding data entity, increasing user operation times by requiring them to manually specify this field for each line created, and leading to possible errors.

When generating an Intercompany Customer Invoice from an Intercompany Expense Report, the Sales Tax Group value is inherited from the default configuration of the intercompany customer instead of using the one specified on the expense report line.

This behavior prevents customers from processing intercompany expense reports smoothly, as the posting does not correctly reflect the sales taxes specified in the expense report. Customers must split their expenses based on whether they are intercompany or not, which increases the manual workload both for users and for the accounts payable team.

This behavior does not allow customers to process intercompany expense reports smoothly as the posting is not correct for the sales taxes specified in the expense report. Customers are required to split their expenses based on if they’re intercompany or not and this increases the manual workload from the user side and from the accounts payable side.

The suggestion is to add a new parameter in the Intercompany Accounting Configuration screen that allows customers to choose whether the Sales Tax Group used on the Intercompany Customer Invoice should be taken from the default value configured for the intercompany customer, or from the Sales Tax Group specified in the corresponding Intercompany Expense Report line.

In Finance, when using the Mexican localization, it is not possible to parameterize the way the name of the electronic invoice PDF is created. Since invoices are sent to the client, a suggestion for parameters that could be included in the name is the following:

Issuer's RFC – The tax identification of the company issuing the invoice.

Invoice number – The unique invoice folio.

Issuance date – In YYYYMMDD format (year, month, day).

Document type – May include labels such as Invoice, Credit Note, etc.

File extension – Usually .pdf

For example, an electronic invoice file might be named: MX123456789-Invoice-20250606.pdf

Currently, when using the email functionality for electronic invoice XML and PDF files in the Mexican Localization, two separate emails are generated for each file. Since most clients process both XML and PDF files for saving to their databases, generating two separate emails for each file can cause confusion.

Ideally, both XML and PDF files could be sent in a single email.

Currently, when using the Mexican Localization feature, it is not possible to download more than one e-invoice PDF file in bulk. Since it is very common for customers to request the sharing of e-invoice history, the only way to obtain them is to download each invoice individually.

Ideally, there would be a menu where it would be possible to specify the range of e-invoices to download, either by ID or by customer account, to facilitate the necessary effort.