BankMatchingTransactions
Retrieves the list of transactions which includes invoices/bills/credit-notes.
Table Specific Information
Select
The driver uses the Zoho Books API to process WHERE clause conditions built with the following columns and operators:
- TransactionId supports the '=' comparison.
- TransactionType supports the '=' comparison.
- ReferenceNumber supports the '=' comparison.
- Date supports the '=,<,>' comparisons.
- Contact supports the '=' comparison.
- ShowAllTransactions. supports the '=' comparison.
You can also provide criteria to search for matching uncategorized transactions.
The rest of the filter is executed client-side in the driver.
For example:
SELECT * FROM BankMatchingTransactions WHERE TransactionId = '1894578000000087001
Columns
| Name | Type | References | SupportedOperators | Description |
| TransactionId [KEY] | String |
BankTransactions.TransactionId | Id of the Transaction. | |
| TransactionNumber | String | Numnber of transaction. | ||
| TransactionType | String | Transaction Type of the transaction. | ||
| Amount | Integer | Amount of the bank matching transactions. | ||
| ContactName | String | Display Name of the contact. Max-length [200]. | ||
| Date | Date | =,<,> | Date when transaction was made. | |
| DebitOrCredit | String | Indicates if transaction is Credit or Debit. | ||
| IsBestMatch | Boolean | Check if the transaction is a best match. | ||
| IsPaidViaPrintCheck | Boolean | Check if it is paid via print check. | ||
| ReferenceNumber | String | Reference Number of the transaction. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| Contact | String | Contact person name, involved in the transaction. | |
| ShowAllTransactions | Boolean | Check if all transactions must be shown. |