1 changed files with 156 additions and 0 deletions
@ -0,0 +1,156 @@ |
|||
<br>Here's the order for learning how to reconcile payment processor deposits to revenue: start with gross sales from your point-of-sale or invoicing system, subtract fees, refunds and reserves, then match what is left to the bank deposit. Any line that does not agree is your work list. For a growing New York City business, this matters because the bank balance will never tell you what you actually sold.<br> |
|||
|
|||
Why a processor deposit never matches your sales total |
|||
|
|||
<br>A processor deposit is a payout, not a sales report. The money that lands in your bank account is what remains after the processor takes its fees, holds back any reserve, and nets out refunds and chargebacks that settled that day. The bank feed shows real cash, but it sits at the end of a chain. The beginning [meaning of outsourced CFO in New York City](https://venturegrowthpartners.com/locations/new-york-new-york-city-outsourced-cfo-services/) that chain lives in your sales system.<br> |
|||
|
|||
<br>Take a hypothetical café in Manhattan that rings up a day of card sales, sends a few invoices to catering clients, and sees a single deposit the next business day. The deposit comes in smaller than the sales total for three reasons: fees, a refund issued from the register the day before, and a settlement delay that pushes some transactions into the next payout. None of that is a mistake. It is simply how the money moves.<br> |
|||
|
|||
<br>The trouble starts when the books record the deposit as revenue. Then the monthly revenue line reflects what the processor paid, not what the business sold, and the fees and refunds disappear into a net figure nobody can explain. A lender reading the profit and loss will ask why revenue moves in step with cash, and a buyer's diligence team will ask the same question sooner.<br> |
|||
|
|||
<br>The good news is that the gap is mechanical. Every dollar in it has a source: a fee, a refund, a reserve, a timing difference, or a deposit that belongs to another month. If you can name each source, you can reconcile it. If you cannot, the books are not ready for an outside reader, no matter how neat the monthly report looks.<br> |
|||
|
|||
<br>So the goal is not to make the deposit equal the sales total. The goal is to explain the difference, line by line, every month, with the same method. Consistency matters more than perfection here. A steady method is easy to audit and easy to repeat as volume grows.<br> |
|||
|
|||
Pull three reports before you open the bank feed |
|||
|
|||
<br>First things first: do not start in the bank account. Start with three reports from the systems that produced the money, because the bank only tells you what arrived. You need the gross sales report from your point-of-sale, e-commerce or invoicing tool, the payout or settlement report from each processor, and the refund and dispute report for the same dates.<br> |
|||
|
|||
<br>Stripe, Square, PayPal, Shopify Payments and Authorize.net each export these reports in different layouts, and the column names differ. Stripe calls the transfer to your bank a payout and tracks the underlying activity as balance transactions, while Square reports deposits in its own batch view. Read each vendor's definitions before you map anything, or you will match the wrong columns and lose time wondering why the totals are off.<br> |
|||
|
|||
<br>Pull all three for the same period. A month that ends on the 30th in your sales system may include payouts that settle on the 2nd of the next month, so decide your cutoff rule and write it down. Many small teams use the transaction date for sales and the settlement date for deposits, then reconcile the difference as timing. Whatever you choose, use it every month.<br> |
|||
|
|||
<br>Check the currency, the time zone and the sales tax handling before you sum anything. Sales tax you collect is a liability, not revenue, so confirm with your CPA whether your sales report shows tax inside or outside the total. A tax column that is included in one report and excluded in another is one of the most common reasons two correct files will not agree.<br> |
|||
|
|||
<br>Save the three exports in one folder with the period in the file name. It sounds like housekeeping, but when a lender or auditor asks for support, a clean set of source files lets you answer quickly instead of rebuilding the trail from memory. It also keeps the reconciliation honest, because you work from the documents rather than from recollection.<br> |
|||
|
|||
Build the deposit-to-sales bridge line by line |
|||
|
|||
<br>Here's the order for the core work. Build a bridge: a simple schedule that starts at gross sales for the period and ends at the bank deposits. Each step removes one known item, and the last line should match the bank statement to the cent. This is the method behind how to reconcile payment processor deposits to revenue, and it works the same whether you use QuickBooks Online, NetSuite or a spreadsheet.<br> |
|||
|
|||
<br>A workable bridge usually runs in this sequence:<br> |
|||
|
|||
|
|||
Start with gross sales for the period, noting whether the report includes sales tax. |
|||
Subtract processing fees charged in the period. |
|||
Subtract refunds issued in the period. |
|||
Subtract chargebacks and disputed amounts that are still open. |
|||
Adjust for reserves the processor held back, and add back reserves it released. |
|||
Adjust for timing: sales from this period that settled next month, and earlier sales that settled this month. |
|||
Arrive at expected net deposits, then compare that figure to the bank statement. |
|||
|
|||
|
|||
<br>Each line needs a support reference, such as a processor report row, a refund ID or a bank line. Without references, the bridge is just a set of guesses that happen to add up. Ask for the reference, not only the total, and you will catch most errors before they reach the close.<br> |
|||
|
|||
<br>Expect a residual difference the first few times. A small gap usually comes from a payout that was split, a fee posted in the wrong month, or a refund the processor settled on a different date. Log each one in a short list with the amount, the cause and the owner. That list becomes your work queue, and it shrinks as the process matures.<br> |
|||
|
|||
<br>Do not plug the difference. A plug is a journal entry to an unrelated account that makes the bank tie out, and it is the fastest way to lose the trust of anyone who reviews the books later. If a gap cannot be explained yet, park it in a clearly labeled clearing account, write down why it is open, and resolve it at the next close.<br> |
|||
|
|||
Account for refunds, chargebacks and reserves without losing the trail |
|||
|
|||
<br>Refunds, chargebacks and reserves are where most bridges break, because each one moves money on a different date than the sale that caused it. A refund issued today for a sale from last month reduces this month's cash, but it belongs to last month's sales story. Decide how you will present returns, then apply that policy every period.<br> |
|||
|
|||
<br>A chargeback works differently. When a customer disputes a card payment, the processor pulls the funds back, often charges a fee, and keeps the dispute open until the card issuer decides it. Track disputes separately from refunds, with the original transaction ID, the amount held, the status and the deadline to respond. A dispute you lose becomes a loss, and one you have not answered stays an open liability until it resolves.<br> |
|||
|
|||
<br>A rolling reserve holds back part of each payout for a set period as protection against future disputes and refunds. Reserves are more common for newer merchants, high-risk categories or businesses with heavy refund activity, and the processor's agreement sets the terms. Your bridge needs a reserve line each period, plus a schedule showing the opening balance, the amount held, the amount released and the closing balance.<br> |
|||
|
|||
<br>Be careful about where you record the reserve. It is cash your processor is holding, not cash you can spend, so classify it as a receivable or a separate asset rather than netting it silently into the bank balance. For a lender, that distinction matters, because available cash shapes how much runway the business appears to have.<br> |
|||
|
|||
<br>Keep the paperwork that proves each event: refund receipts, dispute notices, reserve statements and the processor's terms. If a reserve or dispute affects a loan covenant or an investor meaning of outsourced CFO in New York City report, you will need to explain it with source documents, not with a summary typed the night before the call.<br> |
|||
|
|||
Post the entries so revenue follows ASC 606 timing |
|||
|
|||
<br>The reconciliation tells you where the money went. The journal entries decide what the profit and loss says about revenue, and that is governed by ASC 606, the FASB revenue recognition standard. It asks you to recognize revenue when you satisfy a performance obligation, in an amount that reflects the consideration you expect to be entitled to. For many card-based sales of goods, the obligation is met at the point of sale or delivery.<br> |
|||
|
|||
<br>The complication is the difference between cash timing and revenue timing. A sale on a Friday that settles on the following Tuesday is still a Friday sale. Record revenue when the obligation is satisfied, and record the processor receivable until the cash arrives. That is why a clearing account for processor receivables helps: sales go in when they happen, and the payout clears the balance when it lands.<br> |
|||
|
|||
<br>Processing fees are a judgment call on presentation. Many small businesses record them as an operating expense, while some net them against revenue. Either approach can be defensible, but the choice should be a documented accounting policy applied consistently, and your CPA or auditor should confirm it. Changing it midyear without disclosure is the kind of change that draws questions.<br> |
|||
|
|||
<br>Be specific about what goes into revenue. Sales tax is a liability, so it sits outside the revenue account. Tips collected for employees pass through to staff, so they are also a liability. A gift card sale becomes revenue when the card is redeemed, which means the processor deposit for it lands in a liability first. Each of these needs its own posting rule, or the revenue line will drift.<br> |
|||
|
|||
<br>Test the entries against the bridge. If the revenue account, the processor clearing account and the bank tell the same story after each close, the books are doing their job. If one of them needs a plug to agree, the entries are wrong somewhere, and the bridge will show you where.<br> |
|||
|
|||
Compare who should own this work, from bookkeeper to outsourced CFO |
|||
|
|||
<br>The same reconciliation can sit with four different roles, and the difference is not only price or hours. A bookkeeper records transactions and keeps the ledger current. A controller owns the close, the policies and the review. Outsourced accounting delivers those tasks as a service from a firm. An outsourced CFO, whether fractional or interim, sets the financial direction and decides which reports the business needs before a lender, investor or buyer asks for them.<br> |
|||
|
|||
<br>Here is how they compare on the questions that matter for this process.<br> |
|||
|
|||
|
|||
|
|||
|
|||
Role |
|||
Main job in this process |
|||
Who reviews the bridge |
|||
Usually fits when |
|||
|
|||
|
|||
|
|||
|
|||
Bookkeeper |
|||
Records deposits, fees and refunds in the ledger |
|||
Owner or controller |
|||
Volume is low and the process is stable |
|||
|
|||
|
|||
Controller |
|||
Owns the monthly close, the policies and the reserve schedules |
|||
CFO or owner |
|||
Several sales channels and regular reporting to leadership |
|||
|
|||
|
|||
Outsourced accounting |
|||
Runs the bridge and the close as a service on a set schedule |
|||
Client finance lead |
|||
You need consistent output without a full-time hire |
|||
|
|||
|
|||
Outsourced or interim CFO |
|||
Sets the policy, the reporting standard and the view lenders or investors will see |
|||
Owner, board or lenders |
|||
A raise, loan, sale or audit is near and direction is missing |
|||
|
|||
|
|||
|
|||
|
|||
<br>A bookkeeper can post the entries but may not know whether the reserve belongs in cash or meaning of outsourced CFO in New York City in receivables, or whether the fee policy will hold up in diligence. A controller can own that judgment inside the company. Outsourced accounting can produce a clean bridge every month. An outsourced CFO's value sits above the bridge: deciding what the bridge must prove for the next conversation.<br> |
|||
|
|||
<br>Ask a provider how they would handle the processor reserve and the revenue presentation before you sign anything. A good answer names the policy, the document they would ask for and the person who approves it. A vague answer about being thorough tells you less about fit than a single worked example from a process similar to yours.<br> |
|||
|
|||
<br>Fit depends on your stage, size and industry. A subscription business with thousands of small card payments has different needs from a contractor who invoices a few large clients and takes card payments occasionally. Ask whether the provider has worked with businesses using your processors and accounting platform, and whether the people you meet are the people who will do the work. Do not rely on promised results, because no provider can guarantee a cleaner audit or a faster loan.<br> |
|||
|
|||
Build controls that catch a missing payout early |
|||
|
|||
<br>Controls turn a one-time cleanup into a process that holds. The core control is segregation of duties: the person who issues refunds should not also reconcile the processor account, and the person who records deposits should not approve the bridge. When one person does all three steps, the process depends on trust rather than evidence.<br> |
|||
|
|||
<br>Set up a few simple checks. Compare the processor payout count to the bank deposit count each month. Review every manual journal entry to revenue or to the clearing account. Require a second person to approve refunds above a threshold set in your written policy. None of these need special software, but they only work if someone performs them on a schedule.<br> |
|||
|
|||
<br>Watch for missing payouts. A payout that never arrives is often caused by a bank account change, a disabled payout schedule, or a processor hold after an account review. Set alerts in the processor dashboard for failed or paused payouts, and check the bank feed weekly rather than only at close. A gap caught early is a phone call. A gap caught at quarter-end is an investigation.<br> |
|||
|
|||
<br>Document the controls in a one-page procedure. Name the owner of each step, the frequency, the evidence kept and the review date. A procedure that lives in one person's head fails the first time that person is on leave. A written one lets a new hire or an outsourced team pick up the work without guessing.<br> |
|||
|
|||
<br>Revisit the controls after any change in volume, processor, sales channel or accounting platform. Adding a marketplace or an online ordering tool changes the gross-to-net path, and the bridge needs a new line for it. A control that worked for one channel may miss the fees on the next.<br> |
|||
|
|||
Prepare the bridge for a lender, investor or audit, and know when to hire in-house |
|||
|
|||
<br>When a lender or investor asks for proof of revenue, they want to see that the number ties to cash and that the method has been applied for several periods in a row. One clean month impresses less than a run of consecutive months that follow the same logic. Assemble the bridge for each period in one file, with the close memo and the open items list attached.<br> |
|||
|
|||
<br>Audit preparation follows the same logic with more detail. An auditor will sample transactions, ask for the processor agreements, check cutoff around period-end, and test whether the revenue policy matches what you actually did. Keep the policy memo, the list of processors and their terms, and the reserve schedule together. If an auditor asks why revenue is presented net of fees in one period and gross in another, you need a documented answer ready.<br> |
|||
|
|||
<br>For loan negotiations, the lender will focus on cash conversion: how much of the reported revenue actually arrives as deposits, and how quickly. A bridge makes that visible. Show reserves and disputes as separate lines so the lender does not discover them later and wonder what else was left out. Honest disclosure of open items tends to hold up better in diligence than a clean-looking number that falls apart on the first detailed question.<br> |
|||
|
|||
<br>Know the signs that the process has outgrown a bookkeeper or a simple outsourced model. The bridge needs a plug more often than it should, processor channels keep multiplying, a lender asks questions nobody can answer quickly, or the owner makes pricing and cash decisions without a current view of net deposits. Those signals point to adding a controller or a finance leader, not to more spreadsheets.<br> |
|||
|
|||
<br>An outsourced CFO can cover that gap while the business is not yet ready to carry a full-time executive. It is a useful step when you need senior direction for a funding round, a sale or a stronger close. Decide on the move based on the workload and the decisions ahead, not on a fixed revenue number. Reassess when the process needs someone inside the company every day.<br> |
|||
|
|||
The costliest mistake is booking the bank deposit as revenue, and how to avoid it |
|||
|
|||
<br>The most expensive mistake in this process is treating the processor deposit as revenue. It feels efficient because the cash is real and easy to see. But it hides fees, refunds, disputes and reserves inside one net figure, and every later decision inherits that blur: pricing, cash planning, the tax provision, the loan covenant calculation and the buyer's quality-of-earnings review.<br> |
|||
|
|||
<br>The cost shows up late. Monthly profit looks steady until a large refund cycle or a reserve change lands, and the owner cannot explain why margin moved. Lenders and buyers who open the books will test the same gap, and each unexplained difference lowers their confidence in the rest of the statements. Fixing it at that point means rebuilding months of support.<br> |
|||
|
|||
<br>Avoid it with three habits. Record sales from the sales system into their own revenue account. Post each processor payout to a clearing account, and clear it against the bank deposit when it lands. Reconcile the bridge every month with source references, and log every residual gap as an open item with an owner and a due date. Do the work every period, not only before a deadline.<br> |
|||
|
|||
<br>Start this month, even if the history is messy. Pick one processor, build one bridge for the most recent closed period, and document each line. Then repeat for the next period before you move on. Trying to rebuild a long history in a single weekend usually produces plugs, which is the opposite of what a lender or auditor needs to see.<br> |
|||
|
|||
<br>Keep the standard simple enough that someone else can follow it. If the method depends on one person's memory, it is not a process yet. If a new bookkeeper, a controller or an outsourced team can pick it up from a one-page procedure and a sample bridge, the books will hold up when the business raises capital, takes a loan or prepares for a sale.<br> |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue