Bookkeeping pitfalls common in retail
Retail books fail in the daily reconciliation between the point-of-sale, the merchant processor, and the bank. A single store day produces gross sales, sales tax collected, returns, refunds, gift card sales, gift card redemptions, store credit issued, store credit redeemed, employee discounts, and tender breakdowns across cash, debit, credit, and mobile wallets. The merchant processor settles net of fees and on its own calendar, often T+2, which means the deposit hitting the bank rarely matches a single day's POS report. Operators who book the deposit as revenue and ignore the timing differences end up with an income statement that drifts away from the POS by thousands of dollars a month.
Inventory and cost-of-goods-sold timing is the second compounding issue. Retailers using the retail-method inventory system carry inventory at retail price and apply a cost-complement to compute COGS, which is fine until shrinkage, markdowns, and promotional pricing are not captured consistently. A physical count that reveals shrinkage three months after the fact produces a large adjustment that distorts gross margin in the month it is recorded rather than the months when the shrinkage actually occurred. Multi-location operators see the problem multiply, since a high-shrinkage store can hide inside a chain-level inventory roll.
Sales tax across jurisdictions is the third sustained source of risk. A retailer with stores in multiple cities and counties faces different rates, different taxability rules on specific categories, and periodic sales-tax holidays that exempt particular items for a defined window. Online sales add economic-nexus exposure in states where the retailer has no physical presence. Gift card liability sits on the balance sheet until redemption, breakage, or escheat, and treating gift card sales as revenue at issuance is a frequent error that overstates revenue and understates the liability.
How ATCS handles it
- Multi-account reconciliation pulls operating, merchant settlement, and gift-card processor feeds into one view, so the lag between POS sales and bank deposits is reconciled rather than ignored.
- Department/location coding tags every transaction by store, which makes per-location gross margin, shrinkage, and labor cost visible without rebuilding the books.
- AI-assisted categorization learns the difference between a refund, a return, a chargeback, and a void, which prevents the silent revenue leakage that comes from miscoded reversals.
- Per-transaction document attachments hold the daily Z-report or POS sales summary against the deposit, which is the documentation a state sales-tax auditor expects.
- The close-cycle workflow enforces a monthly inventory and gift-card-liability tie-out so adjustments get caught at month-end rather than at year-end.
FAQ
How should I record a credit-card deposit that arrives net of fees?
Record the gross sale at the POS amount, then book the processor fee as a separate expense, rather than booking the net deposit as revenue. ATCS supports this through AI-assisted categorization that learns the processor's deposit pattern after the first few corrections.
When does gift card revenue get recognized?
Revenue is recognized when the gift card is redeemed for goods or services, not when it is sold. Unredeemed balances may become breakage income or escheat to the state depending on jurisdiction. ATCS holds the liability and redemption sides on separate accounts.
How do I handle sales tax in multiple jurisdictions?
Configure each jurisdiction as its own sales-tax liability account and tag transactions by store location so the period-end filing report ties to the books. Economic-nexus thresholds for online sales should be reviewed annually with the CPA.
Can ATCS detect duplicate deposits from the merchant processor?
Yes. Bank-feed CSV import includes duplicate detection, which catches the recurring case where a processor batch is imported twice or where a settlement is recorded once from the merchant feed and again from the bank feed.
Where to next
To size ATCS for Retail, run the pricing calculator and the live ranges update as you set headcount, account count, and AI usage. For the engineering and infrastructure behind it, see bookkeeping & reconciliation, the AI business assistant, and the infrastructure page.