When you commission an accounting or management system, it feels like all the work sits on the developer’s side. In reality, half the outcome is decided before the first line of code — by how ready your business is to start. The question “what do you need to build an accounting system” has two answers: a technical one (that’s our part) and an organizational one (that’s yours). It’s the second part that most often stalls projects, inflates budgets, and turns a three-month job into a six-month one.

We’ve been building systems end to end since 2018, and we’ve seen the same picture dozens of times: the development itself goes to plan, but the project sits idle because there’s no access to the old database, no one can say how a discount is actually calculated, or the one person who knows everything is on vacation. This article is an honest checklist you can work through on your own, before you even start looking for a contractor. It will save you from the most expensive kind of delay.

Describe the process as it REALLY works

The first thing you need to build an accounting system isn’t a technical spec — it’s an honest picture of how things work right now. Not how it should be “ideally,” not what the old manual says, but how your people actually operate day to day.

Take one typical scenario — say, the path of an order from the customer’s call to shipment — and walk it step by step. Who takes the request. Where they record it. Who sees it next. Where stock is checked. Who issues the invoice. What happens when a customer changes their mind. Where information currently falls through the cracks.

The most valuable thing here is the exceptions. “Usually like this, but wholesale is different,” “for regular customers we calculate the discount by hand,” “at month-end we make a separate report in a notebook.” These are exactly the details everyone forgets to mention, and they resurface during testing and force rework. The more exceptions you write down in advance, the more accurate and cheaper the estimate.

Don’t worry if the process looks chaotic. Bringing order to it is our job. But you can only bring order to something you can see in full.

Get your existing data in order

Any accounting system inherits your previous data: customers, products, stock levels, transaction history. And almost always that data is scattered across several spreadsheets, notebooks, chats, and people’s heads. The state of this data directly affects how long and how expensive the launch will be.

Go through what you have and assess it honestly:

  • Where the data physically lives — files, an old program, paper journals, cloud tables.
  • How current it is — whether the stock on paper matches what’s actually on the shelf.
  • How many duplicates and how much junk it holds — three cards for one customer, products under different names, empty fields.
  • Whether it can be exported — is there an export from the old system, or does everything have to be re-entered by hand.

We don’t demand perfect order — we work with messy data too, that’s normal. But you should understand: the more chaos at the start, the longer the migration stage. Often it’s cheaper to spend a week cleaning up a key reference list (products, for example) with your own team than to pay someone to untangle it for you. We always make that call together, once we see the real volume.

Name one person who owns the project

This is the point owners underestimate most often, and it costs the most. On your side, the project needs one accountable person — someone who makes decisions and answers questions quickly.

During development, forks come up constantly: “Is the discount off the total or per line item?” “Can a manager edit the price?” “What happens when an item is out of stock?” If the answer to each of these takes a week because “we need to ask the director and he’s busy,” the project sits idle that whole week. Ten pauses like that, and two months are gone — not to development, but to silence.

This person doesn’t need to understand the technology. They need to know your business and have the authority to decide. It can be you personally, a department head, or a senior manager with a real vote. The key is that they stay available throughout the project rather than disappearing on business trips during the hottest weeks. Without an owner, even the best development team simply grinds to a halt waiting.

Prepare access in advance

A technical but very down-to-earth part of what you need to build an accounting system is access. Projects regularly lose days to a plain “we can’t log in.”

Sort out and gather in one safe place, ahead of time:

  • access to the old program or database we’ll migrate data from;
  • access to the services the system must integrate with — shipping, point of sale, bank, messengers;
  • the contact of whoever administered the previous system (even if it was an outside contractor);
  • a decision on where everything will live — we offer our own infrastructure and ongoing support, so we often take this on, but it needs to be agreed at the start.

One more piece of advice: hand over passwords and keys securely, not in a chat thread, and decide up front who will hold admin rights after launch. Access looks like a trivial matter right up until it brings the whole project to a stop.

Agree on what counts as success

Before starting, briefly pin down what this is all for. Not “build a system,” but a concrete result: see real stock levels at any moment, cut the time to issue an invoice, eliminate double data entry, get a report in a couple of clicks instead of an evening in a spreadsheet.

This matters for two reasons. First, it filters out the extras — nice-to-haves you can launch without and add later, without bloating the first stage. Second, it gives you an honest way to check the result: the system either delivers what it was built for, or it doesn’t. Without that reference point, it’s easy to build something technically flawless that nobody uses.

A tip from experience: start small. Launch the system on one key process, let people work in it, and the real data will show you what to add next. That’s almost always cheaper and calmer than trying to predict everything upfront.

Where to start

You don’t have to complete this checklist perfectly — even a rough draft of the answers already saves weeks. Describe the process, look at your data, name an owner, gather the access, and articulate what you’ll count as success.

If you get stuck somewhere or aren’t sure which of these is critical for your case, start with a simple conversation. In a short brief we’ll walk these points together and quickly see what your specific accounting system needs and where it makes sense to begin.