u/OkSelf4711

Anyone else feel like this job is 70% nagging and 30% actual bookkeeping?

I sat down yesterday and genuinely timed how much of my day goes to asking clients for documents versus doing real work, Out of about 6 hours of what I call bookkeeping I did maybe 2.5 hours of actual categorization and reconciliation, the rest was sending follow up emails to clients who never respond the first time, texting people to ask if that $847 charge at AMZN MKTP was office supplies or inventory, and waiting on one client who still physically mails me bank statements like its 2008.

I have 18 clients right now, A few of them are great about sending stuff on time but most of them are not, and the frustrating part is the ones who are always late say the same thing every single month, Oh sorry I forgot. And then they do the exact same thing 30 days later....

I've tried setting hard deadlines and they just ignore them. I've tried automated reminders through my project management tool and they ignore those too, I even tried being really nice about it with gentle language and all that and still got ignored, then I tried being slightly less nice about it and now they're offended AND still late so that didnt help either.

I'm starting to think about building a late document fee into my pricin, Like genuinely just adding $50 or $100 if your stuff isn't in by the 5th of the month, has anyone actually done this?

Does it work or do clients just get mad and leave? Part of me feels like the clients who would leave over a late fee are the same clients I don't want anyway but I dont know if that's naive.

Would love to hear how other people handle this because I'm running out of ideas and spending 3+ hours a day on email follow ups is not why I got into this profession

He was here for 5 years. He built the core transaction engine. He's the reason the system works. He's also the reason nobody else understands how it works.

When he gave his notice, our CTO asked him to do a knowledge transfer. He scheduled three one-hour sessions. In the first session, he opened the main file 4,200 lines ,scrolled through it, and said "this is pretty self-explanatory." In the second session, he explained the caching layer by drawing a diagram on a whiteboard that he immediately erased because "you'll figure it out once you look at the code." The third session was cancelled because he took a PTO day.

After he left, three of us were assigned to own his code. We started reading it.

The variable names are single letters. Not in small utility functions. In the main business logic. p, t, x, q. One function takes 11 parameters, all single letters. There's a comment above it that says "don't refactor this. the order matters." We tested it. The order does matter. We don't know why.

There are 47 comments in the codebase that say "trust me" or some variation. "Trust me, this needs to be here." "I know this looks wrong. Trust me." "Don't remove this sleep(200). Trust me." We removed the sleep once. Production went down for 40 minutes.

We've been reverse-engineering this system for 3 months. We have a shared document that's 22 pages long called "What We Think This Does." Page 1 starts with "We are not confident in any of this."

He was a brilliant engineer. I mean that sincerely. The system handles millions of transactions and has never had a data integrity issue. He built something that works perfectly and is completely incomprehensible to anyone who didn't build it. I don't know if that's a success or a failure. It might be both.

I do video work for a mid-sized B2B company. Last quarter my boss came to me the day after their annual conference and said "we need clips from all 12 talks for LinkedIn and Shorts by end of week."

12 talks, average 40 minutes each LinkedIn wants 16:9, Shorts wants 9:16, that's 24 exports minimum, and every single vertical export needed manual reframing because half the speakers weren't centered for a vertical crop.

I did the first talk manually, It took 4 hours, I had 11 left and 3 days.

I called in a favor from a freelancer friend who does a lot of repurposing work, he remote-desktoped into my machine, spent 20 minutes showing me his workflow, and left and I didn't fully get it at first....

Then I tried it myself on talk number 2, uploaded the file, described what I was looking for, let it find the moments each clip auto-reframed for vertical with the speaker tracked, I refined a few cuts at the text level, deleted a sentence here, tightened a boundary there....

Talk number 2 took 45 minutes total, both formats done....

Finished all 12 talks in 2 days, my boss thought I'd pulled an all-nighter but I had not.

I still can't fully explain to non-video people why that reframing piece specifically was such a big deal, but if you've ever spent 20 minutes manually repositioning a speaker crop frame by frame, you know.

There is a pattern I have noticed every time I have brought in a new accountant and I think it says something genuinely useful about how most small business owners relate to their own finances

The first meeting is always the same conversation

They ask me to walk them through my setup. I explain what software I use, who handles the day to day bookkeeping, roughly how things are organized. I feel reasonably confident during this part because I know the basics

Then they start asking specific questions

What is your current chart of accounts structure and why are certain expense categories set up the way they are. How are you handling revenue recognition for the different types of work you do. What is your process for reconciling the accounts each month and who is responsible for that. How are deferred expenses being tracked and amortized

And somewhere in the second or third question I start giving answers that sound like they begin with the phrase I think or I believe my bookkeeper handles that or honestly I am not totally sure

Every time. Three different accountants over six years. The same moment where I realize that I have been trusting a system I do not fully understand to produce numbers I have been making real decisions from

The accountants are never rude about it. They are professionals and they have clearly had this conversation hundreds of times before. But there is always this brief pause after one of my uncertain answers where I can tell they are recalibrating their expectations for how much cleanup the first few months are going to involve

What I have taken from this pattern over the years is not that I should become an accountant or learn everything about accounting software. It is that there is a meaningful difference between having someone manage your books and actually understanding your own financial picture

The first is about compliance and record keeping. The second is about running your business

For most of my six years I had the first without the second and I did not fully realize it until I was sitting across from someone whose job it was to ask the questions I had never thought to ask myself

The most useful thing I did after the third accountant conversation was spend a weekend actually learning what was in my books, not the accounting details but the story they were telling about my business. Where the money was actually coming from. Where it was actually going. What the numbers meant in plain terms rather than accounting terms

That weekend did not make me an accountant. But it meant that the next conversation I had with an accountant felt like a conversation between two people who both understood the business rather than one person explaining things to another person who was mostly nodding along

If you have ever felt like your accountant understands your business finances better than you do, that feeling is worth paying attention to

think about what a 15% flakiness rate actually means in practice across an industry.

every day, millions of CI pipeline runs are failing on tests that do not represent real bugs. engineers are spending time investigating failures that are noise. builds are being blocked by phantom problems. reruns are consuming compute. and most importantly, teams are gradually losing trust in their own safety nets.

there is a number i keep coming back to. Google published research years ago saying that 16% of their tests showed flakiness and it consumed roughly 2% of total engineering time across the organization. google has tens of thousands of engineers. do the math on what 2% of that looks like in salary alone.

now scale that across the entire industry. every company running mobile CI pipelines with meaningful flakiness rates. the accumulated cost in wasted compute, wasted engineer hours, delayed releases, and bugs that slip through because people stopped trusting the results is genuinely staggering.

and the wild part is that most teams have normalized it. 15% flakiness gets described as a known issue or a quirk of the environment. it is treated like weather. something you work around rather than something you fix.

we made peace with a problem that is actively expensive and i am not sure when or why that happened.

I want to share something that took me way too long to figure out because I think a lot of firm owners are sitting in the same situation right now and just accepting it as the cost of doing business

I run a small CPA firm in Charlotte, six full time staff, been operating for nine years. We close about 31 client files every month end, mix of small businesses, a few restaurants, some service companies, a couple of ecommerce stores

For years our month end close window was eleven days. First of the month to the eleventh, sometimes the twelfth, occasionally the thirteenth if something went sideways. I knew it was slow but I had no real baseline for what it should look like so I just assumed it was normal

Last year my office manager did something I had never thought to do. She tracked exactly where the eleven days were actually going

She broke it down by activity across all six staff members for an entire month. Every hour logged, every task recorded, everything categorized

The results genuinely surprised me

Three and a half days out of eleven were being spent on email. Not client advisory emails, not strategic conversations, just the logistics of month end close. Who has the bank statements for client X. Can you send the credit card reconciliation. Still waiting on the restaurant payroll file. Did you finish the reconciliation for the dental practice. Back and forth, back and forth, across email threads that had no structure and no ownership and no way to see at a glance what was done and what was not

Two days were being spent on what she called hunting, going into each client QuickBooks account individually to check the status of transactions, find out what was uncategorized, see what still needed to be reconciled, figure out where things stood. Six staff members logging in and out of 31 separate QBO accounts throughout the day looking for information that should have been visible in thirty seconds

One and a half days were being spent on rework. Transactions that had been categorized incorrectly and needed to be fixed. Reconciliations that had been done but had a discrepancy that needed to be traced. Bank feeds that had pulled in duplicate transactions from integrations that nobody had caught

The remaining four days were the actual accounting work. The skilled work. The work we were billing for and the work our staff had trained for years to do

So out of eleven days, four were accounting. Seven were coordination, hunting and cleanup

The math on that was not comfortable to look at. Our average fully loaded staff cost at the time was about $65 per hour. Eleven days at roughly 250 billable hours across the team came to about $16,000 in staff time per monthly close. If four days was the actual work that was $5,800 in legitimate close time. The other $10,200 was coordination overhead and cleanup that should not have existed

We were spending $10,200 a month on the architecture of doing the work rather than the work itself

Fixing it was not complicated but it required actually admitting what was broken

First we built a proper standardized close checklist that lived in one place, not in someone's email, not in a Google doc that was three versions out of date, an actual task list with ownership assigned and completion tracked. Every client had the same checklist structure. Every step had a name attached to it. Anyone on the team could see in thirty seconds what was done and what was not for any client at any point in the month

Second we stopped doing the status hunting manually. Instead of logging into 31 QBO accounts throughout the day looking for information we set up a centralized view that showed us where everything stood across all clients simultaneously. What was uncategorized, what was unreconciled, where the close stood for each file

Third we actually looked at where the rework was coming from and fixed the source instead of just fixing the output. Most of it was coming from three specific integration issues that had been creating recurring problems for months and nobody had ever sat down and properly resolved because we were always too busy doing the cleanup to address what was causing it

Four months after making those changes our close window was six days. Not eleven. Six.

Same team. Same clients. Same volume of work. Six days instead of eleven

The $10,200 in monthly overhead we were spending on coordination and cleanup came down to about $3,800. We got $6,400 a month back in productive staff capacity without hiring anyone or working extra hours

The thing I keep thinking about is that we had been running eleven day closes for years and I had genuinely never questioned it. It felt like the nature of the work. It was not the nature of the work. It was the nature of a broken process that nobody had ever mapped out clearly enough to see what was actually inside it

If you run a firm and your close window is longer than you think it should be, spend one month actually tracking where the hours go before you assume you need more staff or longer hours. You might find the same thing we did which is that the accounting itself is not the problem at all

So I am doing my placement semester right now at a small accounting firm and I genuinely thought I was prepared

Two years of accounting courses, decent grades, understood debits and credits, could produce financial statements in my sleep, felt pretty confident walking in on day one

First week the senior accountant sits me down and pulls up three client files

He goes through each one slowly and asks me what I notice

I looked at all three. Books balanced perfectly. Reconciliation was clean. Monthly reports generated without errors. Everything looked completely normal to me and I told him that

He smiled and said look closer

First client had been miscategorizing a specific type of revenue for over a year, not dramatically wrong, just consistently going into the wrong account every single month

Second client had duplicate transactions quietly running in the background from a sync issue between their POS system and QuickBooks that nobody had ever caught because the books still balanced

Third client had expenses mapped to the wrong accounts because of how their payment processor categorized things before pushing data into QBO

All three sets of books balanced every single month. Reconciliation passed every time. Reports generated cleanly. Zero errors on the surface.

And all three were wrong in ways that would have mattered enormously for tax filings or if any of them ever needed a loan or had an investor look at their numbers seriously

I sat there feeling genuinely stupid because I had looked at all three files and saw nothing wrong

He told me something that I keep thinking about

He said in school they teach you accounting assuming the data going into the system is correct and your job is to process it right. In real life the data is often wrong and your job is to figure out why before you trust anything you see

Balanced books are not the same as accurate books and that distinction apparently does not get taught anywhere in the academic curriculum, you just stumble across it in your first week at a real firm when a senior accountant decides to humble you a little

Two years of courses and nobody once told me this. It was the most useful thing I learned in my entire accounting education and it happened in a random Tuesday morning sitting at someone else's desk looking at client files

If you are still in school and reading this just know that the real skill is not processing correct data correctly, it is recognizing when the data itself cannot be trusted before you do anything with it

I've been in QA since 2018. every role I've had has been purely manual, no exceptions. first job was UI testing for a mid size SaaS company, all manual. second job same thing but with some API testing thrown in, still all manual. The third role I actually worked somewhere that had an automation team but it was completely separate and I was never anywhere near it. just me and a lot of copy pasting

last week I signed an offer for a role that's 75% automation and 25% manual

genuinely did not think this was going to happen this year. I've interviewed for automation roles before and got pretty far a couple times but always hit a wall when the technical stuff got serious. so I kept picking things up slowly, a bit of python here, some selenium tutorials there, nothing structured just whenever I had the energy after work

somehow it was enough to get through this one, the thing is I'm happy but also kind of dreading the first month. My coding is not where I want it to be and I know there's a difference between getting through interview questions and actually writing automation scripts in a real codebase with real deadlines

feels a little bit like I chewed off more than I could bite.

has anyone else made this jump with shaky coding skills and figured it out and learned on the job or was it a bad ending?

Was a backend dev for 4 years. Burnt out hard. Hated standups, hated sprint planning, hated being on call, hated the part where every feature I shipped was just one more thing that could page me at 3am.

A friend of mine ran QA at a healthcare startup and kept telling me I'd be good at it because I was the only dev on her team who actually wrote tests. I laughed it off for a year. Then I had a really bad Q3 where we shipped a bug that pulled the wrong patient records into a clinician dashboard (caught before it hit production thank god, but still). I realized I cared more about the bug we almost shipped than any feature we'd built that quarter.

Took a 15% pay cut to switch. People in my life thought I was insane. "QA is dying." "AI is going to replace testers." "You'll regret it when there are no jobs."

18 months later:

• I sleep at night. Literally. No on-call.
• I'm better at this than I was at dev work. Turns out caring about edge cases is a personality trait not a skill.
• The "AI is replacing QA" thing is so wrong it's funny. Every AI-generated feature at my company creates 3x the testing surface area. We're hiring.
• I got my pay back within a year. Senior QA at a regulated company pays more than people think.
• I actually like Mondays now. Genuinely never thought I'd type that sentence.

The one thing nobody warned me about: you have to be okay being the person who says no. Devs will hate you sometimes. PMs will try to ship around you. You have to develop a spine. That part was hard for like 6 months.

If anyone's considering the switch, ask me anything. I know everyone says "follow your passion" is bad advice but in this case the passion was "I want to stop being woken up at 3am" and it worked out fine.

I need to vent about something that just happened because I genuinely think other small business owners need to know this can happen to you

I have been using the same local accountant for four years. Decent guy, reasonable rates, I pay him $800 a month to handle my bookkeeping and tax stuff. Everything seemed fine until my accountant called last week saying there were discrepancies in my GST filings from the past three months and he was going to need to spend time fixing them before my next tax return.

I said okay how long will that take and he said probably eight to ten hours of work so that will be $2,400 extra

I nearly fell out of my chair

I asked him what the discrepancies were and he basically said my transaction categorization was inconsistent so some things were being GST exempted that should not have been and other things were getting full GST charged when they should have been partial

Turns out he had been accepting whatever QuickBooks was doing with my transaction categories without actually verifying they were correct for GST purposes every month

He was basically getting paid to not catch this until tax time when it became someone else's problem

The frustration is not even really about the money at that point it is that this was completely avoidable if someone had actually been looking at the categorization from a tax perspective instead of just an accounting perspective

What I ended up doing was spending a Sunday afternoon rebuilding my chart of accounts specifically for GST compliance and adding notes to each account about the GST treatment

I then built QuickBooks rules that coded transactions to those accounts automatically based on the vendor and amount

Takes me literally five minutes a month now to verify everything is categorized correctly for GST purposes and I have not had a surprise since

The hack is just this. Your chart of accounts needs to reflect your actual tax

Not a rant for the sake of ranting, I genuinely want to understand how we got here

I have been doing accounting for eleven years, I passed my CPA exam in 2018 I have a genuinely good grasp of financial principles, tax strategy, advisory work, the stuff that actually requires a trained brain to do properly

And here I am spending ten hours this month matching transactions

Ten hours!!!!

Not reviewing anything complex, not catching fraud, not doing analysis that required a single day of my education, just opening QuickBooks, looking at a transaction, deciding which category it belongs to, moving to the next one, and doing that on repeat until my eyes get sore….

The same vendors I have categorized hundreds of times before, the same bank accounts I reconcile every single month and the same process, the same clicks, the same decisions, over and over, in the year 2026

I keep seeing people talk about AI replacing accountants and I genuinely cannot stop thinking about the fact that AI has not even replaced the most mindless parts of accounting yet, the parts that should have been automated years ago, the parts that require zero expertise to do and yet somehow still eat a massive chunk of a skilled person's working month for the fact ... .my surgeon does not spend ten hours a month filing paperwork by hand, my lawyer does not manually copy information from one document to another for ten hours a month. 

But somehow in accounting we have just accepted that a significant portion of our professional lives will be spent doing work that a reasonably configured piece of software should be handling entirely on its own, the thing is that something exists but QuickBooks has a rules engine It is just not smart enough to handle real world transaction variation without breaking constantly

I finally got serious about fixing this properly last month and the difference was significant enough that I am annoyed at myself for waiting so long to address it but the bigger frustration is that this should not require the accountant to go fix it at all It should just work the fact that skilled people are still burning hours on categorization and reconciliation in 2026 is genuinely embarrassing for the industry

If you are still doing this manually every month I am not judging you because I did it for years, I am just telling you that it does not have to be this way and the time you get back is time you can spend on work that actually uses what you spent years learning how to do

I run a small wholesale business and this has happened to me more times than I can count

A supplier calls asking about extending credit terms and wants to see my financials. A client asks about my capacity before signing a bigger contract. My bank calls about a credit line review.

Every single time I open QuickBooks and the most recent clean data is from two weeks ago because my bookkeeper hasn't finished the month yet and the transactions sitting in the feed are still uncategorized and unreconciled

So what I am actually looking at is a P&L with a giant question mark hanging over it because half the month hasn't been properly processed yet

The number I see is not wrong exactly it is just incomplete and an incomplete number at the wrong moment is basically the same as no number at all

It took me an embarrassingly long time to realize the problem wasn't my bookkeeper being slow it was that the whole process was designed to produce accurate numbers once a month rather than accurate numbers all the time

The moment I fixed the workflow so categorization and reconciliation were happening continuously rather than in one big monthly batch everything changed

I stopped dreading those calls because I actually knew where I stood on any random Tuesday afternoon not just on the 15th of the following month

So every week, without fail, she would open our posts about our HIPAA risk breakdowns, our post which goes with the title "3 things your IT team is ignoring right now" and also the data breach case studies we spent hours putting together.

And I’m not even joking she wasn't just scrolling past, she was reading and was thinking. Forwarding things to her team internally and we thought we were building trust with her but the unfortunate task was that we had absolutely no idea she existed…..

Then came the Q3 and her company finally had a budget allocated for compliance software and this was the exact moment we'd been working for and for which we made all those contents….

 But the part we were worried about the most happened to us, and yes unfortunately she didn't reach out to us.

And what I think would have happened is she opened Google, typed in "HIPAA compliance software", got served three options with good reviews, booked demos with all three, and made a decision within 30 days...

And for the fact, We weren't on that list.

But I’m sure it was not because our product was worse and also not because our content wasn't good enough, the thing is that we never knew she was there, It was like we never reached out, we never started a conversation while she was warm and paying attention.

And unfortunately she found someone else who did…..

But there’s always a way for everything and that’s what kept us going, the Gap is so wide that there’s nothing u can do with that it’s like you have zero visibility about who is watching and who is ignoring ...so one afternoon while I was randomly scrolling my linkedin, I came across a post with the same exact pain point we were going through and you know the drill I jumped into the comments and started going through and there I found a guy who was talking about some tool which monitors your LinkedIn content, detects when someone who matches your ICP engages, enriches their profile, and gets their contact details to you instantly and all that while they're still warm…..and tbh I was curious like wth man!!!

Went to find out what it was and got to know that it goes by the name traxy and we straight forwardly thought of giving it a try and you can see the results in the image attached….

In fact I would like to give a reality check about the brutal reality of posting on LinkedIn and waiting. Sometimes it's like you can be doing everything right posting consistent content, real value, genuine expertise and at the end of the day you still lose the deal because you had no visibility into who was actually watching.

Your best buyers are silent, they don't comment, they don't like posts, they just read, evaluate, and eventually make a decision and that can be with you or without you the compliance officer was always there but we  just needed a way to see her.