If your finance team runs reconciliation software like BlackLine, ReconArt, or Duco, it is reasonable to assume your provider fees are already being checked. These are powerful, well-built tools, and they are doing important work. They are also solving a different problem from fee verification, and the difference is easy to miss until it costs you. The sharpest way to see it is this: a charge can reconcile perfectly and still be wrong. Understanding why is the difference between knowing your records agree and knowing your charges are correct, and it determines which tool you should reach for.
TL;DR
- Reconciliation software automates transaction matching and confirms that two records agree, surfacing breaks where they do not. Tools like BlackLine, ReconArt, and Duco do this very well at high volume.
- Fee verification reconstructs what a charge should have been under the contract and compares it to what was actually charged.
- The reference points differ. Reconciliation checks a record against another record; verification checks a charge against the contract.
- This is why a charge can reconcile perfectly and still be wrong: both sides can agree on a number that the contract says should be lower.
- They are complementary. You need reconciliation to confirm the books agree and verification to confirm charges are correct. Neither substitutes for the other.
- Using reconciliation software to catch fee leakage is a category error, because a reconciliation tool will happily match an overcharge.
Short answer
Reconciliation software and fee verification answer different questions. Reconciliation software, such as BlackLine, ReconArt, or Duco, automates transaction matching to confirm that two records agree, your record against the provider's, or the ledger against the bank, and flags breaks where they do not. Fee verification reconstructs what each transaction should have cost under the provider contract and compares that expected charge to the actual one. The crucial difference is the reference point: reconciliation matches a record against another record, while verification checks a charge against the contract. That is why a charge can reconcile cleanly and still be an overcharge, because both records can agree on a figure the contract says is wrong. The two are complementary, and a reconciliation tool cannot do a verification tool's job.
What reconciliation software does
These tools deserve an accurate description, because they are genuinely good at what they do.
Reconciliation platforms automate the matching of transactions across data sources and confirm that the records agree. Duco is a no-code, AI-powered platform built for financial institutions and fintechs, matching huge volumes of structured and unstructured data, with strong fuzzy matching and exception management, processing billions of records and reaching match rates well into the high nineties. ReconArt is a dedicated reconciliation solution that automates bank, credit-card, balance-sheet, and intercompany reconciliations and integrates with ERPs. BlackLine pairs high-volume transaction matching with the broader financial close. Different emphases, same core function: take two sets of records, match them, and surface the items that do not match.
That function is valuable and hard to do well at scale. A finance team drowning in transactions across banks, ledgers, and systems needs exactly this: automated matching that confirms the two sides agree and isolates the breaks for investigation. None of what follows diminishes that.
The question each tool answers
The clearest way to separate the categories is by the question each one answers.
Reconciliation software answers: do these two records agree? It takes your record of a transaction and another record of the same transaction, the provider's statement, the bank feed, the sub-ledger, and confirms they match. A break is when the two records disagree.
Fee verification answers: was this charge correct under the contract? It takes the transaction, reconstructs what it should have cost from the contract terms, and compares that expected figure to what was actually charged. A discrepancy is when the charge disagrees with the contract.
The two questions sound similar and are fundamentally different, because they measure against different things. One measures a record against another record. The other measures a charge against the agreement.
Why a charge can reconcile perfectly and still be wrong
This is the crux, and being concrete helps.
Suppose a provider charges you $48,200 in FX fees for a period. Your system also records $48,200, because you recorded what you were charged. A reconciliation tool compares the two records, finds they agree, and reports no break. The reconciliation passes cleanly. By every measure a reconciliation tool applies, this charge is fine.
But your contract says the FX spread should have produced a charge of $41,000. The $48,200 is a $7,200 overcharge. The reconciliation did not catch it, and could not, because both records agreed on the wrong number. Reconciliation confirms that two sides tell the same story; it has no opinion on whether the story is true. The overcharge is invisible to it precisely because there is nothing to mismatch: you were charged $48,200 and you recorded $48,200, so the records reconcile, and the leakage sails through.
This is the heart of the distinction. A break requires two records to disagree. An overcharge requires a charge to disagree with the contract. A reconciliation tool watches for the first and is blind to the second, which is why fee leakage survives even rigorous reconciliation. The contract is simply not one of the records being matched.
Different problems, different tools
| Dimension | Reconciliation software | Fintech fee verification |
|---|---|---|
| Core function | Match two records and confirm they agree | Reconstruct the expected charge and compare to actual |
| Reference point | Another record (bank, ledger, statement) | The provider contract |
| A "finding" is | A break: two records disagree | A discrepancy: a charge disagrees with the contract |
| Catches | Missing, duplicated, or mismatched records | Overcharges that are correctly recorded on both sides |
| Misses | Charges that are wrong but recorded consistently | Nothing on this axis; it is the verification itself |
| Question answered | Do these records agree? | Was this charge correct under the contract? |
They are complementary, not competing
The conclusion is not that reconciliation software is flawed or that you should drop it. It is that reconciliation and verification are two different controls, and a mature finance operation needs both.
Reconciliation confirms that your records are complete and consistent, that nothing is missing, duplicated, or mismatched across your systems and your providers' and banks'. That is essential, and a dedicated matching engine does it far better than a spreadsheet. Fee verification confirms that the charges those records describe were actually correct under your contracts. That is also essential, and reconciliation does not do it at all.
The error is not owning a reconciliation tool. The error is expecting it to catch fee leakage, because that expectation assumes the charges are right and asks the tool only to confirm both sides recorded them. The leakage is in the charge, not in the match, and a reconciliation tool will faithfully match an overcharge to your own record of it and report success.
Which tool to reach for
The two needs separate cleanly once stated.
If your problem is "do our records agree, are there breaks between our systems and our providers or banks, and can we close on consistent data," that is a reconciliation problem, and platforms like BlackLine, ReconArt, and Duco are strong answers to it.
If your problem is "are our providers charging us what our contracts say, and can we catch and recover it when they are not," that is a verification problem, and no reconciliation tool will solve it regardless of how high its match rates are, because it matches records to each other rather than charges to contracts. That is the category fee verification occupies, the one Bluefyn was built for, and it sits alongside reconciliation rather than replacing it.
Most scaling fintechs have both problems, which is why the realistic answer is both tools, used for their respective jobs. The clarity worth keeping is simply that a clean reconciliation is not a verified charge.
The bottom line
Reconciliation software and fee verification are different tools for different problems. Reconciliation matches two records and confirms they agree; verification checks a charge against the contract and confirms it was correct. The difference is the reference point, a record versus the contract, and it is why a charge can reconcile perfectly and still be an overcharge: both sides can agree on a wrong number, and reconciliation has no way to know. Tools like BlackLine, ReconArt, and Duco are excellent at matching, and they are not built to verify charges against contracts. The two are complementary, and the mistake to avoid is assuming a clean reconciliation means your charges were right. It means your records agree, which is not the same thing.
Frequently asked questions
Can reconciliation software catch fee overcharges?
Generally no. Reconciliation software matches two records and confirms they agree, so if a provider overcharges and you record what you were charged, both records agree and the reconciliation passes. The overcharge is invisible because there is nothing to mismatch. Catching it requires comparing the charge to the contract, which reconciliation does not do.
What is the difference between reconciliation and fee verification?
Reconciliation confirms that two records agree, your record against the provider's or the bank's. Fee verification confirms that a charge was correct under the contract, by reconstructing the expected charge and comparing it to the actual. The reference point differs: reconciliation measures a record against a record, verification measures a charge against the agreement.
How can a charge reconcile perfectly and still be wrong?
Because reconciliation only checks that two records agree rather than that the agreed amount is correct. If a provider charges an incorrect amount and you record that same amount, the two records match and the reconciliation passes, even though the charge breaches the contract. Both sides agreeing on a wrong number produces no break.
Do BlackLine, ReconArt, and Duco verify provider charges against contracts?
No. They are reconciliation and matching platforms that confirm records agree and surface breaks where they do not, which they do very well at scale. They do not ingest provider contracts or reconstruct what a charge should have been, so they confirm consistency between records rather than correctness against a contract.
Do I need both reconciliation and fee verification?
Most scaling fintechs do. Reconciliation confirms your records are complete and consistent across systems, providers, and banks, which is essential. Fee verification confirms the charges those records describe were correct under contract, which reconciliation does not address. They are complementary controls rather than substitutes.
Which tool should I use to catch fee leakage?
Use fee verification rather than reconciliation software. Fee leakage is a charge that is wrong but recorded consistently on both sides, so it passes reconciliation cleanly. Only a tool that compares charges against the contract, reconstructing the expected cost per transaction, will surface and prove it.
