Sell nimble san code#
Product Code -depending upon the Type, this field displays the name of product, bank account name (or credit card issuer, if applicable) or order type.Payment Line -the payment line that generated the transaction.Order Type -possible values are: New or Adjustment.Order Item Line -the order item line that generated the transaction.Order Item -the order item that generated the transaction.Order -the order that generated the transaction.If the Type is Liability, the GL account that is the prepayment payable GL account is used. If the Type is Payment, the prepayment payable GL account is used. If Type is Payment, the GL account of the payment's bank account is used. If Type is Income, the GL account of the order item line's product will be used. If Type is AR, the order type's AR account is used. GL Account -the GL account that is used for the GL export.Date -the date from the transaction's batch.Category -possible values are: Debit or Credit.Batch -the account that the transaction is part of.If for an event registration, this will be the attendee. Customer -the account that is the "ship to" for the transaction.Bill To -the account with the primary financial responsibility for the transaction.These are key fields on transactions that may be useful for your analytics. Deferred revenue is recognized during a nightly scheduled job.Recurring memberships on the date that they automatically renew (assuming they are not complimentary) and, if auto pay is in use, on the date when they are paid.A prepayment or a refund of a prepayment is entered.A payment or a refund is processed on an existing order.
Sell nimble san full#
In Nimble AMS, transaction records follow generally accepted accounting principles of two–sided entries of debits and credits.
The transaction records hold the accounting details, such as the Batch, Bill To, Product Code, GL Account, Amount, Date, and more, and they are the source of the exports to your general ledger (GL) system. Common actions such as cancelling or modifying orders create the necessary reversing transactions automatically. T o further safeguard your financial audit trail, transactions cannot be edited or deleted by staff or constituent actions. In every case, the creation of the transactions is done automatically by Nimble AMS staff and constituents do not create them directly.
Sell nimble san manual#
The transactions can result from the manual actions entered by staff in Staff View or by constituents in Community Hub-such as submitting an order, or through automated and scheduled processes-such as the recognition of membership deferred revenue. Any place in Nimble AMS where there is an accounting impact, you will find transaction records.
0 kommentar(er)
