Cloud accounting removes some local installation work but does not define a company’s accounting rules. In Dilovod, align reference data, documents and sales-channel integration. Otherwise accounting and the store may give different answers to a simple question: how much stock is actually available.
First establish the source of each figure
Separate product records, physical stock, reservations and sale prices. They may originate in different systems, but each figure needs an authoritative source. Agree who changes names, who records receipts and when the store receives updated quantities.
For example, a store order may reserve stock without constituting a completed sale. If an integration immediately deducts inventory and the accountant later posts it again, movements become incorrect. Map order statuses to accounting events before implementing the exchange.
Prepare data and working roles
Before import, check products, units, counterparties, warehouses and opening balances. It is better to fix duplicates in a controlled file than merge them after linked documents appear. Keep a list of decisions on ambiguous records agreed with accounting.
Staff need individual access and appropriate permissions; integrations need separately managed credentials. Do not include an API secret in an error screenshot or task description. Decide who can revoke access and how integration is restored after credential replacement.
How the API exchange works
Dilovod’s official API provides documented methods for reading and writing data. It is a developer tool, rather than automatic proof that any store is compatible. Check required entities, available fields, authentication rules and the constraints of the chosen scenario.
For retries, retain the external identifier and processing result. A temporary outage must not produce duplicate documents when service resumes. Show the operator which records failed to transfer, the reason and a safe retry action.
Checks before daily use
Run agreed examples covering orders, quantity changes, partial fulfilment, payment and returns. Reconcile documents, inventory and settlements as well as visible statuses. Separately test duplicate notifications and cases where the service response is lost.
Hand over the integration map and discrepancy handling rules. Regular reconciliation should detect missed events even when the log shows no errors. This distinguishes network failures from an incorrect decision about which system owns the data.
Sources and further reading
