EVENTFLOW FE · TECHNICAL DOCUMENTATION · 05
SIFEN Interoperability
Defines the fiscal interoperability boundary between EventFlow FE and Paraguay’s SIFEN environment, including submission, consultation, response handling and fiscal result representation.
Interoperability boundary
EventFlow FE executes the product-side fiscal integration; SIFEN provides the authoritative fiscal outcome.
EventFlow FE prepares the electronic fiscal representation, applies the required document-integrity operations, performs the applicable SIFEN interaction and records the resulting authority response as product state.
Interoperability stages
Responsibility model
| Operation | EventFlow FE | SIFEN |
|---|---|---|
| Fiscal document preparation | Owns product-side preparation | Does not prepare the product document |
| Electronic representation | Generates the representation required for interoperability | Receives the applicable fiscal representation |
| Digital signature and QR | Executes the configured document-integrity stages | Consumes the resulting fiscal document according to applicable requirements |
| Submission | Initiates the applicable fiscal interaction | Receives and processes the submitted document |
| Fiscal decision | Records and represents the returned outcome | Provides the authoritative fiscal result |
| Result consultation | Queries when the applicable interaction requires subsequent result retrieval | Provides the available authority result |
Synchronous interaction
In the synchronous interaction path, EventFlow FE submits the applicable electronic fiscal document and processes the response returned for that interaction. The returned information is recorded according to the fiscal lifecycle represented by the product.
Asynchronous interaction
In the asynchronous interaction path, submission and final result retrieval are separate operations. EventFlow FE records the submission context and subsequently queries the authority result through the applicable consultation path.
Completion of the submission operation does not by itself imply fiscal approval.
Response handling
Authority responses are processed as externally derived fiscal results and represented within EventFlow FE. Product states such as APROBADO, RECHAZADO and OBSERVADO represent the corresponding authority outcome within the product lifecycle.
The state semantics are specified in 04. Document Lifecycle.
Transport and protocol failures
A transport failure is not a fiscal rejection.
A communication or protocol failure prevents the applicable interoperability operation from completing normally. EventFlow FE records that condition separately from authority outcomes so that transport state is not interpreted as a fiscal decision.
Result reconciliation
Where fiscal processing requires later consultation, EventFlow FE reconciles the available authority result with the fiscal state represented by the product. A reconciliation failure is recorded separately from both transport failure and fiscal rejection.
Interoperability invariants
- Electronic document generation precedes fiscal submission.
- The configured document-integrity stages precede submission through the applicable SIFEN path.
- Submission completion is distinct from fiscal approval.
- A transport or protocol failure is not an authority rejection.
- Asynchronous submission may require subsequent authority consultation before a final fiscal result is available.
- Fiscal outcomes represented by EventFlow FE derive from the authority interaction.
- Runtime processing does not initiate or replace SIFEN fiscal transactions.
Document integrity boundary
Digital signing and QR generation belong to the fiscal document preparation path preceding interoperability. Their security and integrity properties are specified in 06. Security & Document Integrity.
Production validation
End-to-end fiscal interoperability has been validated in the SIFEN production environment through document generation, digital signing, QR generation, submission and an approved fiscal result. The corresponding engineering evidence is documented in 12. Production Validation.