--- created: 2023-08-01T00:00 updated: 2024-04-25T14:12 author: ibelsa API team title: Breaking Change September 26, 2023 --- # Breaking Change September 26, 2023 ## Change at two endpoints 1) POST /api/set/roomreservation/splitinvoice [Split Invoice of Roomreservation](/api/doc#post--api-set-roomreservation-splitinvoice) 2) POST /api/set/roomreservation/paidpartial [Pay parts of Roomreservation](/api/doc#post--api-set-roomreservation-paidpartial) Both endpoints provide the ability to remove invoice items from an invoice and transfer them to a new invoice, then close that invoice. These two endpoints are necessary if only **parts of an invoice** are to be paid.\ Unfortunately, there are always cases where all invoice items have been transferred to a new invoice.\ Strictly speaking, this makes no sense. This approach has been tolerated so far. Following the changes in our invoice management, we must now prevent this. This means that at least one invoice item must remain on the original invoice. Otherwise the spit will be rejected. This procedure was tolerated until now. After the changes in our invoice management, we must now prevent this. We plan to put this restriction online on **September 26, 2023**. If you are affected by this restriction, we recommend the following endpoints to close an invoice: 1) GET /api/set/roomreservation/paid/{entity_id}/{template_id}/{payment_method_id}/{send_invoice}/{amount} [Set Roomreservation paid](/api/doc#get--api-set-roomreservation-paid-{entity_id}-{template_id}-{payment_method_id}-{send_invoice}-{amount}) 2) GET /api/set/invoice/paid/{entity_id}/{template_id}/{payment_method_id}/{send_invoice} [Set Invoice paid](/api/doc#get--api-set-invoice-paid-{entity_id}-{template_id}-{payment_method_id}-{send_invoice}) If you have any questions or need assistance, please write to us: api@ibelsa.com

Author: Created: Updated:

This page was generated from a Markdown file.

Would you like to view the content in your favourite Markdown reader? Raw Markdown