Operational flow

The Opera integration is composed of JSON reception, fiscal transformation, tax submission, and structured response to the ERP.

1.1 Transaction reception

• Protocol: HTTPS
• Method: POST
• Format: JSON
• Authentication: Basic Auth

Oracle Opera - Hospitality Cloud sends the complete invoicing transaction information to API-FLIP (JSON payload).

1.2 Structural transformation

API-FLIP performs the following steps:

1. Validates the JSON structure.
2. Converts the JSON into an intermediate XML (DTE-GUF).
3. Applies the transformation through an XSLT file.
4. Generates the DTE-GUF with the fiscal structure required by the country.

This transformation enables:

• Multi-country adaptability.
• Independence from the ERP format.
• Controlled versioning according to each regulation.

1.3 Submission to the tax authority

• API-FLIP invokes the conventional issuance API (SendDocumentToAuthority).
• During this step, the following is performed:
  • Digital signature (if applicable).
  • Final validation.
  • Submission to the tax authority.
• A response is obtained for:
  • Authorization
  • Rejection
  • Observation

1.4 Folio assignment

Once the DTE has been generated and sent to the SendDocumentToAuthority API:

• The API invokes an internal folio service (Gestor de Folios).
• Availability is validated.
• A unique fiscal folio is assigned.
• The DTE is updated with the corresponding folio.

This step guarantees correlativity and tax control.

1.5 Response to the ERP

API-FLIP builds a response in JSON format that includes:

• Operation status (AUTHORIZED / ERROR).
• Tax code.
• Descriptive message of acceptance or observations, depending on the tax authority.
• Assigned folio.
• Fiscal identifier (UUID / CAE / TrackID, depending on the country).
• Authorization date.

You can see a complete example of this response in Response example.