FinanceRecurringClientInvoiceTemplateInput Input Object
The proposal a client-invoice schedule bills. A setup that cannot say what it bills has nothing to generate from, so the mutation refuses one rather than storing a row that would refuse itself on every occurrence.
Nullable, and stays nullable: making it non-null would turn a deployed client that omits it from a friendly refusal into a schema validation error, and the server and the web bundle deploy separately. The rule is stated in the mutation instead.
Fields
#
proposalId