Reconciliation in spreadsheets and OFX files
Someone downloads every bank's statement, crosses it with the ERP by hand and does it all again next month.
Nexus
Reconciliation API: compare any datasets and get the result ready in your system
Statement against ERP, sales against receivables, acquirers against bank. Nexus finds what matched and what differs, with rules you control.
Read the documentation
From R$ 359.90/month
- Free trial
- No charge per CNPJ
Nexus
Bank x ERP reconciliation
pagamentos × notas-fiscais
stats
1,500 records
- matched
- 1,284
- possible
- 37
- open
- 179
Pairs
thresholds 90 / 70
- Pix received 1,284.90NF 10472matched
- TED received 9,450.00NF 10466matched
- Boleto paid 612.35NF 10459possible
- Bank fee 18.90no pairopen
Clients and partners
Mismatches discovered only at month end
The payment that didn't match shows up weeks later, when the deadline is already running.
Every client with different rules
Amount tolerance, date window, CNPJ root: every operation reconciles its own way, and the code can't keep up.
How it works
1Send the datasets or connect the statement through Openi's Open Finance
Each dataset has a typed schema. Up to 20,000 records per call, or a CSV or NDJSON file of any size. The statement can come from Openi's Open Finance API.
2Define the match rules (amount, date, CNPJ or CPF, description)
The ruleset compares amount, date, CNPJ or CPF and description, with weights, thresholds and a date window.
3Receive matched, pending and mismatched items through the API or by webhook
The job records the matches: matched with no review, possible to confirm or reject. Through the API or the matches.created and matches.possible events.
4Settle automatically in the ERP
With the webhook, your system settles what was reconciled as soon as the job finishes. A trigger runs the reconciliation on every new load.
One call, the reconciliation done
curl -X POST "https://nexus-v2.openi.com.br/v1/datasets/$NOTAS_ID/ingestions" \
-H "Authorization: Bearer $NEXUS_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: notas-2026-10-08" \
-d '{"records": [
{"numero_nf": "NF-1", "doc_tomador": "12.345.678/0001-90",
"valor": "100.50", "vencimento": "2026-09-30"}
]}'
# 202: the ingestion is queued.
# Larger volumes go as a CSV or NDJSON file.Use cases
Software houses and ERPs (automatic settlement)
Offer automatic reconciliation to your clients, settling entries through the webhook, without building your own engine.
Read the NDD caseCards and acquirers (fees and receivables)
Sale against receivable, with fees and installments: reconciliation by sum matches one sale with several payouts.
Reconciliation by sumMarketplaces
Every order matched with the payment the merchant actually received, as at Nuvemshop and Tray.
Read the Nuvemshop and Tray caseBPOs and firms with many CNPJs
One ruleset per routine and as many CNPJs as the portfolio has, with no charge per CNPJ.
Rulesets and matching
Differentiators
Configurable rules
Blocking by document and date window, weighted matchers, match and review thresholds and an ambiguity margin. Every change publishes an immutable version, and a dry run tests it before anything is recorded.
- POST /v1/rulesets
- closeness(left.valor, right.valor, 100)
- thresholds: match 90, possible 70
The reason for every match, recorded (audit trail)
Every match carries its score and a breakdown per rule. Confirmations, rejections and manual matches keep the note and the time of the decision.
Reconciliation by sum
1:N, N:1 and N:M, partials and installments: a deposit that settles several invoices, or an invoice paid in parts.
Automatic statements through Openi's Open Finance
Read the transactions through the Open Finance API and send them to the bank dataset, with no OFX file.
Scale
Files of any size and large jobs on an on-demand engine. NDD reconciles more than 100 million records.
Build it in-house or use Nexus
In-house developmentNexus
- Time to launch
- In-house development: A comparison engine, queues, reprocessing and screens before the first match.
- Nexus: Four stages to the first match: datasets, ingestion, ruleset and job.
- Rule maintenance
- In-house development: Rules in code: every tweak is a deploy.
- Nexus: A versioned ruleset: every change publishes a version, and a dry run tests it with real data.
- Bank connections
- In-house development: One parser per bank and per file format.
- Nexus: Statements through Openi's Open Finance API, from more than 800 institutions, or CSV and NDJSON.
- Team cost
- In-house development: Engineering dedicated to keeping the engine running.
- Nexus: A free trial to start and plans from R$ 359.90/month, with no charge per CNPJ.
- Exception handling
- In-house development: A manual queue built on the side.
- Nexus: possible for review, with confirm, reject, undo and manual match through the API.
CaseReconciliation at scale
More than 100 million records reconciled
NDD uses Nexus to reconcile more than 100 million records. Records come in by file or through the API, the ruleset matches the two sides and each match comes back with a status and a score, with no manual queue for what checks out.
- records reconciled
- 100M+
dataset_a (file)dataset_b (API)
Record 000184
R$ 1,284.90
matchedRecord 77A1
R$ 1,284.90
Record 000185
R$ 312.00
matchedRecord 77A2
R$ 312.00
Record 000186
R$ 4,790.15
possibleRecord 77A9
R$ 4,790.51
Record 000187
R$ 96.40
openno pair
Sample data, to illustrate the flow.
Start with the free trial. For large volumes, talk to a specialist.
Starter
R$ 359.90/ month
5,000 events processed / month
R$ 0.25 per overage event
- 3 rule sets
- All supported flows and features
- No per-CNPJ charge
- Onboarding, dedicated support and dedicated infrastructure contracted separately
- Ticket support
Professional
RecommendedR$ 709.90/ month
10,000 events processed / month
R$ 0.20 per overage event
- 5 rule sets
- All supported flows and features
- No per-CNPJ charge
- Onboarding, dedicated support and dedicated infrastructure contracted separately
- Ticket support
Premium
R$ 989.90/ month
20,000 events processed / month
R$ 0.15 per overage event
- 10 rule sets
- All supported flows and features
- No per-CNPJ charge
- Onboarding, dedicated support and dedicated infrastructure contracted separately
- Ticket support
Enterprise
By proposal
Negotiated event allowance
Overage negotiated according to monthly commitment
- Rule sets as contracted
- All supported flows and features
- No per-CNPJ charge
- Onboarding, dedicated support and dedicated infrastructure according to scope
- Support through a direct channel
- Multiple payment methods
Frequently asked questions
Which datasets can I reconcile?
Any data that becomes records: bank statements, ERP entries, invoices, sales, card receivables. Each one is a dataset with a typed schema, loaded as JSON or as a CSV or NDJSON file.
Do I have to use Openi's Open Finance?
No. It is a shortcut for the statement to arrive with no file: you read the transactions through the Open Finance API and send them to the bank dataset. Any other source works the same way.
How do the rules work?
The ruleset says how the two sides relate: blocking keys (document and date window), weighted matchers (amount, date, CNPJ or CPF, description) and thresholds. Above the match threshold the pair is reconciled; above the review threshold it stays possible.
What happens to what doesn't match?
Possible pairs wait for review: you confirm or reject them through the API. A record with no pair stays open and goes into the next job, and you can still reconcile it by hand with a manual match.
Does it work with several CNPJs?
Yes, and there is no charge per CNPJ. Rules can compare the whole document or the CNPJ root, to match companies of the same group.
Can I offer this inside my ERP?
Yes. Everything is an API: your ERP sends the datasets, a trigger runs the reconciliation on every load and the webhook delivers the matches for automatic settlement.
How much does it cost?
The plans cost R$ 359.90 (5,000 events), R$ 709.90 (10,000) and R$ 989.90 (20,000) per month. For large volumes, Enterprise is priced by proposal.