This does reverse the financial entries made around deferred revenue and recognized revenue. Nimble AMS supports full membership cancellation and refunding the money back through a new, a simple interface your staff can easily follow. After you have configured entity crossover, the inter-entity, or due to/due from, transaction are automatically generated.Associations sometimes need to cancel a membership part-way through a member’s term and issue a refund without backing out recognized revenue for the previously recognized months of the membership term. Nimble AMS supports orders that involve more than one entity. The entity is also recorded automatically on order, payments, and transactions. Examples of records that require the entity to be identified include events and batches. In addition to the configuration-oriented objects, transaction-oriented records throughout Nimble AMS are tagged with the entity owner. You can charge and collect sales taxes on the merchandise products you sell to your constituent s. Your products are purchased by your constituent using orders. For example, an event session product has a start and end date, but a merchandise product does not. Your products are set up using product types which define what attributes the products have. In Nimble AMS, you use products to represent the goods or services your association offers to your constituents. Each membership offering requires a separate membership type record, which controls all membership business rules and provides different dues options for staff to sell and constituents to purchase. Membership types in Nimble AMS are the primary building blocks for your association's membership setup, and are vital for tracking membership history on a term-by-term basis for all past, present and future members. All GL accounts set up in Nimble AMS must be tied to an entity. The transactions can then be exported from Nimble AMS and imported into your general ledger with the correct GL accounts. After you set up GL accounts in Nimble AMS, and use them on products, bank accounts, and other financially-related records, the transactions generated by Nimble AMS are automatically tagged with the GL accounts. General ledger accounts, or GL accounts, are used in Nimble AMS to link back to your general ledger. The entity payment methods define the payment methods that are available for a specific entity, along with the bank account that should be associated with that entity payment method. With Nimble AMS, you create payment methods for the ways staff can pay for orders-cash, check and credit card are examples of payment methods. The entity order items you create are listed in the Staff View order process "Let's Get Started" dialog box. Entity Order Itemsīy creating entity order items, you set the order item types that each entity has available to sell. The entity crossover specifies the due-to and due-from general ledger (GL) accounts for the entities. When you set up entity crossovers, products from multiple entities can be processed in a single order, and when a payment is applied to the order, any necessary inter-entity transactions are automatically generated based on the entity crossover. Using entity crossovers, you can manage multiple financial entities within your single instance of Nimble AMS. The Default Entity is set by an administrator. In Community Hub, constituents can enter payments using the entity credit card issues for your Default Entity. The credit card issuer you set up for an entity are available in the staff view order process when your batch is set for that same entity. Entity Credit Card Issuersīy creating entity credit card issuers, you set the entity credit care issuer that each entity has available for credit card payments, as well as setting the bank account that is used for recording the payments. The bank accounts you create are used to set up payment methods and credit card issuers for your entities. When setting up bank accounts in Nimble AMS, at least one bank account should be created for each entity. Using Bank Accounts, you can track cash, checks, and other types of payments. Then, on each order with a balance, the Invoice AR Aging is automatically populated and maintained by Nimble AMS. AR Aging s are first defined on each entity by an Administrator. With Nimble AMS, you can manage and reconcile your accounts receivable (AR) using AR aging categories. Below are the entity-related information that you set up using related objects. Entity Information on Related ObjectsĪdditional configuration information about an entity is stored in related objects. This information is used throughout Nimble AMS and can be used in your analytics. Accounting settings such as bill me enablement, batch export configuration, and invoice terms
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |