- Regulation: Some countries (and some US States) do have guidelines on how this type of software must be constructed, make sure you are compliant to those regulations if it's the case. Example: IIRC you need permits to even start building a POS solutions in some states.
- Integration: An usable accounting software must include HR or have integration with common HR software used by most companies. HR is one of the most complex parts of accounting. Most clients will have outdated solutions they are comfortable working with and won't change completely to your software, make sure you can integrate with tools they want to continue using. Only fight the old if the option you are offering means task elimination. Don't forget you need to integrate with banks, but that's easy.
- Customization: Human systems are not pretty. There are things that do not make sense to accounting and are often loaded with emotional decisions, human relationships and corporate strategy. Sometimes a software just streamlines the human mess, make sure your software can be customized by your clients to a certain point.
I use QuickenPro (or whatever they call it today) and while I dislike it, it has Maximum Accountant InterOperability (MAIO) - since it's what my accountant's office tends to use.
I really like the idea of a simple, straightforward, just enter the data and get stuff done without getting in my way sort of package, but without AIO and preferably MAIO, I ain't even thinkin' 'bout thinkin' 'bout switchin'.
I suspect I'm not the only one in this boat, and "I dislike that other thing" doesn't really make "the other thing" broken - and if it ain't broke, why fix it? (In other words, the pain of sacrificing MAIO likely exceeds any pain from using "the other thing".)
What plans, if any, do you have for data import/export to ease pain and ensure MAIO?
A couple of questions:
How do I set up things like financial year start date, VAT quarters, etc.
Does manager.io support flat rate VAT? (I'm in the UK)
Not that it matters, I'm just intrigued - why is the OSX package so much bigger?
2.) There is no need to setup financial periods, just setup individual reports for periods you need.
3.) OSX package is bigger because it bundles Mono dependency.
In the flat rate VAT scheme I pay 14% of my turnover, instead of [VAT on invoices] - [VAT on purchases], this saves me a bit of money, but there's not much software that supports it.
Any chance you'd develop a generic VAT plugin? The requirements across Europe must be quite similar apart from rates, periods and invoice/receipts based calculation. I ask, because I doubt there'll be much impetus for you to develop an Irish VAT plugin, given the size of our population and there's no point in even trialling the software without it.
I created a request on your uservoice page, for what it's worth: http://manager.uservoice.com/forums/202564-plugin-ideas/sugg...
I have an error on emailing invoices. It says just "Error" in modal.
Have you thought on maybe making a walkthrough screencast for tech guys like us from zero to doing the whole accounting through your app?
Thanks for the app, great job :)
I'm curious as to why have you decided to package this as a desktop software, rather than a web app?
Just guessing
Side Note, for those who haven't downloaded the app. There doesn't seem to be a mention for the cloud storage option on the home page. The app stores data locally, but offers the option of cloud storage with additional benefits for $5/month. Screenshot: http://i.imgur.com/zWYpv7I.png
And, incidentally, you are welcome for this submission ;)
The people who make this could sell to GoogleAppleSoft, get hit by a bus, or start charging stupid money for it, and I'll still have a copy and all my data. A webapp by a company I've never heard of before needs to do much more to reassure me that won't happen.