Does Openi integrate with my system and my version?

The catalog shows the systems Openi works with, but compatibility depends on the version, the active modules and the environment. That's why every integration goes through a technical assessment that confirms objects, actions and method before onboarding.

Which data can be read or updated?

Typically we read master data (chart of accounts, cost centers, companies, customers and suppliers) and open invoices, and we send payables and receivables, financial and journal entries, source documents and settlements. What gets read and what gets updated in each system is defined object by object during onboarding.

Does the integration work both ways?

It depends on the object and the system. Each operation has one direction: the chart of accounts is usually only read from the ERP, while an invoice settlement is sent to the ERP. Both directions apply only when the system supports reading and updating that object.

How often does data sync?

Per event, when the source reports what happened, or in scheduled loads at set times. Frequency is chosen per integration and per object, based on what each system offers. Not every connection is real time.

Can systems without an API be integrated?

Yes, when the system imports and exports structured files or when the architecture allows authorized database access. The method is defined in the technical assessment. Updates go through the layouts and services the system accepts, not by writing directly to ERP tables.

How are mappings and rules defined?

With your team, during onboarding: which source codes map to which accounts, categories and cost centers, which conditions release each action and what becomes an open item. The Openi team configures and validates it all with your operation's data.

Can processes include approvals?

Yes. Steps that need review are routed to the right people, and the flow continues based on their decision. If approval happens in the ERP or another system, it stays there, and Openi waits for the response to continue. Bank payment authorizations happen at the bank.

How do I track failures and open items?

Each run shows what was received, processed and rejected, the step where something stopped and the destination system's response. A record that was sent only counts as done once the destination confirms processing.

How does reprocessing work, when available?

A record with an open item doesn't move on until it's fixed. Once corrected, for example with an adjusted mapping, it rejoins the flow at the step where it stopped. How each integration tracks what has already been sent, so records aren't duplicated, is defined during onboarding based on what the destination system offers.

Can I integrate in-house platforms and databases?

Yes. Internal platforms, back offices and proprietary databases connect through API, events, files or an authorized database connection, after a technical assessment. Operational events are turned into financial records and follow the same rules.

How involved does my team need to be?

Finance and accounting describe processes and rules, validate mappings and handle exceptions. IT shares systems and versions and grants the access defined in the project. The Openi team runs the assessment, the configuration and the validation.

ERP integration and workflows

The routine today

The data lives in your systems.The work lives between them.

Exporting data, fixing fields, checking master records and chasing approvals keeps the operation running, but it eats time and leaves every handoff dependent on manual work.

01
Data that has to be copied
Information leaves one system and gets keyed or imported into another.
Export the statement, build the spreadsheet, import it into the ERP.
02
Different structures
Codes, dates, categories and cost centers have to be adjusted before anything can be processed.
Replace “Sales São Paulo” with CC-014 across 300 rows.
03
Processes that stall between teams
Approvals and open items travel through messages and spreadsheets.
“Did anyone approve the Atlas invoice?”
04
Failures that are hard to trace
The team has to work out whether the problem happened at the source, in the integration or at the destination.
The entry left the spreadsheet. Did it make it into the ERP?

Banks
Export and import by hand
In-house platform
Fix codes by hand
ERP
Check and rekey by hand
Accounting system

Illustration of systems without integration.

Integrated flow

From the source eventto the update in the destination system.

Openi connects every step of the process: it receives data, organizes it, applies rules and routes the actions you defined. The flow keeps sight of what is done and what needs a person.

A flow can start with

Bank transaction
Statement imported
Tax document received
Invoice created in the ERP
In-house platform event
File received
Scheduled time

A matched receipt becomes a settled invoice in the ERP.

TriggerReceipt identifiedR$12,480.00 Pix on the Itaú statement
AutomaticInvoice looked upAccounts receivable in the ERP · customer and amount
AutomaticData matchedAmount, interest, discount and CNPJ validated
RuleRules appliedDifference within the set tolerance
SendSettlement requestedInvoice 4471 sent to the ERP
ConfirmationProcessing confirmedThe ERP recorded the settlement · 9:43 AM

Exception · Inconclusive matchTwo possible invoices for the same amountSent for review. Once someone decides, the flow resumes at the rules.

TriggerReceipt identifiedR$12,480.00 Pix on the Itaú statement
AutomaticInvoice looked upAccounts receivable in the ERP · customer and amount
AutomaticData matchedAmount, interest, discount and CNPJ validated
Exception · Inconclusive matchTwo possible invoices for the same amountSent for review. Once someone decides, the flow resumes at the rules.
RuleRules appliedDifference within the set tolerance
SendSettlement requestedInvoice 4471 sent to the ERP
ConfirmationProcessing confirmedThe ERP recorded the settlement · 9:43 AM

Starting event: Credit received in an account connected through Open Banking or a direct integration
Systems: Bank, Openi and ERP
Data: Transaction, open invoices, customer, interest and discounts
Rule: Match on amount, document and customer, within a set tolerance
Result: Invoice settled and confirmed by the ERP
Exception: An inconclusive match or a receipt with no invoice goes to review

Bank and crypto connectivity Reconciliation

Steps vary with the process configured: not every integration categorizes, reconciles or asks for approval.Illustrative process demo.

Connectors and compatibility

Integrations that respectyour company's environment.

Connect ERPs, accounting systems, internal platforms and operational databases through whichever method each environment offers.

Browse integrations (Portuguese)

APIs: Reading and sending data through the services the system exposes.
Events and webhooks: Flows triggered when the source reports an event.
Structured files: Processing the import and export layouts your company already uses.
Database connections: Authorized access to the data defined in the project, within the environment's architecture.
Custom integrations: Set up for specific needs and in-house systems, after a technical assessment.

Updates go through the services and layouts the destination system offers. Writing directly to ERP tables is not standard practice.

26 systems in the catalog

SAPERPIn production
TOTVS ProtheusERP
OracleERP
Microsoft DynamicsERP
SeniorERP
SankhyaERP
MXM SistemasERPIn production
OmieERP
Conta AzulFinancial management
BlingERP
TinyERP
OdooERP
BaseFinancial management
SuperlógicaFinancial management
NiboFinancial management
QuickBooksFinancial management
TOTVS RMERP
TOTVS DatasulERP
LILinxERP
CIGAMERP
BennerERP
InforERP
GestãoClickERP
vhsysERP
eGestorERP
SIG 2000ERP

Integration profile

Objects: Customers and suppliersPayables and receivablesChart of accounts and cost centersFinancial entries
Reads and actions: Reads master data and invoices; sends payables, receivables, entries and settlements within scope
Method: API, structured files or database, depending on version and environment
To activate: Version, active modules, integration credentials and the layout of each object
In production: SAP with Riocard Mais and Reserva; MXM Sistemas with Unisuam and SolarGrid.

A logo in the catalog does not mean compatibility with every module and version of that system. The objects, actions and method of each integration are confirmed in the technical assessment.

See all integrations (Portuguese)

Beyond internal systems

Banks and tax documents reach the ERP too.

Accounts connected through Open Banking, for European and Brazilian banks, and direct integrations, plus invoices captured in Openi, flow to the ERP through the same layer.

Bank and crypto connectivity Tax document issuing and capture Document management Reconciliation

Import tax documents in the ERP
Create invoices and entries in the ERP
Reconcile transactions and invoices in the ERP
Settle reconciled invoices in the ERP

Sync and transformation

Master data, invoices and entriesconnected across systems.

Use your operation's own structures to organize processing and keep the data each step of the flow needs within reach.

Data synced between the ERP and Openi, with the direction of each operation
Data	Source → destination	Reference	Operation	Update	Status
Chart of accounts	ERPtoOpeni	ERP	Read	Scheduled load	Synced
Cost centers	ERPtoOpeni	ERP	Read	Scheduled load	Synced
Companies and units	ERPtoOpeni	ERP	Read	At onboarding and in loads	Synced
Customers and suppliers	ERPtoOpeni	ERP	Read	Scheduled load	1 without a match
Payables and receivables	ERPtoOpeni	ERP	Read	Every load	Synced
Documents and references	OpenitoERP	Tax document capture	Sent	With the invoice or entry	Confirmed at destination
Financial and journal entries	OpenitoERP	Your operation's rules	Created	Per event or batch	Sent · awaiting response
Invoice settlement	OpenitoERP	ERP	Updated	After reconciliation	Confirmed at destination

Chart of accountsERPtoOpeni
Read · Scheduled load · Reference: ERP
Synced
Cost centersERPtoOpeni
Read · Scheduled load · Reference: ERP
Synced
Companies and unitsERPtoOpeni
Read · At onboarding and in loads · Reference: ERP
Synced
Customers and suppliersERPtoOpeni
Read · Scheduled load · Reference: ERP
1 without a match
Payables and receivablesERPtoOpeni
Read · Every load · Reference: ERP
Synced
Documents and referencesOpenitoERP
Sent · With the invoice or entry · Reference: Tax document capture
Confirmed at destination
Financial and journal entriesOpenitoERP
Created · Per event or batch · Reference: Your operation's rules
Sent · awaiting response
Invoice settlementOpenitoERP
Updated · After reconciliation · Reference: ERP
Confirmed at destination

Each row has one direction. When data also flows back the other way, that shows up as its own operation. Updates happen per event or in scheduled loads, depending on the integration.Sample data.

Every system has its own format.The data has to arrive consistent.

Map fields, match codes and adjust structures so the destination system can process the data, following your operation's rules.

Matching between source and destination fields
Mapping of accounts, categories and cost centers
Standardized dates, amounts and identifiers
Required-field validation
Linking of supplementary data
Handling of incomplete or incompatible data

Data receivedTreatmentSent to the ERP

Cost centerSales São PauloSaved mappingCC-014
CategoryBank feesMatching ruleAccount in the client's chart
Date11/06/2026Format adjustment2026-11-06
AmountR$1,234.50Number standardization1234.50
CNPJ (Brazilian company ID)12.345.678/0001-90Identifier without mask12345678000190
SupplierAtlas ServicesValidationPending review

Sample data.

Transforming is not categorizing. A mapping converts a code that already has a match. When the data has no account yet, like a statement line, Openi's categorization and reconciliation engines take over.

Categorization Reconciliation

Rules and triggers

Define what starts the processand what happens next.

Build flows around events, schedules and conditions in your operation. Each rule sets which data gets checked, which action can go ahead and when an open item should reach the team.

TriggerThe event that starts the flow.
ConditionThe criterion that sets the path.
ActionWhat gets executed.
ExceptionWhat happens when the flow can't continue.

WhenA receipt is identified
IfThe match and validations pass
ThenRequest the invoice settlement in the ERPOtherwiseSend for review, with the candidate invoices

A demonstration of how a process is designed. Each operation's rules are defined and configured with the Openi team during onboarding.

Approvals

Automate the processand keep the decision points.

Route the steps that need review to the right people and continue the flow based on the recorded decision.

01Operational approvalA person validates a record before it moves on, such as a payable.
02Action authorizationA person releases an action in the flow, such as sending a batch to the ERP.
03Destination confirmationThe destination system reports that it processed what it received. Not a human decision.
04Bank authorizationFor payments, the account holder authorizes at the bank. Payments through Brazil's Open Finance are confirmed one by one.

When approval happens in the ERP or another system, it stays there. Openi waits for that system's response before continuing the flow.

Payable · Atlas Services

NF-e 000.318.442 · Due 11/20/2026 · Branch 02

R$18,400.00

Awaiting approval

Owner: Finance management · Branch 02
Reason: First payment to a newly registered supplier: the process rule requires approval before recording.

History

9:12Document received
9:13Data extracted and validated
9:14Approval rule applied
9:14Routed to the owner

Approved

The payable goes to the ERP and the flow continues until the record is confirmed.

Changes requested

The record comes back with the owner's comment and resumes the flow once fixed.

Sample data.

Monitoring

Know what was processedand where the flow needs attention.

Track runs, system responses and open items to pinpoint problems and keep the operation moving.

Today's runs4 flows

Run at 9:30

Journal entries

Openi → Accounting system

Received: 54
Processed: 51
Needs attention: 3

Cost center not recognized by the destination

Step: Delivery to destination
Destination response: CC-019 does not exist for company 02.

History

9:2854 entries built
9:29Cost center mapping applied
9:30Batch sent to the accounting system
9:3151 accepted · 3 rejected by the destination

Review the mapping before resending: “Marketing Rio” points to CC-019, which doesn't exist in company 02.

A record with an open item doesn't move on until it's fixed. Once corrected, it rejoins the flow at the step where it stopped.Sample data.

ReceivedThe record arrived from the source.
ValidatingData, mappings and rules being checked.
Awaiting approvalStopped at a decision point.
SentDelivered to the destination, not yet confirmed.
Confirmed at destinationThe destination system processed the record.
Needs attentionNeeds a fix or a decision to move on.

Sent is not done: a record only counts as updated once the destination system confirms processing.

Onboarding

Start with the systemsyour company already uses.

The integration starts from your environment: the systems, versions, processes and rules already in place. Timing depends on the systems and processes involved.

1MapSystems, versions, modules, processes and what each flow needs to read and update.
2DefineObjects, integration methods, mappings, rules and approval points.
3Configure and validateConnectors and flows tested with your operation's data, through to confirmation at the destination.
4Follow upRuns, open items and rule adjustments, day to day.

Who's involved

Finance, accounting and operations
- Describe current processes and rules
- Validate mappings, accounts and cost centers
- Define owners and approval points
- Handle day-to-day exceptions
IT
- Share systems, versions and environment
- Grant the credentials and access defined in the project
- Point to the available layouts, services and events
- Follow the technical validation
Openi team
- Assess compatibility and choose the method
- Configure connectors, transformations and rules
- Validate flows through to confirmation at the destination
- Support the operation and its adjustments

Customer stories

How the integrations workin real operations.

See all customer stories

Crypto payments

Deposits and withdrawals reconciled and posted to the books

Open Finance
Categorization
Reconciliation
Athenas

Read the full story

Integrated environment: Athenas, the company's accounting system, with statements from hundreds of accounts through Brazil's Open Finance.
Process: Crypto deposits and withdrawals that turn into Pix payments (Brazil's instant payments), fees and transfers in reais, each to be posted to the right GL account.
What Openi runs: Categorizes and reconciles every transaction and exports the entries to Athenas through the API.
How the team follows it: Entries logged by account, date and cost center; any unidentified transaction goes to review.

Proven results

transactions processed: 10M+
of accounting entries categorized automatically: 98%
saved every month on statements and data entry: 80 h
estimated payback: 6.5 months

FAQ

Before you integrate.What people ask before signing up.

Didn't find what you were looking for?

Talk to a specialist and get your answer straight from our team.

Talk to a specialist

No. The ERP stays your system of record, within the architecture defined for your company. Openi adds integration, processing and automation around the processes you already run.

Demo

See Openiin your operation.

Leave your details. An Openi specialist will get back to you by email.

You leave your details
It takes less than a minute.
A specialist gets in touch
To understand your banks, your ERP and what takes up the most time today.
You see Openi at work
Reconciliation, categorization and reporting in cases like yours.

Connect your ERP to the processesthat run your operation.