Hi, Our company has Use In-Transit Vendor Payments by Default turned on. We create vendor bill payments via the SuiteTalk REST Record API (

POST

to

.../record/v1/vendorPayment

) and want non–in-transit payments in some cases, without having to run

@confirm

(or similar) immediately after every create. We send a body that includes the in-transit flag set to false (and we’ve also tried the camelCase name from the REST schema,

isInTransitPayment

, in case the API ignores unknown keys). Example:

{
  "entity": {
    "id": "1659"
  },
  "account": {
    "id": "192"
  },
  "subsidiary": {
    "id": "6"
  },
  "currency": {
    "id": "4"
  },
  "tranDate": "2026-04-03",
  "memo": "Manual none in-transit payment 4",
  "isInTransitPayment": false,
  "apply": {
    "items": [
      {
        "doc": {
          "id": "28339"
        },
        "amount": 1
      }
    ]
  }
}

After create, the payment still shows as In transit in the UI, as if the preference always wins. Has anyone successfully overridden “Use In-Transit Vendor Payments by Default” on create via REST, and if so what did your payload (and headers) look like? Any gotchas (custom form, required fields order,

replace

query param, etc.)?