What an ERP actually changes day to day

“ERP” sounds like something for large corporations. In practice it is just one database that everyone in the company uses, instead of each department keeping its own.

Here is how that plays out across four concrete tasks.

Goods receipt

Before: the warehouse manager retypes the delivery note into a spreadsheet. The bookkeeper enters the purchase invoice separately. Costings are worked out by hand, then the retail price is retyped into the till.

After: the purchase invoice is entered once. The costing calculates itself, the new price reaches the till the same moment, and stock goes up without a single extra entry.

Issuing an invoice

Before: the sales rep opens a Word template, copies items from the price list, works out discount and VAT by hand, then sends the invoice to accounts to be posted.

After: the invoice is issued from the system. Price and discount come from that customer’s terms, VAT calculates itself, posting to accounts happens automatically, and stock is released at the same moment.

Month-end

Before: bank statements, branch takings and purchase invoices are joined up by hand. One document is always missing.

After: turnover was posted through the month, as it happened. Closing the period is a check, not a reconstruction.

The question from management

Before: “How much of this item did we sell in Banja Luka last week?” — and then everyone waits for someone to build a spreadsheet.

After: the same question is one report with three filters, and the answer arrives while the conversation is still going.

What an ERP does not change

To be fair: a system does not fix badly negotiated prices, it does not collect your debts for you, and it does not replace someone who knows the trade. What it changes is the amount of time spent retyping and hunting for data — usually between five and fifteen hours a month per back-office employee.

If you want a rough estimate for your own company, there is a slider calculator on the site. It is orientation, not a quote.