The end of the accounting search
lwn.net
lwn.net
1) Forcing all their customers to migrate to the online version of their program. Many of the clients I've spoken to were happy with and preferred the Desktop version. The Desktop version is faster and can do more than the online version.
2) Throwing major updates at the online version that hides or moves functionality. I work with multiple clients and based on the client their version of QuickBooks can be very different from another's. Even the same client that has multiple businesses and has to use multiple subscriptions could have a different look. I don't know what drives this at Intuit but it's confusing for me and I'm supposed to be the expert.
3) Relentlessly raise prices. Intuit has been annually raising their prices in what appears to be an attempt to eventually price everyone out of their product. Some clients have to pay 200.00 a month for the advanced version for one feature they need to have for their business! The attitude from Intuit feels like "So where else are you going to go?"
For most of my adult life I've worked as an accountant that works mainly with QuickBooks but I'm worried that I'm going to have to try to find a new way of supporting myself because Intuit appears to be demonstrating by their recent decisions that they don't need to show loyalty to customers or even keep customers. If they can have a few stay on to pay ridiculous subscription fees that's all they need.
Users can slowly adapt, but most businesses larger than a sole proprietorship need multiuser capability.
It could be because it's indeed so easy that it's boring, or could be that anyone with the necessary knowledge of accounting standards makes way more money doing other stuff than coding for free.
If you want to change either your bookkeeper or your accountant, your new bookkeeper and accountant know how to use it.
Every time I have to open up QB, I cringe. Painful!
Agree with the points above about updates and $$$ increases. The worse!
I recently attempted to help a non profit setup Gnucash. It turned out to be cheaper to get commercial software (Xero) as they were spending too much time on upskilling in Gnucash.
They took a week to onboard to the new system and are amazing at how quickly they can do everything they need to do.
They’re one step from just using excel because it won’t change on them.
Are your accounting people quite young? Excel moves and changes stuff, though not on quite such an aggressive timeline. Modern Office is not like 1990s Office where you buy it and then it doesn't change unless you decide to change it.
This is fine, the universe's one constant is change, if we fight it we'll lose, but it's worth calling out that there will be change, just some of these outfits are taking the piss.
That may be one part.
But another part is companies that need to demonstrate to their uses that a version change is a big change.
Microsoft is (im)famous for this: as far as I can tell, there has been little need for the constant UI churn in windows aside from convincing users that a new version is big enough to warrant that appellation (as opposed to a service pack/patch).
So I don't know where this conspiracy theory comes from, but it's entirely unfounded unless you're talking about a designer like Jony Ive with the power to go through multiple obstacles with ease, in which case the change isn't happening to prove he's needed but because he has a different vision.
Definitely not the case everywhere.
EDIT: rather than downvoting, maybe you could engage? Following the thread back the question was about accountants using Excel and then someone weighed in that they use Libre/open office. I have never seen an accountant use libre office for accounts work, hence my question. Are you an accountant who moved from Excel because of whatever, or was your comment irrelevant?
I had used excel 2003 until I was forced to use win 10 at which point it barely functioned anymore (i.e., it worked great in win 7)
I still miss excel 2003, it has been downhill from there
As for accounting software, they all mostly stink though serve a purpose in larger companies where you need some degree of separation of duties to reduce (at least in appearance as much internal control is theatre) error/theft risk...
In all fairness, back them I also had to use MS Office for certain other tasks, but luckily I don't need that anymore.
Now there is Confluence instead however to mangle our docs and waste our time.
And I don't hate the ribbon interface, I think it's totally fine--but also, in Excel specifically, I almost never click a button on it.
QuickBooks's online version, on the other hand, has terrible discoverability and doesn't have standard keyboard controls.
The Excel data format has changed once, significantly, in the past 2 decades (which was forced on MS and even though MS has tried to sabotage the openness of the new formats they were required to create, its still much better than the predecessors).
It’s hard to think of any other change that wasn’t just an addition (new formulas, higher column/row limits).
But, importantly, that data format change didn't mean you were forced to stop using the old format.
Excel UI interface changes but it won't change your spreadsheet content, which is the core functionality Excel users care about.
I've been using 15 year old .xlsx files with no issues across Excel 2007, to 2021, and Excel online.
I've seen companies using files with an absurd amount of worksheets within the file, or with an absurd number of rows (up to the limit), and those haven't been broken.
And I don't remember transitioning from xls to xlsx to be that painful, but this might be untrue for people using some very specific features.
The problem with all of these enterprise web applications is that they all suck. I worked for a big government agency that transitioned from a mostly homegrown, mainframe 3270 based accounting system to PeopleSoft. The staff revolted.
We joked about the “Revenge of the Beancounters”, but looking at it, they were right. It took them 4-6 months to train a new person with the old system, but they were hyper-productive. With the new system, they actually needed to grow the staff because you couldn’t build out workflows that the business needed.
They did get some benefits, like improved payments and invoice tracking. (Which drove the business case) But the general financial operations suffered.
(for those who don't know/understand, the "joke" in the industry about SAP is that it's a perfect fit for you, so long as you are willing to change all your processes and workflows to fit SAP. And no, it's not really a joke)
> Outside of fundamentally better workflow improvements, most professional fields don't randomly change their tools. If you gave a professional artist a new pencil that had to be gripped differently for no reason, they'd throw it in the trash.
>
> But in software, we tolerate buggy tools that change all the time for no discernible reason. We tolerate software that simultaneously targets professionals and casual users, serving both segments poorly. We tolerate software that can't be customized or adapted for specific workflows. It's tough to put into words, but if you watch a musician or a painter interact with their tools, there's a very clear difference that emerges, and over time you start to realize how much better all of their stuff is.
>
> In most professional artistic settings, workflow changes only happen because they have a clear benefit -- drawing from your shoulder instead of your wrist, changing your embouchure if you play an instrument. And even in those fields, it's generally accepted that over time people will end up with very specialized setups that are very consistent and refined and that remain constant for years and years.
>
> Only in the software industry would someone tell me that my professional tools should change because change is inherently good. Only in commercial software would an elegant, consistent interface like Markdown that allowed me to build up decades of muscle memory until my computer was an extension of my fingers and I didn't need to think about the way I typed -- only in software would that be considered a bad thing.
I was working at a software company years back that was doing this significant interface change. I suggested we have an 'end goal' interface and breakdown changes into multiple releases over time, organised it so each version change is easier to adapt to and educates somewhat in the changes as they occur, but this approach got no traction. I still wonder if its the correct approach or its better to get it over with in one go and then try to be stable.
The other ends up feeling like death by a thousand cuts.
I once offered to fix the tab order on an input form, so the cursor started in the right box. The manager of that team got very excited and asked me not to change anything, the team had got used to the keystrokes!
My control key is hard to reach, so I hold spacebar instead,
and I configured Emacs to interpret a rapid temperature rise
as "Control."
Good ol' "M-x spacebar-thermometer-mode".Is that you, Arlene?
Seriously, everything you list (and more) are things my accountant complains about. You're not alone in being a QuickBooks insider who hates QuickBooks and would love to move their clients onto something else.
Historically, a huge strength of Intuit was the huge population of bookkeepers and accountants who would recommend QuickBooks to clients, but I don't see how anyone would recommend it at this point.
Ugh.
Many people don’t see software engineering as creative but it certainly can be!
Not the vocation for me but it's very interesting to talk with her about her experiences, because they're so remote from mine...
Accountants are extremely limited by rigid tools they use and laws they have to adgere to. Then comes given company's 'way we do things here' limit.
Take any modern programming language, you start with unique big problem/task, have to crack hundreds little and big problems, often with use of stackoverflow and other webs, but ie hard alghoritmic problems I solve mostly on my own since nobody faced those in exact mix of technologies, data and other constraints. There are sone further limits but my alghoritms are my solid creations, nobody ever questioned them nor made me refactor them for any reason.
To outsiders it may look exactly same weird nerd stuff of course. To me, accounting has very little room for creativity, its there but almost microscopic. And the joy you describe is also present, thats there in many jobs that actually create stuff, digital or not
There is some creativity in defining where to stash this or that number so that everything works out in the best way for the business. As others said, it's a bit like solving puzzles, and it's harder than it looks - it requires a significant level of preparation, and keeping up with constantly changing regulations.
What a lot of them also get pride from is formatting their reports "just so" - so that they're readable and enjoyable by businesspeople, while still being exact, comprehensive, and meeting formal standards. To me, that sort of thing is kinda boring and trivial, but for them it can be career-defining, life-or-death stuff. In a way, it's a hyper-specialized branch of graphic design.
I am an accountant, I never do any bookkeeping.
Last week a few things I did were
1) worked on a way to get sales rebates to correctly reflect in the product cost. This is half accounting knowledge and half ERP.
2) presented accounts at a meeting where I was trying to use the numbers to make the business take a different strategic direction.
3) reviewed and questioned the commercial sense in other people's plans
4) worked out how to run a new process through the ERP so the accounts flowed through correctly
In other weeks I may be forecasting cash needs, doing an investment appraisal, building business plans, getting funding, writing sql to get data, building a BI system...
I like the creativity and the amazing variety of what I get to do in accounts.
Digital feudalism is a real thing.
Edit: intuit and quickbooks
That’s what I think this is all about
It's not about looks, it's about locking people to the platform and milking them in a subscription model
In contrast, QB Online has a REST API.
i've not found any local solutions that i like, at a cost (perpetual license is a requirement) that i like. so i moved to xero. it's slow and annoying in lots of ways, but it's very usable. some things are less abstract than QB, ie the method of entry for those is closer to just doing a journal entry, i guess this is good or bad depending on the user.
I guess that, behind the scenes, Quickbooks might run each client on its own code base or some limited multi-tenancy on a shared code base. So if your clients span those code bases, they could easily be on different versions. And the heuristics for when a code base is upgraded may depend on factors that you can’t see.
This is just a hypothetical, but that’s where my money is.
I'm curious what the secret sauce is that Intuit/QB has provided advisors, like yourself, to stay on their platform for the past 20 years. What would it take for another accounting software company to get you, and others in your same situation, to commit to their platform for the next 20 years?
What? I work in accounting and I was reading your post with curiosity until this. How do you support yourself—being a QB Pro advisor or as an accountant?
>Crashes were frequent; QuickBooks users know to make backups every few minutes to avoid losing work.[...] More recently, Intuit has discontinued support for the desktop version entirely in an effort to force all users to its online, paid-by-the-month service.
Both of these statements are not true, based on both my professional and personal use of Quickbooks desktop for over 15 years. QB uses transaction logging[0] so that transactions are not lost, even after for example a power outage. And the desktop versions are still available, but no longer with a perpetual one-time license, but rather $800 annual subscription for the Accountant's version. (This is a doubling in price over just the last few years).
So, I will be able to use my 2022 desktop version into the future at no extra cost, however some of the internet-based services (receiving payments, for example) will no longer be supported after 3 years.
I have installed and started to migrate to GnuCash because I am not going to pay $800/yr to Intuit, especially when less and less of my use is for professional purposes.
Network clients crashing can cause issues that are difficult to unwind. It should not be possible to get the database into a state where backups + verification fail if it was enforcing referential integrity, but that seems to be common.
The official tools to get yourself out of a pickle from Intuit are guesses at best. There is a cottage industry of people who will (for a great fee depending on how urgent it is), attempt to recover/correct the database for you, because they have experience peeking behind the curtain and building additional tools on the XML API.
Good luck if you are using EDI or other electronic document exchange with other customers, and you transmit sales order numbers for a few hundred orders in the morning, and then things go pear shaped and QB refuses to cooperate and open the file in the afternoon. Going back to last night's backup means carefully/manually re-ordering 4 hrs of work to make sure that everything lines up, so you're probably in for a late day.
Intuit "officially" supports a linux based server for QBE, but the community seems to thumb it's nose up at it, and offers no support for this configuration.
QB, for many years was a very good price for the SMB market. There was a LOT of pricing headroom to the next best accounting package. Someone @ intuit has figured that out over the last 10 years and they are ratcheting up the price till customers fall out -- figuring it's finally worth it to drop QB for another solution.
I'm aware of a migration from QB Enterprise to QB Online, that after signing up and paying, Intuit basically aborted the process. "Sorry, we don't support doing multiple tax rates for employees in multiple states in the QB Online version, here's your money back". Maybe they fix that eventually, but that's where it stood last year.
QB is a frustrating product, for the inertia it currently has.
Intuit has an obvious disrespect for their customers - some important bugs have gone unfixed for years amid continual complaints, while the newbie support people suggest they be reported to Intuit!
I handle the accounting for a small non-profit. We need the ability to categorize our revenue and expense, which now requires the full QBO.
At $850 / year, the cost is out of line with our $30K / year revenue. But, I'm rather stuck because the organization needs to be able to transfer the work to another accountant if something happens to me, and GnuCash, ledger, hledger, etc. aren't well known. Also, we need the ability to accept payments from PayPal and Stripe without a lot of manual entry.
QB online would be too expensive. Xero might work. The fact that entering bills is an "advanced feature" in most packages gives me pause.
She had one of those "not calculators" with a built-in printer. Not sure what they are properly called.
Her "not calculator" was old, stained with cigarette smoke and coffee and she did not wish for a new one.
I got paid a bit a few times to clean it up inside and out. The thing was a tank. (If it still exists, it should still work with a bit of care and attention.)
She used some form of financial software running on a terminal. I think it was from an AS/400.
She was an expert on both.
Whatever key combinations were required to enter data on the terminal had become so ingrained that if you asked her how to do it, she would have to look at what her hands did. (weird).
The UX on the terminal was shit if you had to learn it. (Since I got paid to do some data entry, I felt the pain).
But if you got used to it, it was damn fast. No lag, no mouse pointing, and it stayed entirely consistent. A bit like VI I guess.
As far as I know the system never crashed on her. The server did need care, but it would order it on its own.
At some point they brought in Windows PCz and Lotus Symphony, I think. She hated that.
She found it all slow, inconsistent and did not like the mouse one bit.
The other way around though. When someone new was hired and we were in the age of Microsoft Windows, new people were horrified by the old terminal software.
I still sometimes see people at warehouses or stores that use terminal driven software and some of them are just as fast. It is fun to see.
The majority though hunt, scratch head, peck, hit whatever undo is, and try again.
Should we make easy to use software or software as a tool for those who go through the effort to learn?
I dont think any "windows/osx/linux/" screen UI accounting system would be as fast to use.
I worked with the end users a lot to make sure the UI matched the workflow, iterated over several versions and it definitely paid off.
Doesn't make sense for such a general assertion, you can fully replicate the keybinds of any terminal system and make all the "screen UI" strictly additive to the keyboard experience
As an Emacs user, I'm like that too. I don't know which keys I need to type to perform some operations, only the movement. I'm pretty sure a lot of Emacs users are like that too.
Would love if someone tried to package it into a standalone migration tool, so non-technical folks could make use of it!
- https://github.com/frappe/books
Do check it out!
May I ask how you fund development? What is your feeling on the future?
We have one full time engineer working on it. If end up using it, please give us feedback and help spread the word.
I use the SQLite backend for the same reason Jonathan chose GnuCash: scripting. I can script in bash with the `sqlite3` command-line tool.
I also use the reports extensively.
I personally enter every transaction because I want to know where the money is going and categorize every expense into a budget, but yes, import is important.
As soon as I can, I am going to support GnuCash better than just shilling.
My minimum price to go back to QB online would probably be $150k, maybe even more. Here is why: - constant down time - constant errors - clueless offshore support - inflexible reporting - constant UI changes for no reason
Switched to Xero, havent looked back.
QB Desktop was quite good but working offline is impossible these days for any tech startup.
If you’re not an accountant, and want someone to take it over for your business, they usually start you on QB.
When you're an business owners employee you don't have time or authority to change accounting software because you're overworked & thought of as a cost centre.
When you're a business' owner you do whatever your accountant says which is usually a legacy software because a lot of tax preparers & accountants aren't actually in the trenches anymore and don't know about the granular bookkeeping part of accounting and how much better software has gotten in the last decade.
When you're an tax preparers employee you don't get to talk to the client.
When you're the tax preparer director/owner you don't use software anymore.
Source: accounting startup who has doubled revenue 2 years in a row thanks to all of the above
The problem to use it in France is that there is regulatory barriers preventing to use it officially. In theory accounting solutions have to comply with rules that are complicated to follow with your own opensource solution!
[https://en.wikipedia.org/wiki/PEPPOL Peppol]
Is anyone working on something like that?
But there is also a requirement for certifying that the data of the software can't be altered, and you are not allowed to certify yourself. This is the bad catch 21 situation. Even if it was possible to ensure that data can't be modified on your computer, something like android protected storage, I guess most people would not like that because if you use open source it is to have control over your machine.
So the only solution is the "cloud"/hosted solution by a provider, but again, if you use open source in the first place, probably it is because you don't want some external people to have control over your data.
In theory, a pretty simple scheme of publicly posted cryptographic hashes would prove to anyone you send the data to (presumably tax authorities? Auditors?) that you haven't altered data. Maybe periodically post a running hash of the list of transactions. Even if that works in theory, I'm guessing it's hell to get it actually certified.
Checking the XML data into text-based version control is a really interesting idea. you could probably do something similar with the SQLite data, using a tool like Dolt.
However, it may not scale the way QB does, and folks you bring on won't have had experience with it's way of doing things.
That being said, with QB's changes, chances are that's true of QB folks as well (ha, ha).
Plain Text Accounting - https://news.ycombinator.com/item?id=36022005 - May 2023 (31 comments)
ERPnext is my favourite while Odoo currently supports the taxation in my country (Germany) a bit better...
- Frappe Cloud: https://frappecloud.com
In addition to the Frappe Bench setup process, Frappe provides instructions for self-hosting ERPNext with Docker and Kubernetes:
- Docker: https://github.com/frappe/frappe_docker
- Kubernetes: https://helm.erpnext.com
There's also a third-party Docker image from pipech that's easier to setup, but it's not always up to date:
- Third-party Docker (pipech): https://hub.docker.com/r/pipech/erpnext-docker-debian
Bitnami packages ERPNext in single-tier (AWS, Azure, or GCP) and virtual machine (local computer) offerings:
- Bitnami: https://bitnami.com/stack/erpnext
To anyone reading this, if you only need software for accounting and not an entire enterprise resource planning (ERP) suite, do yourself a favor and follow the advice in TFA to use GnuCash.
I resisted Frappe Cloud because I want to own my ERP code and run it on my own server.
I recently started using Beancount, and liked the concept of plain text accounting so much, I want an ERP with the same spirit.
It's not open source, but I can export practically everything as CSV or TSV, so there's data portability.
The integration between Hubdoc and Office365 is clunky because for reasons I can’t fathom, they only support Dropbox and Google Drive for archiving, but we have a script that we run on our Synology NAS that copies the invoices from Google Drive to SharePoint (OneDrive).
Nothing against GnuCash or open source, we use a lot of FOSS. But we’re in Australia and we switch banks all the time. Those compounding factors would mean that we’d spend a lot of time updating bank roll integration with GnuCash
It’s astonishing how slow the transition to online accounting is in the USA.
https://plaintextaccounting.org
Maybe this was primarily done based on the users being comfortable with a GUI driven system?
FWIW I started prototyping a plaintext accounting 'app' that combines a popular plaintext accounting system (beancount) with the most used web frontend for it (fava) - it's called beancolage and makes use of eclipse theia (vscode-like experience): https://github.com/seltzered/beancolage
My observation is the plaintext accounting ecosystem is wonderful but a bit diffuse to so many specific usecases held by a more technical userbase. My aim for prototyping beancolage was to ask how things could look if there was a more common 'download and try' experience accessible to more people for basic workflows. Also have a talk on the motivations here: https://youtu.be/mxgoFqmSCFc
When I moved out of that role, the next Treasurer wanted to use Quickbooks so I had to help import the data. That's another problem with using obscure software -- it's more difficult to hand it off to someone else who only knows the mainstream systems.
this is a AGPL V3.0 licensed accounting software aimed at small businesses and schools and professionals.
Its currently being developed for indian market because devs are all based out of india so if anyone wants to implement for their own country, please submit a PR.
we need more accounting softwares that are free and open source
Well that’s a surprising statement, i’ve heard it touted as more lispy than common lisp.
The Lisp world is extremely confusing.
I'd wager that at this time, most people in that space can't even agree on what "being a LISP" means.
The entire disagreement is about languages that deviate from the core design patterns set out in the ancestral Lisps, some of whose adherents want them to be regarded as Lisp.
> Such systems are unwieldy to work with and difficult to get started with. In truth, many of them appear to have been developed as platforms for consulting businesses, though surely nobody would deliberately make their software complex and tricky just to motivate clients to purchase their services.
Or perhaps some businesses have complications to deal with that go beyond what a newsletter website needs? Some businesses have inventory, subsidiaries, multiple currencies, have to report sales tax in multiple countries with ever changing requirements (hence the support and updates that this writer doesn't think are required). Some companies have local statutory books that are different than their group books.
Really it is a bit like learning 'echo "hello"' and calling oneself a programmer. Then maybe one might ask why are lwn making Linux so complicated...
So ... perhaps there should be a version of Quickbooks that serves the simpler needs of smaller customers better?
Like: Simple. Desktop. Requires no upgrades as long as its functionality at-time-of-purchase continues to serve well. No forcing of upgrades via dropping of old formats, etc.
I also have given up on Quickbooks.
That wasn't the point I was discussing, but there is an answer anyway.
But reasonableness would also price even critical functionality relative to how hard it was to actually implement.
I.e. don't hold hostage a customers' investments in a software product. Don't force customers to pay a ransom to get a simple-to-implement feature.
GnuCash is fine for the solo but I don't think the external people will like it. I think LWN will do what it takes to make the reports that the accountant will need, but as it stands it is not ready for that out of the box in my opinion.
Other packages, like Odoo, treat double-entry accounting as a trade secret and so it's not really open-source. There are add-ons but their level of maturity is not clear.
If I tried to use ledger (plain-text accounting) I think even my business consultant would tell me to take a hike. I used it when I did a little contract work and it was fine, but my needs were very simple.
Still, getting off of QB and into Zoho for my business has been great. Everything can be exported if I need (to CSV files) and it handles almost all of my needs. But it's not open source.
I wonder why MS killed it.
Every now and again I look around for something similar.
The combination of a simple text format (that I version), extensible CLI-based querying and reporting tools, and free software makes it absolutely perfect to me.
I assume the person who posted this to HN is not the article's author, but if the author happens to be reading, it would be very helpful to see these scripts. The difficulty of writing custom scripts for GnuCash data is one of its main limitations IMO.
But yes I heartily agree, those scripts would be immensely helpful even just as an example/reference for somebody writing their own.
https://quickbooks.intuit.com/desktop/ -- it's the "Work on desktop" options.
I wonder if LLMs can help with these gaps in documentation and examples?
I wonder if LLMs can do someone's taxes.
But I'm not going to be the first to try it.
It descended into me arguing with the machine over whether or not 2b even existed. "GPT, I'm literally holding the physical paper in my hand and staring at the box labeled 2b!" "That is incorrect. Form blah has never had a box labeled 2b"
So, I'm going to go with: probably wanna hold off on the LLM taxes.
So, 2b, or not 2b? That was the question?
Can I see the transcript?
Sounds like ChatGPT can already obsolete the tax office.