I wouldn't really count the feeds sage has... We moved to the now-extinct SBCFN on account of the feeds. A mere swift 7 months later they're functional. There are errors everywhere and if you have 2fa on your banking, you have to jump through extra hoops.
And the matching is not even half as good as Xero had when I last used it 10 years ago.
Late to the party but have you read up on misophonia?
Difference between regular noise issues vs miso is the scale - if you get a lil' irritated, you're probably just a bitty crochety. If you get pushed to anger you might be in miso territory.
Avoidance, mimicking, mindfulness are easy & common practices. SSRIs/CBD/CBT are more clinical methods and then there's the good ole high-five-the-bugler-in-the-face-with-a-chair approach.
Last one might not be totally kosher nor recommended.
Methinks someone jumped on the SEO bandwagon so hard their common sense fell out.
And they wonder why people think accountants are a dry bunch...
TSO used to be good until they got bought over by GoDaddy. Now they're a complete joke. They fail the uptime promise every month and you have to fight them to get the contracted refund.
Their hosting also attracts ddos - For a year, I had a constant stream of attempts - about 5/min. For a year. The second I moved from TSO, they stopped.
So if you look at Adaptive, what can it not provide that you believe you could?
Who goes into Dragons Den giving away 20% equity? Start from 5% and negotiate up. #aimfortheskies /s
We're biting the bullet and moving to SBC. It's... okay.
We're at a stage where Sage50 isn't enough but proper ERP systems are too much. SBC does enough. Our main draw was the dimensional accounting and the approvals process which brings us from using folders for invoice approvals to a semi-modern environment.
-you can't use the invoice batch import with invoice approvals which makes the input a bit slower than it should be
-editing a transaction is a ridiculous process
-you're on your own to learn it
-stock/fixed assets is pants
-consolidation is pants
On the flip side;
-it's easy to learn (but it's not just like Sage50! If the draw is that it's a Sage product and thus skills easily transferable, it isn't - if Xero is your preference, might as well bite the bullet and go for it as the learning curve is about the same)
-it does what you need it to and more
-they're trying to replicate Xero with the bank feeds. Which is kind of working, but kind of not. Still better than nothing!
-multiple control accounts
We ended up choosing it mainly because the built-in approvals, and we need an easy-to-learn system (our team is firmly stuck in the stone age. Even this is causing palpitations in our guys' tender little hearts). And I'm personally not a fan of Xero or Quickbooks so there's that.
TL;DR - It's not bad but it's not a superhero.
All this will be a thing of the past with MTD. ©
Thanks, I needed a laugh this morning!
We've had this issue recently, and basically got told you can't do much; the duplicate record is now there and the employees should be the ones to sort it from their end. *sigh*
If you want to keep on going with Payroo, keep going (don't P45 them!) as that's now the "correct" record.
What I did was:
- put the month of the switchover into query so HMRC can note that there is an issue on the employers' side of this. Still waiting on a response but I've made sure they know everything's in dispute so they can poke it with the interest.
-wrote a long-winded letter to the PAYE & SA side of HMRC (they will not speak to the employer on the phone but do accept letters from employers apparently) stating what's happened, that there are duplicate records with Mr A, B and C and could they please delete the incorrect records, attaching their P60s (as ours was PY), snapshots of the employee records with the correct/final RTI references and payslips for the periods in question. This sorted it from the employee's side pretty quickly.
It's a headache.