How the integration works?

How the Integration Works

The integration between SAP and Brinta Filing is designed to be simple, modular, and secure. Brinta receives structured data extracted from SAP systems through prebuilt ABAP programs (“extractors”). These extractors collect fiscal, accounting, and master data, which is then transmitted to Brinta’s cloud environment for validation, reconciliation, and filing.

The entire process can be divided into three main layers: Extraction (SAP), Transmission (Middleware), and Processing (Brinta).

Extraction Layer (SAP)

At the SAP layer, Brinta provides a set of ABAP programs grouped under the namespace ZCOI_INT_BRINTA. These programs read from standard SAP tables and functions, collecting the data required for compliance reporting. No modifications to SAP standard objects are needed.

Each extractor focuses on a specific business domain:

Extractor	SAP Modules	Purpose
ZCOI_INT_BRINTA	SD / FI	Outbound fiscal documents (e.g. NF-e, invoices, service billing)
ZCOI_INT_BRINTA_BP	MM / FI	Vendor and partner master data
ZCOI_INT_BRINTA_BL	FI / CO	Trial balance and accounting balances
ZCOI_INT_BRINTA_PC	FI	Chart of accounts and ledger structure
ZCOI_INT_BRINTA_PRODUCT	FI-AA	Fixed assets and related data
ZCOI_INT_BRINTA_EA / CEPLUS	FI	Accounting entries and complementary adjustments

When executed, each extractor:

Reads relevant data from SAP standard tables (such as BKPF, BSEG, J_1BNFDOC, MARA, MARC).
Filters records based on the input parameters (company code, posting date, fiscal period, document type, etc.).
Prepares a structured dataset in JSON or XML format, depending on middleware configuration.
Stores a copy of the run in a Brinta control table (Z*) for audit and reprocessing.

This logic ensures that SAP remains the system of record while Brinta receives only the data required for tax compliance.

Transmission Layer (Middleware)

After data extraction, the information is transmitted securely to Brinta’s API layer. This step is typically handled by SAP Cloud Platform Integration (CPI) or an equivalent middleware (e.g. SAP PI/PO, Boomi, MuleSoft).

The middleware performs:

Authentication with Brinta using an integration token stored in SAP (ZBRINTA_KEY)
Secure HTTPS communication (TLS 1.2+)
Optional data transformation or enrichment, if required by customer-specific mapping
Message orchestration and retry logic in case of temporary connectivity issues

Each middleware message contains:

A unique run ID for traceability
Payload in JSON format with key fields such as company code, document number, tax type, and posting period
Metadata for error handling and monitoring

All middleware transactions can be monitored directly from the CPI dashboard.

Processing Layer (Brinta Cloud)

Once received by Brinta, the data undergoes validation, enrichment, and classification according to local tax rules. The platform then:

Performs automated reconciliation between SAP source data and filing requirements
Generates tax calculation and reporting files (e.g. SPED, EFD, DCTFWeb, etc.)
Produces digital payment slips or XML submissions as required by the tax authority
Submits filings electronically to the government’s systems

All processed data is available in Brinta’s interface for audit and review by tax or accounting teams.

Integration Characteristics

One-way data flow: SAP → Brinta (no updates to SAP master data)
Event-driven or scheduled execution: Jobs can run manually or on predefined schedules
Customizable extraction logic: Parameterization available per company code, fiscal year, or tax type
Traceability: Each extraction and submission is logged for audit purposes
Resilience: Failed messages can be retried automatically via middleware or manually via SAP

Error Handling and Recovery

If an extractor run fails or a message cannot be delivered:

The error is logged in the Brinta control tables (Z*)
The record remains flagged for reprocessing
The job can be re-executed for the affected range without duplicating successful records
CPI will retry delivery according to its configuration (typically three attempts before escalation)

For complete guidance on error recovery and log reprocessing, please contact [email protected].

Key Benefits

No impact on SAP core objects or upgrade paths
End-to-end traceability between SAP document and tax submission
Rapid implementation (average 1 month for deployment and testing)
Secure communication and compliance with data privacy standards

For access to the extractor packages, CPI configuration, or middleware mapping templates, please contact: [email protected]