Create BankTransfer record
Create a new BankTransfer record with the provided data. Validates all required fields and business rules.
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.
Additional validations
- 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. - A reference that the record or its linked source record already holds passes these checks.
Authorizations
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.
255Query Parameters
When false, store submitted line classifications, including an empty list. When omitted, organization defaults apply to new lines with omitted or empty classifications only when the organization setting is enabled.
Body
Input schema for creating BankTransfer records.
x > 0sending, receiving x > 0x > 01 - 128draft, posted, archived Response
OK
Posting date (GL date) - the date when the transaction is recorded in the general ledger
Transaction date (inception date) - the date when the transaction actually occurred
Transfer amount
^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,2}0*$^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,16}0*$^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,2}0*$^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,2}0*$^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,16}0*$^(?!^[-+.]*$)[+-]?0*\d*\.?\d{0,16}0*$draft, posted, archived Date and time the record was created
Date and time the record was last updated
Schema for audit actor information.
Schema for audit actor information.
sending, receiving