Welcome to 2020! One of the most popular questions we receive at this time of the year is for assistance with setting up application fees for the new year
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
There are some scenarios where you can't use the dues billing tools to charge for services
Dues Cycles and its child entities are used to define the rules for membership and members. A Dues Cycle is typically the amount of time for which you invoice members, (e.g. If your membership runs for one year and follows a calendar year you would set up a new Dues Cycle for each calendar year.) You will most likely set up a dues cycle only once unless you have dramatic changes in your rules for membership or billing periods
Take a look through this community thread that explains where to update your App Fees for the new year
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
Take a moment for important tips on suspending members who did not complete cycle 6 Code of Ethics training
Dues Options are designed to allow for you to give your members options when to renew their association dues. An example of this might be to allow a member to pay their dues for two years rather than for one. Each Dues Schedule must have at least one Dues Option which is marked as the default. However, you are welcome to have as many Dues Options as you would like for your members to select between when renewing through the Portal
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 - I understand the lock down on the portal pages and know you are working with us to customize a few things for our associations. 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? For example, on a Dues Option, there is a description field, but this does not display on the webpage. I looked at entities to see if there was a publish to portal feature and did not see it