It is exactly SMB-friendly accounting systems that invest the most in efficient billing & invoicing technology, as larger companies are usually looking at tools they can integrate with their bank service providers, and handle payments from their original accounts. The challenge is, as you noticed, to get a standalone and restrictions-free product, or at least one where you don’t have to pay recurring fees each time you cross a predetermined limit.
Billy is attractive, basic accounting software for small service-oriented businesses. With it, you can create quotes, estimates and invoices, record expenses and generate reports. It connects to your business bank and credit card accounts to automatically download transaction data and has a proactive reconciliation process that predicts matches. It has an iPhone app and a Chrome extension for capturing receipts. billyapp.com
Quicken lets you manage both your personal and business finances in one place, making it a convenient solution for really small businesses and home-based entrepreneurs who don't need accounting software designed for larger or more established businesses. The downside, however, is that the software isn't cloud-based and is only available for Windows, though it has iOS and Android apps that allow you to view your data. quicken.com
But if test automation is so limited, why do we do it in the first place? Because we have to, there is simply no other way. Because development adds up, testing doesn’t. Each iteration and release adds new features to the software (or so it should). And they need to be tested, manually. But new features also usually cause changes in the software that can break existing functionality. So existing functionality has to be tested, too. Ideally, you even want existing functionality to be tested continuously, so you recognise fast if changes break existing functionality and need some rework. But even if you only test before releases, in a team with a fixed number of developers and testers, over time, the testers are bound to fall behind. This is why at some point, testing has to be automated.
This article uses the term “tester” to refer to the person involved in testing software with automation tools. It is not meant to distinguish by job title or technical proficiency. Jim Hazen describes himself as a hybrid, or “technical tester,” because he can write test scripts and develop what he refers to as “testware.” The trend is to hire for multiple skillsets, but that does not mean the non-technical stakeholders involved in software development don’t benefit from automation testing.