Evekon

Challenge

Construction contractor with sites from Moscow to Yakutsk. Work done in Excel and messengers: payment requests approved via chats, documents lost, no overall picture of sites, contractors and accountable persons. Needed an ERP with proper approval workflow — "initiator → approver → accountant → payment".

What We Did

• Domain model: Construction sites → Warehouses → Suppliers/Contractors with requisites → Payment requests / Balance top-ups / Accountable top-ups → UPD / Receipts.
• 4-status workflow: Under Review → Pending → Topped Up → Rejected. Colour-coded badges show state at a glance.
• Payment requests: ID, date, initiator, site, contractor, supplier, amount, VAT, purpose. Expense categories configurable.
• Parallel flows: balance top-up requests, accountable top-up requests, UPD with states, warehouse movements.
• Fine-grained role model: initiator / accountant / manager / admin.
• Sites linked to Russian regions (Moscow, Yakutsk, Khabarovsk, Irkutsk, Vladivostok, Sakhalin, Siberia, etc.).
• Import/export for migration from Excel. Telegram bot for order intake and status notifications.

Result

• Moved from Excel + messengers to complete ERP with transparent financial workflow.
• Real data: 1,136 payment requests, 225 UPD, 32 construction sites, 23 warehouses, 205 contractors, 145 suppliers.
• Every payment linked to site, contractor, supplier and expense type — full analytics.
• Unified UI flow: list → status filters → table → detail card → create new record.