Every payment must reconcile.

What needed to work

Partial payments, rounding, dates, and renewal must keep balances and reports consistent.

My contribution

A collaborative product engineering, calculations, and automation case. I reused existing engines and adapted the full interface, persistence, audit, and messaging into an isolated demo.

Engineering choices

• Validated amounts and atomic state updates.
• Fixed scenario clock and idempotent overdue updates.
• External sending blocked in production too.

Two ways to explore

1Simulation → contract → installments.

2Collection → payment → balances → score → report → WhatsApp preview.

What the demo demonstrates

Original: Collaborative contracts, calculation, rule based scoring, collection, and reporting system.

Demo: Isolated persistence, controlled clock, synthetic scenarios, previews, and simulated queue. Excess payment adaptations are documented.

Clear boundaries

The score is rule based. This version adds no AI inference to Lume Crédito. People and amounts are synthetic; the demo grants no loans and sends no collections.

State belongs to your visitor session. Restart from the demo bar.