Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My ERP or accounting software does not fit how my business works

Short answer

A system feels rigid when your process does something it never expected. The answer is rarely rebuilding it. First separate what the system must hold (money, stock, tax) from what is your own workflow, then add that workflow around the system through its supported extension points.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Staff keep spreadsheets next to the system to do the real work.
  • Every change request is quoted as a big customisation.
  • Staff type the same order into two places.
  • The system forces steps my staff never do, or lacks one they always do.
  • Upgrades break our customisations.

Why does this happen?

  1. The system models a generic business

    ERP and accounting products fit common processes. Your approval step, quote format or pricing rule may be outside what they ship.

  2. Customising the core makes upgrades painful

    Changes made inside the product can break when the vendor updates it, so every upgrade becomes a project or is postponed.

  3. The process was never written down

    Staff know how it really works, but the system was configured from a sales demo. The gap is found only after go-live.

  4. Workarounds hide the cost

    Spreadsheets and re-typing seem free, but errors, delays and one person who knows the file are real costs.

  5. Integrations are shallow

    If other tools only get a nightly export from the ERP, anything needing fresh data lives in a spreadsheet.

What can I do about it today?

  1. Write down the process as it really runsAsk the staff who do the work to describe each step, including the spreadsheet parts.
  2. Mark which steps the system must ownMoney, stock, tax and legal records belong in the system. Other steps may not.
  3. List the workarounds with their costHours per week, errors found, and who depends on them.
  4. Do not change the system's core settings in a hurryWrong tax, stock or numbering settings are hard to undo once transactions exist.
  5. Ask the vendor how extensions are meant to be builtSupported add-ons, APIs and custom fields. Ask what survives an upgrade.

When should I bring someone in?

  • A workaround holds money, stock or tax data outside the system.
  • A quoted customisation is large and you are unsure it is needed.
  • You are considering replacing the whole system.

How do I handle it?

  1. Compare process and systemI list each step of your process, and show which the system covers, which it can be configured to cover and which it cannot.
  2. Prefer configuration, then add-onsSettings first, then supported extensions, and customising the core only as a last choice.
  3. Build around, not insideYour special workflow sits in a small separate tool that reads and writes through the system's documented interface.
  4. Protect the booksAnything touching accounts is tested on a copy, with a reconciliation against the real ledger before it goes live.
  5. Decide on replacing with evidenceIf the gap is too large, I help write what a replacement must do, rather than leaving the choice to a demo.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I replace the ERP?

Only if the gaps cannot be closed by configuration or add-ons. Replacing is the largest and riskiest option.

Can a small tool sit beside the ERP?

Yes, if the ERP offers a supported way to read and write data. This is often the cheapest and safest change.

Will customisation break on upgrade?

It can if it changes the core. Work done through supported extension points is more likely to survive.

Do you give accounting advice?

No. Tax and accounting rules are for your accountant. I work on the software side.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.