Skip to main content
A credit card collection voucher records money collected from one or more customers by credit card. It has the exact same shape as an incoming bank transfer (each line carries the amount collected from a customer and produces a customer movement); the difference is that it also carries a POS charge date and an optional repayment plan.

​
Required fields

  • VoucherNumber: unique in the company across all bank voucher types, at most 20 characters. Send "Next" to generate it from the same "BANKAFİŞNO" series used by bank transfers. Cannot be "Next" on update.
  • Date: voucher date. If a time is sent it is stored as the voucher time, otherwise the current time is used.
  • BankAccountCode: one of the company’s bank accounts. Every line of the voucher is recorded against this account.
  • Lines: at least one line.
Description and SharingCode are optional; an empty SharingCode makes the voucher visible to everyone, otherwise it must be one of the user’s sharing codes.

​
Lines

In addition to the same line fields as a bank transfer (CustomerCode, Amount, ExchangeRate, Description, and CustomerAmount/CustomerCurrencyCode/CustomerExchangeRate for the customer movement override):
  • PosChargeDate: required, the date the card was charged.
  • RepaymentPlanName: optional, one of the bank account’s own repayment plans.

​
Value date (Valor)

When RepaymentPlanName is sent, the line’s Valor field in the response is calculated by the API: the voucher’s Date plus the selected plan’s DayCount. When no plan is sent, Valor stays empty.

​
Line identity on update

Same rule as bank transfers: since a line’s customer movement is referenced by the closed-record and payment-plan tables, lines are matched by their position on update and updated in place.

​
Posted and settled voucher

  • When IsPosted is true (the voucher has been linked to an accounting entry) it cannot be updated or deleted (8708).
  • When IsRepaid is true (the voucher has been settled by a bank repayment voucher) it cannot be updated or deleted (8709).
Also, when a line’s customer, amount, currency or rate changes and that line’s customer movement has already been closed by a collection/payment or has a payment plan, the request is rejected (8809/8810), exactly as with bank transfers.