Sharing our success story implementing automated credit approval workflows in Creatio. Previously, credit applications went through manual review by underwriters checking credit scores, debt-to-income ratios, and employment history - taking 4-6 hours per application. We built decision tables in Creatio 7.18 that codify our approval criteria and integrated with external credit bureaus for real-time data. The system now auto-approves straightforward cases in under 2 minutes and routes complex cases to senior underwriters with pre-populated risk assessments. Processing time dropped 85% for standard applications while maintaining approval accuracy. Interested in how others have leveraged decision tables for financial workflows.
The audit trail point is critical for financial services. Beyond logging which rules executed, you need to capture the input data state at decision time for regulatory examination. If a customer disputes a denial six months later, you must be able to reconstruct exactly what data the decision table evaluated. We store decision snapshots including all input parameters, rule evaluation results, and external data responses. This has protected us in several dispute scenarios where customers claimed their credit score was higher than what our system showed.
We set conservative thresholds initially - credit score above 720, DTI below 35%, and stable employment for 2+ years triggers auto-approval for amounts under $50K. Everything else goes to manual review. The decision table evaluates 12 factors simultaneously including payment history, existing credit utilization, and income verification. For exceptions, underwriters can override any decision with documented justification, and those overrides feed back into our decision table refinement process quarterly.
This is a great use case for decision tables. We implemented something similar for insurance underwriting. One tip - make sure you build robust audit trails into your decision table execution. Regulators want to see exactly which rules fired and why an application was approved or denied. Creatio’s decision table logging helped us pass our first compliance audit with zero findings. Did you implement any A/B testing to validate that automated decisions match historical underwriter decisions before going fully live?
How did you handle the external data integration with credit bureaus? We’ve looked at similar automation but the API costs for real-time credit pulls are significant. Did you implement any caching or batch processing strategies to reduce API calls? Also curious about data freshness requirements from a regulatory perspective.