Overview

Returns the billing adjustment options for an endorsement proposal. This shows how the premium difference between the original policy and the endorsement will be distributed across invoices. The response includes the total premium adjustment and two sets of invoice adjustments: pending adjustments (already queued) and next-invoice adjustments.

Preconditions

• The proposal should be an endorsement (not a new quote).
• The proposal should be rated so that premium differences are calculated.

Examples

Scenario 1: Endorsement with a premium increase:

GET /api/Quotes/Proposals/12345/EndorsementBillingOptions

200 OK
{
  "PremiumAdjustmentTotal": 1500.00,
  "PendingInvoiceAdjustments": [
    {
      "InvoiceDate": "2026-06-01T00:00:00",
      "DueDate": "2026-06-15T00:00:00",
      "Adjustment": 750.00,
      "NewTotal": 2000.00
    }
  ],
  "NextInvoiceAdjustments": [
    {
      "InvoiceDate": "2026-09-01T00:00:00",
      "DueDate": "2026-09-15T00:00:00",
      "Adjustment": 750.00,
      "NewTotal": 2000.00
    }
  ]
}

Scenario 2: No premium difference:

GET /api/Quotes/Proposals/12345/EndorsementBillingOptions

200 OK
{
  "PremiumAdjustmentTotal": 0.00,
  "PendingInvoiceAdjustments": null,
  "NextInvoiceAdjustments": null
}

Notes

• The PremiumAdjustmentTotal is sourced from the proposal's OriginalTotalCostDifference field, defaulting to 0.00 if null.
• The pending and next invoice adjustment arrays may be null (not empty arrays) when there are no adjustments.
• This endpoint is intended for endorsement proposals. Calling it on a new (non-endorsement) quote will return results based on whatever data is present, which may not be meaningful.
• The billingStatus parameter on POST /api/Quotes/Proposals/{proposalId}/BindQuote determines which adjustment strategy is used when the endorsement is actually bound.