Custom accounting often begins with a spreadsheet between systems: someone manually allocates costs, calculates remuneration or matches documents. When that calculation becomes critical, it should become a managed module or gateway. Preserve an explainable result without turning the whole ERP into uncontrolled customisations.
Separate accounting rules from technical problems
Establish what is missing: a formula, analytical dimension, approval or data transfer. A missing report does not always require a new accounting core. Existing data may only need a validated view; missing data first requires a change at its source.
The financial rule owner approves examples of correct results. Record units, currency, effective dates, rounding and exceptions. A developer should not independently decide how to allocate a disputed amount because a formula has several interpretations.
Choose the customisation boundary
Options include an extension, a separate calculation service or an integration gateway. Compare upgradeability, API availability, permissions and maintenance. A module should access data through an agreed contract rather than modify a product’s internal tables without control.
For example, costs may need allocation across projects using an agreed basis. The module retains input values, the rule version and allocation results. The accountant can review the explanation and approve it before documents enter the main system.
Make reruns safe
Integration must distinguish a new document, a correction and a repeated request. Retain external identifiers and processing statuses. If a response is lost after a write, retrying must not create another posting. Design behaviour around the receiving system’s capabilities.
Correcting a posted operation needs a separate agreed procedure. Do not silently rewrite history when a user changes the input file. Show differences, ownership and effects on subsequent calculations so results remain reproducible and verifiable.
Accept the module based on results and maintainability
Test normal and edge cases: empty data, currencies, rounding, cancellation and retries. The financial owner confirms expected results. Separately reconcile the result against the document and report in the main system.
Hand over formula definitions, the integration contract, source code as agreed and restoration instructions. Limit access to required operations and store secrets outside public files. The custom module must remain understandable to the next specialist after a team change.
Sources and further reading
