Financial services · commercial agreements implemented in software

A commission starts with the agreement behind it.

When a business works through partners, commercial agreements carry through into its administration. Who introduced an application? Which terms apply? Is a subpartner involved? IndustrylinQ handled analysis, design and development of an application and partner portal and its API for a financial services client.

Application and partner platform

The commercial agreement shapes the processing.

  1. Application

    External status becomes meaningful in the portal.

  2. Partner agreement

    Partner, subpartner, calculation basis and commission tier.

  3. Commission

    Calculated using the agreed terms.

  4. Administration

    Authorised processing in consistent batches.

Portal and API as one product

IndustrylinQ provided analysis, design and the complete development.

The question: how do agreements become consistent operations?

The platform supports applications, partners and subpartners with individual financial terms. Administrators need different views and actions from partners. Applications also have their own progress, distinct from financial processing.

We worked those relationships into the product. Commission tiers, percentages, calculation bases and costs became explicit business logic. A partner is more than a contact attached to an application: the relationship helps determine how the service is administered.

External progress, translated for the portal

Application information comes from an external system. We mapped those statuses to the business states used by administrators and partners in the portal.

Financial administration builds on that progression. The platform calculates commissions from the recorded terms and supports batch processing. The application, introducing partner, applicable agreement and administrative outcome remain connected.

Relational data and coordinated transactions

We built the interface in Vue and the API using Express and TypeScript. Sequelize and MySQL support the relational data model; the environment includes configuration for App Engine and Cloud SQL.

The API checks the administrator role when a commission batch is registered. Related administrative changes are processed within a single SQL transaction. This operation records commissions and payouts; it does not execute a bank payment.

That distinction matters to the person using the product. They need to understand what has been calculated, what has been recorded and which action takes place outside the portal.

What this means for the business and its people

Commercial terms become calculations and operations in the portal. Administrators can work from an application to the relevant partner agreement and financial processing. Partners receive an environment appropriate to their own role.

The engagement connects business analysis with software engineering. An agreement is not merely stored; its meaning carries through the product.

Explore our data and cloud architecture choices or our approach to permissions. Developing your commercial model can also be a standalone consulting engagement.

Your next step

An idea, or a detailed brief?

We start from where you are. Discuss the application, any existing requirements and the team we would work alongside.

Talk about your next step