We Almost Shipped Auto-Send Invoicing. Our Customers Talked Us Out of It.
I lead product at Belvak, and I want to tell you about a decision we almost got wrong. When we designed our recurring invoicing feature, the obvious approach was fully automated: set a schedule, and invoices go out automatically every month. No human intervention. Maximum efficiency. Every competitor does it this way. We were three weeks from shipping it.
Then we talked to our users. Actually talked to them. Not a survey - real conversations with agency owners and ops people who manage recurring billing.
And what we heard, over and over, was some version of: "I don't want invoices going out without someone looking at them first."
The Problem With Fully Automated Invoicing
Here's what Sarah, who runs a 30-person marketing agency, told me: "We had auto-invoicing set up in our old tool. One of our clients paused their retainer for a month because they were restructuring. We told account management, but nobody updated the billing system. The invoice went out automatically. The client was furious. We had to apologize, issue a credit, and it took two months to rebuild that trust. For a $3,000 invoice."
Another founder, who runs an IT consultancy with about 40 maintenance contracts, said it even more bluntly: "The last thing I want is my billing system sending out something I haven't reviewed. One wrong invoice to a big client can undo a year of relationship building."
The thing about recurring invoicing errors is that they're not one-time mistakes. If something's wrong with the template or the amount, that mistake goes out every single month until someone catches it. A billing error on a manual invoice is embarrassing. The same error repeating for six months is a disaster.
Why We Chose Approval-Based
So we redesigned the feature around a human-in-the-loop model. The system generates upcoming invoices automatically - it knows the schedule, the amounts, the client details. But instead of sending them out, it presents them in a queue for review.
Someone on your team (usually an ops person or finance lead) opens the queue, sees all the invoices that are due or overdue, reviews them, and hits approve. The ones that need adjustment get edited first. The ones that should be skipped - client on pause, credit applied, whatever - get marked as skipped. Then the approved ones go through.
Honestly, it takes about 15-20 minutes a week for most companies. Some of our users with 50+ recurring invoices spend maybe 30 minutes. That's it. For the peace of mind of knowing that every invoice that goes to a client has been seen by a human being, that's a pretty good trade.
The "skip" functionality turned out to be more important than we expected. About 15% of recurring invoice periods get skipped for legitimate reasons - client pauses, credits, renegotiations, seasonal adjustments. In a fully automated system, these either go out wrong or require someone to proactively cancel them before the send date. In an approval-based system, you just skip them. The schedule advances, an audit trail records who skipped it and when, and life goes on.
Sequential Enforcement: The Feature Nobody Asked For But Everyone Needs
This one came from our own experience. We had a customer who accidentally approved their June invoice before May's had been processed. They ended up with a gap - May was missing entirely, and nobody noticed until the client's accounts payable team flagged it two months later.
So we added sequential enforcement. You can't approve March until February is done. Period. If February needs to be skipped, fine - skip it explicitly. But you can't jump ahead. It sounds restrictive, but every single customer who's used it has told us it prevents more problems than it creates.
It also prevents duplicates. If an invoice already exists for a given period on a given project, the system won't let you create another one. You wouldn't believe how often this comes up when two people on a team are both "handling" invoicing.
Multi-Currency Is Harder Than You Think
We're based in Lebanon, and a lot of our customers operate across borders. They might have clients paying in USD, EUR, and GBP on the same monthly cycle. Recurring invoicing in multiple currencies adds real complexity.
Our approach is simple but important: we store the currency on each project or contract, and invoices inherit that currency. We don't do currency conversion. If the contract says EUR, the invoice says EUR. Conversion is between the client and their bank, or it's negotiated separately.
The display formatting matters more than you'd think. A USD amount formatted European-style with period separators and comma decimals confuses American clients. An amount without the currency symbol confuses everyone. We format according to the currency code on every invoice - small detail, big impact on professionalism.
The number one rule: once you start billing a client in a specific currency, don't switch mid-contract. I've seen this cause accounting nightmares on both sides. If you need to change currencies, do it at renewal with a new contract value.
The Errors That Repeat
I keep a list of the recurring invoicing mistakes our customers have reported. Here are the ones that show up most often, and what we built to prevent them.
The phantom invoice. A recurring invoice just doesn't get created one month. Nobody notices because there's no alert - the absence of something is harder to spot than the presence of something wrong. We solve this with the upcoming invoices dashboard. It shows every recurring project and its next expected invoice. If something's missing, it's visible.
The stale amount. A contract gets renegotiated from $5,000/month to $6,000/month. Someone updates the contract but the invoicing template still has the old amount. We pull the amount from the project/contract record at generation time, not from a cached template. Update the source, and every future invoice reflects it.
The wrong client details. Client changes their billing address or contact person. The invoicing system has the old info cached from when the recurring schedule was set up. Same fix - we pull current client data at generation time, every time.
The accidental double. Two people approve the same invoice. Or the system generates a duplicate because of a retry. Period-based deduplication handles this. One invoice per period per project, enforced at the database level.
Bulk Operations Are Not Optional
If you're managing 10 recurring invoices, reviewing them one by one is fine. At 30, it's tedious. At 50+, it's untenable.
We added an "Approve All" button that lets you review the full queue and push everything through in one action. Sounds simple, but the design matters - you need to be able to scan the list quickly, spot anything unusual, and pull individual invoices out of the batch if needed. It's not just "click and pray."
We also show overdue periods prominently. If a client should have been invoiced in January and it's now March, that needs to scream at you, not hide at the bottom of a sorted list.
The Payment Side Completes the Loop
Generating the invoice is half the job. The other half is knowing whether it got paid.
We auto-update invoice status based on payments. When someone records a payment against an invoice, the status changes. Partial payment? It shows "partially paid." Full amount received? It marks complete. If a payment gets deleted or adjusted, the status reverts. No manual status management.
This matters for recurring billing because you need to see the collection rate over time, not just for individual invoices. If a client consistently pays 15 days late on their recurring invoices, that's a pattern you should address at renewal. If your overall collection rate on maintenance contracts is 92% instead of 99%, those missing 7 percentage points are worth investigating.
Getting Your Recurring Invoicing Right
If you're currently doing this manually - creating each monthly invoice from scratch, checking a spreadsheet for who's due, typing amounts from memory - here's how I'd approach the transition:
First, list every recurring billing relationship you have. Client, amount, frequency, currency, current status. This audit alone usually surfaces two or three contracts that have been under-billed or forgotten entirely.
Second, start with approval-based workflow. You can always move to auto-send later once you trust the system and your data is clean. Starting with auto-send on dirty data is a recipe for apologetic emails to clients.
Third, set up a weekly routine. Pick a day - we recommend Monday morning - and spend 20 minutes reviewing and approving the queue. Build the habit before you try to optimize it.
The goal is simple: spend less than 30 minutes a week on recurring invoicing while being 100% confident that every invoice is correct. That's not a fantasy. That's what a well-designed approval workflow gives you.
