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.BankAccountName: 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.ValueDate: optional, the line’s value date (valör).
Value date
The line’s value date (ValueDate) is a field you send; the API does not calculate it and stores it as sent. The Noyax application calculates it as the voucher’s Date plus the selected repayment plan’s DayCount; if you want the same result, calculate and send it yourself. It stays empty when not sent.
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
IsPostedistrue(the voucher has been linked to an accounting entry) it cannot be updated or deleted (8708). - When
IsRepaidistrue(the voucher has been settled by a bank repayment voucher) it cannot be updated or deleted (8709).
8809/8810), exactly as with bank transfers.