Does Revel integrate with QuickBooks?
Yes, you can integrate Revel POS with QuickBooks Online or QuickBooks Desktop using Autymate. Each Revel establishment's closed business day posts to its own books, with sales by category, comps, sales tax, tips, service charges, gift cards and refunds on separate lines, and the bank deposit matched to the day. Every record is checked before it posts. The same connection can send Revel data to Sage Intacct, NetSuite, Xero and 300+ other systems, and Autymate builds, runs and monitors it for you.
Connects to
- QuickBooks Online
- Sage Intacct
- QuickBooks Desktop
- NetSuite
- Xero
- Payroll, delivery and reporting
- and 300+ more systems
Revel is a cloud, iPad-based POS built for multi-location restaurants. When Shift4 agreed to buy it in 2024 for $250 million, more than 18,000 restaurant locations used Revel, including Dave's Hot Chicken, The Halal Guys and Kung Fu Tea. Revel to Sage Intacct is one of the ten POS connections Autymate is asked for most.
Revel records what happened at the counter. Your books need to know what that money actually is: sales you earned, tax you owe the state, tips and service charges you owe staff, gift cards guests have not spent, fees you paid the processor, and a deposit that arrives later and smaller. This page explains how a Revel integration keeps those apart, and how to keep your books steady if Revel itself changes underneath you.
What Revel Data Moves, and Where It Lands
A Revel order carries products, modifiers, discounts, taxes, tips, service charges and the payments that settled it. Each of those belongs somewhere different in your books. Get the routing right once and every establishment posts the same way.
Sales and discounts
- Sales by category
- Comps and discounts
Money you hold for others
- Sales tax
- Card tips
- Service charges and auto-gratuity
- Gift cards sold
- Gift cards redeemed
Refunds and channels
- Refunds and voids
- Delivery and online orders
Payments and settlement
- Cash payments
- Card payments
- Processing fees
| In Revel | Where it belongs | What it costs you when it is wrong |
|---|---|---|
| Sales and discounts | ||
| Sales by category | Income accounts by category and establishment | One lump of sales, so you cannot see food cost or beverage margin by store |
| Comps and discounts | Shown as a discount against the sales they reduce | Promotions look free and sales look smaller than they were |
| Money you hold for others | ||
| Sales tax | Sales tax payable | Tax you owe the state counted as revenue |
| Card tips | Tips owed to staff, then payroll | Staff money shown as profit, and tip-outs rebuilt by hand |
| Service charges and auto-gratuity | Income or staff liability, per your policy | The wrong tax and payroll treatment for large-party charges |
| Gift cards sold | Gift card liability until redeemed | Revenue booked weeks before the guest eats |
| Gift cards redeemed | Sales, with the liability reduced | Revenue counted twice, once when sold and again when spent |
| Refunds and channels | ||
| Refunds and voids | Against the original sales account | Refunds disappear inside a smaller deposit nobody can explain |
| Delivery and online orders | Sales by channel, with commission as an expense | Delivery looks more profitable than it is |
| Payments and settlement | ||
| Cash payments | Cash on hand, then the cash deposit | Drawer overs and shorts hidden inside sales |
| Card payments | A holding account until the deposit lands | Bank and sales never match, so the month will not close |
| Processing fees | Merchant fees expense | The cost of taking cards vanishes from your P&L |
One Revel Day, Posted Properly
Here is a single Friday at one Revel establishment. Net sales after comps were $5,914.00. Guests paid $7,535.09 by card. The bank received $7,291.22. All three numbers are right. They answer different questions, and an integration has to keep the bridge between them.
Mapped properly
| From Revel | Posts to (same accounts) | Amount |
|---|---|---|
| Food sales | Sales: Food | $4,860.00 |
| Beverage sales | Sales: Beverage | $1,240.00 |
| Comps and discounts | Discounts | −$186.00 |
| Sales tax collected | Sales tax payable | $502.69 |
| Card tips | Tips owed to staff | $868.40 |
| Gift cards sold | Gift card liability | $250.00 |
| Refund | Refunds and returns | −$42.50 |
| Processing fees | Merchant fees expense | −$201.37 |
| Bank deposit | Bank, through the holding account | $7,291.22 |
Ties out$7,535.09 collected − $42.50 refund − $201.37 fees = $7,291.22 deposit | ||
Deposit booked as sales
| What gets posted | Posts to (same accounts) | Amount |
|---|---|---|
| Friday deposit | Sales | $7,291.22 |
| Sales tax owed | Inside sales | $0.00 |
| Tips owed to staff | Inside sales | $0.00 |
| Gift cards not yet spent | Inside sales | $0.00 |
| Processing fees and refund | Nowhere | $0.00 |
OverstatedFriday reads $1,377.22 above net sales of $5,914.00 | ||
- Sales tax you owe the state
- +$502.69
- Card tips you owe staff
- +$868.40
- Gift cards guests have not spent
- +$250.00
- Processing fees, missing from view
- −$201.37
- Refund, missing from view
- −$42.50
- Friday overstated by
- $1,377.22
Inside that $1,377.22, $502.69 is tax you owe, $868.40 is tips you owe and $250.00 is gift cards guests have not spent, while $201.37 in fees and a $42.50 refund disappear from view. Multiply that by every service and every establishment and food cost percentages stop meaning anything. The fix is the mapping on the way in, not a correction at month-end.
Illustrative figures for one establishment's day. Cash is counted at close and deposited separately.
Where Revel Data Can Go
Collect each establishment once, then shape the data for whichever system needs it. Adding a destination later is cheap. Changing how much detail you post is not, so that is the decision to make first.
- QuickBooks Online
- A daily sales receipt or journal entry per establishment, with tax, tips, gift cards and fees on their own lines. QuickBooks Online integrations
- Sage Intacct
- Entity, location and department dimensions on every entry. One of the Revel connections restaurant groups ask us for most. ERP integrations
- QuickBooks Desktop
- The same mapping delivered to Desktop company files, so a mix of Online and Desktop runs on one workflow. QuickBooks Desktop integrations
- NetSuite
- Each establishment routed to its subsidiary, department and class, for groups that have outgrown one ledger. ERP integrations
- Xero
- Invoices or manual journals by tracking category, with the deposit matched to the bank feed. Accounting integrations
- Payroll, delivery and reporting
- Tips and hours to payroll, delivery payouts reconciled to orders, and every ticket to a warehouse or BI tool. Restaurant integrations
Moving Off Revel Without Moving Your Books
If you run Revel today, you have probably heard that change is coming. Here is what is on the public record, and what it means for your accounting.
Shift4 agrees to buy Revel for $250 million and says it will roll the best of Revel into its own restaurant POS, then called SkyTab.
SkyTab is renamed Shift4 Dine. Revel is still supported and still receiving updates.
On its second-quarter earnings call, Shift4's chief executive describes "a beginning of conversion of Revel merchants over to Shift4 Dine."
No end-of-life date or conversion timeline for Revel has been announced. Whether you stay, move to Shift4 Dine or choose another POS is your call.
Whatever you decide, the POS is the part that changes. Your chart of accounts, your entities and the way your accountant wants a day recorded should not. That is how Autymate builds a Revel integration from the start:
The mapping belongs to you, not to Revel
Where sales, tax, tips, gift cards and fees land is written against your chart of accounts. A new POS gets a new connection onto the same mapping, not a new accounting project.
History comes with you
Before an establishment switches, its Revel history is exported and kept, so year-over-year reporting does not break at the cutover date.
Mixed estates report as one
Switching one establishment at a time is normal. Stores on Revel and stores on the new POS post to the same accounts, so the group view never has a gap.
Every establishment has a cutover date
Each store switches on a set business day, so no day posts twice and no day goes missing between the old system and the new one.
- DowntownPosting dailyRevel
- MidtownPosting dailyRevel
- RiversideCut over, history keptNew POS, from Nov 3
Same accounts
- Downtown class
- Midtown class
- Riverside class
| Establishment | POS | Posts to (same accounts) | Status |
|---|---|---|---|
| Downtown | Revel | Downtown class | Posting daily |
| Midtown | Revel | Midtown class | Posting daily |
| Riverside | New POS, from Nov 3 | Riverside class | Cut over, history kept |
Switching POS systems is also when groups find out how much of their accounting lived inside the old connector. See data migration services.
How Revel Connects
Revel has a REST API, but access is not self-serve, and each account has a daily limit on how much you can ask for. What takes care is getting access set up properly, staying inside that limit, and pulling fee and deposit detail from the processor each establishment actually uses.
One closed day, step by step
Reads
Midtown's closed Friday from Revel, over the API.
Replaces:Exporting each establishment's day by hand
Gathers
Fee and deposit detail from the processor's SFTP file.
Replaces:Pulling fees off processor statements
Sorts
Every line to its own account: sales, tips, gift cards and deposits.
Replaces:Coding the day into the chart of accounts
Checks
$7,535.09 collected − $42.50 refund − $201.37 fees = $7,291.22 deposit. A payment recorded twice is held for review.
Replaces:Tying out the deposit at month-end
Posts
To Midtown's books in QuickBooks Online.
Replaces:Keying journal entries per establishment
Matches
The $7,291.22 deposit, matched to the day.
Replaces:Hunting for it in the bank feed
Read from Revel
APIOrders, payments, products and establishments read from your Revel account each business day, on the schedule you choose.
Reports and statements
File exportRevel reports and processor statements fill in deposit and fee detail where the API does not carry it.
Files from your processor
SFTPSettlement files from your payment processor are picked up and matched to each establishment's business day.
For your IT or accounting team: the technical detail
- Access is issued by Revel
- Revel does not offer a self-service way to create REST API credentials. You request access, and Revel issues an API key and secret tied to your account's revelup.com subdomain. We handle that request with you.
- A daily call allowance
- Revel does not publish a numeric rate limit, but it enforces a daily allowance and rejects requests above it until it resets. Daily runs pull only what changed, and large history loads are spread across days.
- Establishments
- One Revel account can run many establishments. Each is mapped to its own class, location, company file or entity, so one store's day never lands in another's books.
- Business day, not calendar day
- Late closes cross midnight. We post by the establishment's business day, so a Friday that closes at 1 a.m. stays on Friday.
- Processors vary
- Many Revel merchants now process through Revel Advantage on Shift4's rails, while some still use other processors, and some older processor options have reached end of life. Fee and deposit detail comes from whichever processor each establishment uses, and we confirm the source during setup.
Revel Across Several Establishments
At one restaurant the question is whether the total is right. Across a group you also need to prove every dollar reached the right establishment and the right entity, and that no store went quiet. If each establishment is not mapped on its own, store results drift into each other.
Map every establishment on its own.
Each Revel establishment routes to its own class, location, company file or subsidiary, whether the group shares one entity or each store is its own company.Write the mapping once.
Your accountant approves one mapping for the whole group. A new establishment copies it on day one instead of becoming a new project.Keep what varies separate.
Tax rates, tip policies, service charge rules, bank accounts and processors stay per establishment, because they really do differ from store to store.Watch for silence.
A store that sends nothing raises no error. We compare each establishment's trading days with what arrived and flag a missing day the same day.Compare stores on the same terms.
Because every establishment posts to the same accounts, food cost, beverage margin and labor finally compare across the group without restating anything.
| Establishment | Mon | Tue | Wed | Thu | Fri | Status |
|---|---|---|---|---|---|---|
| Establishment A | Posted | Posted | Posted | Posted | Posted | |
| Establishment B | Posted | Posted | Posted | Posted | Posted | |
| Establishment C | Posted | Posted | Posted | Nothing arrived | Posted | Flagged the same day |
| Establishment D | Posted | Posted | Posted | Posted | Posted |
See restaurant integrations and franchise and multi-location integrations.
Revel Accounting App or a Managed Integration?
Start with the smallest thing that controls your risk. Third-party apps connect Revel to QuickBooks Online. Shogo, for example, posts the previous day's Revel sales to QuickBooks Online as one journal entry by category and maps each location to a class or location. Amaka posts Revel sales as invoices, is configured by its own consultants and is priced per establishment. For one or two stores with standard books, an app like these may be all you need.
Export and re-key
Very low volume or a stopgap
Revel accounting app
One or a few establishments, one QuickBooks Online or Xero file
Autymate managed integrationSeveral establishments or entities, Sage Intacct or NetSuite, books that have to be right
| Your situation | Export and re-key | Revel accounting app | Autymate managed integration |
|---|---|---|---|
| Sage Intacct, NetSuite, QuickBooks Desktop | By hand | Depends on the app | Yes, on the same mapping |
| Each establishment to its own books | By hand | Usually a class or location in one file | Class, location, company file or entity |
| Fees and deposits tied out | Rebuilt from statements | Depends on the app and your processor | Matched through a holding account |
| Switching off Revel | Start again | Find a new app for the new POS | Same mapping, new connection |
| An establishment that sends nothing | Found at month-end | Depends on the app | Flagged the same day |
| Who fixes it when it breaks | Your team | Your team and the app's support | Autymate |
If an app already handles your Revel store well and you are not planning a switch, keep it. We would rather tell you that on a call than sell you something you do not need.
How Setup Works
Most of the work happens before anything runs on its own. Five steps, and only one of them needs real time from your team.
Connect
We request Revel API access with you and connect your accounting system.
Map
One or two sessions with whoever owns your books to agree where sales, comps, tax, tips, service charges, gift cards, fees and deposits land.
Validate
We post one real closed business day and check it inside your books: sales match Revel, liabilities are separated, and the deposit ties out.
Automate
Every establishment posts on the schedule you choose, as a daily summary or ticket by ticket.
Monitor
Missing days, rejected records, duplicates and API limits come to our team, not to a help article.
Decide this before anything is built
Daily summary or ticket-level detail. A summary keeps the books readable. Ticket-level detail supports menu margin and audit. Changing it later means reprocessing history, so it is the one choice worth an extra hour now.
What we need from you
- Approval to request Revel API access for your account
- Access to your accounting system
- An hour or two from whoever owns the chart of accounts
- A quick review of the first week's postings
Proof From Multi-Location Networks
The hard part of a Revel integration is not Revel. It is running the same daily close across many locations without anyone noticing a gap. These are networks where Autymate does exactly that today, on other systems.
Kidd's Restaurants, Jimmy John's
Macromatix, not RevelA restaurant franchisee's weekly sales summaries now post to QuickBooks automatically with its own business logic, instead of being re-keyed by a full-time admin.
- a week saved
- 40 hrs
- a year
- $31,000+
- stores
- 15
Minuteman Press
Monthly file drops, not RevelEvery franchisee's transactions post to QuickBooks Online on one standardized chart of accounts, so the franchisor can compare locations across the whole network.
- franchise locations
- 900
- a week saved per franchisee
- 3 hrs
- chart of accounts
- 1
Results described are from specific Autymate engagements. Results are not typical and will vary with data volume, source quality, system access and project scope.
Revel Integration FAQs
Yes, you can integrate Revel POS with QuickBooks Online or QuickBooks Desktop using Autymate. Every Revel establishment posts its business day to its own books, with sales, comps, tax, tips, gift cards and fees on separate lines and the deposit matched, whether you run one store or fifty. Autymate builds, runs and monitors the connection, so your team has nothing to configure.
Yes. Autymate posts Revel data to Sage Intacct and NetSuite with entity, location and department on every entry, on the same mapping used for QuickBooks. Revel to Sage Intacct is one of the connections restaurant groups ask us for most.
Card tips post to a tips liability account and can feed payroll. Service charges post as income or as a staff liability, depending on your policy. Gift cards sold post to a gift card liability and only become sales when they are redeemed.
Yes. Each establishment can post to its own class, location, company file or entity. Stores owned by different legal entities usually keep separate books; stores under one company usually share one file with a class or location for each.
No end-of-life date has been announced, and Revel is still supported. Shift4, which bought Revel in 2024, said on its August 2026 earnings call that it has begun converting Revel merchants to Shift4 Dine, its own restaurant POS formerly called SkyTab. Either way, an Autymate integration keeps your books stable, because the mapping is written against your chart of accounts, not against Revel.
The new POS gets a new connection onto the same mapping, Revel history is exported and kept, and each establishment switches on a set business day so no day is posted twice or missed. Stores on Revel and stores on the new POS keep reporting as one group throughout.
No. Every establishment keeps its current processor, and the books stay in the system your accountant already uses. The integration sits between them.
It depends on four things: how many establishments, how many destinations, how much detail the books need, and where fee and deposit data comes from. The fastest way to scope it is one real closed business day from one establishment. Revel API access has to be requested, so we start that on day one.
Autymate holds a SOC 2 Type II report. Revel access is issued for your account, only the fields the approved mapping needs are read, and every run is logged so you can see exactly what moved.
Sources and Method
Facts about Revel and Shift4 on this page come from public reporting, Shift4's earnings call and integration partners' documentation, checked on October 19, 2026. Revel's ownership and roadmap are changing, so confirm details for your account during setup. The worked examples use illustrative figures.
- Restaurant Business, Shift4 to acquire Revel Systems for $250M restaurantbusinessonline.com (opens in a new tab)
- The Motley Fool, Shift4 Payments Q2 2026 earnings call transcript, August 13, 2026 fool.com (opens in a new tab)
- Merchant Cost Consulting, what's changing for Revel merchants in 2026 merchantcostconsulting.com (opens in a new tab)
- iPaaS.com, Revel connections and settings support.ipaas.com (opens in a new tab)
- Celigo, set up a connection to Revel Systems docs.celigo.com (opens in a new tab)
- Shogo, Revel POS to QuickBooks Online shogo.io (opens in a new tab)
- Amaka, Revel and QuickBooks Online FAQ amaka.com (opens in a new tab)
- Autymate, the POS connections we are asked for most autymate.com (opens in a new tab)
Bryan Perdue
Founder & CEO, Autymate
Bryan founded Autymate after more than a decade building financial automation systems, and leads client engagement on the integrations the team ships. His focus is turning manual, multi-system workflows into low-code data integrations and custom applications for multi-location and financially sensitive businesses.
Last reviewed
Bryan on LinkedInResults described are from specific Autymate engagements. Results are not typical and will vary with data volume, source quality, system access and project scope.
