Create a draft loan product

Allow full term length for each tranche disbursement. Only available for PROGRESSIVE schedule type with multi-disbursement enabled.

Charge entries; existing charge ids plus optional per-association flags.

How the final instalment is rounded when it differs from the others. Absent means the currency's own precision.

System-defined disbursement payee category. Optional; product-type applicability is a client-side concern until the parameter-metadata framework serves it.

how the stub between disbursement and the first instalment is billed. Priced by the CONTRACTUAL schedule type; refused for the others.

day-count convention for broken (stub) periods; same choices as dayCountConvention (parity). Null = regular-period behaviour. Declarative product configuration: stored as sent; the broken-period interest engine consumes it in a later phase.

Whether the product may participate in a co-lending arrangement. Optional; defaults to false.

whether broken-period interest is collected at disbursement. Refused for a schedule type that prices no broken period. Not yet consumed: no transaction or journal entry nets it from the proceeds (mock-up term preEmi). Defaults to false; explicit null is rejected. Declarative: stored as sent; the BPI engine consumes it in a later phase.

whether APR should be computed for KFS disclosures. Optional; defaults to false. Declarative: stored as sent; the APR/KFS engine consumes it in a later phase.

Create the product as a DRAFT: it cannot originate loans whatever its start and close dates say, and appears in no product selection list, until POST /v2/loanproducts/{productId}/activate releases it. Optional; defaults to false, in which case the product has no activation lifecycle at all and behaves exactly as it does today. TRANSITIONAL; this exists so the activation flow can be exercised before clients integrate the activate call; drafting becomes the V2 default once they do.

stable day-count convention name; the V2-only ALTERNATIVE way to fulfil the mandatory daysInMonthType/daysInYearType axes (the backend derives and persists both). Supplying the raw axes alone remains valid (convention stays null); supplying both requires consistency with the derivation (ACT_365→1/365, ACT_360→1/360, ACT_ACT→1/1, D30_360_US and D30E_360→30/360; stored distinctly; the engine-level US-vs-30E distinction is deferred).

product-level java.math.RoundingMode NAME (never an ordinal or any internal identifier). Null inherits tenant rounding. Declarative: persisted via the shared rounding profile; engine wiring consumes it in a later phase.

fixed nominal rate increment in percentage points per annum. Fixed-rate products only; must be null/omitted for floating products. Null = continuous.

maximum calendar days between disbursement and the first repayment; the ceiling sibling of minimumDaysBetweenDisbursalAndFirstRepayment (must be >= the floor). ACTIVELY enforced at loan origination for both schedule types. Null/omitted = no ceiling.

payment-formula variant. Optional; defaults to STANDARD_PMT (current engine behaviour). PRECISE_PMT is stored as declarative configuration; the precise-PMT engine consumes it in a later phase. Explicit null is rejected; send STANDARD_PMT to reset.

principal increment anchored at minimumPrincipal. Null/omitted = continuous band. Requires the complete principal band when supplied; the default principal must sit on the grid.

Stable category-tag codes from code group LoanProductCategory. Optional; duplicates rejected.

Stable product-type code from code group LoanProductType (see productTypeOptions in the template). Optional.

pinned monthly repayment day(s), 1-31, unique; CONTRACTUAL, monthly-frequency products only. The ONLY external recurrence representation (the internal rule string is never exposed). Derived first repayment dates snap forward to the earliest named day and supplied dates must fall on one of them (days 29-31 follow the existing short-month clamping). Several days collect several instalments a month, so at most one may be 28 or later (they would share February's last date) and they require a repayment interval of 1. Null clears; returned sorted ascending.

The weekday a contractual product collects on (MO..SU). Mutually exclusive with repayOnDay. On a monthly product it needs repayOnWeekdayOccurrence alongside it; on a weekly product every occurrence of the weekday is a collection.

Which occurrence of repayOnWeekday in the month a monthly product collects on: 1 to 4 counting from the start of the month, or -1 for the last. Refused on a weekly product.

residual (balloon) schedule eligibility flag. Declarative: stored as sent; the residual schedule engine consumes it in a later phase.

declarative input-mode selection for a configurator/LOS (D-27). Optional and NULLABLE; omitted or null means "not configured"; there is no server default. All five values are storable and none changes backend behaviour. The backend never derives Loan terms from scheduleSolver: Loan Product and Loan APIs always receive fully determined Principal, tenor and interest-rate values regardless of the configured solver.

increment in NUMBER OF INSTALLMENTS over the repayment-count band (never a calendar duration). Null/omitted = continuous.