Postman collection
Payments Write Deprecated

pixiCreateInkassoBookings

Creates manual customer account bookings for open, reminded invoices handed over to debt collection (Inkasso); deprecated outside specific databases.

The call checks the name of the current database.

  • Database pixi_GCH or pixi_GCH_test: the internal procedure Pixi_CA_CreateinkassoManualBookings is executed with the three parameters. It creates manual booking events on the customer account so that the affected invoices are no longer open. No result set is returned in this case.
  • Any other database: nothing is booked. The call returns a single row with Status = Info and a message saying that the call is no longer supported.

The internal procedure works as follows:

  1. It reads the booking event ID from the setting CA_Inkasso_ManualBookingID. If the setting is empty or 0, INU is used.
  2. It only continues if a customer account event with this ID exists in CustomerAccountEvents and has OriginalAmountMultiply = -1 (negative event).
  3. It selects invoices with Total > 0 and an open amount (Total - PayedSum) > 0. The customer must be matched according to fPixi_CA_IsMatched. The customer must also have at least one open invoice that meets all of these conditions:
    • reminder level between MinimumReminderLevel and MaxReminderLevel;
    • invoice date older than MinimumAgeInDays days.
  4. For each selected invoice it writes a log entry to LogTable. It then calls Pixi_CA_InsertManualBookingEvent with the negated open amount, the text Manual booking, the user pixi* Automatic, the customer account key of the invoice and its currency.

All open invoices of a qualifying customer are booked, not only the invoices that meet the age and reminder criteria.

Notes

  • Deprecated: outside the databases pixi_GCH and pixi_GCH_test the call does nothing except return the Info row. The message text contains the typo suported.
  • No feedback: in the supported databases no result set is returned. Success can only be checked via LogTable or the customer account.
  • Not documented here: the definitions of Pixi_CA_InsertManualBookingEvent, fPixi_CA_IsMatched and fPixi_GetSetting are not attached. Their exact behaviour is therefore not documented.
  • Dynamic SQL, no transaction: bookings and log entries are built as dynamic SQL and executed without an explicit transaction. The log entries are written before the bookings, so a failing booking can leave log entries without matching bookings.
  • Dirty reads: reads use NOLOCK.
  • No duplicate protection: repeated calls can create further bookings while invoices still appear open.

Tables used

Invoices · Read Customers · Read Addresses · Read CustomerAccountEvents · Read CustomerAccount · Read LogTable · Write
SQL object:
dbo.pipiCreateInkassoBookings
Updated at 2026-10-30