Business documents had to produce correct stock and financial movements across connected company processes.
02 / How I approached it
How I approached it
I examined how companies operated and translated those rules into documents, reports, queries and integrations in 1C УТП/УНФ. Custom modules addressed transport logistics and production operations, alongside material norms, costs and internal data exchanges.
System flow
Business operation
Document
Stock & money movements
Reporting
What that means in practice
Architecture & decisions
01
Understand the company before configuring the system
I worked directly with customers to understand their technological and administrative processes, including projects built from the ground up. That meant discussing how materials, documents, stock and money actually moved before configuring accounting and integrations. The customer’s operational model shaped the software model.
02
Production, materials and spending plans
The work included production planning, material norms and consumption, stock movements, costs, payroll and spending plans. My manufacturing background helped connect the figures in 1C to the operations creating them. Reports and complex queries made that operational information usable for planning and control.
03
Custom modules for real operations
I developed transport-logistics modules and tools for accelerating or improving production operations. Data exchanges and integrations connected these modules with the rest of the company’s accounting. This experience established the document-to-movement model that later reappeared in financial services and the Python business operations platform.
03 / The outcome
The outcome
The experience connected software models to physical stock, money and operational consequences, forming a foundation for later financial and business systems.