| Name |
Type |
Description |
Notes |
| account_id |
str |
|
[optional] |
| var_date |
date |
The transaction date in ISO format (e.g. 2016-12-01). Future dates (scheduled transactions) are not permitted. Split transaction dates cannot be changed and if a different date is supplied it will be ignored. |
[optional] |
| amount |
int |
The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored. |
[optional] |
| payee_id |
str |
The payee for the transaction. To create a transfer between two accounts, use the account transfer payee pointing to the target account. Account transfer payees are specified as `transfer_payee_id` on the account resource. |
[optional] |
| payee_name |
str |
The payee name. If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee. |
[optional] |
| category_id |
str |
The category for the transaction. To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object. If an existing transaction is a split, the `category_id` cannot be changed. Credit Card Payment categories are not permitted and will be ignored if supplied. |
[optional] |
| memo |
str |
|
[optional] |
| cleared |
TransactionClearedStatus |
|
[optional] |
| approved |
bool |
Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default. |
[optional] |
| flag_color |
TransactionFlagColor |
|
[optional] |
| subtransactions |
List[SaveSubTransaction] |
An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. |
[optional] |
| import_id |
str |
If specified, a new transaction will be assigned this `import_id` and considered "imported". We will also attempt to match this imported transaction to an existing "user-entered" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a "user-entered" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API). |
[optional] |
from ynab.models.new_transaction import NewTransaction
# TODO update the JSON string below
json = "{}"
# create an instance of NewTransaction from a JSON string
new_transaction_instance = NewTransaction.from_json(json)
# print the JSON string representation of the object
print(NewTransaction.to_json())
# convert the object into a dict
new_transaction_dict = new_transaction_instance.to_dict()
# create an instance of NewTransaction from a dict
new_transaction_from_dict = NewTransaction.from_dict(new_transaction_dict)[Back to Model list] [Back to API list] [Back to README]