Atlas Ehwcutmpm1

Acodei Help Center

Stay updated on the status of all your company's support tickets.

Customer portal

There are a number of possible causes and solutions for Payouts that don't sync. This article will cover the most common reasons.

An unsynced payout protects your QuickBooks account from having incorrect and irreconcilable data, but it should be addressed immediately.

If you use Undeposited Funds as your Stripe Holding Account, we use the transaction log we receive from Stripe to automatically select every transaction in that payout to include in the bank deposit.

As a review of our app's basic functionality, Acodei will create a Bank Deposit in QuickBooks whenever an automatic payout occurs in Stripe. Typically, a payout not syncing is caused by interference in our ability to match every transaction from Stripe to a bank deposit. 

By using our app, most QuickBooks actions regarding your Stripe account should be automated. If you are actively managing transactions from Stripe in QuickBooks, it can lead to errors.

One of the most common payout errors on the data feed is related to missing data. Payouts contain data from various dates. A payout for January 10th might contain transactions from January 6th, 7th, and 8th. As a result, if you join Acodei on January 9th, you would have a mismatch due to missing data on the January 10th payout because Acodei does not automatically retrieve the data for all dates in a payout.

This error is shown on the data by the message, "This would create a mismatch in QuickBooks due to the missing data."

To resolve this issue, you can order historical data for a particular month through the Acodei Data Feed using this button in the upper right:

Alternatively, if you only have a few payouts you would like synced and are on a paid plan, you can message us through your user portal, and we can sync unsynced payouts with this error free of charge.

Because payouts always contain data from a previous period, most users will always have some unsynced payouts with this error. A January 1st payout will contain data from late December. How you choose to handle a payout from the current year that includes data from a previous year is best determined with the help of a CPA. One alternative to avoid this issue is to utilize a separate holding account other than Undeposited Funds to capture transaction data.

A common error is when a user accidentally matches a sales receipt on the bank feed, which prevents Acodei from creating a bank deposit for the required payout. 

This error is shown on the data feed by the message, "Transaction has already been applied to another Deposit."

To avoid this error, make sure to match only deposits (not sales receipts) on your bank feed in QuickBooks. Also, make sure the deposit you match on your bank feed is correct for that payout.

To resolve this error, you must go through your categorized transactions, undo the deposited sales receipt, or manually create the deposit that caused the issue. Sometimes, the required solution is to undo many transactions on the bank feed around that date. Then, return to the Acodei Data Feed and try to resync that payout. Then, return to QuickBooks, refresh, and try to match a deposit for each payout in the bank feed.

Sometimes, if a payout only contains one sales receipt and no additional fees, this error is unimportant from an accounting perspective. This is because the deposit created by QuickBooks and the deposit created by Acodei would be the same. However, to be consistent, we recommend you always match only to a deposit, not a sales receipt.

If you have a low volume of transactions, consider 

Some Stripe transaction types require additional information for us to process. Some examples include Stripe Capital financing transactions, Stripe Connect transfers, Reserved Funds, Stripe Climate Contributions, and other Adjustments, such as disputes. There are 

This error is shown on the data feed with a message containing the language, "[Balance transaction type] detected, please turn on [transaction type] in Uncommon Transaction Mapping."

If you see this error message, you must go to the Uncommon Transaction Mapping page, accessed through the Account Mapping page.

Example of an account that needs to map uncommon transaction types

On the subsequent page, you will be required to add a product for every balance transaction type. For some of these transaction types, like Stripe Capital, you should create a new account in your chart of accounts and a new corresponding product linked to that account. For other transaction types, you may want to map them to an existing product, like Sales or Refunds.

Determining which transaction type will be linked to which product is totally up to you and your accountant. For more information on managing products in QuickBooks, see 

Another common issue that causes payouts to not sync is related to sales tax on products in QuickBooks.

QuickBooks has the functionality to apply tax to transactions, and Acodei has the functionality to capture tax from Stripe, but the two pieces of functionality require some adjustment to work together. With tax applied, sales receipts will add up to more than the payout amount received from Stripe.

This error is shown on the data feed by the message, "This deposit does not match the Stripe payout amount ... #3. You have sales tax enabled on QuickBooks".

In most situations for US-based companies, you can resolve this by going to the "Products and Services" page in QuickBooks. Ensure that all of the products you use for Acodei are listed as "Nontaxable" and do not have the "Taxable" check mark.

Once you have taken these actions, return to the Acodei Data Feed, resync your sales and refunds, and then payouts. If you are on a paid plan, please message us, and we can resync in bulk on your behalf.

 from Stripe but doesn't use QuickBooks' sales tax functionality to avoid confusion. Instead, we add sales tax as a line item on the sales receipt or in the bank deposit.

For Canadian companies and other worldwide companies with required VAT and utilizing QuickBooks tax tracking status, we continue to build the functionality around tax. Please refer to the section 

For non-US companies, VAT or GST tracking may be required in QuickBooks. We continue to build and improve our functionality around VAT tracking for non-US companies. Please read 

This error is shown on the data feed by the message, "Make sure all your transactions have a VAT rate before you save."

We have developed back-end functionality for paid customers, which can be enabled on our back end. Please message us through the customer portal, and we can enable a VAT rate for your transactions according to your preferences.

We always seek more feedback on VAT requirements from accountants outside the US. If you would like to do a video call with our product team or send us a screen recording detailing your desired process, we'd be happy to try to implement that logic.

While uncommon, we have seen some QuickBooks Apps and integrations modify Acodei-generated documents (sales receipts, refund receipts, invoices, payment receipts, etc) associated with the payout.

This error is shown on the data feed by the message, "This deposit does not match the Stripe payout amount ... #1. Another integration modified Acodei-generated transactions".

Because we match sales receipts to create a deposit, if another integration impacts one of our sales receipts, that would modify the total amount of the deposit we are attempting to create.

If another integration may have impacted Acodei-generated transactions, ensure the other integration is turned off, then resync affected transactions in the Acodei Data Feed.

While uncommon, a payout may not sync if you have manually modified one of the documents (sales receipts, refund receipts, invoice, payment receipt, etc) associated with the payout.

This error is shown on the data feed by the message, "This deposit does not match the Stripe payout amount ... #2. You manually modified an Acodei-generated transaction".

Because we match all sales receipts to create a deposit, if you did modify a sales receipt, it would modify the total amount of the deposit.

If you think you may have manually modified an Acodei-generated transaction to resolve it, you can resync any documents on the Acodei Data Feed. This will reset the document and allow you to sync the deposit.

Stripe handles ACH payments differently than credit cards. With a credit card, payment succeeds or fails, and settlement into your balance happens instantaneously. Per the Stripe documentation, with ACH payment, we have to wait four days for success or failure to appear.

This error is shown on the data feed with the message: "This payout contains a pending payment. Once the payment is completed, the payout will sync. A delayed ACH payment typically causes this."

Practically speaking, from Acodei's perspective, this means that we can only sync a payout once the ACH has succeeded or failed. So, you may see a payout that has not synced as we await the ACH status.

Once we receive a webhook from Stripe about the status of the ACH contained in the payout, we will be able to sync the payout. The payout should automatically trigger to sync once we receive the notice from Stripe.

Although we constantly improve our app's functionality, sometimes a payout may get stuck "In Progress." If you see this on your data feed and it stays that way for more than an hour, please message our support team so we can take a look at the error.

Typically this issue is caused by a QuickBooks API timeout, although there could be a variety of causes that we continue to identify and fix.

If your deposit account has changed (i.e., the account that Stripe deposits your payouts into, typically a checking account) or has been deleted, you may see this error.

This error is shown on the data feed with the message, "This Stripe account does not have a deposit account assigned. Please assign one in Account Mapping."

To fix this error, you can go to the Account Mapping page and update your Payout Deposit account. Then, go to the Acodei Data Feed, and try to resync your payouts. This should create new bank deposits inside QuickBooks associated with your newly assigned bank account.

Stripe Payouts not Syncing

One of the complex issues our app handles is a reconciliation of your Undeposited Funds account with your Stripe Balance. First, let's review what we mean by these two terms.

Undeposited Funds is an asset type in QuickBooks Online. It can have different names (such as Payments to Deposit), but the detail type is always Undeposited Funds. The functionality of this account is simple. It is the account where funds are held prior to being deposited. So if you generate an invoice in QuickBooks, and someone pays that invoice (debit to the asset), but the deposit has yet to come to your bank, you will have a balance in Undeposited Funds. Once the deposit arrives in your bank account, Undeposited Funds are emptied (credit to the asset). 

Our app uses this functionality because your Stripe Balance has the same functionality. Stripe holds funds that you have been paid (revenue) but have not been transferred or deposited into your bank account. 

At any time, you can view your current Stripe Balance within the Stripe dashboard UI. This number represents the amount of money Stripe is currently holding on your behalf, waiting to be paid to you in a Stripe payout.

You can view your Stripe balance historically and even see day-by-day Stripe balance information. You can view your current balance under the Balances tab and your historic balances by looking at Reports -> Balance.

While Undeposited Funds and your Stripe Balance should be constantly in balance, there are several reasons why they may not be. Some reasons are more complex than others, and depending on your transaction volume, you may need to consult with your accountant to reconcile these accounts. 

Note that Acodei only offers accounting support within our help articles.

Non-Stripe Transactions in Undeposited Funds

We will now break down each of these issues and recommend solutions. If you believe none of these cases match your specific situation, please message us at support@acodei.com

This case is fairly simple to understand. Imagine you have a $1,000 Stripe Balance when you sign up for Acodei. Due to various factors, Acodei will always start the Undeposited Funds balance at $0. If you run historical data, Undeposited Funds will be at $0 at the very start of your historical data. 

 for Undeposited Funds for your Stripe Balance at the start of using the Acodei app. Alternatively, you could run historical data back to a point where your Stripe Balance was $0. 

We have written another article to explain the complexities of mismatching on the banking feed, which you can take a look at if you need to understand this issue. 

To review our logic from earlier, a payment made in Stripe creates a debit to Undeposited Funds. A payout from Stripe creates a credit to Undeposited Funds. If the payout is incorrectly matched on the banking feed, the credit to Undeposited Funds will fail to happen, and your balance will be thrown off.

To correct this, you need to ensure that all payouts from Stripe are appropriately matched to the Acodei-generated bank deposit. To do this, go to the banking feed in QuickBooks, look at categorized transactions, and review the transactions from Stripe. If this is the error, undo the payouts, verify that all payouts have synced on the Acodei Data Feed, then add the deposits again, ensuring they are properly matched to their Acodei-generated payout. 

Review Undeposited Funds again to see if there is still a balance mismatch.

The Stripe payout contains a large amount of information - including all transactions and fees included in a payout. Most importantly, for our purposes here, the Stripe payout contains fees and sometimes other charges that are not contained in the normal transactions we capture. 

For example, if you subscribe to Stripe Radar or if you have a Stripe Capital Loan, we will only capture that information upon Payout. Since payouts occur only daily or weekly, the balance and Undeposited Funds will always be off by some amount as we retrieve those additional charges. Typically, this does not result in significant discrepancies, but it is possible to see fairly large differences depending on what's happening with your Stripe payouts.

The most complex issue to tackle is if other non-Stripe transactions are also regularly flowing through Undeposited Funds. Although we like Undeposited Funds for a number of reasons, this is why some accountants feel Undeposited Funds can be a bit of a black hole. Imagine if you have Paypal, Square, Stripe, and Invoices all running through Undeposited Funds - it can turn into quite the mess!

If the non-Stripe transactions are relatively minimal, it is easy to add up non-Stripe transactions and add those to the Stripe balance to reconcile. 

If non-Stripe transactions are plentiful and Undeposited Funds truly are a black hole, you or your accountant will need to break down that complexity and reconcile the total based on the Stripe balance and other elements in the account. While this is a lot of work, we anticipate that the Stripe component of the audit will be the least complex since we debit and credit every single transaction that takes place on Stripe.

There are some times that demands from certain Stripe accounts go beyond the functionality currently in our app. For example, at this time, we need a more robust connected account feature. Although we are working on a solution for this and may have one in the future, a complex situation like this would make payouts not match and would therefore throw off the match between Undeposited Funds and your Stripe Balance. If this is the case, we recommend deleting out your data and finding another solution. 

As you can see, the reconciliation of Undeposited Funds and your Stripe balance can be a lot of work - however, we hope our app makes this process easier for you. If you get to the point of frustration and you decide the complexity here is too much, we are always happy to delete out data and offer refunds as needed. Feel free to contact us anytime at support@acodei.com

Reconciling Undeposited Funds and Your Stripe Balance

We love to help our customers get set up!

Please message us through your app support portal or via email at support@acodei.com.

Based on your needs and your tier, we will send you an email or set up a Zoom call.

Onboarding Help

For our app to work correctly, you need to have an Undeposited Funds account in QuickBooks. While new QuickBooks accounts come with Undeposited Funds accounts, sometimes they may have been deleted or made inactive.

To create an Undeposited Funds account, go to your Chart of Accounts in QuickBooks. Click "New". Create the new account with the Account Type as "Other Current Assets" and the Detail Type as "Undeposited Funds" as shown below. After that, save the account. If you need this account for your account mapping, use the small refresh button next to the dropdown.

Create an Undeposited Funds account

When we create a bank deposit based on a payout, the bank deposit has to contain all of the transactions in the payout for it to be successful. For example, imagine that you have a transaction on January 1st, then join our app January 2nd, and a payout occurs January 3rd. If the January 1st transaction is not captured by our app, then it would cause an error in the payout. For accounts running lots of transactions, this becomes an issue.

The simplest / self-service way to solve for this problem is to run a historical pull for the month with the missing data. However, it is likely that the first payout on your data feed will always have this issue unless you are a small company. If you’d like us to take a closer look, email us at 

Payouts Not Syncing - Mismatch

After you connect your bank to QuickBooks Online, you will see the bank import data directly, or you will periodically import a CSV with a list of your bank transactions. Whenever a Stripe Payout occurs, you will see that reflected in your bank feed.

Acodei creates Deposits or Transfers based on your settings. These Deposits and Transfers match the amounts of Stripe Payouts and the amount on your Bank Feed.

Do not match a Sales Receipt on your Bank Feed. A Bank Deposit automatically selects Sales Receipts. Only Deposits and Transfers should be matched.

If the amounts match between the Bank Deposit created by Acodei and the Bank Feed entry from your bank, you are good to click "Match." If you would like more troubleshooting or reconciliation, please read below.

Using Undeposited Funds as your Stripe Holding Account

Not using Undeposited Funds as your Stripe Holding Account

I don't have a "Match." What should I do?

https://quickbooks-stripe.acodei.com/data?type=payouts

. Are you getting a specific error? If so, try to follow the prompts to address the error. Use this article to help address specific errors: 

https://help.acodei.com/article/17-payouts-not-syncing

If you still can't figure out why you don't have a match, message support through your Support page inside the app or via email at 

To reconcile your Deposits or Transfers, follow two essential steps:

Log into your Stripe account, then visit Balances -> Payouts. You can click any payout made from Stripe to your bank on this page. You can then cross-reference this Payout information with the Deposit created by Acodei, waiting for a "Match."

Regularly reconcile your Checking account in QuickBooks Online.

Getting a Bank Feed Match in QuickBooks Online

We are a small, US-based company. We do our best to respond within 24 hours, Monday - Friday, and we give priority to standard and premium tier subscribers. We do not generally offer support on weekends or holidays.

Click support on the left menu within the app to send us your message. Alternatively, please email us at support@acodei.com.

Contact Us

While uncommon, the QuickBooks API periodically creates duplicates of sales receipts or other documents. Although we have addressed the issue as comprehensively as possible within our code, the possibility of duplicates still remains. With this in mind, we have developed two tools that you can use to manage potential duplicates.

1) On the data feed page, you can run a duplicate check anytime using the button in the top right of the page. This will automatically search for duplicates and delete them if found. This search runs in the background and doesn't require any additional action.

2) On the account mapping page, you can enable "Advanced Duplicate Protection". This feature inputs a unique identifier on each sales receipt that prevents duplication. Before you 

Duplicate data

Typically, real-time transactions we receive from Stripe are pushed through our queue very quickly. However, sometimes transactions become stuck due to an error from QuickBooks or a high volume of transactions. If you see a transaction that has been stuck in progress for an extended period of time, please email us at 

The rate at which we can process historical data depends on various factors. If you are making a large historical data request, you can anticipate that we will sync approximately 500 transactions per hour. Depending on the case, we might process more or less. 

Payouts are always the last thing to sync in a historical pull. This means that if you order 12 months of data, we will attempt to push all sales receipts and refund receipts to QuickBooks before matching them up for a deposit. 

If you have any concerns about your historical pull, feel free to contact us at support@acodei.com

Transactions on Data Feed Stuck on "In Progress"

You can easily delete any data we have imported into your QuickBooks account. Go to your data feed, and select the transaction(s) you want to be deleted (click on the gray box on the right side of the transaction). Then go to the drop-down menu and select "Delete in QuickBooks." 

If you want data deleted and you are canceling your subscription, be sure to delete the data (or email us to do it for you) before you disconnect from the app. Once you're disconnected, we can't delete the data any longer. 

If you get a "Failed to Delete" as the status for the transaction, you'll need to unmatch the deposit from the payout on your banking feed in QuickBooks and then delete the data again.

Deleting Data

In order to connect a QuickBooks Online and a Stripe account to our app, you must have admin-level access to both the QuickBooks account as well as the Stripe account. 

If you need help connecting one of your accounts, please make sure you have admin access on both accounts and that you are logged into the right account.

Trouble connecting my QuickBooks or Stripe account

Because Stripe Sync by Acodei uses Intuit's single sign-on functionality, we cannot change the admin email address for users. This action needs to be taken by the user. This will modify where receipts and other transactional email updates are sent.

To make a change, have the person you want to be the new admin log into our app (https://quickbooks-stripe.acodei.com). After they log in, they should see a screen like this:

By changing admin, you will change the internal communications recipient and the primary account holder for our purposes.

How to change app admin

On the Account Mapping page, ensure you have selected the account (usually a checking account) into which Stripe deposits your payouts.

By choosing the correct account, our app can correctly create deposits for the payouts or move the funds from the Undeposited Funds/Payments to Deposit accounts in QuickBooks.

If the account into which you receive your Stripe Payouts changes, the best thing to do is immediately change your Deposit Account on the Account Mapping page. If it has been a few days or payouts have occurred, change your account, then you can always resync the relevant deposits on the Data Feed.

Connecting a Deposit Account

One of the most common payout errors on the data feed is related to missing data. Payouts contain data from various dates. A payout for January 10th might include transactions from January 6th, 7th, and 8th. As a result, if you join Acodei on January 9th, you will have a mismatch due to missing data on the January 10th payout. Acodei does not automatically retrieve the data for all dates in a payout.

Alternatively, if you only have a few payouts you would like synced and are on a paid plan, you can message us through your user portal, and we can sync unsynced payouts with this error for free.

Monthly / Annual Split Date of Stripe Payouts

Because payouts always contain data from a previous period, most users using Undeposited Funds will always have some unsynced payouts with this error.

A January 1st payout will contain transaction data from late December. How you handle a payout from the current year that includes data from a previous year is best determined with the help of a CPA. One alternative to avoid this issue is to utilize a separate holding account other than Undeposited Funds to capture transaction data.

Mismatch in QuickBooks due to Missing Data

Stripe Climate is a program by Stripe enabling businesses to combat climate change by investing in renewable energy projects and offsetting their carbon emissions. It allows companies to calculate their carbon footprint and support initiatives that reduce greenhouse gas emissions. Stripe Climate helps businesses take action against climate change by funding projects that lower their environmental impact.

Is Stripe Climate compatible with Acodei?

Yes, Acodei supports Stripe Climate. You'll be able to read on to understand how to feed Stripe Climate into QuickBooks Online.

Before adding Stripe Climate to Acodei, you must create a product (for use in invoices and sales receipts). If you need clarification about creating a product in QuickBooks, read our quick tutorial 

. You will likely want to link this product to an expense account.

Add the product to Uncommon transaction types

Once we detect Stripe Climate or any other uncommon transaction type on your account, you will see a new red text under your Stripe Holding Account, which indicates you need to map Stripe Climate. It will look something like this:

Add your newly created product on the Uncommon transaction mapping page as shown here:

Submit your changes, and Acodei will then process financing transactions on the daily balance summary or upon payout based on your preferences. Check your expense account to ensure the balance is changing correctly.

Correcting a Stripe Climate Error in your Data Feed

To fix a Stripe Climate Sync Error, go to the Account Mapping page (

https://quickbooks-stripe.acodei.com/mapping

). Please read the setup step above to ensure you have an existing product for Stripe Climate.

Then, click on the red "+ Add mapping for uncommon transaction types" button:

On the Uncommon Transaction Mapping page, choose the product from the dropdown menu you want Stripe Climate mapped to:

Click on the blue "Submit changes" button to confirm the addition of this product.

Once you have followed these steps, you can visit the Payouts tab in the Data Feed. If a payout is not synced because of a Stripe Climate error, you can resync the Deposit.

If you are still trying to fix the error, please message us at support@acodei.com, and we can resync your payouts that need to be synced.

Read more about Uncommon Transaction Mapping here:

https://atlas-kb.com/atlas-ehwcutmpm1/articles/251036-stripe-payouts-not-syncing

Stripe Climate Sync Setup and Debugging

Occasionally, Acodei may lose its authorization to connect via API to a QuickBooks company. This is a common issue in many API-based integrations and can be resolved with simple steps. Here's a detailed guide on how to re-establish the connection:

API connections can sometimes be interrupted or invalidated due to various factors such as updates in security protocols, password changes, or system updates in either QuickBooks or Acodei.

Steps to Reauthorize Acodei's Connection with QuickBooks:

Navigate to the top-left of your toolbar:

Common Issues