What Is Revel?

Revel is a cloud based point of sale platform running on iPad hardware, aimed at restaurants, quick service concepts, and retailers with more complex needs. It combines order and menu management, inventory tracking, employee scheduling and management, customer features, and reporting, and it is designed to scale across multiple locations under one system.

On the money side, Revel processes card payments through its integrated payments or connected processors, funding deposits net of fees on a settlement schedule. It also offers an integration to QuickBooks that can push sales, tax, tips, and related data into accounting. That integration is a convenience and a risk at once, because it will faithfully post whatever mapping it is given, correct or not, which makes setup and review the difference between clean books and confident errors.

Who Is Revel Good For?

Revel suits established restaurants, multi unit quick service operators, and retailers that need inventory control, employee management, and the ability to run several locations on one platform. Businesses that have outgrown a simple tablet register and want structured reporting and scalability often land on Revel.

It is a more involved system to configure and maintain than lightweight registers, so very small or simple operations may find it heavier than they need. For growing multi location businesses, the tradeoff is that Revel can centralize operations and feed accounting through integration, provided the mapping and reconciliation are set up with care rather than left to defaults.

Deposits, Fees, and Where the Bank Stops Matching

As with any integrated payments system, Revel card sales fund the bank net of processing fees on a settlement schedule, so the deposit never equals the gross sales figure. If the deposit is booked as revenue, gross sales and processing cost both disappear, and the tie between the register and the bank breaks.

Reconciling correctly means recording gross sales, booking fees to their own expense account, and matching each deposit to the batch that funded it, while accounting for settlement timing that shifts sales into a later deposit date. Refunds, voids, and chargebacks net against funding and need offsetting entries. Where multiple locations or processors are involved, each funding stream reconciles on its own path before rolling up.

• Record gross card sales rather than the net deposit.
• Book processing fees to a dedicated merchant fees expense account.
• Match each deposit to the batch that funded it.
• Account for settlement timing between sale and deposit dates.
• Post offsetting entries for refunds, voids, and chargebacks.
• Reconcile each location or processor funding stream separately before consolidating.

The QuickBooks Integration Done Right

Revel’s integration to QuickBooks is where most of its accounting outcomes are decided. The integration can post daily sales, tax, tips, discounts, and payments, but only as accurately as the account mapping behind it. If sales categories point to the wrong accounts, tax and tips are not separated, or deposits are synced at net, the integration will reliably produce wrong numbers with the appearance of automation.

A sound setup maps each Revel sales category, tax, tip, discount, and tender to the correct general ledger account, routes card sales through a clearing account, and keeps processing fees as their own line. It should be validated against the bank and the Revel reports for a period before it is trusted, and reviewed whenever menus, locations, or tax settings change. The integration is a tool, not a guarantee, and it inherits whatever discipline is put into it.

• Map every sales category, tax, tip, and tender to the correct account.
• Route card sales through a clearing account the bank deposit settles against.
• Keep processing fees as a separate, visible expense.
• Validate the sync against bank and Revel reports before relying on it.
• Review the mapping when menus, tax rates, or locations change.

Inventory, Multi Location, and Cost of Goods

Revel tracks inventory and can manage it across locations, which for restaurants and retailers is the raw material for cost of goods. But inventory movement only becomes an accurate cost figure when items are received at correct costs, valued consistently, and reconciled against physical counts. Revel shows what sold and what should be on hand; the books have to turn that into cost of goods sold and an accurate inventory asset.

Across multiple locations, consolidation requires a chart of accounts and location tagging that keep each site identifiable while rolling up cleanly, and inter location transfers of stock have to be handled so they do not distort individual results. Getting inventory valuation and location structure right is what lets a multi unit operator compare sites fairly and see true margin rather than blended estimates.

Common Revel Issues We See

Revel problems tend to concentrate around the QuickBooks integration and deposit reconciliation, with inventory close behind.

• Net deposits booked as revenue, hiding gross sales and fees.
• QuickBooks integration left on default mapping and never validated.
• Sales tax and tips not separated in the sync.
• Processing fees buried in net funding rather than tracked as cost.
• Settlement timing separating sales dates from deposit dates.
• Inventory received at wrong costs, distorting cost of goods.
• Physical counts not reconciled against Revel’s on hand records.
• Multi location results blurred by weak location tagging.
• Inter location transfers distorting individual site margins.

How Accounting Your Life Helps With Revel

Accounting Your Life has experience advising around Revel and turning its integrations into dependable financials. The priority is a validated QuickBooks mapping and a deposit reconciliation that ties the register to the bank.

• Configure and validate the Revel to QuickBooks mapping account by account.
• Build a deposit to batch reconciliation with a card clearing account.
• Isolate processing fees so payment cost is measurable.
• Establish inventory valuation and cost of goods posting that hold up.
• Reconcile physical counts against Revel on hand records.
• Structure the chart of accounts for clean multi location consolidation.
• Standardize a fast, reliable close across locations.

When Revel Starts Holding the Business Back

Revel shows strain when growth outruns its setup. A default or unreviewed QuickBooks integration that once seemed convenient becomes a source of confident errors, deposits stop tying cleanly to sales, and multi location consolidation turns into manual rework. If leadership cannot trust the synced numbers or spends the close reconciling what the integration posted, the limitation is the configuration and process rather than the platform. Tightening the mapping, deposit reconciliation, and location structure usually restores trust, and only if that fails is it time to question whether Revel still fits the operation.

Executive Questions to Ask About Revel

• Is our Revel to QuickBooks mapping validated against the bank and Revel reports?
• Do we record gross sales, or is the integration posting net deposits?
• Are tax, tips, and processing fees separated correctly in the sync?
• Can we trace each bank deposit back to the batch that funded it?
• Is cost of goods posted from real inventory movement and counts?
• Can we produce clean, comparable financials for every location?

Frequently Asked Questions

Related Platform Insights

• Toast POS accounting and reconciliation issues
• Square POS accounting and reconciliation issues
• Clover POS accounting and reconciliation issues
• Restaurant365 POS accounting and reconciliation issues
• QuickBooks accounting cleanup and reporting issues