The following entities now include an updated_at field in API responses:

• Customer
• Invoice
• Payment
• Credit Memo

This field contains a timestamp of when the entity was last modified, useful for synchronization and caching scenarios.

• Breaking Change: The amending_reference field is now required when amending a contract item. Previously, amending was required. Update your integration to use amending_reference to identify the item being amended.

New capabilities for updating invoices with different scopes:

• UpdateFullInvoiceRequest - Full invoice update (existing behavior)
• UpdateRevenueRecognitionOnlyInvoiceRequest - Update invoice for revenue recognition purposes only

Use the scope discriminator field to specify which type of update you're performing:

• FULL - Updates all invoice fields
• REVENUE_RECOGNITION_ONLY - Updates only revenue recognition-related fields

Added support for explicitly terminating contract items in amendments:

• New TERMINATED_ITEM type in contract amendment requests
• Use RevenueRecognitionOnlyContractTerminatedItemRequest to specify items being terminated by their external reference

The tax_amount field is now optional when creating or updating:

• Contract items
• Invoice items
• Credit memo items

This allows you to create these entities without specifying tax amounts upfront, which is useful when tax calculation is handled separately or when creating drafts.

• Added discount_amount field to InvoiceScheduleInvoiceItem, allowing you to see discount amounts on scheduled invoice items.

• The API now supports multiple versions. Version 2 (V2) introduces new features and improvements while maintaining backward compatibility with Version 1 (V1).

• Added name filter parameter to GET /customers to search customers by name

• Contract amendments now support an effective_date parameter to specify when the amendment should take effect

• Revenue Recognition Only Contracts now support discounts on contract items