What is customization
Customization is the adjustment and refinement of an accounting system to fit the specifics of a particular business. Unlike development from scratch, customization works with an existing system—adding fields, reports, rules, and integrations.
Typical examples of customization: additional fields in documents (for example, "contract number with the counterparty"), custom reports (sales by region, margin by brand), special calculation rules (volume discounts), integrations with external services (bank, marketplace, CRM).
Customization is a normal practice. More than 80% of implementations include some degree of modifications.
When customization is really needed
1. Unique business logic. You have processes that are not found in most businesses in your industry. For example, a complex cost formula, specific document flow, custom bonus calculations.
2. Integration with external systems. Bank, website, marketplace, courier services, CRM. If there is a need to exchange data automatically — integration through API is required.
3. Specific Reporting. If the manager or shareholders expect reports in a very specific format that is not provided for by the standard. Or the industry requires special types of reporting (pharma, licensed activities).
4. Special requirements for the interface. In your field, there is a specific logic for data entry that is inconvenient to implement with a "box" solution. For example, for retail — quick input via a scanner, for manufacturing — multi-step approval.
5. Security requirements. Separate roles, additional action logging, integration with the corporate authorization system.
When customization is NOT needed
1. "I want it to be like it was in the old program." Before requesting modifications, check — perhaps in the new system, it is done differently, but just as effectively (or better). It's not worth bringing old habits into the new system.
2. Minor conveniences for one employee. "Our Olena finds it inconvenient that the field is at the top instead of the bottom." This is not a reason for customization — it is a reason for user training.
3. Standard functions without proper training. It often seems that "the system can't do this," but in reality, the function exists — it's just that no one has shown how to use it.
4. What can be solved by a process, not a system. If the problem lies in the processes, not in the tool — customization will not solve it, but only mask it.
How to understand when customization is really necessary
At the implementation stage, ask an experienced partner: have they encountered a similar task in other projects? How did they solve it? Perhaps there is a standard solution without customization.
Useful tip: launch the system "as is" and work for 2-3 months in the typical functionality. During this time, it becomes clear what really hurts and what only seems to be a pain. Most of the "mandatory" improvements filter themselves out.
Make a prioritized list of improvements. Not everything at once — first the critical ones, then the important ones, and finally the "nice to have" ones. This way, the budget is spent more effectively.
How much does customization cost?
The cost depends on the volume and complexity of the work. Benchmarks in the Ukrainian market: simple customization (new field, simple report, basic rule) — from 3,000 to 10,000 UAH, medium (new module, complex report, bank integration) — from 20,000 to 50,000 UAH, complex (new business logic, API integrations, multilingualism) — from 80,000 UAH and above.
A useful guideline: the total amount of customization during implementation usually ranges from 20% to 50% of the cost of licenses + basic implementation. If it's higher, it's worth checking whether all the modifications are truly necessary or considering whether the chosen software product is appropriate.
Pitfalls of Customization
Compatibility with updates. Each modification will complicate future system updates. A quality contractor makes customization as compatible with updates as possible — but this is additional work.
Documentation. Without documentation, customization becomes a "black box" — after a year, no one remembers how and why it works. Always request documentation for every modification.
Dependency on the contractor. If one company has done the customization, it is then difficult to transfer it to another. It is better to choose a long-term partner.
Cost overruns. Without clear business requirements and specifications, customization can easily "inflate" — what started as simple turned out to be three times more complex. Document the scope before starting work.
How to avoid unnecessary revisions
First, understand your system. Spend time on comprehensive training — and you'll find that many of the "desired" features are already there.
Ask "why." For every customization proposal: "What will happen if we don't do this?" Often the answer is "nothing critical."
Test in a typical configuration. Run the system "as is" and see how it actually works. Do not make decisions based on assumptions.
Allocate a budget for customization of 20-30% of the base cost — for "unforeseen" expenses. If you don't use it — that's fine. If you need it — you'll be ready.
Are you planning to implement with customization?
SPOC has experience with complex custom projects in various industries. Leave a request — we will discuss what is truly needed in your case and what can be done without.