Before you buy an accounting and stock system

A checklist for an Iraqi company choosing software for invoices, stock and customer balances, and the questions to settle before a supplier quotes you.

Few companies in Baghdad decide one morning to buy an accounting system. More often the stock count sits in an Excel file on the accountant's laptop, the warehouse manager keeps a notebook of his own, and the owner works out the month's profit on a calculator. Nobody can say with confidence how much of one item is in the store, or which customer still owes money from August.

List the transactions you handle in a normal week

Before you look at any program, write down what passes through your office between Sunday and Thursday:

  1. a cash sale at the counter, with a printed invoice and a stamp;
  2. a sale on account to a known customer, paid in two or three parts;
  3. a purchase from a wholesaler, often arriving with a handwritten invoice;
  4. goods returned by a customer, and goods sent back to a supplier;
  5. stock moving between the store and a branch, or between two stores;
  6. damaged or expired goods taken out of stock;
  7. one item priced in dinars and another priced in dollars.

Every line on that list needs a place to go in the system you buy. A supplier who does not ask about these seven things will build or configure around the two or three he happens to know. If your list runs past a dozen lines, you have not written a wish list; you have written a description of your business, which is exactly what a supplier needs in order to quote properly.

The four numbers the system has to produce

A system earns its place by answering a small set of questions from the data your staff entered. These are the four to insist on:

NumberQuestion it answersWho asks for it
Stock on hand, per itemDo we have 12 of this in the store, or 4?Sales staff, warehouse
Customer balanceHow much does this customer owe, and since when?Owner, accountant
Cash positionHow much is in the drawer and how much in the bank today?Owner
Margin per item or per monthWhich items earn, and which only move?Owner

A program that cannot produce these four from the data your staff typed is not doing the work, whatever its feature page lists.

A checklist to fill in before you talk to a supplier

Answer these in writing, one page, before the first meeting. The answers decide whether a ready-made package fits or whether your work needs something built around it.

  1. How many items do you sell, and does each one already have a code or a barcode?
  2. Which units do you sell in: piece, carton, kilo, metre, litre?
  3. Is any item bought in cartons and sold in pieces? What is the conversion?
  4. How many places hold stock: stores, branches, a delivery vehicle?
  5. How many people will use the system at the same time, and on what: desktop, laptop, phone?
  6. Which customers buy on account, and what credit limit do you allow each of them?
  7. How do you price: fixed price, a special price for one customer, a discount for quantity?
  8. Do you sell in dollars as well as dinars, and who decides the rate on the day?
  9. Which invoices does your accountant need, and which statement do you hand the customer?
  10. Who may change a price, delete an invoice, or write off stock?
  11. How do you count stock now, and how often?
  12. What must appear on the printed invoice: logo, stamp area, phone numbers, a serial number?

On the currency question, decide one rule and write it down, because staff will otherwise invent three. If you invoice in both currencies, the way you record the rate on the day matters more than the symbol on the paper; there is more on that in Dinar and dollar: invoicing in two currencies.

Where a ready-made package is enough

For a company that buys and sells standard goods, from one or two stores, with a handful of users and no production, a ready-made accounting and stock program is usually the cheaper and faster choice. Invoices, balances and stock work at a reasonable level, staff can be trained in a few days, and the risk stays small.

It starts to fit badly when your differences are the daily work rather than the exceptions: items sold in units with conversions, a special price list per customer, goods out on a delivery round with the driver collecting cash, material turned into a finished product, or a monthly report your management asks for that no other company asks for. In those cases a system built around your process is worth the longer project, and it is worth describing your process on paper first, as we explain in From Excel to a system and in our software development work.

One person has to own the data

Most failed rollouts are not software failures. A sale is not entered on Tuesday, a return is written on a slip, and by month end the stock figure is wrong and everyone goes back to the notebook. Name one person responsible for the system and give them the authority to refuse a transaction that is not entered. Count stock against the system every month, in the first year especially, and correct the difference the same week. Decide now what happens when the power or the internet line drops: a numbered paper invoice from a booklet, entered the next morning, is enough.

Move the balances across, not the history

Clean the item list before the move. One name and one code per item, no "item new" and no "test". Bring across four things: the item list with cost and selling price, the stock count as of the go-live date, the customer list with the balance each one owes, and the supplier balances. Two or three years of old invoices are rarely worth importing; keep the old file readable and searchable instead. Agree the go-live date with your accountant at the start of a month, when balances are already closed.

Test it with one real week of your paper

Do not accept the work on a demonstration. Give the supplier a real week of your documents: thirty invoices, one return, one stock transfer, one customer paying part of an old balance, and one price change in dollars. Then check the four numbers yourself, against the paper. Ask for a short written handover: how the backup runs and where it is kept, how to add a user or remove one when an employee leaves, and who to call when something breaks. Pay the last part of the money after that week, not before it.

If you are choosing a system now, start with the two lists above: the transactions of a normal week and the twelve questions. PearlFibers builds Loop for companies that need invoices, stock and customer balances in one place. If you are unsure whether a ready-made program or a system built for your work is the better answer, send us the filled checklist through the contact page and we will tell you which of the two fits, including when neither is needed yet.

More from the blog

← All articles