Billing System

Development Duration

9 Months

Technology Stack

Task

• Client context: A growing retail company was accepting payments through separate providers, while its accounting team reconciled invoice and payment information from different sources. The existing tools no longer matched the business's workflows.
• Manual work: Fiscal receipt processing required manual intervention, and financial reporting involved combining exported data. The client needed these activities connected to the order and payment lifecycle instead of managed as separate tasks.
• Integration scope: The platform needed connections to payment gateways and the fiscal data operator (FDO), together with invoice management, balance tracking, reconciliation and reporting. It also had to accommodate additional payment providers.
• Finance-team visibility: Accounting staff needed a shared view of payments and balances, tools to investigate discrepancies, and reporting interfaces with filters and exports for their financial workflows.

What was done

• Modular billing architecture: We connected order processing, invoice creation, payment data exchange, balance management, reconciliation and reporting. Provider integrations were separated from the core billing logic so new connections could be added without redesigning the whole workflow.
• Payment and fiscal integrations: We implemented connections for YooMoney, Sberbank and internal payment gateways, along with a gateway for transmitting receipt data to the FDO. Payment acceptance and fiscal receipt processing became parts of the same operational flow.
• Invoice lifecycle: The platform generates invoices, tracks balances, records balance holds and updates payment and order states through confirmation and closure. These records let staff follow progress without reconstructing the invoice's status from separate systems.
• Reconciliation and reporting: Accounting interfaces combine payment and balance information with customizable filters and data exports. The reconciliation tools match payments to invoices and highlight exceptions for human review, supporting investigation when records do not match.
• Event notifications: Notifications keep relevant users and connected systems informed about payments, issued invoices, balance holds and errors. Staff can see changes in the billing workflow and respond to issues that need attention.

How it works

• Order and invoice: A customer places an order, and the platform generates an invoice and sends the relevant notification. The customer pays through a supported payment provider.
• Payment and receipt: The system tracks payment confirmation and updates the invoice and order. The fiscal workflow generates receipt data and sends it through the FDO.
• Reconciliation and review: Accounting staff compare payment and invoice records, investigate highlighted exceptions and use filters and exports for reporting. Notifications make payment events and errors visible to relevant users.
• Operational outcome: Orders, invoices, payments and balances are brought into a shared platform. Routine processing is automated, while finance staff retain tools for investigating discrepancies and reporting on financial flows.
• Further changes: Developers can add provider integrations and adapt billing rules for different product categories, customer types and use cases while retaining the shared billing workflow.