How to Reconcile POS Batches and Fees Against Bank Deposits in Sage Intacct (July 2026)

When your processor batches POS transactions and sends a net deposit to the bank, point of sale reconciliation in Sage Intacct starts with a gap. Gross sales happened days earlier. Processor fees were deducted before settlement. The bank line shows one number that reflects multiple transaction dates, and your team is left matching batch reports against bank feeds while manually accounting for the fee delta. Add multiple terminals or locations, and the timing mismatches compound into a reconciliation backlog that gets harder to clear with every close cycle.

TLDR:

• POS deposits collapse gross sales, processor fees, and net settlement into one bank line, requiring you to match each batch settlement against bank deposits while accounting for fee differences.
• Batch settlements typically lag 1-3 business days behind transaction dates, creating timing gaps that misalign your POS reports against bank statements.
• Sage Intacct's matching rules engine automates batch-to-deposit pairing using amount tolerances, date ranges, and reference field mapping to surface only exceptions requiring manual review.
• Record processor fees as separate GL entries instead of netting them against revenue to preserve accurate income statement reporting and audit trails.
• Truewind automates POS reconciliation for Sage Intacct by matching batch totals, processor fees, and bank deposits in a single workflow that flags discrepancies with transaction-level context.

Understanding POS Batch Reconciliation in Sage Intacct

When a retail or hospitality business closes out a POS terminal, the processor batches those transactions and sends a net deposit to the bank after deducting processing fees. Sage Intacct does not receive that raw transaction feed automatically, so your accounting team must manually match each batch settlement to the corresponding bank deposit, then account for the fee difference. With multiple terminals, locations, or processors running simultaneously, this creates a reconciliation gap that compounds daily if left unattended.

The Three-Part Structure of POS Deposits

Every POS deposit is three things collapsed into one bank line: gross sales, processor fees, and net settlement. Sage Intacct only sees the net figure that hits your bank account, so accounting for all three components separately falls on your team.

The timing mismatch is where the gap opens. Gross sales are captured at point of transaction. Batch settlement follows 1-3 business days later. Processor fees are deducted at settlement, though some processors bundle them into a separate monthly charge instead of pulling them per batch. By the time the net deposit posts to your bank, it may reflect sales from multiple calendar days under a single line item.

Common Timing Mismatches Between POS Batches and Bank Deposits

Three specific mismatches trip up POS reconciliation more than any others.

Batch close timing is the first. Most processors run a 24-hour settlement cycle, but the cut-off time matters more than you might expect. A transaction hitting at 11:05 PM when your batch closes at 11 PM rolls into the next settlement window, even though the sale date reads today. Over a week, that drift quietly misaligns your POS reports against your bank statement in ways that are not obvious at first glance.

Processing delays add another layer. For restaurants and retail businesses, settlements typically take 48 to 72 hours to reach the bank as an actual deposit. Your POS report shows Saturday. Your bank statement shows Monday or Tuesday.

Setting Up Bank Feeds in Sage Intacct for POS Accounts

Three prerequisites need to be in place before connecting any bank feed to a POS settlement account in Sage Intacct:

• An active Cloud Services subscription on your instance
• ISO country codes configured in company settings
• Cash Management permissions assigned to the relevant user roles

With those confirmed, go to Cash Management, open Bank Accounts, and select the account receiving your processor's net deposits. Use the Connect Bank Feed option to search for your financial institution. Sage Intacct Bank Feeds connects to over 10,000 banks worldwide, so coverage for most settlement banks is not an issue. Once linked, daily transactions flow in automatically, giving you the deposit data to match against your POS batch reports.

Creating Matching Rules for POS Transactions in Sage Intacct

Sage Intacct's matching rules engine lets you define exactly how incoming bank deposits should be paired with POS batch records. Getting this configuration right upfront saves hours of manual review every close cycle.

There are a few core rule types worth setting up for POS workflows:

• Amount-based matching ties a deposit to a batch when the dollar values align within a defined tolerance, which accounts for processor rounding differences without flagging false mismatches.
• Date-range matching accounts for the typical one to three day settlement lag between a batch close and when funds actually clear your bank feed.
• Reference field matching maps your POS batch ID or terminal ID to the bank transaction memo, giving the engine a secondary identifier to confirm a correct pairing.

Once rules are saved, Intacct applies them automatically, surfacing only the exceptions that fall outside your defined parameters for manual review.

Accounting for Payment Processor Fees

Payment processor fees are among the trickier elements of POS reconciliation because they rarely appear as clean, predictable line items. Processors like Square, Stripe, and Toast typically deduct fees before settling funds, meaning your bank deposit will always be less than your gross POS sales total. Accounting for this gap correctly requires booking both the gross revenue and the corresponding fee expense separately, so your income statement reflects true sales figures instead of net deposits.

Handling Chargebacks and Refunds in Your Reconciliation

Chargebacks and refunds create two distinct problems in POS reconciliation: timing gaps and gross-versus-net reporting differences. Most processors report refunds netted against gross sales in the same batch, but chargebacks often post days later as separate debit adjustments to your bank account.

In Sage Intacct, the cleanest approach is to record refunds and chargebacks as separate journal entries tied to the original transaction date instead of the settlement date. This keeps your audit trail intact and prevents your AR aging from showing inflated balances during the reconciliation window.

Using the Two-Tab Reconciliation Interface in Sage Intacct

Sage Intacct organizes POS reconciliation work across two dedicated tabs: Batches and Fees. Each serves a distinct purpose in matching POS activity to what actually posts to your bank.

Batches Tab

The Batches tab is where you match each POS batch settlement to its corresponding bank deposit. For every batch, you confirm the settlement amount, verify the deposit date, and flag any timing differences that fall outside your acceptable threshold.

Fees Tab

The Fees tab handles processor charges separately, letting you match fee debits against what the processor reported and code each to the correct GL account without conflating fee variances with settlement variances.

Building a Repeatable Month-End POS Reconciliation Checklist

A structured checklist turns a chaotic month-end into a repeatable process your team can own with confidence. Start by pulling your POS batch settlement reports for the full period before touching anything in Sage Intacct. Then verify that each batch total matches the corresponding bank deposit, accounting for processor fees and timing differences.

• Confirm all POS batches are closed and settled before the period cutoff, since open batches create deposit discrepancies that are hard to trace retroactively.
• Match each net deposit in your bank feed to a cleared batch in Sage Intacct, flagging any gaps immediately.
• Record processor fees as a separate GL entry instead of netting them against revenue, which keeps your income statement clean and auditable.
• Review any chargebacks or refunds that settled mid-period, as these often hit bank accounts days after the original transaction date.
• Run a final variance report comparing total POS sales to total bank deposits for the period before closing the books.

Completing this sequence in the same order every month reduces the time spent hunting discrepancies and gives your audit trail a consistent shape reviewers can follow without additional explanation.

Automation Strategies to Reduce Manual POS Reconciliation Work

Sage Intacct's native matching holds up for low-volume, consistent POS setups. Add more terminals, more locations, or a processor that changes memo formats periodically, and the rule-based approach starts producing unnecessary exceptions that pile up faster than your team can clear them.

Fuzzy matching speaks to this directly. Instead of requiring exact description matches, it recognizes that "SQLOCATION-BATCH-1042" and "SQLOCATION-BATCH-1043" are structurally the same transaction type and routes them accordingly. Fee splitting automation applies configurable rate logic against incoming batch amounts without manual calculation, which removes a repetitive step that adds no judgment value. Both capabilities push POS reconciliation toward an exception-only review model.

The goal isn't removing humans from the process. It's making sure humans are only reviewing what actually requires a decision.

For teams processing a handful of daily batches across one or two terminals, native Sage matching is probably sufficient. Once you cross into multi-location or multi-processor territory, the math changes. Manual matching at scale is slower and more error-prone, since fatigue compounds with volume in ways that automated matching does not experience.

How Truewind Automates POS Reconciliation for Sage Intacct Users

Truewind's Sage Intacct integration and automates the most error-prone parts of POS reconciliation. Instead of manually cross-referencing batch reports, processor statements, and bank feeds, your team gets pre-built matching logic that compares POS batch totals, net settlement amounts after processing fees, and actual bank deposits in a single reconciliation workflow.

When discrepancies appear, Truewind flags them with supporting context so your accountants can investigate specific transactions instead of hunting through raw data. The result is a faster, more auditable close.

Final Thoughts on Automating POS Reconciliation

The core challenge with point of sale reconciliation in Sage Intacct is that processor settlements, bank deposits, and fee deductions all operate on different timelines. Your team ends up manually matching three data sources every close cycle. Automation solves this by applying rules that account for settlement lag, processor rounding, and fee timing without constant manual review. Set up your matching logic once, then let it run. Request a Truewind demo to understand how AI can clear batches while your team focuses on real discrepancies.

FAQ

Can I clear POS batches in Sage Intacct without manually matching every deposit?

Yes, Sage Intacct's matching rules engine lets you define amount-based, date-range, and reference field rules that automatically pair bank deposits with POS batches. Once configured, the system applies these rules during each reconciliation run and surfaces only exceptions that fall outside your defined parameters for manual review.

How should I account for processor fees when the bank deposit is always less than gross sales?

Book gross revenue and processor fees as separate journal entries instead of recording just the net deposit amount. This keeps your income statement showing true sales figures and creates a clean audit trail, while the fee expense posts to its own GL account for accurate P&L categorization.

What's the best way to handle timing differences between when a POS batch closes and when it hits my bank?

Set up date-range matching rules in Sage Intacct that account for the typical one to three day settlement lag between batch close and actual deposit clearing. This prevents false mismatches while still flagging transactions that exceed your acceptable timing threshold.

Sage Intacct matching rules vs AI-powered reconciliation for multi-location POS?

Sage Intacct's native matching works well for low-volume, consistent setups but struggles when you have multiple terminals, locations, or processors with varying memo formats. AI-powered fuzzy matching recognizes structural patterns across variable transaction descriptions and automatically splits fees without manual calculation, pushing you toward exception-only review instead of line-by-line matching.

Why do chargebacks create reconciliation problems days after the original sale?

Chargebacks typically post as separate debit adjustments to your bank account days or weeks after the original transaction, while refunds usually net against gross sales in the same batch. Recording chargebacks as separate journal entries tied to the original transaction date instead of the settlement date prevents AR aging inflation and maintains an accurate audit trail.