Skip to Main Content
Status Future consideration
Workspace Reckon One
Categories Banking
Created by Guest
Created on Mar 22, 2018

Transaction rules to also perform wildcard searches

Currently transaction rules have multiple search options available however none of these options perform a wildcard search.

Sometimes you need the rule to identify some text within a string of text. Currently you cannot do this in R1. I'm sure this would be simple to implement & a useful function to R1 users. 

  • Attach files
  • Guest
    Reply
    |
    Jan 6, 2024

    Sorry but I have to say the transaction rules situation is intolerable. It's costing me dozens of hours a year.

    What's so difficult about inserting logic code that allows better selection of key words? The current code is very basic, and makes the Reckon and their programmers look primitive.

    It would save immense amounts of time, since most of mine transactions are from the same supplier, and I could just click 'match' but mostly I cannot. I need to be able to select say a short string, not have to enter the whole transaction string to get a match.

    The fact Reckon does not even provide proper definitions of the various logic operations says it all. Compare the 3 options in Reckons drop down box, none of which seem to work very well, to say Excels extensive logic options.

    Sorry but very unimpressed. It should be top priority.


  • Guest
    Reply
    |
    May 5, 2023

    This feature is becoming more important as more card transactions include the Date & Time but do not leave a space before the merchant name.

    Therefore the reference looks like "EFTPOS 01/01 15:45Cornerstore123"

    I am regularly trying to add new rules, then realising i already have one but it doesn't work because it is looking for the whole string.

    Could the priority of this be increased so it is developed soon?


  • Guest
    Reply
    |
    Feb 4, 2023

    This would be a very useful feature. Sometimes an invoice number is part of the transaction and the type is only identified by the first two digits of this invoice number.

  • Admin
    Jason Hollis
    Reply
    |
    Jan 10, 2021

    Hi Hariharan, this task is sitting in the backlog as we have decided to replace the banking rules with our new bank transaction product that was released last year for Reckon Accounts Hosted. This work will commence later in this first quarter with new bank account onboarding, then the replacement of the current bank transaction screen which includes rules, and then we'll focus on rule improvements. Apologies for not updating the followers of this idea with our plans.

  • Guest
    Reply
    |
    Jan 9, 2021

    @Jason - It has been 6 months since your comment - any progress? This would be really useful.

  • Guest
    Reply
    |
    Aug 30, 2019

    There are related posts about the way Transaction Rule set the "description" as a standard but in many instances the existing description is fine and should be retained.  Any update to the transaction rule function should look at this aspect as well. Allowing wild card character to "keep" the exisitng description would be great.

  • Admin
    Jason Hollis
    Reply
    |
    Aug 11, 2019

    Hi Ashley. We were trying to work through ideas based purely on vote numbers. Given the position of this request I would say probably 6 months.

  • Guest
    Reply
    |
    Aug 10, 2019

    Is there a time frame for this feature?

  • Guest
    Reply
    |
    Nov 24, 2018

    Yes this would be extremely useful.

  • Guest
    Reply
    |
    Nov 6, 2018

    Great idea. Please add this feature. 

5 MERGED

BankData - Allow the use of WildCards in Transaction Rules

Merged
BankData - Allow the use of WildCards in Transaction Rules
over 5 years ago in Reckon One / Banking 2 Future consideration