| Name | Type | Description | Notes |
|---|---|---|---|
| account_id | str | ||
| date | date | ||
| amount | float | The transaction amount in milliunits format | |
| payee_id | str | The payee for the transaction. Transfer payees are not permitted and will be ignored if supplied. | [optional] |
| payee_name | str | The payee name. If a payee_name value is provided and payee_id is not included or has a null value, payee_name will be used to create or use an existing payee. | [optional] |
| category_id | str | The category for the transaction. Split and Credit Card Payment categories are not permitted and will be ignored if supplied. | [optional] |
| memo | str | [optional] | |
| cleared | str | The cleared status of the transaction | [optional] |
| approved | bool | Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default. | [optional] |
| flag_color | str | The transaction flag | [optional] |
| import_id | str | If specified for a new transaction, the transaction will be treated as Imported and assigned this import_id. If another transaction on the same account with this same import_id is later attempted to be created, it will be skipped to prevent duplication. Transactions imported through File Based Import or Direct Import and 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. If import_id is specified as null, the transaction will be treated as a user entered transaction. | [optional] |