Quick answer

QuickBooks POS sync errors usually mean the store file on the server workstation cannot be reached, or the Financial Exchange between Point of Sale and QuickBooks Desktop accounting software is failing. Missing sales and duplicate entries come from partial or repeated exchanges. Back up the store file first, fix the database service or network, then retry only the affected date range.

What "sync" means in QuickBooks Point of Sale today

QuickBooks Desktop Point of Sale 19.0 can still ring up sales, but Intuit discontinued it on October 3, 2023 and retired the connected services at the same time: Point of Sale Payments, the Gift Card Service, Mobile Sync, Intuit Store Exchange, the Webgility ecommerce integration, live support, and the Vendor Lookup Service. The Point of Sale discontinuation guide explains what that means for existing users.

So a sync error now is almost always one of two local problems. The first is the Financial Exchange — the process that hands daily sales, receipts, and inventory activity from Point of Sale to QuickBooks Desktop accounting software. The second is multi-workstation access, where client registers reach the shared store file on the server workstation. Services that once synced through Intuit's cloud are gone for good, and no repair brings them back.

Version note. Menu names changed across Point of Sale versions. In most builds the exchange and its advanced options sit in the Financial Center, and hardware setup opens from the File menu. Check your build before following a version-specific path.

Symptoms of sync and store-file problems

  • Sales rung up at the register never appear in QuickBooks Desktop, even though Point of Sale totals look correct.
  • The Financial Exchange stops partway and names an account, item, or customer it cannot match.
  • The same day's sales post twice after a failed exchange is retried.
  • Point of Sale stalls while opening the company file, often on one workstation only.
  • Client workstations lose the server mid-shift, or the server answers by IP address but not by name.
  • Inventory counts and end-of-day totals disagree between workstations.

Common causes, ranked by how often technicians see them

  1. A partial exchange followed by a blind retry. If the first attempt wrote some sales before failing, sending the same date range again creates duplicates.
  2. Unmatched records. The exchange halts when a Point of Sale item, account, or customer points at something missing or inactive in QuickBooks Desktop.
  3. The server workstation was asleep, restarting, or closed. Client registers cannot reach the store file unless the server is running.
  4. The Point of Sale database service stopped. The service can fail after a Windows update or an abrupt shutdown, and registers then report connection errors.
  5. Network name resolution and mapped drives. Registers should find the server by computer name. Mapped drive letters get reassigned and break the connection.
  6. Store-file damage. Power loss, failing disks, and hard shutdowns damage the database. Intuit's own Point of Sale guide warns that infrequent restarts and power problems lead to database corruption.
  7. An old backup restored late. Restoring the store file to an earlier date after sales were already sent makes the exchange send those sales a second time.

Before you begin: protect the store file

Point of Sale keeps its company data in a shared Data folder created under Public Documents\Intuit on the server workstation; the folder name includes your version. Confirm the exact location on the server instead of guessing from a forum post.

Back up before you repair. Close Point of Sale on every workstation, then copy the entire Point of Sale Data folder to an external drive. A copy of one file inside the folder is not enough. Also copy the built-in Point of Sale backup if your build has one. Repairs and restores can compound damage, and Intuit no longer offers live support for this product.

How to fix QuickBooks POS sync and data problems

1

Back up the whole Data folder and the Point of Sale backup

Work on the server workstation. Close Point of Sale on every register, then copy the whole Data folder to an external drive. If your build offers a backup command (usually on the File menu), create that backup as well and store it outside the Data folder. This copy is your recovery point for every step that follows; see QuickBooks backup and restore if you want a structured routine.

2

Restart the Point of Sale database service on the server

On the server, open services.msc and find the QuickBooks Point of Sale database service. Its display name includes the product and a version suffix, so confirm it before you act. Right-click the service and choose Restart, then open Point of Sale and close it again to rebuild the connection. If the service will not stay running, restart the server and try once more.

3

Fix how registers find the server

From a failing register, ping the server twice: once by computer name and once by IP address. If the IP responds but the name does not, name resolution is the problem; if neither responds, the network path itself is down. Point Point of Sale at \\ServerName\Share rather than a mapped drive letter, which Windows can reassign. If multi-user access was never stable, compare your setup against the Point of Sale setup order — server first, then each client.

4

Prove the store file opens on the server before touching the exchange

Open Point of Sale on the server with every other workstation closed. If it opens and rings a test sale, the store file is probably healthy and your problem is the exchange or the network. If it will not open, treat it as data damage and follow the data damage recovery order before you attempt any sync. A test sale you immediately return is a normal technician check.

5

Reconcile unmatched accounts, items, and customers

Open the Financial Center and review what the last exchange complained about. In QuickBooks Desktop, confirm the account, item, or customer still exists and is active. Correct the mapping in Point of Sale, or reactivate the record in QuickBooks Desktop. A single inactive account can stop an otherwise healthy exchange every time.

6

Re-run the Financial Exchange for the affected date range only

Send the smallest range that covers the missing sales — usually one day, or the days since the last clean exchange. Do not resend months of data to "catch up". Watch the progress window until it finishes, then confirm the range was sent. If it fails on another record, stop and repeat Step 5 for that record.

7

Clean up duplicates deliberately

Back up the QuickBooks Desktop company file before removing anything. Run a sales report for the affected dates and compare entries against the Point of Sale daily sales report. Keep the copy that matches the register total and delete the extras. Never re-run an exchange for a range you have already cleaned; that recreates the duplicates.

Verify the fix

  1. Ring one test sale in Point of Sale, complete it, and immediately return it.
  2. Run the Financial Exchange and confirm it completes without an error.
  3. In QuickBooks Desktop, open the matching sales report and confirm the test sale and the previously missing sales appear once.
  4. Compare the Point of Sale end-of-day total with the QuickBooks report total for the same date.
  5. Open Point of Sale from a second register and confirm it connects.

If sync errors come back

Recurring failures usually fall into two groups. If the exchange keeps stopping on records, your Point of Sale and QuickBooks Desktop data have drifted apart — fix the mappings rather than retrying. If the store file itself keeps failing, the damage is likely beyond field repair. Keep the original folder untouched and consider a professional data recovery service, because Intuit support for Point of Sale ended on October 3, 2023.

When the store file is stable but the exchange is no longer worth maintaining, plan the move. Intuit's discontinuation notice points existing merchants to Shopify POS with the QuickBooks Desktop Connector app, which supports QuickBooks Desktop Pro Plus, Premier Plus, and Enterprise 2021 through 2023. The connector moves products, customers, and vendor data — it does not move sales receipts and other transactions, which stay viewable in Point of Sale.

Prevention

  • Put the server on an uninterruptible power supply and restart it weekly, as Intuit's Point of Sale guide recommends.
  • Copy the entire Data folder to an external drive on a schedule you actually keep, and test one restore per quarter.
  • Keep the registers on a private network. Point of Sale receives no security patches, so treat it as an offline system.
  • Never send an exchange range twice, and confirm the progress window completed before closing it.
  • Write down the server name, data folder path, QuickBooks Desktop version, and driver versions in use, so the next person to troubleshoot has a starting point.

Frequently asked questions

Does QuickBooks Point of Sale still sync with QuickBooks Online?

No. Point of Sale exchanged data with QuickBooks Desktop accounting software through the local Financial Exchange. The cloud services that once bridged it to other systems, including Mobile Sync and Intuit Store Exchange, were retired with the product on October 3, 2023.

Can the Financial Exchange create duplicate sales in QuickBooks?

Yes. A partial exchange followed by a retry, or restoring an older store-file backup after data was already sent, makes Point of Sale send the same sales again. Clean duplicate entries in QuickBooks Desktop once, then avoid resending that date range.

How do I know whether the POS store file is damaged?

Open the file on the server with all other registers closed. If it fails to open, crashes at startup, or reports errors when posting a simple test sale, treat it as damage. Back up the folder before any repair attempt so a recovery specialist has something to work with.

Is QuickBooks Database Server Manager used for a POS store file?

No. Database Server Manager hosts QuickBooks Desktop .QBW company files for multi-user access. The Point of Sale store file is served by its own database service on the server workstation. The Database Server Manager guide covers the desktop tool.

Sources & further reading