Financial services: controls first, speed second, and both are achievable

Analysing loan turnaround for our clients consistently shows the same pattern: underwriting takes hours, and the process takes days. The time goes into document collection, chasing missing items, verification, and waiting for a file to move between desks.

We compress that by moving collection and verification to the front and running them in parallel. Digital application with document upload from the customer's phone. e-KYC through Aadhaar or PAN with automated validation. Bank statement analysis producing income and obligation figures automatically. Bureau pull integrated. Penny-drop account verification. Each of these runs as soon as its input arrives rather than in sequence.

By the time the file reaches an underwriter, the data is complete and validated. Decision turnaround in our deployments has typically moved from around four days to under six hours, without reducing the depth of assessment.

Maker–checker is implemented at the transaction level rather than as a screen. Any action with financial or customer consequence — a disbursal, a limit change, a waiver, a write-off, a master data amendment — requires a separate authorised user to approve, and the system prevents the same person from doing both regardless of their role combination.

Audit logging is append-only and captures the actor, the timestamp, the before and after values, and the approval chain. It is retained beyond any plausible investigation window and it is queryable, because an audit trail that requires a database export to interrogate does not get used.

Segregation of duties is enforced through role design done with your compliance function, not by developers guessing. Access is reviewed periodically with a report showing who has what, which is the evidence an auditor asks for and which most institutions compile manually.

Most lenders operate a policy that is partly written and partly held in the heads of experienced credit officers. Encoding it produces two benefits: consistency, and a record of what the policy actually was when a decision was made.

We build a rules engine where policy is configured rather than coded — eligibility criteria, exposure limits, deviation thresholds and approval matrices can be changed by an authorised business user with a versioned record of the change. Scorecards, where used, are versioned identically so a decision can always be evaluated against the policy in force at the time.

What we do not do is remove the human from consequential decisions. The system produces a recommendation with the reasons for it, including any deviations from policy; a credit officer decides. That structure is both better lending and better defensible when a portfolio is reviewed.

Collections is where portfolio quality is preserved or lost, and most operations run it as an undifferentiated calling exercise. The result is that low-risk accounts that would have paid anyway are contacted while genuinely deteriorating accounts get the same attention.

We build bucket-wise strategy: segmentation by risk and behaviour, differentiated treatment ladders — automated reminder for the reliable late payer, early field visit for the account showing deterioration signals — allocation to field agents with route optimisation, and outcome capture from a mobile app with geotagged evidence.

The measurable effect is concentrated in bucket-1 roll-forward, which is where intervention has the highest leverage. Clients typically see roll-forward reduce by around thirty per cent, which flows directly to provisioning and profitability.

Regulatory returns are usually compiled by a small team over several days each period, from data extracted and reworked. It is laborious and it introduces the risk of a filed figure not matching the operational record.

We generate returns from the operational ledger with the classification rules encoded — asset classification and provisioning under the applicable norms, ageing, exposure concentration, and the specific returns your registration requires. The reviewer checks and approves rather than compiles.

For audit, the useful deliverable is not a report but the ability to answer a question quickly. When an auditor selects fifty accounts and asks for the complete file including approvals, the response should be a query rather than a week of retrieval. That capability is designed in.

For insurance brokers and corporate agents the problems are different but the control requirement is similar: policy issuance and renewal tracking, commission reconciliation against insurer statements — an area of chronic under-recovery — claims assistance workflow, and IRDAI-aligned record-keeping.

Commission reconciliation is usually the highest-value module. Insurer statements are compared automatically against the policy record and the agreed commission structure, with variances flagged. Brokers who have never reconciled systematically are routinely surprised by the cumulative shortfall.