Skip to main content

The Spanish version is the authoritative reference. View in Spanish

General Process Flow

Below is the complete journey of a document, from its generation in Oracle through its final status being reflected back in Oracle.

Step 1 · XML Generation in Oracle​

  • Trigger event: issuance of an electronic document in Oracle.
  • Oracle generates a custom XML.
  • The file is stored in a path defined on the Oracle server (/Localhost/ERP/, depending on each customer's environment).
  • The file name follows the format: 01-M001P001-00000031.xml

Step 2 · Canonical Extraction​

  • Responsible service: Gosocket Canonical Extractor.
  • Frequency: every 5 minutes (configurable).
  • Protocol: HTTPS.
  • The extraction endpoints are segmented by document type and by environment — see the detail in Extraction endpoints.

Process:

  1. Checks for the existence of new files.
  2. Downloads the file.
  3. Marks the file as processed.

Step 3 · XSLT Transformation #1 (Oracle → DTE)​

  • Input: XML generated by Oracle (step 1).
  • Output: XML in Gosocket's DTE format.
  • Validations applied:
    • XML structure.
    • Mandatory fields.
    • Tax format.
    • Totals.
ScenarioResult
SuccessThe flow continues to step 4.
ErrorThe error is logged together with the corresponding technical log.

Step 4 · DTE Submission to the Gosocket API​

  • Endpoint: https://developers-sbx.gosocket.net/api/v1/Document/SendDocumentToAuthority
  • Method: POST
  • Headers:
    • Authorization: Basic auth
    • Content-Type: application/xml

Internally, Gosocket performs: document reception, structural validation, and the XSLT #2 transformation.

Step 5 and 6 · XSLT Transformation #2 and DGI Validation​

  • Input: DTE XML (obtained in step 3).
  • Transformation: XSLT #2, which converts the DTE into the official format required by the DGI.
  • The DGI receives the document, processes it, and responds with a status code. See the detail in Response codes.

Step 7 · Recording in the Inbox​

Regardless of the outcome (approved or rejected), the document is recorded in the Gosocket Inbox Portal, storing:

  • Original XML (Oracle).
  • DTE XML.
  • DGI XML.
  • Document status.
  • Submission date.
  • Generation code.
  • Reception stamp.

Step 8 · Notification Webhook​

Gosocket notifies Oracle of the result via a webhook. The notification endpoints are also segmented by document type and environment — see Notification endpoints, which also shows an example of the payload sent.

  • Method: POST
  • Security: token validation, IP whitelist, and SSL certificate.

Step 9 · Update in Oracle ERP​

Oracle receives the webhook notification and:

  • Updates the document status.
  • Marks the document as Approved, Rejected, or Technical Error.
What happens if something fails along the way?

Review the XSLT Transformations and Error Handling sections to learn about error scenarios and recovery recommendations.