By department · Reconciliation

Reconciliation is manual. The error only shows up months later.

Abstra matches bank statements, cards, acquirers and marketplaces against your ERP automatically: it handles refunds and discrepancies, writes off and leaves an audit trail.

Book a reconciliation demo See reconciliation processes

The reconciliation pipeline

1
Ingest
OFX, CSV, Open Banking, gateway and acquirer report
2
Match
Rules by date, amount, tax ID and customer mapping
3
Handle
Refund, chargeback, discrepancy and MDR validation
4
Write off
ERP write-back and accounting entry with a log

Exceptions do not block: a low-confidence match goes to human approval, then returns to the flow. Underneath it all: audit, closed period and dedup.

Workflow example · statement and SAP into reconciliation, with refund, chargeback and exception · 100% customized per customer

Read statement / OFXbank, Open Banking, gateway

Automatic reconciliationmatches amounts, dates and identifiers

Match →→ Exception

Read SAP open itemspostings and open status

Confirmed matchwrite-off or status per the rule

Flag refund / chargebackown rule; otherwise, review

SAP updaterecords the decision and keeps the history

Exception reviewapproves, adjusts or reclassifies

back to SAP

Dashboard example · real time, connected and 100% customized

Reconciliation, discrepancies and SAP updates

Illustrative data for demonstration.

automatic match

last 30 days

Lines this month

128 mil

Auto-reconciled

93%

Discrepancies handled

842

Refunds / chargebacks

126

Awaiting review

ERP updates

119 mil

Month pipeline

From statement to update

01
Ingested
128 mil
statement + ERP open items
02
Auto-reconciled
93%
automatic match rate
03
Discrepancies
842
need specific handling
04
In human queue
58
waiting on review now
05
ERP updates
119 mil
write-offs and status with trail

Mix

How lines closed this month

Auto match93%
Mismatch4%
Refund / CB2%
In queue1%

7-day volume

Automatic vs. human touch

AutoHuman

Mon

Tue

Wed

Thu

Fri

Sat

Sun

Live queue

Items that need attention

BK-441
Itaú · tax ID 12.345 · R$ 18,420
Mismatch
Statement amount vs. 2 SAP open items totaling R$ 18,100
AI suggestion · Match to the 2 open items · R$ 320 gap as a fee · approve or suggest another match
3h 20m
CB-088
GetNet · chargeback
Refund
Chargeback with no mirror open item in SAP
AI suggestion · Create a refund in SAP and clear the original open item · approve or reclassify
1d 2h
PX-219
Bradesco PIX · multi-deposit
Review
3 deposits that need to sum to a R$ 9,800 target
AI suggestion · Group the 3 PIX into the R$ 9,800 open item · approve or split to another target
42 min

What automatic financial reconciliation is

Automatic financial reconciliation is the pipeline that ingests statements, cards and acquirers, applies matching rules, handles refunds and discrepancies and writes off in the ERP with an audit trail. With Abstra, match rules and the multi-bank/multi-entity view are customized per customer: mapping, tolerance and write-back follow your operation.

Proof in reconciliation

Less spreadsheet. More accurate write-off.

Daily receivables reconciliation in the ERP

In the Clinicorp case, daily receivables reconciliation in the ERP matches bank statements, payments and invoices automatically, with receivable write-offs and operational reports.

Automated financial reconciliation

In the GF Pneus case, automated financial reconciliation routines match transactions, write off in the ERP and provide ongoing operational follow-up.

If your reconciliation looks like this, we fix it.

“I match the vendor spreadsheet against revenue by hand and only see the discrepancy weeks later.”

“The statement comes in OFX, the control sheet is in Excel: hours matching tax ID and amount one by one.”

“Multiple banks and multiple tax IDs; no one has a consolidated view of the group.”

“Refunds and chargebacks come in and no one reconciles them; money disappears along the way.”

Matching and group

Customized matching rules and a multi-bank/multi-entity view.

Every group has different banks, gateways and mappings. We build matching and write-off the way finance already closes the month, with per-entity isolation and a consolidated trail.

Rules by amount, date and tax ID

Tolerance, multiple deposits that sum to a target and customer mapping are codified. Low-confidence matches go to human approval.

See process

Multi-bank and multi-entity

Open Banking, OFX and acquirer reports across separate accounts, with a consolidated group view and auditable write-back per entity.

See process

Gateway, card and refunds

Charges, payouts, chargebacks and MDR in the same pipeline, with idempotent ERP write-off and only discrepancies in the queue.

See process

100% shaped per customer

Closed period, competence lock and audit evidence follow your house governance, not a fixed template.

Where to automate first

How automatic bank reconciliation in the ERP works

Bank, card, payments, close and audit. Start with the process that blocks the month most.

Accounting reconciliation

Statement and ledger in the same match, with rules and a trail for close.

See process

Payment reconciliation

Gateway and bank against open items, with write-off and dedup.

See process

Month-end close

Open items, closed period and a consolidated view before closing the month.

See process

Financial reports

Auditable output after the match: what matched, what was left and why.

See process

Balance sheet analysis

Multi-entity consolidation and group view without a parallel spreadsheet.

See process

Audit and compliance

Match trail, period lock and evidence for audit.

See process

Abstra vs Excel, ERP bank module and BI

What changes when matching must write off in the ERP and truly close multi-account.

Criterion	Abstra	Excel / spreadsheet	ERP bank module	BI / dashboard
Customized matching	Rules by tax ID, tolerance and multi-deposit	VLOOKUP and manual review	Vendor’s fixed rules	Visualizes, does not write off
Multi-bank / multi-entity	Consolidated ingestion with trail per entity	Separate tabs, hard to audit	One account per instance	Aggregates after manual close
Refunds and chargebacks	Dedicated rules in the same pipeline	Forgotten manual row	If the ERP supports it	Out of operational scope
ERP write-back	Idempotent write-off and entry with log	Manual typing or import	Native, locked to the module	Does not write to the ERP
Best for	Groups with many banks, gateways and house rules	Low volume, small team	One bank, one ERP, simple operation	Post-reconciliation analysis

Integrations

Connected to banks, gateways and the ERP reconciliation already uses.

OFX, Open Banking, Stripe/Pagar.me, acquirers and ERP write-back. Spreadsheet, RPA or agent when there is no API.

200+ connectors and custom integrations

SAP

ERP

Itaú

Banks

Microsoft Dynamics

ERP

Santander

Banks

Oracle

ERP

Bradesco

Banks

SAP

ERP

Itaú

Banks

Microsoft Dynamics

ERP

Santander

Banks

Oracle

ERP

Bradesco

Banks

TOTVS

ERP

Banco do Brasil

Banks

Google Sheets

Spreadsheets

NetSuite

ERP

Microsoft Excel

Spreadsheets

Omie

ERP

TOTVS

ERP

Banco do Brasil

Banks

Google Sheets

Spreadsheets

NetSuite

ERP

Microsoft Excel

Spreadsheets

Omie

ERP

Gmail

BTG

Banks

PostgreSQL

Data

BigQuery

Data

Snowflake

Data

Gmail

BTG

Banks

PostgreSQL

Data

BigQuery

Data

Snowflake

Data

See all integrations

Beyond named cases

Real reconciliation patterns

Multi-bank group

Reconciles 5+ banks via Open Banking/OFX against the ERP, classifies by rule+AI and writes back across entities with an audit trail.

Subscription SaaS

Full gateway reconciliation (charges, payouts, refunds, chargebacks, fees) with MDR validation.

Mid-size distributor

Reconciliation by tax ID (OFX + bank API vs. spreadsheet), matching multiple deposits that sum to a target.

Payments fintech

Reconciles PIX (Itaú/Bradesco) + card (GetNet/PagBank), with automatic accounting entry.

Reconciliation needs deterministic matching, idempotent write-back and real bank/gateway integration. Rules for the bulk, AI for the ambiguous, a human on the exception. A dashboard alone does not write off open items.

Why not generic AI?

Frequently asked questions

Can we customize matching rules?+

Yes. Amount and date tolerance, customer mapping, multiple deposits and refund handling are built per customer. Low-confidence matches go to human approval before write-back.

Which banks, gateways and ERPs do you integrate?+

Itaú, Bradesco, Santander, BB, Safra via Open Banking/OFX; Stripe, Pagar.me, PagSeguro, GetNet and others; Omie, SAP, Protheus, Conta Azul, Granatum. With no API, CSV/spreadsheet ingestion or a browser agent.

How does multi-bank and multi-entity work in practice?+

Each account and entity ingests in isolation; the group sees consolidated open items. Write-back and audit trail stay per entity, aligned with your close and governance.

Do you replace my ERP or BI?+

No. Abstra matches sources, applies match rules and writes off in the ERP you already use. BI stays for analysis; the pipeline handles operational reconciliation.

How do you handle refunds and chargebacks?+

They enter the same pipeline with their own rules. Discrepancies and low-confidence matches go to human review before write-back.

Does it work with multiple banks and tax IDs?+

Yes. Multi-account ingestion and a consolidated group view, with isolation and an audit trail per entity.

Where should we start?+

With the highest-hour flow: daily bank reconciliation, card settlement or payment reconciliation. Use the processes below for the detail.

Execution capacity

Automate without building a technical team.

Abstra specialists map, implement and evolve finance automations with your team. Execution capacity without building an internal technical structure.

Abstra builds for you
Your team builds
Hybrid build

See implementation with specialists Talk to an expert

Bring one month of statements and an acquirer report.

A reconciliation demo with your match rules, multi-entity setup and ERP write-off.

Book a reconciliation demo Or explore the processes