Savings plan ERP with multichannel collections for Grupo ZAG

Grupo ZAG sells real estate through payment plans. Its product is not charged once but month after month for years, so every owner has a plan and every plan generates periodic commitments to settle, collect and post.

In an installment model, a payment that comes in and does not get posted correctly is not an accounting error: it is an installment the system keeps demanding and a customer who receives a notice they do not deserve.

• Four collection channels: bank transfer, direct debit, ATM self service and bill payment platforms, each with its own format.
• Accounts that are not the holder's: a relative pays from their own account and the system has no way to recognize it.
• Complex ownership: owners with more than one unit and units with more than one co owner break any simple posting rule.

Without a circuit that closes end to end, the cost is not administrative: it is the trust of a customer who pays and keeps getting chased.

We built the ERP that governs the whole business: it generates plans, settles commitments, receives money through every channel, posts it and keeps outflows under the control of whoever has to authorize them.

The system was not handed over as a black box: every process was documented as a procedure the client's own team can run.

Plan management

• Creation and setup of new payment plans, with the system's initial configuration.
• Discount and promotion schemes, with their operational checklist.

Collections across four channels

• ATM self service: the customer enters their ID number and pays upcoming or recently due installments, with the receipt layout defined and web services for the integration.
• Bank transfer and the bill payment platforms in widest local use.
• Management of related bank accounts, to recognize money arriving from accounts other than the holder's.
• Cases resolved for owners with more than one property and units with more than one co owner.

Internal control and close

• Payment approval module, so outflows are authorized by the corresponding role.
• Monthly administrative close process.

Architecture and technology

• Custom ERP with documented APIs, including those for plan sales.
• Integration with self service ATMs, transfers and bill payment platforms.
• The customer portal, the CRM and the mobile apps consume those APIs as the single source of truth.

Learn more about software development.

The business went from collections spread across channels to a single system that settles, collects and posts.

Starting point

• Collections scattered across channels, with no circuit closing end to end.
• Payments from accounts other than the holder's with no way to be recognized.
• Business data replicated across the systems consuming it.

Strategic impact

• Four collection channels coexist on one posting circuit.
• Money outflows are authorized by role rather than by trust.
• The portal, the CRM and the apps consume the same source of truth instead of keeping parallel data.
• Every process was documented as a procedure the client's team can run.