---
title: "QuickBooks Online Integration — Transactions Not Pushing"
slug: "quickbooks-online-integration-transactions-not-pushing-third-pass"
description: "Fix R365 QuickBooks Online sync issues for DSS journal entries and AP invoices by checking connections, GL mappings, permissions, and approvals."
status: "new"
updated: 2026-10-09T15:23:21Z
published: 2026-10-09T15:23:21Z
canonical: "docs.restaurant365.com/quickbooks-online-integration-transactions-not-pushing-third-pass"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt
> Use this file to discover all available pages before exploring further.

# QuickBooks Online Integration — Transactions Not Pushing

R365 can push approved transactions — including Daily Sales Summary (DSS) journal entries and AP invoices — to a connected QuickBooks Online (QBO) company. When the push stops working, the most common causes are an unmapped GL account on a specific journal entry, an expired QBO connection, or a mapping issue introduced after recent account changes. This article covers what you can check yourself before escalating.

## **Symptoms**

- DSS journal entries are not appearing in QBO after being approved in R365
- AP invoices are not being pushed to QBO
- You are receiving error email notifications about failed QBO pushes, or the push is silently failing with no email
- The QBO integration page shows a disconnected status

## **Steps to Resolve**

### Step 1: Check the QBO Integration Log and Connection Status

1. Open the **Admin** app.
2. Under **Integrations**, click **Integrations**.
3. Find the **QuickBooks Online** row and click its name to open the integration record.
4. If the connection status shows as disconnected or expired, click **Reconnect**.
5. Sign in with your QuickBooks Online credentials when prompted and authorize the connection.

### Step 2: Identify the Failing Record

If system error emails show a specific error referencing a journal entry or GL account:

1. Open the **Accounting** app.
2. Navigate to the specific DSS or journal entry identified in the error.
3. Open the record and review each line for a GL account that appears blank, unmapped, or flagged in red.

### Step 3: Recreate the Journal Entry to Refresh Account Mappings

If a DSS journal entry has a missing or stale account mapping:

1. Open the failing **Daily Sales Summary** record.
2. Click the **Action** button (or **Actions** dropdown) in the toolbar.
3. Select **Recreate Journal Entry**.
4. After the journal entry is recreated, attempt to approve the DSS and push to QBO again.

### Step 4: Confirm QBO Error Notification Settings

If you are not receiving error emails when pushes fail, verify that an email address is listed in the QBO integration record for error notifications. Without this, failures occur silently.

1. Open the **Admin** app.
2. Click **Integrations**.
3. Click **QuickBooks Online** to open the integration.
4. On the **General** tab, confirm that the notification email address is populated.

### Step 5: Verify the QBO Integration User's Banking Permissions

Confirm the user account used for the QBO integration has up-to-date banking integration permissions.

1. Open the **Admin** app.
2. Click **Users & security**.
3. Click **Users**.
4. Locate the appropriate user and open the record.
5. Access the **Permissions** tab.
6. Expand the **Banking** section.
7. Review the user’s permissions and adjust as necessary.

## **Limitations**

QBO only receives records that are in a complete or approved state in R365 — it does not perform bulk historical exports. If you need to push a large backlog of records, each record must be individually approved in R365 before it will sync.

R365 can connect to multiple QBO companies and map each location to the appropriate company. If you need to set up a new QBO connection or reconfigure location-to-company mapping, R365 Support assistance is required. For setup reference, see [QuickBooks Connection Window](https://docs.restaurant365.com/docs/quickbooks-connection-window).