Closing the Quarter as an Independent

March 31 hits differently when you have a VAT number.

It's not a direct tax deadline — the quarterly VAT communication is due by May 31, and the F24 payment follows the same timeline. But it is the end of the period. Tomorrow the slate resets: new registers, new liquidations, new invoices that will accumulate over the next three months.

There's something useful about this externally imposed rhythm. The fiscal quarter forces you to stop and look at the numbers, even when you'd rather not. It's different from the annual review — too distant, too abstract — and from the monthly check-in, which is often just noise. The quarter is the right granularity to see whether you're actually moving in the direction you thought you were.

The accounting reconciliation

The first thing I do at the end of each quarter is reconcile everything that passed through. Invoices issued, supplier invoices, credit notes, bank movements. It's not an elegant process — it's exactly the work you kept putting off doing properly during the quarter because something more urgent always came up.

The classic independent developer problem isn't failing to track finances. It's tracking them in fragments: an invoice issued here, a payment received there, an expense note forgotten somewhere. End of quarter is when the bill arrives. Not in a punishing sense — just in the sense that you have to reconcile everything and approximation no longer works.

I built an internal accounting system for Honeyside precisely for this. Not out of ideological opposition to commercial accounting software — out of practical necessity. My workflow has specific characteristics: electronic invoicing through the Italian SDI, international clients with VAT-exempt invoices, reverse charge, occasionally split payment. No off-the-shelf software adapts cleanly without workarounds that become their own kind of technical debt — accounting edition.

The system reads invoice XML from the SDI, cross-references it with bank movements imported from CSV, calculates VAT by period, and produces the raw data for the quarterly VAT communication. It's not a masterpiece — it's precise enough to cut my reconciliation work in half.

The VAT filing

The quarterly VAT communication isn't conceptually hard — I took it apart two days ago. The hard part is having the right data going in.

The form fills itself out almost automatically if the bookkeeping is clean. The operation totals come from the VAT registers. The tax aggregates are straightforward arithmetic. The carryover from previous periods is mechanical.

Where things go wrong is upstream: incomplete VAT registers, invoices with wrong registration dates, reverse charge transactions filed in the wrong column. The filing is just the communication format — the errors live in the register.

For this first quarter, the position is a credit. A handful of significant expenses — servers, tooling, a laptop — concentrated in a period where income was distributed more evenly. The credit carries forward to Q2. Not a problem, just the normal mechanics of periodic liquidation.

The product review

The less formal part — and the one that matters most — is the review of what I actually built and shipped in the quarter.

Barba Studio received two updates: a revision of the onboarding flow (it was too long for a barber registering from their phone during a break) and integration with a second payment provider. Neither was planned in January — both emerged from real usage. The product is stable enough to receive clear signals from users, which is already a result worth noting.

ReD Sposi is in the most intense phase of its lifecycle: the wedding is in August, and the main features — RSVP, gallery, chat, the betting game — are all live. The last three months were about stabilizing the media pipeline, optimizing push notifications, and polishing the betting game. From April onward it's maintenance and guest support, not active development.

This blog became a real habit over the quarter. Thirty posts in just over a month wasn't a declared goal — it happened because I had a lot stored up and found a rhythm that works. The question for Q2 is whether I can maintain consistency at a lower intensity.

The master's degree — the thesis is written. It's titled Automated Fiscal Compliance for Italian Companies in International SaaS Services and compares Payment Gateways (Stripe) and Merchant of Record solutions (LemonSqueezy) as fiscal compliance strategies for SMEs selling software internationally. The technical contribution is Sistema Nexus: a payment router that routes transactions to the most appropriate provider based on configurable per-merchant rules, and closes the fiscal loop end-to-end by notifying the Gestionale Molinari system, which generates the FatturaPA invoice and sends it to the SDI. Barba Studio is the primary case study: Italian clients → Stripe with SDI integration, international clients → LemonSqueezy which assumes full tax liability. Exams are still ahead, but the heavy part is done.

Elemental Machines — the full-time job — had a demanding Q1 on the IoT product side. I can't go into specifics, but it's the kind of work that stays in your head even after you've closed the laptop.

The quarterly rhythm

There's a reason the quarter works better than the month or the year as a unit of measurement for an independent.

The month is too short. The natural fluctuations of income and expenses, productivity and blocks, momentum and stagnation — these variables have cycles that don't show up in four weeks. A slow month says nothing. An exceptional month can mislead. The granularity is wrong.

The year is too long. A year is enough time to go in the wrong direction, correct, get back on track, and then close thinking "it went well" — without ever being clear on what actually went well and why. The annual review is useful, but it's a result, not a navigation tool.

The quarter is long enough to smooth out noise and short enough to react. Three months of trend says something. If revenue is down for three consecutive quarters, it's not randomness — something's not working in the product, the pricing, or the acquisition. If a product hasn't moved in a full quarter, it's not a lack of time — it's a lack of priority.

The Italian tax system chose the quarter as the VAT liquidation unit probably for practical reasons of revenue flow and oversight. But as a side effect, it imposes a review cadence that — if you use it actively rather than endure it passively — is more useful than any productivity system you might voluntarily adopt.

The honest part

End of quarter also means accounting for what didn't happen.

There are Barba Studio features I wanted to ship that are still in the backlog. There's at least one Honeyside client I communicated with less than I should have. There are weeks where the master's degree was completely absent from my mental stack because everything else was pushing.

I'm not writing this as performative self-criticism. I'm writing it because a quarterly review has no value if it excludes the losses. An independent who only counts the ships and ignores the slips isn't doing a review — they're composing a narrative.

The useful exercise is asking: what fell behind for valid reasons — shifted priorities, finite energy, conscious decisions — and what fell behind for reasons that don't hold up on second reading? Only the second category is worth acting on.

For this quarter, the answer is fairly clear. The priorities were right. The pace was sustainable. The red items have explanations that hold.

Q2. Starting over.