Update VendorPaymentV2 record (partial)
Partially update an existing VendorPaymentV2 record. Send only the fields you want to change. Anything you don’t send stays as it is. Updates are subject to the same constraints as the full update endpoint: period locks, payment-applied restrictions, and approval-workflow rules apply.
Side effects
- If an approval workflow matches this request, DualEntry can set
record_statusback todraft. - If this record already has an active bank match, and an approval workflow holds the record, DualEntry returns those matches to
draft. - If the customer or vendor is intercompany, DualEntry also writes a transaction in the elimination company.
- If the record has a bank account and a payment method that prints checks, DualEntry creates a
not_printedpaper check, even if the record isdraft. - If a printed or not-printed paper check already exists, DualEntry skips paper-check creation.
- If you clear
payment_method_id, or set it to a payment method that does not print checks, DualEntry sets the associated unprinted paper check toarchived.
Additional validations
- Fails with
422if the request changescheck_numberwhile a paper check isnot_printed. - Fails with
503if the exchange rate for the transaction date is unavailable. - Fails with
422if the bank currency differs from the transaction currency andbank_or_credit_card_amountis missing, or is0while the applied amount is not0. - Fails with
422and the error codeposting_date_after_limitifdateis after the latest posting date that your organization allows. - Fails with
422if you set an inactive, archived, or draft customer or vendor, or an inactive company. - Fails with
422if a line account is not available to the record’s company. - Fails with
422if you set the customer or vendor that stands for the record’s own company as a party. - A reference that the record or its linked source record already holds passes these checks.
Headers
Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.
255Body
Partial update for PATCH /public/vendor-payments/{number}/.
Send only the fields you want to change. Unset fields stay as they are. The save uses the same rules as a full update. Period locks, applied-payment checks, and approval workflow rules apply. A sent attachments list replaces the existing files. Omit attachments to keep them. A sent items list replaces the application lines. Omit items to keep them.
AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BYN, BZD, CAD, CDF, CHF, CLF, CLP, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HTG, HUF, IDR, ILS, INR, IQD, IRR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KPW, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SHP, SLL, SOS, SRD, STN, SVC, SYP, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VES, VND, VUV, WST, XAF, XAG, XAU, XCD, XDR, XOF, XPD, XPF, XPT, YER, ZAR, ZMW, ZWL If you omit this field, DualEntry keeps the stored rate. If you omit this field and you change transaction_date or currency_iso_4217_code, DualEntry calculates a new rate. This also applies when you change company_id to a company with a different base currency. A change to date also changes the transaction date when your organization does not keep the two dates independent. DualEntry stores a rate that you send, including 1.0, and calculates a new rate when you send null.
If you omit this field and you do not change the bank account, DualEntry keeps the stored amount. If you send null, DualEntry calculates the amount again, as for a change of the bank account. If you change the bank account and you omit this field, DualEntry uses the payment amount when the currencies match. If the bank currency differs from the transaction currency, send this field. Send 0 only when the applied amount is 0.
x >= 0Response
OK
AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BYN, BZD, CAD, CDF, CHF, CLF, CLP, CNY, COP, CRC, CUP, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HTG, HUF, IDR, ILS, INR, IQD, IRR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KPW, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SHP, SLL, SOS, SRD, STN, SVC, SYP, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VES, VND, VUV, WST, XAF, XAG, XAU, XCD, XDR, XOF, XPD, XPF, XPT, YER, ZAR, ZMW, ZWL