How List Styles Affect Your Import
A custom transaction type can have any of three list styles. The list style dictates which fields are available when you add or update a custom transaction. For more details, see the following sections:
Basic
When working with an instance of the basic transaction type, be aware of the following:
-
Each transaction must have at least one line in the Lines sublist.
-
Each line must include a value for the Account field and a value for the Amount field. The Account field identifies the account that is to be debited or credited by this transaction. (Whether the account is debited or credit depends on how the transaction type is configured. For details, see Account Field Setup for Custom Transaction Types.) The Amount field identifies the exact value of the credit or debit.
For more information about the Basic list style, see Basic.
Journal
When working with an instance of the journal style transaction type, be aware of the following:
-
The transaction body does not include a Memo field. However, you can set the Memo field for any line in the Lines sublist.
-
Each transaction instance must have at least two lines in the LineList. More lines are permitted, but at least one line must set a value for the Credit field and one must set a value for the Debit field. The values of all lines must balance.
For more information about the Journal list style, see Journal.
Header Only
With the Header Only style, it is not possible to interact with the Lines sublist. The only lines associated with these transactions are the lines generated by a custom GL Lines plug-in implementation. For more details, see Header Only.