Transfer marking in PocketSmith

For other details about transfer transactions, read this guide: Transfers.

All transactions assigned to your transfer category will be marked as transfers and displayed with the transfer icon, making them easy to recognise around your PocketSmith account.

You can also manually mark transactions as transfers.

Transfer transactions like this will be removed from the Earning and Spending chart on your Dashboard, the Digest page, and the Income & Expense statement. 

They will also be excluded by default from the totals on the Budget Summary (at the top of the Budget page) and from the overall figure on the Trends page.

Creating a transfer category

When you create a transfer category, it will mark any new transactions assigned to this category as transfers; however, it won't mark existing transactions assigned to this category as transfers.

To mark the existing transactions as transfers at this time of changing the category to a transfer category, you will need to select the following option that will become available to you: Mark transactions already assigned to this category as transfers.

Removing a transfer category

If you want to remove a transfer category so it becomes a regular income or expense category, you can do this by editing the Transfer options and deselecting the option This is a transfer category.

Following this, you'll be given the additional option: Unmark transactions already assigned to this category to no longer be transfers. It's important to consider this option because, if left unchecked, all transactions within the category will still be marked as transfers.

See: Reverting a transfer category to a regular category for further details

Automatic transfer marking analyses your transactions to identify and mark both income and expense transactions that match a transfer between accounts, regardless of whether these transactions have been assigned to a transfer category.

This is based on a complex matching rule that compares the amounts, dates, merchant names, and accounts of the transactions.

For example, a $100 credit transaction occurring on January 5th in one of your accounts will likely be matched with a $100 debit transaction occurring on January 4th in another of your accounts. Both transactions will then be automatically marked as a transfer.

PocketSmith won't mark transactions as transfers if it finds conflicting transactions.

Transfers are seen as conflicted when there is more than one possible match for a given transaction. For example, if you had two expense transactions within a day or so of each other, and one income transaction on the same day, PocketSmith might not be able to determine confidently which of the expense transactions should be associated with the income transaction.

PocketSmith will attempt to resolve these conflicts by inspecting merchant descriptions and stored account numbers. If PocketSmith cannot resolve these conflicts through these means, then it'll err on the side of caution and leave the transactions unmarked as transfers.

A way to resolve these conflicts manually is to search for possible transfers on the Transactions page. Just head to the Transactions page, use the Tools menu, and choose Possible transfers. This will show all possible transfers based on a simpler matching algorithm and lets you quickly track down transactions that were considered conflicted during import.

You can review transactions that have been automatically marked as transfers in the Awaiting confirmation section of the Transactions page. If you have any transactions you'd like to unmark as transfers, you can do so here.

Your transaction review settings let you choose whether to review these types of transactions.

You can manually mark or unmark transactions as transfers when editing a single transaction, or use the bulk edit tool to change multiple transactions in one go.

To mark or unmark a single transaction as a transfer, click the transfer icon in the Edit transaction form:

For more details, including how to mark or unmark multiple transactions in one go, please see:

If some of your transactions have been incorrectly marked with the transfer icon and don't have a matching credit or debit transaction in another account, this is likely caused by the auto-categorise feature.

If you have the auro-categorise feature turned on (feed accounts only), and your transactions are being incorrectly assigned to a transfer category, they are simultaneously marked with the transfer icon. However, if you manually reassign a transaction to a different (non-transfer) category, the transfer icon won't be removed during this process, and you'll need to remove it manually.

Instead of manually reassigning a transaction, it's best to create category rules or filters to ensure the transaction is assigned to your preferred category. To learn how to create category rules or filters, please see:

To help find transactions which have been incorrectly marked as a Transfer, you can use the Search Panel on the Transaction page:

You can then Edit multiple transactions in bulk to remove the transfer marking on any transactions incorrectly marked as transfers.