Guides / Statement does not match ledger
Why your bank statement doesn't match your ledger: 7 usual causes
Most differences between a bank statement and a ledger come from seven causes: timing, fees, FX, chargebacks and refunds, rounding, duplicates and partial settlements. Total both sides, pair what matches on amount and a date window, then sort the leftovers by cause.
Start here: find the size of the gap
- Total both sides for the same period and the same currency. The difference is what you have to explain.
- Match what matches. Pair rows with the same amount and a date within 3 days. Take them out of the pile. Matching on a reference is stronger if both sides have one.
- Sort the leftovers into rows only in the bank and rows only in the ledger. Each leftover is usually one of the seven causes below.
| Cause | How it looks | How to find it |
|---|---|---|
| 1. Timing | Same amount, dates 1 to 5 days apart. Rows near month-end on opposite sides. | A date window of 3 to 5 days. |
| 2. Fees | Bank credit is lower than the sale, by a steady percentage plus a fixed amount. | Compare net to net. Divide the difference by the gross. |
| 3. FX | Currencies differ, or amounts never equal. | Match on a reference. Check the rate. |
| 4. Chargebacks and refunds | Negative rows, weeks after the sale, often with an extra fee. | Filter negatives. Search the original reference. |
| 5. Rounding | Differences of 0.01 or 0.02. | An amount tolerance of 0.01 to 0.05. |
| 6. Duplicates | The same amount and date twice on one side. | Count by date, amount and reference. |
| 7. Partial settlements | One invoice and several credits, or a batch with one item held back. | Sum by reference. Compare to the invoice. |
1. Timing
How it looks. A sale in the ledger on 29 October. The credit on the statement on 2 November. Same amount. Banks do not post on weekends or holidays, and a provider's payout date is not the day the bank books it. A sale on the last day of the month often sits in October in the ledger and November in the bank.
How to find it. Match on amount with a date window. Use 3 days, and 5 around a long weekend. A CAMT.053 file has two dates, the booking date and the value date. Use the one your ledger records. Then list what is left near the end of the period: it will be paired with the start of the next period.
2. Fees
How it looks. The ledger says 1,200.00. The bank says 1,164.90. The gap is 35.10, which is 2.9% plus 0.30. Providers net their fees out of the payout, so the bank never sees the gross amount.
How to find it. Compare the net amount, not the gross. If the file has a fee column, subtract it first. If it does not, divide the gap by the gross amount on a few rows. A steady percentage plus a fixed amount is a fee schedule. A gap that varies from row to row is something else, and is usually one of the other causes.
3. FX
How it looks. The ledger is in USD and the bank in EUR. The amounts never agree, and every row is off by a different amount because the rate changed each day. Or the currency column is missing, and a EUR row is read as USD.
How to find it. Check the currency column on both sides first. Then match on a reference, not on the amount. Once paired, multiply the foreign amount by that day's rate and see whether it lands within a percent or so of the other side. Do not add up amounts in different currencies. Milyo does not convert: a EUR row and a USD row never match, and mixing them is an error, not a guess.
4. Chargebacks and refunds
How it looks. A debit on the statement for a sale you made weeks ago. Or a refund that reduced a payout, so the credit is smaller than the sales you listed. A chargeback is often the disputed amount plus a separate dispute fee, as two rows.
How to find it. Filter both files for negative amounts. Search for the original charge's reference or the customer. Check the sign convention in the bank file: a MT940 line can be a reversal (RC or RD), which flips the meaning. The MT940 guide explains the marks.
5. Rounding
How it looks. Many rows differ by 0.01 or 0.02. One side rounds each line and the other rounds the total. Currencies with no decimals, such as JPY, can be rounded differently from currencies with two.
How to find it. List the differences. If they are all 0.01 or 0.02, it is rounding. Set an amount tolerance of that size, and nothing larger. A wide tolerance hides real errors and makes more rows fit more than one way. The free matcher has an amount tolerance setting on each pass, and every match shows its amount difference, so you can check.
6. Duplicates
How it looks. Two rows with the same date, amount and reference on one side, and one on the other. Common causes: a file imported twice, a retried payment, a bank that presented an item twice.
How to find it. Count rows by date, amount and reference on each side. In a spreadsheet, COUNTIFS on those three columns, then filter for 2 or more. The counts on the two sides should agree. If they do not, the side with the extra row has the duplicate. In Milyo's matcher, a row that has two equal candidates is flagged as an exception with the reason More than one possible match. You decide which one is real.
7. Partial settlements
How it looks. A customer pays an invoice in two instalments, and the statement shows two credits against one ledger row. Or a provider holds part of a batch back as a reserve, so the credit is lower than the batch total.
How to find it. Sum the bank credits that carry the same reference, and compare the sum with the invoice or batch. The rest is the amount still owed or held. That is a 1:N or N:1 match, and the 1:N guide explains it. Today, the free matcher matches one row to one row, so group the rows in a spreadsheet first.
What Milyo does for you today
The free matcher at try.milyo.app does step 2 above. It matches rows on a reference, or on amount and a date window, and it shows which rule made each match. What it cannot settle is listed with a reason: Amount differs, Date too far apart, More than one possible match, or only in File A or File B. That is a ready-made list of leftovers. It runs in your browser, nothing is uploaded, and it reads CSV, XLSX, CAMT.053 and MT940. It does not group rows (1:N), convert currencies or find fees for you.
Questions
How big should the date window be?
Start with 3 days. Widen it to 5 around weekends and public holidays. Check month-end rows by hand.
Should I allow an amount tolerance?
Only for rounding, 0.01 to 0.05 per row. A wider tolerance makes more rows fit more than one way, and those need a person.
What if I cannot explain the difference?
Split the leftovers into rows only in the bank and rows only in the ledger, and total each side. If the two totals differ by your original difference, the leftovers explain it. Then go through them by cause.
Put both files in. See what matches, and what is left, with the reason. No account.
Open the free matcher