Enterprise Systems Architecture

ERP and financial systems built for real-world operations

Enterprise platforms developed from real business needs, with backend architecture focused on domain modeling, APIs, and reliable operational workflows.

Businext ERP

Enterprise ERP system developed from scratch to support real operations across finance, sales, inventory, and human resources within a unified platform.

Business context

Businext originated inside a real business operation that initially relied on a legacy POS system developed in C# and running on physical servers. That system presented technological limitations, vendor dependency, and difficulties evolving toward new operational requirements. A first web version was later developed using Web2py focused on sales and inventory. Although this version still operates certain processes such as point-of-sale and stock control, its functional evolution stopped. Based on that experience, Businext ERP was created as a new platform designed to progressively replace previous systems and centralize the company's operational infrastructure.

What it solves

Businext ERP consolidates processes that were previously distributed across spreadsheets, disconnected tools, and external systems. The platform integrates financial operations, HR management, purchasing workflows, CRM, accounting, and administrative control within a domain-oriented backend architecture. This approach enables clearer business rules, operational traceability, and long-term platform evolution.

Core technologies: Python · FastAPI · React · MySQL / MariaDB · REST APIs · AWS · Linux · Nginx | Architecture: Domain boundaries · Service layer · Transactional workflows

Architectural approach

• Domain boundaries defined for finance, inventory, HR, sales, and accounting.
• API-first architecture that enables explicit workflows and independent module evolution.
• Modular FastAPI backend with clear service layers for business rules.
• Production deployment on AWS over Linux and Nginx with controlled change release.

Impact

• Central platform for the company's administrative and financial operations.
• Enterprise codebase with more than 125k lines under continuous evolution.
• System designed to support critical business rules, operational consistency, and financial traceability.

Technical challenges

• Keeping accounting and inventory rules isolated while still supporting cross-domain workflows.
• Evolving a 200k+ LOC ERP without turning every new feature into a platform-wide regression.
• Designing APIs and modules that match the business process instead of mirroring database tables.

Operational results

• Reduced process fragmentation by consolidating administrative workflows in one operational model.
• Made finance, sales, inventory, and HR changes easier to reason about through explicit service boundaries.
• Created a maintainable internal ERP foundation that can absorb new modules without reworking the whole platform.

TR0V1 Credit Platform

Financial platform designed to manage credit accounts, payments, interest calculations, and account statements within a real credit operation.

Business context

TR0V1 was created to support a new business model based on providing credit to customers within a commercial operation. The platform needed to manage balances, billing cycles, payments, interest, and account statements while maintaining long-term financial consistency. The first version was built using Web2py for both internal users and client access. As the system evolved, a full migration was performed to a modern architecture using FastAPI and React. A complete migration of data, documents, and historical records was later executed to move the system into the new platform. TR0V1 currently runs on this architecture and was recently integrated into Businext ERP as part of the broader enterprise platform.

What it solves

TR0V1 models the full lifecycle of a credit account including: credit applications, approvals and contracts, credit lines, purchases and charges, payments and reconciliation, and account statement generation. The platform focuses on financial consistency, operational traceability, and clear business rules across critical transactions.

Core technologies: Python · FastAPI · SQLAlchemy · React · REST APIs | Architecture: Service layer · Transactional workflows · Financial domain modeling

Architectural approach

• Backend focused on financial business rules and state transitions.
• Domain modeling for credit accounts, payment flows, and interest calculations.
• APIs consumed by both internal administrative tools and client interfaces.
• Architecture designed to preserve financial consistency in critical operations.

Impact

• Platform used to operate a real credit model for customers.
• Maintains consistency between balances, billing cycles, and payments.
• Improves traceability of financial events for reconciliation and operational control.

Technical challenges

• Preventing duplicate financial events during retries and asynchronous flows.
• Maintaining balance consistency over time with partial payments and interest calculations.
• Designing services that represent financial workflows instead of simple CRUD operations.

Operational results

• Made credit lifecycle rules explicit across charges, billing periods, payments, and statements.
• Improved operational control by detecting reconciliation differences early.
• Delivered a backend platform supporting both internal operations and client visibility.