How List Styles Affect Your Integration

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
Journal
Header Only

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 LineList.
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 credited 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.
With this style, the lines do not use the credit or debit fields. Values entered for these fields are ignored.

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 memo body field is not available. However, you can set the memo field on any line in the LineList.
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 the lines must balance.
With this style, the lines do not use the amount field. Values entered for these fields are ignored.

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 LineList. 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.

Basic

Journal

Header Only

Related Topics