How to reconcile payment deposits to your bank

Why the deposit never equals the sales total

A card deposit is the sales total minus everything that was deducted or held back before the money left, so it is not supposed to match. Reconciliation is not the search for a matching number; it is the exercise of accounting for every difference until nothing is left unexplained.

Clause C.1 of the RapidCents Services Agreement states the shape of it in one line: settlement of approved transactions to your designated payout account is net of applicable fees, chargebacks, refunds, reserves and fines. Most of your reconciliation is the itemized version of that sentence.

Processing fees come out per transaction or in a monthly bill, depending on whether you settle net or gross. Refunds reduce the deposit, and the sale a refund reverses may have settled weeks earlier in a different batch and a different month. Chargebacks and dispute fees are debited under clause C.4 from your account balance, payout account or reserve, and the debit does not necessarily arrive on the same day as the notice. Reserve funding, where a reserve applies, may be taken as deductions from incoming settlements, direct debits from the payout account, a percentage of daily volume held back, or a direct deposit you make — clause C.7 lists all four. Holds and payout suspensions are permitted under clause C.6.3 for risk management or compliance reasons, and funds held that way earn no interest. Adjustments and corrections appear too: under clause H.5 RapidCents may correct an error by debit or credit to the RapidCents account, the payout account or the reserve, whether or not you reported it.

Timing is the last difference and the most common source of panic. A batch closes on one day and the funds move on another, which means the deposit landing today usually belongs to yesterday’s sales, and the last sales of a month often fund in the next one. Keep the distinction between a difference and a break: a difference is expected and explained, a break is a difference you cannot yet account for. Only breaks need investigating.

Gross versus net settlement changes the whole exercise

Net settlement deducts fees before the money arrives; gross settlement deposits the full amount and bills the fees separately, usually once a month. Which one your account uses determines the shape of your daily work, and it is the first thing to establish before designing a process.

Under net settlement every deposit is a small arithmetic problem: the batch total, less that day’s fees, less refunds, less any adjustments. Nothing has to be chased and no fee invoice has to be funded, which is the advantage. The cost is that fee analysis takes an extra step, because the fees are spread across every deposit rather than sitting in one document, and you need deposit-level fee detail or you cannot prove the number you arrived at.

Under gross settlement the deposit lines up with the batch much more closely, which makes daily matching quick, and the monthly fee invoice becomes a single journal entry that makes rate analysis straightforward. The cost is that the fee debit is a separate cash event you have to fund, and it lands on a schedule that may not line up with your own balance.

In either model, book three things and not one: the gross sale as revenue, the processing fee as an expense, and the net cash as what reached the bank. Recording only the net deposit as revenue understates both revenue and expense, and it makes the effective rate impossible to compute afterwards without rebuilding the month from source data.

Batches, cut-off times, weekends and holidays

A batch is the set of transactions closed together and submitted for settlement, and the cut-off time is the moment that decides which day’s deposit a sale belongs to. A sale taken after cut-off belongs to the next batch, which is why an evening sale on the last day of a month can settle in the following month.

In a multi-terminal or multi-location business each device may close its own batch, and a lane that never closed leaves an open batch and a missing deposit the next morning. Automatic close at a fixed time removes the most common cause of a missing batch, which is a staff member going home without closing the till. Where a device runs offline, its transactions join the batch when it reconnects, so the settlement date can be later than the sale date by more than the usual gap.

Weekends and holidays add the second layer. Card networks and banks do not move money every day, so Friday, Saturday and Sunday sales tend to arrive together, and a statutory holiday pushes everything a day further. Canadian holiday calendars are not uniform: provincial holidays differ, so a business with locations in more than one province can watch one bank process while another is closed. Build the calendar into the expectation rather than raising a break every long weekend.

Do not build a process around a promised timeline. Under clause C.6.2 your payout schedule is the one specified in your dashboard, payouts are subject to network settlement delays and any holding period applied for risk management, and the schedule can be changed. Reconcile to your own observed pattern over a few weeks, document it as the expected lag, and treat departures from your own pattern — not from a number quoted in a sales conversation — as the signal.

Multi-currency settlement and where the conversion shows up

When you accept a payment in one currency and receive settlement in another, a conversion happens between the sale and the deposit, and it has to appear somewhere in your records or the deposit will never tie out. The gap is not a fee and should not be posted as one.

Clause C.6.4 sets the terms where RapidCents offers multi-currency processing and you use it: the service is subject to additional terms and fees, including conversion rates determined by RapidCents or its partners at the time of the transaction or of the refund, and you must provide a valid payout account for each settlement currency you request. Two practical consequences follow. First, a refund converts at the rate on the refund date rather than the rate on the original sale, so a fully refunded cross-border sale rarely nets to zero and the residue is a foreign exchange item, not an error. Second, adding a settlement currency is a banking task as much as a configuration one.

Record on the same line the transaction currency, the amount in that currency, the settlement currency, the settled amount and the rate applied. Post the difference to a foreign exchange account rather than folding it into processing fees or netting it against revenue — otherwise your effective rate will read as though your pricing changed when only the dollar did.

Watch separately for cards issued outside Canada that settle in Canadian dollars. Nothing converts in your ledger, so it is not a foreign exchange item at all, but the transaction usually carries different interchange and cross-border assessments. It shows up as fee variance on an otherwise ordinary deposit, and looking for it in the wrong place costs an afternoon.

Matching a deposit to a batch when the bank reference is opaque

Match on amount and date first, then on the identifier the processor puts in the deposit description, and treat the bank memo as the last resort rather than the first. Bank descriptions are truncated and normalized differently by every institution, and building a process on them means rebuilding it the next time the format changes.

The order that works: pull the settlement report for the period from RapidCents reporting, which ties settlements back to the transactions behind them, and take the deposit or batch identifier from it as your key. Match by exact amount within a window of a few business days, which resolves most deposits uniquely on its own. Where two deposits share an amount — two locations with the same daily total is less rare than it sounds — disambiguate by location, by terminal or by the trailing characters of the identifier. Where one deposit combines several batches, work from the report side rather than the bank side: sum the batches the report says funded together and match the sum.

When no match exists, do not force one. Record it as an open item with the date, the amount and what you already checked, and carry it forward. An unexplained deposit is as much a break as a missing one, and the credit that nobody could explain is the one that turns out to be a correction or somebody else’s money.

Write the processor’s identifier into your ledger at the moment you post the entry. Recovering it three months later means reading bank statements line by line against a report, which is the single most avoidable hour in a finance team’s month. Reporting exports carry the fee detail and settlement columns in CSV and PDF, generally cover more than a year of history, and can be scheduled to arrive on their own, so the practical arrangement is to treat the export as the source and the bank statement as the check.

The common breaks and what each one usually means

Almost every reconciliation break falls into one of six patterns, and recognizing the pattern tells you where to look before you open anything. A missing batch is the first: the batch never closed, or closed after cut-off. Check the lane that was unusually quiet, check whether a device was offline, and check the close times rather than the totals. It usually appears in the next day’s deposit; if it does not, it is a genuine exception and worth raising.

A duplicated refund is the second, and it is nearly always a process problem rather than a system one. The refund was issued twice — once in the payments dashboard and once in the point-of-sale or accounting system, or once by a manager and once by the clerk who had already done it. It shows up as a deposit short by exactly twice a known sale. The fix is a single place where refunds are issued and permissions that keep it that way.

A chargeback debited before its notice arrived is the third. The debit and the notification travel by different routes and the debit can land first, so an unexplained deduction is worth checking against the dispute queue before it is treated as an error. Under clause C.4 the chargeback amount plus the dispute fee is debited from your balance, payout account or reserve, and the amount will match a specific original sale.

An interchange downgrade is the fourth and does not break a deposit at all. The deposit is right and the fee is higher than expected on a subset of transactions — a card-not-present sale submitted without the data elements that would have qualified it, an authorization settled late, a missing address verification, or a commercial or premium card in a batch that is normally consumer. It surfaces as effective rate drift, so you find it in the fee detail rather than in the deposit total. The fifth is a fee change: a new line item or a changed rate, from a network assessment change, a scheme fee introduced at a semi-annual release, or a change on your own account. Compare fee lines month over month by name rather than comparing totals, because a total can stay flat while the composition moves.

The sixth is a timing difference, which is not a break at all: the money is on its way. Prove it by finding the deposit in the next period before writing anything off, and note it in the working papers so the next person does not investigate it again.

A month-end process worth repeating

A repeatable month-end is a daily job that leaves nothing for month end except a review. Every process that saves reconciliation for the last week of the month arrives at the same place: a pile of differences too old to explain, investigated by someone who was not there when they happened.

Daily, pull the settlement and deposit report for the previous day, confirm that every terminal and location closed its batch, match each deposit to its batch, and log anything unmatched as an open item with the date, the amount and what you checked. Weekly, clear the open item list: anything older than a week gets a named owner and an escalation date, and the dispute queue gets compared against the debits that appeared in deposits.

Monthly, reconcile total gross sales to total settled volume, reconcile total fees to the fee report or invoice, recompute the effective rate and compare it with prior months, and review refunds as a percentage of sales by location. Where you operate more than one site, sign off per location before consolidating — per-site reporting exists precisely so that a single problem store does not disappear into a company total.

Two structural points make the difference between a process and a habit. The person who issues refunds should not be the only person who reconciles them, because a duplicated or misdirected refund is invisible to the person who made it. And the process should be written down with the report names, the filters, the account codes and the expected timing, because reconciliation quality collapses in the month that the one person who knew the routine is on vacation.

What to keep, and for how long

Keep enough to reproduce any deposit from the transactions behind it, and keep it longer than the period in which someone can ask you about it. The test is not whether a file exists but whether a person who was not there can rebuild the number from what you kept.

The minimum set is the daily settlement and deposit reports, the batch close records, the fee detail, refund and chargeback records with their reason codes and dates, the bank statements, and the reconciliation working papers themselves showing open items and how each was resolved. Working papers are the part most often skipped and the part an auditor asks for first, because they are the evidence that the differences were explained rather than ignored.

Two clocks run on retention. The general one is tax and corporate: the Canada Revenue Agency requires books and records to be kept for six years from the end of the last tax year to which they relate, with exceptions that can extend it. The second is practical — reporting exports generally reach back more than a year, with extended retention available on request, so anything older than that should already exist in your own systems as an export rather than being assumed to be waiting in a dashboard. Export on a schedule and store the file where your other financial records live.

When a break is worth escalating, and what to send

Escalate once a difference is still unexplained after you have checked the batch closes, the refunds, the dispute queue and the following period’s deposits — and escalate on a clock, because the agreement sets one. This is the part of reconciliation with a real deadline attached, and missing it converts a recoverable amount into a closed matter.

Clause H.5 states the periods. A statement, settlement report or account activity record is treated as made available when RapidCents posts it in the dashboard, whether or not you open it. You must give written notice of any error, omission, unauthorized entry, incorrect fee, incorrect rate or other discrepancy within sixty days after it is made available, identifying the entry objected to, the amount and the basis of the objection. If notice is not given in that window, the statement is conclusively treated as complete, accurate and accepted, and claims arising from it are waived.

A payout that never arrived runs on a shorter clock: written notice within thirty days after the date the payout was scheduled to be made under the payout schedule in clause C.6.2, or the claim in respect of that payout is waived. The agreement explains the reason for the shorter window — a payout not traced quickly may no longer be traceable through the receiving institution or the payment system. The operational consequence is direct: a close that habitually runs two months behind is not merely untidy, it runs past the window in which a wrong fee can still be objected to.

What to send is the same information the clause asks for, plus what makes it verifiable: the entry objected to, the amount, the basis of the objection, and then the deposit or batch identifier, the date range, the report the figure came from, the bank statement line or a note that there is none, and the expected figure beside the actual one. One item per notice, because a message containing five loosely related questions gets one answer to the easiest of them.

One more line of H.5 is worth knowing before you escalate an unexpected credit. RapidCents may correct an error by debit or credit to the RapidCents account, the payout account or the reserve whether or not you reported it, and a correction made after a period has expired is not a waiver of the deadline. An unexplained credit in a deposit may therefore be a correction rather than a windfall. Trace it before you book it.

What finance teams get wrong

The recurring mistakes are structural rather than arithmetic. Booking the net deposit as revenue, which hides both the sale and the fee and makes the effective rate unrecoverable. Reconciling monthly instead of daily, which converts a five-minute question into a forensic exercise. Treating a chargeback debit as a processing fee, which understates disputes and overstates cost of acceptance at the same time. Chasing a change in the effective rate without segmenting by card type and channel, when in most months the mix moved and the price did not.

Two more are worth naming because they are quiet. Assuming a deposit that combines several batches is one batch, which produces a break that looks like a shortfall and is actually an arithmetic assumption. And leaving open items on a list that has no owner, which is how a genuine missing payout ages past the thirty-day window in clause H.5 while sitting in plain sight on a spreadsheet everyone has seen.