Nice step, thank you. Depending on community feedback, I would like to suggest an additional configuration be *considered* for action or enhancement baccklog.
------------------------------ An additional configuration setting would determine the behavior of the disbursedAmountPercentageForDownPayment field: - *Direct Edit Mode*: The field is manually editable. This mode is suitable for situations where the down payment is a simple, single-entry value and source-level verification isn't required by the application itself. - *Calculated Field Mode*: The field is non-editable. Its value is automatically calculated elsewhere and populated from a separate *child feeder system*. Child Feeder System Example The child feeder system might be UI modal which allows for *multi-instance data entry*. It captures individual down payment sources and their amounts. IF these child fields were core fields, great, but if not they could be extensions. For example: - 2.5% (Source: Gift from Parents) - 12.5% (Source: Savings of Borrower) - 5.0% (Source: Work Equity) The system then sums these entries and passes the total (e.g., 20.0%) to the main, non-editable disbursedAmountPercentageForDownPayment field. Business Reason The primary business reason for structured and referenced downpayment is to *streamline* loan manufacturing process and meet *compliance and verification requirements*. While a direct edit field is simple, and is perfect for many loan types, it doesn't provide a structured way to capture and verify multiple sources of funds, which is often a *regulatory necessity for mortgage* and other large purchase type loans. Anticipating some type of "child feeder system" ensures that the final down payment percentage COULD support loan level detail of documented sources, streamlining the verification process without expanding scope past the additional configuration point at this time. Thanks for any feedback or consideration, Paul
