---
search:
  tags:
    - billing
    - PATCH
seo:
  description: >-
    What can be updated: This endpoint allows partial updates to… Reference for
    the PATCH /billing/potential-invoices/{id} endpoint in the Leadtime Public
    API API.
sidebar:
  badge: PATCH
  label: Update potential invoice settings
title: Update potential invoice settings
type: openapi-operation
---
**What can be updated:**
This endpoint allows partial updates to potential invoice settings. Only the fields you provide in the request body will be updated; all other fields remain unchanged. This means you can update just one field, multiple fields, or all fields in a single request.

**Updatable fields:**
- **billedFrom**: Billed from date (ISO 8601 date string). Sets the start date for the billing period that will appear on the final invoice document. This can differ from the actual service period (periodFrom) if you want to show a different date range on the invoice.
- **billedTo**: Billed to date (ISO 8601 date string). Sets the end date for the billing period that will appear on the final invoice document. This can differ from the actual service period (periodTo) if you want to show a different date range on the invoice.
- **contactId**: Contact ID (organization member UUID). Sets the invoice recipient who will receive the invoice when it is sent via email. Set to null to clear the contact and remove the recipient assignment.

**How partial updates work:**
- If you only provide billedFrom, only that field will be updated
- If you only provide contactId, only that field will be updated
- You can provide any combination of the three fields
- Fields you omit will remain unchanged

**Invoice ID Format:**
The invoice ID follows the format: {type}::{projectId}::{dateFrom}::{dateTo}
- Example: SingleProject::0e9d033a-ab41-4212-8637-66c4e3b01fe2::2025-10-01::2025-10-31

**Date format:**
Dates can be provided in ISO 8601 format:
- Date-only: "2025-10-01" (recommended)
- ISO timestamp: "2025-10-01T00:00:00.000Z"

**Contact validation:**
When setting a contactId, the system validates that:
- The contact exists and is active
- The contact belongs to the project customer organization
- If the contact is invalid, a NotFoundException is returned

**Permission requirements:**
Requires Invoices.manage permission and access to the project to update potential invoice settings.

<Operation source="api-reference" id="potentialinvoicescontroller-patchpotentialinvoice" />