Cannot identify a transaction when Transaction Rule set to match Payee name Exactly

Legacy KB ID: 5462

Question

I have setup a rule using the EXACTLY criteria for my Payee.  Why are the transactions not identified?

Answer

Use the criteria CONTAINS for “Payee is”

 

The Issue

When you use the criteria EXACTLY, your qualification must match the incoming field "exactly".

The Payee field can contain up to 32 characters which will include spaces.  The banks do use this field for coding information about the type of transaction and will separate that code from the Payee by a number of spaces.

When using EXACTLY, you must include the exact number of spaces included in the incoming field.

For example, if the incoming information is PVISA(5 spaces)My Shop, then the 5 spaces between PVISA and My must be included in your qualification.

 

Workaround

Avoid using EXACTLY.  Use CONTAINS wherever possible.

 

When CONTAINS cannot be used:

  1. Open the QIF or QBO file in Notepad
    1. BankData imports are saved in C:\Documents\Reckon Limited\olacclst.qbo.
    This file is not accessible to Hosted users.
  2. On the line for your Payee, place the cursor under the first space after the first word (for example, PVisa) and use the right arrow to move and count the spaces up to the cursor resting under the first character of the name (for example, M…)
  3. Determine the space count for all gaps between words;
  4. In creating the Transaction Rule, ensure the correct number of spaces are used between each word.

 


Need more help?

Ask the Reckon Community at: https://community.reckon.com/categories/reckonaccounts

Or Log a Support Ticket: https://www.reckon.com/au/support/

 


How did we do?

Reckon Accounts Desktop: \Select Bank Account greyed out when importing files

Reckon Accounts Desktop: Finding cleared transactions that have been changed or deleted

Related Articles

Cannot delete PDF attachments to a transaction
Cannot delete a pdf attachment attached to a transaction.
Cannot replace a category on a transaction in Quicken
Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)