Skip to main content

Unmatched payouts and transfers

Fix payouts and transfers Finaloop couldn't match between your accounts and apps (Anomaly Detector), so money moving between your own accounts isn't counted as income or expenses.

Written by Emily Burrows

About

Applies to: Finaloop Accounting

Finaloop's real-time Anomaly Detector helps keep your books accurate by flagging transactions that seem to be missing a matching entry. It's a list of deposits and transfers Finaloop couldn't link to a sale, payout or account. This usually happens when we expect to see both sides of a transaction but can't find the match.

The Anomaly Detector is especially helpful when you have transfers or payments between different stores, payment processors, banks, or credit cards. Our system works to identify these transfers from both sides and match them up to make sure everything reconciles smoothly. Use this guide to see why a transaction goes unmatched and what information we'll need from you to resolve it.


1. Why the Anomaly Detector flags a transaction

You may see an anomaly flagged when there's a transaction that should have a match, but we can't find it. Here are some common types of transfers we keep an eye on:

  • Payouts from sales channels or payment processors to your bank. For example, when Amazon sends money to your checking account.

  • Transfers from your bank or credit card to stores or payment processors for things like chargebacks, refunds, or fees. For example, moving money from an Amex card to PayPal or Stripe.

  • Paying down your credit card from your bank account. For example, a payment from your checking account to your credit card.

  • Bank transfers between two of your business accounts. For example, transferring money from a Wells Fargo account to a Mercury account.

On the Transactions page, these transfers show with a status such as Payout from Shopify - Additional input required, Bank transfer - processing or Credit card payment - processing. A bank transfer or credit card payment stays in processing for 7 days while we look for the other side. If we still can't find it, the status changes to Additional input required and we ask you.

Why a transaction may be unmatched

Sometimes, we can't find both sides of a transfer to match it up. Here are some reasons why that might happen:

  • The account isn't connected to Finaloop, including:

    1. A bank or credit card account was never connected or was disconnected. We'll ask you to connect or reconnect the account.

    2. The transfer involved a personal account. We'll need you to confirm who owns the account.

    3. The bank or credit card account isn't supported by our integrations. If that's the case, we might need a CSV file with the missing transactions or for you to grant us a bookkeeper role in your account.

    4. The transfer was sent to or received from another party. For example, if your Shopify payouts go directly to a lending institution or a related business.

  • The account is connected but is missing some transactions. This could be because some banks limit how far back we can import transactions. In this case, we might ask you to upload a PDF statement with the missing transactions.

  • Our system didn't automatically catch the match. It doesn't happen often, but if it does, we'll ask you to help match the transactions from a list we provide.


2. How to fix anomalies

When an anomaly is flagged, we'll let you know with a Review unmatched money movements mission (a task in My missions where we ask you for information we need, or in your Getting started checklist) and ask for a little help to fix it. You can also reach the Anomaly Detector by clicking Review next to Unidentified payouts & transfers in your reports, or Go to the Anomaly Detector in the Year-end Hub.

The Anomaly Detector page on the Open issues tab, with the category list on the left and a payout row showing the Your input needed tag.

① Open issues and Processing tabs, ② the category list, ③ the Your input needed tag.

  1. Open the Anomaly Detector from the mission (Let's check it out) or the checklist task (Review).

  2. On the Open issues tab, pick a category on the left: Payouts from apps, Transfers to apps, or under Internal transfers, Missing 'sending account' or Missing 'receiving account'. Use Period to narrow the dates.

  3. Click Your input needed on a row.

  4. If we found a likely match, you'll see Possible matching transaction found. Select the right transaction, or select None of the above to continue.

  5. Otherwise, choose where the money went or came from, then click Next. For a payout the options are:

    • Received in an existing account: select the bank account or card.

    • Received in an unconnected bank account: we'll ask you to connect it. If you can't, you can upload its transactions as a CSV file instead.

    • Received in a personal account: tell us who owns the account.

    • Other: choose Related business or party, Lenders or lending platform or Another third party.

For transfers to apps, the same options read Sent from.... For internal transfers between your own accounts, Other is replaced by It's not a bank transfer, which lets you categorize the transaction instead.

The Select the receiving account window, with options for an existing account, an unconnected bank account, a personal account and Other.

① Received in an existing account, ② Received in an unconnected bank account, ③ Received in a personal account, ④ Other.

Depending on the situation, here are the fixes we would ask from you:

The issue

The fix

A bank or credit card account was never connected or was disconnected from Finaloop

Connect or reconnect the account from the Anomaly Detector, or on Settings → Banks & Credit Cards.

A bank or credit card account isn't supported by our integrations

Upload a CSV file with the missing transactions when we ask for it.

The transfer involved a personal account

Confirm the ownership of the personal account by answering the questions in the Anomaly Detector.

The transfer was sent to or received from another party

Provide details of the transaction and the other party by answering the questions in the Anomaly Detector.

The account is connected but is missing some transactions

Choose Upload a bank statement and upload a PDF statement for any missing transactions.

Our system didn't automatically catch the match

Help match the transaction from the list we suggest.

Note: In the Anomaly Detector, bank statements are uploaded as PDF files (Upload .PDF file). CSV files are only requested for accounts that can't be connected.

Once everything's cleared up, we'll update your books to reflect the correct entries. Some answers resolve the item right away (Issue resolved successfully). Others, like statement uploads, move it to the Processing tab while our team reviews it. No action is needed from you while it's there.

Why your input keeps your books accurate

Reconciliation issues are one of the most common causes of inaccurate books in traditional accounting software. Oftentimes, these types of errors can result in double counting transactions or erroneously classifying a transfer as additional income or expense.

As accuracy-obsessed accountants, we built Finaloop with our real-time Anomaly Detector to ensure any of these types of transactions are flagged and reconciled correctly, giving you complete confidence in the accuracy of your books. In order to ensure this level of accuracy, we'll sometimes need some input from you so we have all the pieces of the puzzle to give you the full picture of your finances.


Related articles


Need help?

If you have any questions or run into any issues, our Support team is always here to help. Just reach out to us at [email protected].

Did this answer your question?