Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Payments & billing

One back office for invoicing, payment collection and debt recovery

A Java billing back office covering invoices by customer segment, payment batches, approval workflows, adjustments, write-offs, credit scoring and GL posting.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

The client is a payments operator that bills corporate, government and retail customers for cards, devices and transaction services.

MultiGenesys worked on its billing, payment and debt-management back office: the system finance teams use to raise invoices, record payments, approve adjustments, chase overdue debt and post everything to the general ledger.

The challenge

What needed solving

Many customer segments, many invoice types

Corporate, government and retail customers each needed different invoices, payment terms and reversal handling, plus manual invoices for one-off charges.

Controls on every money movement

Adjustments, manual invoices and write-offs needed approval by the right authority, with attachments and a full history for audit.

Collections and overdue debt

Finance teams had to track overdue invoices, ageing and delinquent accounts, and decide how to treat each customer based on its credit standing.

Clean hand-off to the ledger

Every billing and payment event had to post correctly to the general ledger, with tax codes applied consistently.

The solution

What we built

  1. Modular billing application

    A three-tier Java application (global, core and web modules) on a rapid enterprise application framework, with MySQL and role-based screens for each finance team.

  2. Invoicing and payments

    Automatic and manual invoice generation by customer segment, invoice payment terms, payment batches, check payment batches, manual payments, advance payments and refunds or reversals.

  3. Approval workflows

    Configurable delegated-authority rules route manual invoices, adjustments and write-offs for approval, each with attachments and history.

  4. Debt management

    Overdue-invoice tracking, ageing information, delinquent-account handling, credit scoring, threshold monitoring for fleet accounts and annual-fee calculation.

  5. Ledger and tax

    A GL processing service builds general-ledger transactions and distribution entries from billing events, with tax rates and transaction codes kept as reference data.

  6. Reports, imports and notifications

    JasperReports and YARG templates produce invoices and finance reports, mass upload handles bulk data with summaries, and email templates notify customers.

The outcome

What changed

Billing and collections in one place

Invoicing, payment posting, approvals and debt follow-up run in one application instead of separate spreadsheets and tools.

Audit-ready approvals

Every adjustment, manual invoice and write-off carries its approver, attachments and history.

Consistent ledger postings

Billing and payment events flow into GL transactions through one service, using shared tax and transaction codes.

Technology used

  • Java
  • CUBA Platform
  • Gradle
  • MySQL
  • Apache Tomcat
  • JasperReports
  • YARG
  • REST API
  • JaCoCo

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk