Treasury reconciliation is how finance teams prove that the cash in their general ledger matches what their banks and payment provider actually hold. Teams stay accurate by matching transactions daily, explaining every unmatched transaction (also called an exception) with a documented reconciling item, and addressing exceptions before they turn into month-end problems. Much of the effort goes into netted payouts, settlement timing, and bank statements that arrive in different formats across institutions.
Below, we’ll go over the core reconciliation processes, how manual and automated workflows compare, common challenges, ways to improve accuracy, and more.
Key takeaways
Treasury reconciliation confirms that the cash recorded in your ledger matches the activity in your bank and payment accounts. Finance teams compare balances across operating accounts, clearing accounts, and payment provider balances, then document every difference as a reconciling item. That verified balance supports audits, liquidity decisions, financial reporting, and early detection of unauthorized debits.
Discrepancies often trace back to settlement timing, netted payouts, and data spread across disconnected systems. Card payouts are received days after capture, providers deposit amounts net of refunds and fees, and each bank sends statements in its own format. Thin remittance data and high transaction volumes make each unmatched item harder to identify and explain.
Daily matching, documented rules, and payment data that carries your own identifiers make exceptions faster to find and resolve. An exception aging policy (i.e., rules dictating how long unmatched transactions can remain unresolved) with clear owners and escalation dates keeps issues from carrying forward unnoticed.
Why is treasury reconciliation necessary for treasury operations?
Treasury reconciliation is necessary because audits, liquidity decisions, and financial reporting all depend on a ledger cash balance that matches what’s in the bank. The process compares the cash balances and transactions in your accounting system against records from your banks, payment provider, and other financial institutions, then investigates and resolves every difference.
Treasury cash management looks ahead to decide how much cash you’ll need and where it needs to sit. Reconciliation looks backward and confirms that the cash you’ve recorded is actually there. Cash is one of the easier balance sheet lines for an auditor to verify directly with your bank, so errors there tend to surface fast.
Treasury reconciliation comes up in the following scenarios:
Audit confirmations: Auditors request balance confirmations from your banks. If the ledger shows, say, $4.2 million and the bank confirms $4.17 million, you’ll need support for every reconciling item behind the $30,000 gap.
Liquidity decisions: Treasury puts cash into short-term investments or pays down a credit line based on reported balances. An overstated balance can lead to an overdraft, and an understated one leaves cash sitting idle.
Financial reporting: US public companies assess their internal controls over financial reporting under Section 404 of the Sarbanes-Oxley Act. Bank reconciliations with documented preparer and reviewer sign-offs are a routine control that auditors test.
Fraud detection: Under Nacha rules, a bank generally has two banking days after settlement to return an unauthorized debit to a business account. Many banks set an even earlier deadline for customers to report it, so a monthly reconciliation catches these too late for a routine return.
Error containment: Imagine a $200 variance caught in March, sitting inside one statement and a few hundred transactions. If left until June, it will be buried under three months of activity and possibly masked by offsetting errors—and tracing it means reworking every month in between.
What are the core treasury reconciliation processes?
Many treasury teams run four connected reconciliation processes. Each one narrows the gap between a business’s ledger and external records.
These core treasury reconciliation processes are:
Cash reconciliation: Teams adjust the bank balance for deposits in transit and outstanding checks, then adjust the ledger for unbooked fees, interest, and returned payments. When the ledger and bank are in agreement, the account is reconciled.
Account reconciliation: The same logic applies to clearing accounts, intercompany balances, and funds held with a payment provider. Payouts arrive net of refunds, disputes, and fees, so each one has to be broken down into its components.
Transaction matching: Teams pair ledger entries with bank or provider transactions, including many-to-one matches such as 2,000 card charges settling as one deposit. Rules compare amount, date window, and reference data such as invoice numbers.
Exception management: Teams classify unmatched items, assign each one an owner, and track how long it stays open. For example, an item open for five days is usually a timing difference, while one open for 60 days probably needs escalation.
How do manual and automated reconciliation workflows compare?
Manual and automated reconciliation workflows use similar processes, but automated workflows tend to be faster and less error-prone. With manual workflows, someone matches a downloaded comma-separated values (CSV) or Bank Administration Institute Version 2 (BAI2) statement against the cash ledger in a spreadsheet. It’s flexible but slow, hard to review, and prone to broken formulas. With automated workflows, bank and payment data arrive daily through application programming interfaces (APIs) or a Secure File Transfer Protocol (SFTP), and rules route only exceptions to a person. Loose rules can create false matches, which are harder to catch than obvious gaps. Many teams use a mix of both.
What are common treasury reconciliation challenges?
Reconciliation is generally manageable for a single account with a few hundred transactions a month. However, each bank, entity, payment method, and transaction you add makes it harder.
Here are the challenges that frequently come up:
Fragmented data: Each bank might send statements in a different format (e.g., BAI2, plain CSV, Message Type 940 (MT940), International Organization for Standardization (ISO) 20022 camt.053). Each format labels transactions differently, and each bank sets its own cutoff time for the day’s activity.
Timing differences: A direct debit payment initiated on the 30th might not settle until the 1st or 2nd, and a check mailed in March can post in April. Card payouts are typically received a few business days after capture, so the last days of every month tend to generate reconciling items.
Net settlement: Payment providers often deposit net amounts after refunds, disputes, and fees. Without itemized details, you can’t match a deposit to the sales behind it.
Thin reference data: Wire transfer remittance fields can arrive empty or unstructured, and direct debit addenda records are often optional. When a customer pays without an invoice number, you have to identify the payment by amount and payer name.
Volume: If your business processes hundreds of thousands of transactions a month, you can’t review them individually. Summarized entries and matching rules take over, and then there’s a greater impact if a rule is wrong.
Multiple entities: Intercompany transfers have to reconcile in both entities’ ledgers. A transfer booked by the sender but not the receiver throws both sides out of balance.
How can finance teams improve treasury reconciliation accuracy and efficiency?
Finance teams improve treasury reconciliation by fixing data problems before transactions reach the matching step and by resolving exceptions while they’re still recent. Most mismatches start earlier in the process, with payments that lack reference data, deposits that combine hundreds of transactions, or statements that arrive late or in inconsistent formats. When complete data arrives on a set schedule, matching rules can clear most transactions automatically, and preparers can spend their time on the items that don’t match.
Certain changes tend to have a significant effect. You’ll want to:
Reconcile daily: Small daily batches catch problems while they’re still easy to trace. Most of the month’s reconciling items are already explained before the close starts.
Pull data automatically: Scheduled bank feeds and automated provider reports replace manual downloads, so preparers stop working from different versions of the same statement. Every reconciliation then starts from one complete set of source files.
Document matching rules: Write down the amount tolerances, date windows, and reference fields each rule uses so every preparer gets the same result from the same data. Review the rules quarterly, and tighten or retire any that produce false matches.
Carry your own identifiers: Attach invoice numbers, order IDs, or customer IDs to payments when you create them so those references appear in settlement and payout data. Preparers can then match on an exact identifier instead of searching by amount and payer name.
Centralize payment data: When payment activity, payouts, and account balances live in one system of record, fewer transactions have to be matched across separate systems. Stripe’s payout reconciliation report, for example, lists every charge, refund, dispute, and fee bundled into each automatic payout, and metadata you attach to payments carries through to reporting exports.
Set an exception aging policy: Assign an owner to each exception type and set a point when unresolved items escalate, such as at 30 days. That way, old items don’t carry forward from one close to the next without anyone reviewing them.
Keep spreadsheets out of matching: Spreadsheets work for analysis, but they’re a weak system of record because edits and overwritten formulas are hard to track and review. Run matching in dedicated reconciliation software, and use spreadsheets to analyze the results.
How does treasury reconciliation support broader financial controls?
Treasury reconciliation supports financial controls by turning recorded cash into a verified balance that every other cash process can rely on. Forecasts, payment approvals, audit evidence, and board reporting all start from those balances. When accounts reconcile daily, treasury can report a 9 am cash position based on the previous day’s activity.
That accuracy carries into the following controls:
Forecast accuracy: Cash forecasting depends on reconciliation because a 13-week forecast starts from an opening balance. If that opening balance is off by $300,000, every week of the forecast carries the same error into liquidity decisions.
Segregation of duties: The person who reconciles an account shouldn’t also be able to initiate payments from it. Keeping those roles separate makes it much harder for one employee to move money and hide the evidence.
Review and sign-off: A second person reviews each completed reconciliation and signs off with a date. The signed reconciliation, plus support for each reconciling item, becomes audit evidence.
Period-end cutoff: Reconciling at period-end confirms that transactions are recorded in the correct month. A payment the bank cleared on April 1 but the ledger booked in March, for example, shows up as a reconciling item rather than a misstatement of either month’s cash.
Board and investor reporting: Quarter-end cash in a board deck or investor update needs to trace directly to reconciled bank balances. Any unexplained difference becomes a question the chief financial officer (CFO) has to answer.
Outage detection: If a bank has an outage or a payment file fails, a team that reconciles daily knows within a day which transactions didn’t go through. The team can then resubmit payments before vendors, payroll, or customers are affected.
How Stripe Treasury can help
Stripe Treasury brings payments and finances together on Stripe, so businesses can receive, store, send, and spend funds in one place. It’s built for startups and growing businesses that want to move money faster and spend less time managing financial operations. Platforms, marketplaces, and fintechs can also offer financial services to their users with Treasury for platforms.
Treasury can help you:
Simplify your financial operations: Manage money, payments, card spend, payouts, and more from the Stripe Dashboard.
Move money faster: Access settled Stripe earnings right away and send instant transfers to other businesses on Stripe without cost.
Get more from your money: Earn cashback on card spend and Stripe fee credits on qualifying balances.
Operate globally with ease: Hold balances in multiple currencies, convert only when needed, and send payouts to recipients in 160+ countries.
Automate financial operations: Use agents to analyze cash flow and automate tasks such as paying invoices, moving money, and converting currencies within limits you set.
Learn more about how Stripe Treasury can help you manage your finances and payments in one place, or get started today.
Stripe Treasury includes various distinct Stripe products. See applicable product terms. Stripe is not a bank. Checking accounts are provided exclusively by Fifth Third Bank, National Association, Member FDIC. Deposits are insured through Fifth Third Bank.
FAQs about treasury reconciliation
The content in this article is for general information and education purposes only and should not be construed as legal or tax advice. Stripe does not warrant or guarantee the accurateness, completeness, adequacy, or currency of the information in the article. You should seek the advice of a competent attorney or accountant licensed to practice in your jurisdiction for advice on your particular situation.