My idea is simple, and should be easy to implement with minimal coding requirements.
Bank rules - great for future transactions from a feed. Helps cut down a lot of the workload going forward, but, what about when you're sent a new client who has an entire year to do a week before their end of year? They send you the details to set up a bank feed, and it loads with 6000 transactions.
You set up bank rules for the one off transactions, then manually process the rest of that bulk reference the same way. It works, but it's slow, time consuming and can be very stressful when you already have dozens of companies to finalise for submissions.
Recoding the options for bankrules could solve hours or even days worth of work a week. Recoding the ability to create bank rules through the normal banking screen, prior to importing a bank feed could cut off a lot of this. Likewise, unresteicting the rules from post forward, to post historically (for unmatched transactions) would help mitigate this.
With recent... Issues... In sage, global auth service and banks own tech, this would be a very helpful tweak to the program for us, and I hope for others.
Guest
