Does Brink POS integrate with QuickBooks?
Yes, you can integrate Brink POS (now PAR POS) with QuickBooks Online or QuickBooks Desktop using Autymate. Each store's closed business day posts to its franchisee's books, with sales by category, promotions, sales tax, gift cards, delivery orders and refunds on separate lines, the bank deposit matched to the day, and royalties and ad fund accrued from net sales. Every record is checked before it posts. The same connection can send Brink data to Sage Intacct, NetSuite, Xero and 300+ other systems, and Autymate builds, runs and monitors it for you.
Connects to
- QuickBooks Online
- QuickBooks Desktop
- Sage Intacct
- NetSuite
- Xero
- Payroll, delivery and reporting
- and 300+ more systems
Brink is PAR Technology's cloud POS for quick-service and fast casual chains. PAR renamed it PAR POS in September 2024, but most operators still call it Brink. In October 2023 PAR said Brink ran in more than 21,000 restaurant locations, the same month it was chosen as the exclusive POS for traditional Burger King restaurants in North America, and Zaxby's is among the other brands that run it.
Brink is usually a brand-level decision. The franchisor picks the POS, but each franchisee keeps its own books, often across several companies. So the hard part is not reading Brink. It is getting every store's day into the right franchisee's books, on the same chart of accounts, with royalties and ad fund calculated the way the franchise agreement says.
What Brink Data Moves, and Where It Lands
A Brink business day carries sales by category, promotions, taxes, tenders and more. Each of those belongs somewhere different in the franchisee's books. Get the routing right once and every store posts the same way.
Sales and discounts
- Sales by category
- Promotions and coupons
- Employee meals and comps
Tax, delivery and gift cards
- Sales tax
- Delivery orders
- Gift cards sold and redeemed
Refunds, payments and fees
- Refunds and voids
- Cash, paid-outs and over or short
- Card payments
- Processing fees
Owed to the franchisor
- Net sales for royalty
| In Brink | Where it belongs | What it costs you when it is wrong |
|---|---|---|
| Sales and discounts | ||
| Sales by category | Income accounts by category and store | One lump of sales, so food cost by store is a guess |
| Promotions and coupons | Shown as a discount against the sales they reduce | Brand promotions look free and net sales are wrong |
| Employee meals and comps | Discount or employee meal expense, per your policy | Free food hidden inside sales or food cost |
| Tax, delivery and gift cards | ||
| Sales tax | Sales tax payable | Tax you owe the state counted as revenue |
| Delivery orders | Sales by channel, with commission as an expense | Delivery looks more profitable than it is, and payouts never match |
| Gift cards sold and redeemed | Gift card liability until redeemed | Revenue booked before the guest eats |
| Refunds, payments and fees | ||
| Refunds and voids | Against the original sales account | Refunds disappear inside a smaller deposit |
| Cash, paid-outs and over or short | Cash on hand, paid-out expenses, cash over and short | Drawer differences and petty cash buried in 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 |
| Owed to the franchisor | ||
| Net sales for royalty | Royalty and ad fund expense, owed to the franchisor | A royalty draft that nobody can tie back to sales |
One Store's Day, Posted Properly
Here is a single Saturday at one Brink store. Net sales after promotions were $7,827.00. Guests paid $8,514.03 by card. The bank received $8,257.69. All three numbers are right. They answer different questions, and an integration has to keep the bridge between them.
Mapped properly
| From Brink | Posts to | Amount |
|---|---|---|
| Food sales | Sales: Food | $6,940.00 |
| Beverage sales | Sales: Beverage | $1,385.00 |
| Promotions and coupons | Discounts | −$498.00 |
| Sales tax collected | Sales tax payable | $587.03 |
| Gift cards sold | Gift card liability | $100.00 |
| Refund | Refunds and returns | −$36.50 |
| Processing fees | Merchant fees expense | −$219.84 |
| Bank deposit | Bank, through the holding account | $8,257.69 |
Ties out$8,514.03 collected − $36.50 refund − $219.84 fees = $8,257.69 deposit | ||
Deposit booked as sales
| What gets posted | Posts to | Amount |
|---|---|---|
| Saturday deposit | Sales | $8,257.69 |
| Promotions | Nowhere | $0.00 |
| Sales tax owed | Inside sales | $0.00 |
| Gift cards not yet spent | Inside sales | $0.00 |
| Processing fees and refund | Nowhere | $0.00 |
OverstatedSaturday reads $430.69 above net sales of $7,827.00 | ||
- Sales tax you owe the state
- +$587.03
- Gift cards guests have not spent
- +$100.00
- Processing fees, missing from view
- −$219.84
- Refund, missing from view
- −$36.50
- Saturday overstated by
- $430.69
The gap is $430.69: $587.03 of tax you owe and $100.00 of unspent gift cards are counted as revenue, while $219.84 in fees and a $36.50 refund disappear. And because royalties are a percentage of net sales, the wrong net sales number also means the wrong royalty accrual, every day, in every store.
Illustrative figures for one store's day. Cash and delivery orders are counted and settled separately.
Royalties and Ad Fund From Brink Sales
Most franchise agreements charge royalty and ad fund as a percentage of net sales, drafted by ACH every week or month. Many franchisees only see that draft when it hits the bank. Autymate calculates both from each store's Brink net sales, accrues them in the right period, and matches the franchisor's draft when it lands.
Net sales for the week, from Brink: $52,340.00. Royalty at 5.0%: $2,617.00. Ad fund at 4.0%: $2,093.60. Together 9.0% of the first figure. ACH draft expected: $4,710.60, matched on the bank when it lands.
| Line | Posts to | Amount |
|---|---|---|
| Net sales for the week, from Brink | Basis for the calculation | $52,340.00 |
| Royalty at 5.0% | Royalty expense, owed to the franchisor | $2,617.00 |
| Ad fund at 4.0% | Advertising fund expense, owed to the franchisor | $2,093.60 |
| ACH draft expected | Matched on the bank when it lands | $4,710.60 |
If the draft is different from what the sales say it should be, it waits for review with the difference shown, instead of being booked blind. For franchisors on the other side of the same draft, Autymate can calculate and collect royalties from every franchisee's sales. See franchise and multi-location integrations.
Where Brink Data Can Go
Collect each store 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 store, with each store as a class or location and royalties accrued. QuickBooks Online integrations
- QuickBooks Desktop
- The same mapping delivered to Desktop company files, so entities on Desktop and Online run on one workflow. QuickBooks Desktop integrations
- Sage Intacct
- Entity, location and department on every entry, for franchisee groups that run several companies. ERP integrations
- NetSuite
- Each store routed to its subsidiary, department and class, for large groups and brand-owned estates. ERP integrations
- Xero
- Invoices or manual journals by tracking category, with each deposit matched to the bank feed. Accounting integrations
- Payroll, delivery and reporting
- Hours and tips to payroll, delivery payouts reconciled to orders, and every store's day to a warehouse or BI tool. Restaurant integrations
How Brink Connects
Brink is a cloud POS with an API, so store data can be read without touching the registers. What takes care is that access is opened store by store through PAR, and that a group with dozens of stores has dozens of connections to keep healthy.
One closed day, step by step
Reads
Store 1042's closed Saturday from Brink POS, over the API.
Replaces:Exporting each store'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, tax, delivery and royalty.
Replaces:Coding the day into the chart of accounts
Checks
$8,514.03 collected − $36.50 refund − $219.84 fees = $8,257.69 deposit. A payment recorded twice is held for review.
Replaces:Tying out the deposit at month-end
Posts
To Store 1042's books in QuickBooks Online.
Replaces:Keying journal entries per store
Matches
The $8,257.69 deposit, matched to the day.
Replaces:Hunting for it in the bank feed
Read from Brink
APIEach store's sales, tenders and labor read from PAR's cloud each business day, on the schedule you choose.
Back office and delivery reports
File exportBack office reports and delivery platform payout reports fill in detail the POS does not carry, such as commissions.
Files from your processor
SFTPSettlement files from your payment processor are picked up and matched to each store's business day.
For your IT or accounting team: the technical detail
- Access is opened per store, through PAR
- You ask your PAR representative to grant access to each location's API, and PAR issues that store's connection details, including a location token. We send the request wording and track each store until it is live.
- One connection per store
- A 40-store group means 40 store connections. Each one is monitored, and a store that stops answering is flagged the same day, not at month-end.
- New stores and remodels
- A new store needs its own access from PAR. Our onboarding checklist covers it, so a new store posts from its first business day.
- Business day, not calendar day
- Late closes and overnight drive-thrus cross midnight. We post by each store's business day, so the whole day lands on the right date.
- PAR's back office
- Many Brink groups also use PAR OPS, which brings together PAR Data Central and Delaget for inventory, labor and reporting. Autymate works alongside it rather than replacing it. See our Delaget integration guide.
Brink Accounting App or a Managed Integration?
Start with the smallest thing that controls your risk. Third-party apps connect Brink to accounting. Shogo, for example, posts the previous day's Brink sales to QuickBooks Online every morning as one journal entry, with tips, taxes, discounts and payment types, and maps each store to a class or location. For a few stores under one company, that may be all you need.
Export and re-key
Very low volume or a stopgap
Brink accounting app
A few stores in one QuickBooks Online file
Autymate managed integrationFranchisee groups with several entities, Sage Intacct or NetSuite, books that have to be right
| Your situation | Export and re-key | Brink accounting app | Autymate managed integration |
|---|---|---|---|
| Each entity to its own books | By hand | Usually a class or location in one file | Class, location, company file or entity |
| QuickBooks Desktop | By hand | Depends on the app | Yes, on the same mapping |
| Royalty and ad fund | Calculated in a spreadsheet | Usually not included | Accrued from net sales, matched to the ACH draft |
| Delivery commissions | Rebuilt from payout reports | Depends on the app | Matched to each platform's payouts |
| A store 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 stores well, keep it. We would rather tell you that on a call than sell you something you do not need.
Franchisee groups with several entities, Sage Intacct or NetSuite, books that have to be right? That is the setup Autymate builds and runs.
Talk to us about yoursBrink Across a Franchisee Group
At one store the question is whether the total is right. Across a group you also need to prove every dollar reached the right store and the right company, and that no store went quiet. Franchisee groups grow by buying stores, so the setup has to make the next store easy.
Route each store to its company.
Stores owned by one company share a file with a class or location for each. Stores bought into a separate company post to that company's books, on the same mapping.Write the mapping once.
Your accountant approves one mapping for the group, including royalty and ad fund rates. A new or acquired store copies it on day one instead of becoming a new project.Keep what varies separate.
Tax rates, royalty terms on older agreements, bank accounts and processors stay per store, because they really do differ.Watch for silence.
A store that sends nothing raises no error. We compare each store's trading days with what arrived and flag a missing day the same day.Compare stores on the same terms.
Because every store posts to the same accounts, food cost, promotion cost, delivery mix and royalty load finally compare across the group.
| Store | Mon | Tue | Wed | Thu | Fri | Sat | Status |
|---|---|---|---|---|---|---|---|
| Store A | Posted | Posted | Posted | Posted | Posted | Posted | |
| Store B | Posted | Posted | Posted | Posted | Posted | Posted | |
| Store C | Posted | Posted | Posted | Nothing arrived | Posted | Posted | Flagged the same day |
| Store D | Posted | Posted | Posted | Posted | Posted | Posted |
Groups that run Brink in some brands and another POS in others report as one too. Each system gets its own connection, shaped to the same standard. See restaurant integrations.
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
You ask your PAR representative to open API access for each store, using the wording we give you, and we connect your accounting system.
Map
One or two sessions with whoever owns your books to agree where sales, promotions, tax, gift cards, delivery, fees, deposits, royalties and ad fund land.
Validate
We post one real closed business day and check it inside your books: net sales match Brink, liabilities are separated, the deposit ties out and the royalty accrual is right.
Automate
Every store posts on the schedule you choose, as a daily summary or ticket by ticket, and royalties accrue as sales come in.
Monitor
Missing stores, rejected records, duplicates and lost access come to our team, not to a help article.
Decide this before anything is built
Daily summary or ticket-level detail, and which company each store belongs to. Both decide what gets written to your books, and changing them later means reprocessing history, so they are worth an extra hour now.
What we need from you
- A request to your PAR representative to open API access per store
- Access to your accounting system
- Your royalty and ad fund terms, and an hour or two from whoever owns the books
- A quick review of the first week's postings
What a Brink POS Integration Looks Like in Autymate
Every store's closed day becomes one run. You see what posted and what waits.
Autymate turns each store's closed Brink POS day into one run. Your team sees every store in one list: what posted, what is held and why, and any store that sent nothing, which is flagged and posts once its data arrives. Held items wait for your decision while the rest of the day posts. Every run keeps its mapping version and a log of each step, and Autymate's team monitors the runs.
Saturday Across Every Store
Each store's Saturday is one run: what posted, what needs a decision, and who sent nothing.
Replaces:Logging into Brink POS and each company file to check the day closed
Autymate app · sample data
History All stores Saturday3 runs1 needs review1 flagged
Saturday for every location: how many transactions each run posted, and which location sent nothing Automation Location Date Posted Status Brink POS daily sales Store 1041 Sat 6:02 AM 8 of 8 Completed Brink POS daily sales Store 1042 Sat 6:02 AM 8 of 91 to review Needs review Brink POS daily sales Store 1047 Sat 6:02 AM 8 of 8 Completed Brink POS daily sales Store 1051 Sat 6:02 AM Nothing arrived Flagged Autymate app · sample data: History for Saturday: one row per location, with Store 1042 showing 8 of 9 posted and 1 to review, and Store 1051 flagged because nothing arrived. Store 1042's Saturday, One New Promotion Held
A new brand promotion had no discount account yet, so it was held. The other eight posted.
Replaces:Finding the bad line at month-end close
Autymate app · sample data
History Store 1042 · Saturday
Brink POS to QuickBooks Online.Store 1042 · SaturdayNeeds review
Brink POS daily sales · Saturday at 6:02 AM · Store 1042
Started by the scheduleMapping version 48 of 9 posted
Transactions (9)Mapping snapshotEvent log
Transactions in Store 1042 · Saturday: what each line from Brink POS posts to, its amount and its status From Brink POS Posts to Amount Status Food sales Sales: Food $6,940.00 Posted Sales tax collected Sales tax payable $587.03 Posted Processing fees Merchant fees expense −$219.84 Posted Weekend combo promotion Nothing posted −$54.00 Needs reviewResolve + 5 more posted No account for this promotion
The weekend combo is a new promotion in Brink, and the mapping does not supply a discount account for it.
Nothing was posted for this transaction.
- Post it to Discounts, like the other promotions (chosen)
- Skip it for now
Do this automatically from now on (ticked)
Autymate app · sample data: The Store 1042 · Saturday run: 3 of its posted lines, and Weekend combo promotion held: No account for this promotion. The weekend combo is a new promotion in Brink, and the mapping does not supply a discount account for it. Chosen: Post it to Discounts, like the other promotions. Missing-Day Checks
A store that sends nothing is flagged, and its day posts once the data arrives.
Replaces:Finding a missing day yourself and asking for it to be posted
Autymate app · sample data
Missing-day checks Store 1051 Last 7 days- Sun: posted
- Mon: posted
- Tue: posted
- Wed: posted
- Thu: posted
- Fri: posted
- Sat: flagged, then posted when its data arrived
Saturday: nothing arrived from Brink POS by 6:02 AM, so Store 1051 was flagged. The data arrived at 9:40 AM, and Saturday posted to QuickBooks Online.
Autymate app · sample data: Store 1051's week, with Saturday marked. Saturday: nothing arrived from Brink POS by 6:02 AM, so Store 1051 was flagged. The data arrived at 9:40 AM, and Saturday posted to QuickBooks Online. A missing day posts once Brink POS has the day's data. If it is late in Brink POS, the day waits until it is there.
Every Run Is Kept
The log records each step, the mapping it used and the deposit matched to the day.
Replaces:A spreadsheet of what was imported, when and by whom
Autymate app · sample data
Transactions (9)Mapping snapshotEvent log (9)
- Sat 06:02:00Run started by schedule.
- Sat 06:02:01Read Store 1042's Saturday from Brink POS: 9 transactions.
- Sat 06:02:01Applied mapping version 4.
- Sat 06:02:02One connection per store: Store 1042 reads through its own PAR location token.
- Sat 06:02:02Overnight drive-thru sales after midnight kept on Saturday's business day.
- Sat 06:02:021 transaction held for review. None of it reached your books.
- Sat 06:02:03Posted 8 transactions to QuickBooks Online.
- Sat 06:02:04$8,257.69 deposit matched to Saturday.
- Sat 08:41:10Resolved "No account for this promotion" by Alex Rivera.
Sales Receipt · QuickBooks Online · mapping version 4 · kept exactly as this run used it
Autymate app · sample data: The run's event log, step by step, and the mapping snapshot it kept: Sales Receipt · QuickBooks Online · mapping version 4 · kept exactly as this run used it.
Want this view for every store? Talk to us about your setup
Proof From Franchise Networks
The hard part of a Brink integration is not Brink. It is running the same daily close across many franchise locations without anyone noticing a gap. Here is a network where Autymate does exactly that today, on another system.
Minuteman Press
Monthly file dropstoQuickBooks OnlineEvery 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.
Brink POS Integration FAQs
Yes, you can integrate Brink POS (now PAR POS) with QuickBooks Online or QuickBooks Desktop using Autymate. Every store posts its business day to its franchisee's books, with sales, promotions, tax, gift cards, delivery and fees on separate lines, the deposit matched, and royalties and ad fund accrued from net sales. Autymate builds, runs and monitors the connection, so your team has nothing to configure.
Yes. PAR Technology renamed Brink POS to PAR POS in September 2024. It is the same cloud POS, and most operators still call it Brink.
Yes. Autymate posts Brink data to Sage Intacct and NetSuite with entity, location and department on every entry, on the same mapping used for QuickBooks. That suits franchisee groups that run several companies.
Yes. Each store routes to its own class, location, company file or entity. When a group buys stores into a new company, those stores start posting to that company's books on the same mapping.
Yes. Royalty and ad fund are calculated from each store's Brink net sales at the rates in your franchise agreement, accrued in the right period, and matched to the franchisor's ACH draft when it lands. A draft that does not match waits for review with the difference shown.
Delivery orders post as sales by channel at their full value, and each platform's commission and fees post as an expense, with the platform's payout matched back to the orders it covers.
Yes. PAR opens API access store by store at the operator's request. We give you the request wording, and we track each store until its connection is live.
No. If you use PAR OPS or another back office for inventory, labor and reporting, keep it. Autymate connects the POS and your accounting system and works alongside those tools.
It depends on four things: how many stores and companies, how many destinations, how much detail the books need, and where fee, delivery and royalty data comes from. Weigh it against what the manual close costs you now: for a 15-store Jimmy John's franchisee, re-keying sales into QuickBooks took 40 hours a week, and automating it saves over $31,000 a year. The fastest way to scope it is one real closed business day from one store. Store access comes through PAR, so we start that request on day one.
Autymate holds a SOC 2 Type II report. Brink access is opened by PAR for each store, 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 Brink and PAR on this page come from published reporting, PAR's announcements and integration partners' documentation, checked on October 20, 2026. Brink features and access terms change, so confirm details for your stores during setup. The worked examples use illustrative figures and rates.
- QSR Magazine, PAR rebrands core product names, September 2024 qsrmagazine.com (opens in a new tab)
- QSR Magazine, ParTech chosen as exclusive POS software for traditional Burger King restaurants in North America, October 2023 qsrmagazine.com (opens in a new tab)
- Punchh, Zaxby's selects PAR's Brink POS and Punchh punchh.com (opens in a new tab)
- Business Wire, PAR Technology launches PAR OPS, January 2025 businesswire.com (opens in a new tab)
- GRUBBRR help center, setting up a PAR Brink integration help.grubbrr.com (opens in a new tab)
- Shogo, Brink POS to QuickBooks Online shogo.io (opens in a new tab)
- Autymate, Delaget integration guide 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.
