Skip to content
FelgorFELGOR
Financial reconciliation•Operations with high card-transaction volume and recurring monthly close

FELGOR Match

Bank reconciliation that turns weeks into seconds — bank, acquirer and ERP in one engine

The problem

Month-end close stalls at the controller's desk. Bank statement in PDF, acquirer in a different CSV per card brand, ERP with entries that don't quite match — and someone has to reconcile line by line in a spreadsheet. That's 3-5 days of work that doesn't move anything strategic, just closes the books for the accountant. Worse: human error at this stage breaks the P&L, delays taxes, and hides cash gaps that surface only months later.

The solution

FELGOR Match unifies bank, acquirer and ERP in a single reconciliation engine. It reads statements, matches transactions against card settlements, matches settlements against ERP entries — all automatic, with match suggestions learned from each company's historical behavior. The controller validates or accepts with a keyboard shortcut. Instead of 3 days of spreadsheets, the books close in hours with a full audit trail.

Capabilities

What the product does

  • Imports bank statements (OFX, CSV, PDF), acquirer settlements (Cielo, Stone, Rede, PagSeguro) and ERP entries in one place
  • N:N matching — one bank deposit covering several card batches minus advance fees and brand commissions, no manual decomposition
  • Match suggestions with calibrated confidence — controller accepts with key A, rejects with R, skips with S
  • Auto-accept rules for recurring patterns that appeared 5+ times (monthly fees, card-brand transfers)
  • Divergence detection: expected deposit that didn't arrive, ERP entry without bank counterpart
  • Pre-formatted close report for the external accountant — no export rework
  • Auditable trail per transaction: who accepted, when, with what confidence

Where it applies

It's not a vertical product

The engine is the same. What changes is the catalog trained for each context. Below are the sectors where we've already seen it make sense — but the use cases don't stop here.

  • Retail (chain stores and franchises)
  • Food service (restaurant, bar, QSR)
  • E-commerce with physical operations
  • Services (gym, beauty, wellness)
  • Logistics and last-mile
  • Healthcare (clinics, labs, ambulatory)
  • B2B SaaS with recurring billing

How it works

Day to day

  1. 1

    Connects to ERP (Omie, Conta Azul, similar) and acquirers via API

  2. 2

    Upload bank statement (OFX/CSV) and the system processes in seconds

  3. 3

    Controller opens the match queue and validates with keyboard shortcuts

  4. 4

    Recurring patterns become auto-accept rules for next month

  5. 5

    At month-end, exports a close-ready report for the accountant

Gains

What changes in the operation

  • Controller closes the month in hours, not days
  • Reconciliation typos disappear — system matches, human validates
  • Cash gaps surface the same day, not in an audit three months later
  • Finance team stops losing weekends to month-end close

Who this is for

Any operation where card transactions are a material part of revenue and month-end close goes through a controller. Sector doesn't matter — restaurants, retail chains, e-commerce with physical stores, gyms, clinics. The engine recognizes Brazilian acquirer patterns (Cielo, Stone, Rede, PagSeguro, Mercado Pago) and popular ERP patterns (Omie, Conta Azul, similar).

Works best when:

  • Card revenue is 30%+ of monthly volume
  • The company has a structured ERP (not loose spreadsheets)
  • A dedicated controller or finance person handles the close today

Very small operations (1-2 finance people, under R$ 2M/yr) can manage with a spreadsheet. Above that, manual reconciliation becomes a chronic bottleneck.

What FELGOR Match isn't

Not an ERP. The company keeps using Omie, Conta Azul or whatever it has — Match consumes data, doesn't replace the management system. Not an accountant. Match cleans and organizes for the accountant to work — doesn't replace tax classification. Doesn't promise 100% auto-reconciliation without humans. Promises to remove the repetitive work and leave the human only where judgment matters.

How it fits in

Setup is direct. Connect ERP via existing API, connect acquirer via API, upload first statement. The first weeks the controller validates a lot (the model learns each company's pattern: who charges advance fees, which batch comes in which deposit, which tax rules show up). From the second month on, manual validation drops to exceptions. In 60-90 days, month-end close stops being a weekend event.

Want to learn more about FELGOR Match before booking?

Read articles on this solution

Got a problem similar to FELGOR Match in your operation?

In 30 minutes with the founders, we'll map your context and tell you whether an adaptation makes sense — or whether a different approach fits better. Straight talk.

Book a diagnosis for my case

30 min · free · with the founders