EventFlow FE integrates external systems through explicit boundaries that separate source-system operations from fiscal execution. Integration transfers the information required for fiscal processing and returns the resulting fiscal state without transferring ownership of the fiscal lifecycle.
Integration Model
An integration connects an external business operation to EventFlow FE through a defined exchange boundary. The external system remains responsible for its source-domain operation, while EventFlow FE assumes responsibility for fiscal document processing once the required information is accepted into its execution boundary.
Exchange Direction
Integration Responsibilities
| Integration participant | Responsibility |
|---|---|
| External system | Owns the originating business operation and its source-domain data |
| Integration boundary | Exchanges the information required between the external system and EventFlow FE |
| EventFlow FE | Owns product-side fiscal document preparation and execution |
| SIFEN | Determines the fiscal authority outcome |
Inbound Integration
Inbound integration provides EventFlow FE with the information required to construct or initiate a fiscal document from an external operation.
| Information class | Integration purpose |
|---|---|
| Transaction reference | Relates the fiscal operation to its originating external operation |
| Issuer information | Identifies the fiscal issuer |
| Recipient information | Identifies the fiscal recipient when applicable |
| Items and amounts | Represents the economic content required for the fiscal document |
| Tax information | Provides the applicable fiscal classification |
| Supporting metadata | Carries additional information required by the applicable integration |
Inbound information becomes subject to EventFlow FE fiscal validation and document rules at the integration boundary.
Outbound Integration
Outbound integration makes the resulting fiscal state available to the originating or consuming system after processing by EventFlow FE.
| Information class | Integration purpose |
|---|---|
| Document identity | Identifies the fiscal document created or processed by EventFlow FE |
| Fiscal lifecycle state | Represents the document state reached within EventFlow FE |
| Authority outcome | Represents the result established by SIFEN when available |
| Fiscal references | Provides applicable fiscal identifiers associated with the processed document |
Integration Boundary
Connected systems exchange domain information with EventFlow FE without transferring ownership of their source-domain operations. Once accepted for fiscal processing, the resulting fiscal document follows EventFlow FE document and interoperability rules independently of the connected system’s internal implementation.
Related Documentation
- 02. System Scope & Boundaries — system responsibility boundaries.
- 03. Fiscal Document Model — fiscal information represented by EventFlow FE.
- 04. Document Lifecycle — lifecycle applied to fiscal documents.
- 05. SIFEN Interoperability — fiscal authority interoperability.
- 07. Operational Architecture — separation of fiscal and operational processing.