This issue also applies (but even more so) when bulk tagging transactions.
↧
Why are descriptions mandatory when tagging a transaction?
↧
UX Feedback: Auto-tagging applicable pending transactions after a tagging rule has been created
Although I’m now set up, this feedback goes back to when I was setting up…
Imagine I’ve uploaded a few thousand transactions and I’m now going through them and tagging them. As I go along, I’m also creating tagging rules to make things easy for me in the future.
After creating a tagging rule, what I would really loved to see was something like this:
“There are another 189 untagged transactions which match this rule. Would you like to auto tag them?”
Without that, I had to keep searching for the text string myself and bulk tag for every 50 transactions. So what the UX could have done for me there and then, I had to do myself. I might sound spoilt, but the experience is particularly painful when you have to do this again and again for each supplier.
Xero, QuickBooks and (I think) Wave do this, so please consider it as a way of making the first experience even more awesome.
↧
↧
VAT Return - and Wages
Are you definitely sure it’s the wages you’re seeing? If you “download calculations” on the VAT return screen and open the resulting CSV in excel or google sheets it’ll show you exactly what makes up the box totals.
↧
Affinity profiles have been automatically detached
@mgeezy - I’ve responded to your other post for you.
↧
HMRC hasn’t processed my VAT Return
This topic was automatically closed after 7 days. New replies are no longer allowed.
↧
↧
Re-Run bank tagging rules
Although I’m now set up, this feedback goes back to when I was setting up…
Imagine I’ve uploaded a few thousand transactions and I’m now going through them and tagging them. As I go along, I’m also creating tagging rules to make things easy for me in the future.
After creating a tagging rule, what I would really loved to see was something like this:
“There are another 189 untagged transactions which match this rule. Would you like to auto tag them?”
Without that, I had to keep searching for the text string myself and bulk tag for every 50 transactions. So what the UX could have done for me there and then, I had to do myself. I might sound spoilt, but the experience is particularly painful when you have to do this again and again for each supplier.
Xero, QuickBooks and (I think) Wave do this, so please consider it as a way of making the first experience even more awesome.
↧
Re-Run bank tagging rules
In addition to the above, I’d love to see the same on in the bank tagging rule section.
At the moment, we see this:
Rather than telling me that the rule will only apply to newly created bank entries, it would be great to have it as options:
- Only apply rule to newly created entries
- Apply rule to the following 15 existing entries
After the 2nd option, you can then show the list of entries as you do at the top of that same page:
It seems like all the logic is there to make this happen.
↧
UX Feedback: Auto-tagging applicable pending transactions after a tagging rule has been created
2 posts were merged into an existing topic: Re-Run bank tagging rules
↧
UX Feedback: Auto-tagging applicable pending transactions after a tagging rule has been created
↧
↧
Re-Run bank tagging rules
Hi @fambi
I’ve merged your thread into the existing request for this.
We’ll continue to monitor the interest here and will happily take a further look into the feasibility of this if there’s enough interest from the community.
↧
UX Feedback: Auto-tagging applicable pending transactions after a tagging rule has been created
↧
Why are descriptions mandatory when tagging a transaction?
I’m not convinced it’s a good idea to remove the requirement to enter a description. Firstly there’s now a “Same as last invoice” link next to the description field, which is almost as good as having a supplier default (albeit 1 extra click).
The other reason is to encourage good indexing of information and easier retrieval. This may not be a factor for everyone, but I think it’s good practice for new users who are just coming onboard with MTD.
I suppose we could allow it to be optional based on an account level setting, and then when blank either set as “N/A” or the nominal account name. That could be an option… just not universally making it optional for everyone.
@fambi Incidentally the “Same as last invoice” link may be missing on your screenshot above if it’s the first item you’re tagging to that supplier.
↧
PayPal Feed Not Marking Off Paid Invoices
Hi @favdes
If the invoice is created through QuickFile and then paid through PayPal, via the “Pay Online” link, it should tag automatically.
If the invoice is created in QuickFile but paid through PayPal directly (rather than the “Pay Online” button in QuickFile), then it won’t be tagged automatically.
What I think @Lurch was referring to, is the PayPal feed automatically creating the invoice at the same time the feed runs.
↧
↧
Why are descriptions mandatory when tagging a transaction?
I appreciate the idea of encouraging good indexing is great as a best practice, but I believe that type of encouragement belongs in guides and tooltips… not hard-coded into mandatory requirements that create user frustration for the many cases where it is not relevant.
Users do eventually learn to live with frustrations like these when they feel that software as a whole beats the competition as a whole. But it’s never good when software providers allow that to happen as it’s a frustration that could have been done away with.
Your suggestion of going with the nominal account name sounds like an excellent halfway point.
So perhaps you do something like this… The first time someone tries to leave the description blank, throw up a warning that says something like, “You’ve left the description empty. We recommend you to provide a description so that [explanation goes here].” followed by a “Don’t show this again.” confirmation checkbox.
(Note: If you’re not limited by privacy restrictions, why don’t you guys run some type of database summary on your side to see how many entries you’re getting such as “Misc”, “Miscellaneous”, “NA”, “N/A” etc to see how many other users are keying in useless information just to circumvent the mandatory requirement.)
↧
PayPal Feed Not Marking Off Paid Invoices
Yes, thank you for putting my thoughts into words, I was struggling for a moment!
I guess you mean ‘paid through PayPal directly’ here?
↧
Why are descriptions mandatory when tagging a transaction?
Btw, I’m now experiencing the same thing now when tagging sales.
We only sell 1 thing, so I’m now being forced to key the same value for about 900 customers (and can’t be saved by the “use previous” option as all of these are different customers).
↧
Why are descriptions mandatory when tagging a transaction?
@fambi - I’m assuming you’re trying to do this with a large number of clients in one go? If so, I think you’re going to be better off importing your invoices from a CSV file rather than entering them manually.
There’s a guide on this, here: Importing sales and purchase invoices
↧
↧
Integration Request: Add support for Capital On Tap
Yodlee works by screen scraping internet banking. I suspect when they get errors like this that suggest the bank has changed something in the layout of their internet banking pages it is automatically referred to their developers who then update their scraper to work with the new format within a few days.
↧
Integration Request: Add support for Capital On Tap
Hi @fambi,
If you are still getting this error after a couple of days then we can certainly try and raise it with Yodlee, but usually they do resolve themselves in a few days.
↧
PayPal Feed Not Marking Off Paid Invoices
Spot on - thanks 
. I’ve updated the post
↧