The Custom Transactions feature has the following benefits:
- You can name your custom transaction types in a way that reflects your business logic.
- Like standard transactions, each custom transaction type can have its own numbering scheme, permissions, and workflow logic.
- You can create custom transaction types in multiple styles.
Multiple Custom Transaction Styles Supported
- The Custom Transactions feature supports multiple transaction formats. That is, you can create transaction types in any of the following styles:
- Basic – Lets users record credit or debit lines to specified accounts. The corresponding account to be adjusted for balancing purposes is defined on the transaction type record. This approach is similar to the expense report transaction, which always debits the same predefined account.
- Journal – Lets users record sets of debits and credits to accounts that a user manually specifies when entering the transaction. As with a standard journal entry record, the total value of credits must equal the total balance of debits.
- Header only – Relies on a GL plug-in implementation to calculate the GL impact. That is, the transaction does not include a Lines sublist for users to manually enter debits and credits to specific accounts. Rather, the plug-in implementation calculates the impact based on other data. This data can consist of values that users enter on the transaction header or of values they enter on a custom form created by using SuiteScript objects.
- Sales – Provides functionality similar to a sales transaction, including the Item sublist , taxes (SuiteTax only), and inventory impact. Sales custom transactions behave similar to invoices, cash sales, or credit memos.
- Purchase – Provides functionality similar to a purchase transaction, including the Item and Expenses sublists, inventory impact, taxes (SuiteTax only), and amortization. Purchase custom transactions behave similar to vendor bills