The three types of reconciliation are bank reconciliation, vendor reconciliation, and intercompany reconciliation. Each one compares different sets of records to catch errors, fraud, or mismatches before they snowball into bigger problems.
If you run operations, finance, or any function that touches money moving between systems, you’ve probably felt the pain of reconciliation. It’s tedious, error-prone, and usually lives in spreadsheets or manual workflows. But understanding the three main types helps you know what you’re actually checking, and why it matters.
Let’s break down each type, when you need it, and how to stop doing it by hand.
Type 1: Bank Reconciliation
Bank reconciliation is the most familiar one. You compare your internal accounting records against what the bank says you have.
A check you recorded last week might not have cleared yet. Or maybe a wire you sent is still in transit.
Bank reconciliation catches these timing gaps. It also catches actual errors, a duplicate charge, a transaction posted to the wrong account, or fraud.
You usually do this monthly, matching your general ledger balance to the bank statement. Any differences get investigated and resolved before you close the books.
The real challenge? If you’re managing multiple bank accounts across entities or regions, doing this by hand takes forever and leaves room for mistakes. Flows360 can automate the comparison and flag discrepancies in real time, so you don’t wait until month-end to find problems.
Type 2: Vendor Reconciliation
Vendor reconciliation compares what you think you owe vendors against what vendors say you owe them.
This one trips up a lot of teams. You record an invoice in your system. The vendor records the same invoice in theirs. But sometimes the amounts don’t match, or the payment dates don’t line up, or one system has the invoice and the other doesn’t.
Vendor reconciliation finds these gaps. It makes sure you’re not paying invoices twice, and it catches invoices the vendor sent but you never received.
This is especially critical if you’re working with recurring vendors or complex payment terms. One mismatch can damage vendor relationships fast.
You typically reconcile vendor accounts monthly or quarterly, depending on your payment frequency. The problem is that vendor data lives in your AP system, your ERP, maybe an email, and definitely in a spreadsheet somewhere. Pulling it all together manually is slow and error-prone.
Type 3: Intercompany Reconciliation
Intercompany reconciliation resolves differences between related companies or business units in your organization.
If you have a parent company and subsidiaries, or multiple entities that bill each other internally, you need this. Company A sends an invoice to Company B. Both record the transaction, but the amounts or timing might not match.
When consolidated financial statements are required, these mismatches become a real problem. You can’t close the books if intercompany transactions don’t reconcile.
This type is trickier because it involves multiple systems, multiple teams, and sometimes different accounting standards across entities. Flows360 helps you orchestrate intercompany workflows across disconnected systems, pulling data from each entity’s records and flagging where the numbers don’t line up.
See where your workflows are leaking time?
Why These Three Matter
Each type protects a different part of your financial picture.
Bank reconciliation keeps you from overspending or overdrawing. Vendor reconciliation keeps relationships healthy and payments accurate. Intercompany reconciliation makes sure your consolidated reports are actually true.
Together, they give you control and visibility. Without them, you’re flying blind.
The Real Problem: Speed and Scale
Most teams still do reconciliation manually. They export data from multiple systems into spreadsheets, then manually match rows, chase down discrepancies, and update records.
This approach breaks at scale. If you’re handling dozens of accounts, hundreds of vendors, or multiple entities, manual reconciliation becomes a bottleneck. Errors slip through. Close timelines slip. Teams burn out.
The better approach is to automate the data gathering and matching, then focus your team’s time on investigating and resolving real issues, not data entry and copy-paste.
That’s where workflow orchestration comes in. You can pull data from your bank feeds, your AP system, your GL, and your vendor portal automatically. Match records against your rules. Flag discrepancies. Then route exceptions to the right person for investigation.
Getting Started with Reconciliation
Start with your highest-risk area. If you’re in finance, bank reconciliation probably comes first. If you’re in RevOps or Customer Success, vendor and intercompany might matter more.
Document your current process. Where does the data live? How long does reconciliation take? Where do errors usually hide?
Then think about automation. Can you pull raw data automatically? Can you match records against a clear set of rules? Can you flag exceptions instead of reconciling everything manually?
The remaining work is exception handling, which is where real judgment lives anyway.
If you’re managing multiple systems or entities, Flows360 can help you build a reconciliation workflow that actually scales with your business.
People Also Ask
What’s the difference between bank reconciliation and general ledger reconciliation?
Bank reconciliation compares your records to the bank’s statement. General ledger reconciliation makes sure all your account balances are correct and complete inside your own accounting system. Both matter, but they’re checking different things. Bank reconciliation is external; GL reconciliation is internal.
How often should I reconcile?
Bank and vendor reconciliation typically happen monthly. Intercompany reconciliation happens monthly or quarterly, depending on your consolidation schedule. If you have high transaction volume or strict compliance requirements, more frequent reconciliation might be necessary.
What if reconciliation doesn’t balance?
Don’t panic. Start by checking timing differences (transactions recorded in different periods), check for duplicate entries, and verify that amounts were entered correctly. If the discrepancy is small, it might be a rounding error. If it’s large or you can’t find the cause, escalate to your finance team or the other party (vendor or intercompany partner) for investigation.
Can I automate reconciliation?
Yes. The data gathering, matching, and flagging can all be automated. The investigation and resolution of exceptions usually still requires human judgment, but automation removes the tedious parts and catches discrepancies faster.
See where your workflows are leaking time?