Hello!
We're excited to share an important update to how DTE documents are transmitted to Chile's tax authority, SII. This change brings a more efficient, traceable process that better serves organizations operating in Chile.
What's Changing?
The previous Chile Send DTE iFlow is being retired. In its place, we're introducing a modular design that distributes responsibilities across multiple flows, each with a clear purpose.
Key Improvements
- Better Traceability: Each flow has a distinct role, making it easier to identify and resolve issues if they arise.
- Multiple Sender Support: The system now uses the sender identification (RUT Emisor) to select the appropriate certificate for signing documents, enabling support for multiple senders within your organization.
- Smarter Token Management: The new process calls a Get Token flow, which retrieves and reuses valid tokens. This helps preventing seed exhaustion, a common challenge in high-volume environments.
- Long Signature Native Support: All signatures are now split automatically to avoid rejection when they exceed the tax authority's limit.
- Immediate Error Feedback: If a document isn't uploaded with status 0 (the tax authority's OK response), you'll receive an error message immediately. This allows you to identify rejection reasons, make corrections, and resubmit quickly.
The New Chile Upload DTE iFlows
- Chile Upload DTE – 1 Receive (/DTE/Receive): Receives XML from SAP S/4HANA and orchestrates signing and transmission.
- Chile Upload DTE – 2 Sign (/DTE/Sign): Handles document signing with the appropriate certificates and splits the resulting signatures.
- Chile Upload DTE – 3 Transmit (/DTE/Transmit): Manages environment routing (test/production) based on the NroResol XML tag, calls Get DTE Token iFlow to retrieve the token, transmits to SII and handles the response.
The Enhanced Chile Get DTE Token iFlow
Chile Get DTE Token (/eDoc/Chile/DTE/getToken & Chile/DTE/getToken): Retrieves and manages authentication tokens via Direct Process (/eDoc/Chile/DTE/getToken) or SOAP Request (Chile/DTE/getToken) with improved error handling.
Implementation Steps
To activate the new process, consulting teams need to update the SAP Document and Reporting Compliance: Electronic Documents for Chile integration package, deploy the new artifacts, and update the endpoint from /cxf/SendMultipleDTE to /cxf/DTE/Receive.
For more information, see the documents section on SAP Document and Reporting Compliance: Electronic Documents for Chile on SAP Business Accelerator Hub.
This modular approach represents a significant step forward in managing Chilean tax compliance more effectively.
Was this post helpful? Leave a like (kudo) and share the content with your colleagues. Feel free to leave feedback, comments, or questions in the space below.
Source link
