Products are used to store data on any good or service sold. For example, Products are used for Dues but there is nothing physical which is actually sold. Products may represent a physical tangible object or something more abstract such as the benefits of membership with your organization. All Products are linked to a Price List Item that stores the cost of the Product
Dues Products act as a link between Dues Options and Products in the Product Catalog. There may be multiple Dues Products for any given Dues Option so that you may easily divide the funds which your association receives according to the amounts of the various Dues Products
Price list items act as a connection between a Price List (the pricing category for a contact) and the product. Price list items are what you create in RAMCO to determine what someone on a given price list will pay for a product. Most organizations will have two Price Lists, which also means that ever product in such an organization will have two price list items: one for each price list
Dues Proration records are used to define the proration schedule for the selected product for new members. The system will automatically generate the Dues Proration records for a Dues Product with a Daily, Weekly, Monthly, or Quarterly pricing strategy. Dues Proration records must be manually created for a Dues Product with a tabular or custom pricing strategy. Dues Proration records should never be created for a Dues Product with pricing strategy of None
On a Dues Item, the status of "Renewal Opt-Out" indicates the member does not plan to renew that year's dues and, once selected and saved, will deactivate the Dues Item and the related Order
Orders in RAMCO AMS are those items for which you would like to receive payment, but your member may not have yet agreed to the charges. Typical examples of Orders are Dues- your association wishes for each of its Members to renew, but it is not required
2 Comments - Is it possible to see a flowchart for the life cycle of an order?
Portal Pages vary from regular website pages in that you cannot add or edit the layout and text of most portions of them. Portal pages have code behind them, so that information may be displayed from your RAMCO AMS and sent back to your RAMCO AMS – for this reason you cannot have free design control over them. You can think of portal pages as pages which “talk” to your database. Your Portal will be “skinned” to match the template used by your CMS. The idea behind this is that your members/portal users will be able to move seamlessly from a website page to a portal page without being aware of the difference
4 Comments - Hi Renee, the Dues option description should display on the portal...But I just wanted to check to see if there is a process to add existing fields from the db to the display on a webpage?
This release fixes a number of issues and also introduces the dues import module for state associations processing dues received from local associations
Now that we've added in the final setup pieces for payment plans and early-bird dues, we've recorded a new set of tutorials on dues creation
Invoices are created once a customer agrees to pay the fees or buy a specific product or service. This entity does create batch items and GL Account entries because it indicates an agreement between the customer and your company that the amount indicated on the Invoice will be paid by the customer