Buying or renewing a membership package creates or updates your membership record. This article explains what changes automatically, why some details wait for payment, and when welcome or confirmation emails are sent.
Joining or Renewing
When a membership package order is fulfilled, Rhythm creates a membership for a buyer who does not have one, or renews the buyer’s existing membership. A person or organization can hold only one membership, so a second package line on the same order for the same owner renews the membership created by the first line instead of creating another one. In a group order, each line can name a different owner, so one order can buy separate memberships for other people.
If the application behind the purchase needs staff approval, Rhythm does not create the membership yet. See How Membership Applications Are Held for Approval for what happens while it waits. If the package’s payment rule has not been met, Rhythm creates the membership record, but the membership stays inactive until the payment catches up.
When you submit a new application, Rhythm treats it as a rejoin if you already have a member record or any prior membership, including one that lapsed or was terminated long ago.
If you are processing a membership already held by an organization’s people, renew the organization instead of running a join. A join does not include the renewal behavior those existing members need, so using it can leave them without the access they expect.
A join or renewal usually creates an application record in the Console along with the order and payment. If something interrupts that step, no application record is created, and the membership can stay stuck even when the order, invoice, and payment all look complete. If a completed order does not update the membership and you cannot find a matching application, contact support.
Warning
Do not bundle a specific membership package directly onto an event registration to sell membership. That path is not supported, and the purchased membership will not become active on the buyer’s record. To sell a membership with an event registration, use an embedded membership component on the registration form. A membership bought that way is written to the buyer’s record like any other membership purchase.
A staff-created order in the online store, or a storefront order used because the usual renewal path was unavailable, still creates or renews the membership after it is paid. However, it can produce a different result than the standard membership process. For example, buying through the online store without an application can advance the membership by only one term, even when you expected something else. If the result looks off, compare the order with what the standard join or renewal process would have produced.
If a former member’s membership expired but was never dropped or terminated, they can still use the ordinary renewal process. Completing it extends the expiration date by one more term from where it left off, rather than placing them into the current term the way a fresh join would. To bring someone back as a current-term join instead of an extended renewal, terminate or drop the old membership first so they can go through the join process.
Rhythm does not use imported financial transactions to decide whether someone should be offered the renewal path. Only the actual membership record, including its dates and status, controls that.
For an institutional or organizational membership, process the renewal through the membership application or order workflow instead of creating an invoice directly in the finance area. A finance invoice alone does not advance the membership record. Also confirm that the organization’s own contact information is filled in on the membership record. A renewal for an organization with missing required contact details may not update as expected, even after payment.
When staff enter a payment on someone else’s behalf, such as a parent or employer paying for a member, enter the payer’s name and billing address on the payment. Keep the member’s own details under the person joining or renewing. Mixing the two can leave the wrong name on the transaction.
Where you enter the payment also affects whether the membership updates and activates. A payment made in the Portal is expected to move the membership into its current term and active status. If you record payment directly in the finance console instead, check afterward that the membership’s expiration date and status changed. Entering a payment there settles the invoice, but it is separate from the membership renewal or reactivation, and one does not automatically guarantee the other.
If you update a contact’s organization during the membership process, Rhythm reflects that change on the resulting order and invoice, as well as on the contact record.
Tip
The membership record’s Is New indicator turns on the first time a contact or organization completes a membership process. Rhythm removes it automatically the first time that member completes a renewal, so you do not need to bulk-update this field before opening a renewal cycle.
A membership can still show as new after a long time for two common reasons: no renewal application has ever been processed for it, or the membership is partway through a multi-year deferral term and stays flagged as new until its first renewal.
Warning
If a built-in contact field, such as date of birth, is optional on a renewal application form, it can still show a validation error as though it were required. This has been reported specifically on renewal forms. The same field working as optional on a join form does not guarantee the same result on a renewal form for the same process.
When the New Details and Dates Take Effect
Some packages update your membership dates and details as soon as the order is fulfilled. Others wait until you have paid the percentage or amount the package requires. Until that payment rule is met, Rhythm does not calculate your term dates or apply your type, package, chapters, sections, and add-ons. Once the rule is met, all of those details update together.
Tip
Two separate package settings control this timing, and they can be set differently from each other. One decides when your membership dates move forward, and the other decides when your membership information — type, package, chapters, sections, and add-ons — updates. A package can update dates immediately while holding other details until the invoice is paid in full, or the reverse. If a package is edited so its information rule differs from its dates rule, treat the two rules separately when you check why a field did or did not change yet.
For a join, Rhythm discards any existing expiration date and starts a fresh term. For a renewal, upgrade, or reinstatement, Rhythm extends your existing expiration date instead of replacing it. The extension follows the term of the package you bought. For example, a two-year membership purchase moves the expiration date ahead by two years instead of resetting it to a one-year renewal. In general, a renewal is expected to add one configured term from the renewal date, not more. If you do not want a renewal to advance the expiration date again, such as when you are correcting a record rather than extending it, process that renewal using a different package whose expiration setting is Never, so the term does not move forward.
If your membership had lapsed and has a termination date, and your account has a reinstatement period configured, buying again within that period brings the membership back as a reinstatement instead of a plain renewal. Rhythm records a reinstatement date and clears the termination date. The reinstatement period matters only to a reinstatement. A fresh join, or a renewal on a membership that is still terminated, does not use one. Whether or not a reinstatement period applied, any purchase that reaches a terminated membership clears its termination date and records the reinstatement date. Check this first if renewal dates look wrong: a lapsed member still inside a reinstatement window follows the reinstatement path instead of an ordinary renewal. On a reinstatement, the reinstated order also becomes the membership’s Last Order, and Rhythm calculates the new expiration date from that order, not from the order the membership pointed to before.
For an anniversary package, your reinstatement date and expiration date can differ even though both changed from the same purchase. If you are still inside your grace period when you pay an outstanding invoice, Rhythm sets the reinstatement date to the invoice payment date. The expiration date follows the package’s own term and month-cutover settings, so it does not have to match that payment date.
Your join date is set only once and is not automatically replaced by a later purchase. It changes only if an application explicitly overrides it, or on your very first payment. If a membership has no join date yet, the next transaction that applies dates sets the join date from that transaction. This can happen because the join date was removed, or because a record created by data import is completing its first membership application as a renewal. In that situation, your join date can match your renewal date or reinstatement date because there was no earlier join date to preserve, not because a later purchase overwrote a valid one.
Tip
Right after a new membership is created, the Join Date may briefly show a relative time like several hours ago instead of “just now.” The join date has no stored time of day, and Rhythm’s display starts showing a relative time only after at least a full day has passed. A same-day relative time like this is expected and does not mean something is wrong.
Tip
If a package is marked to not provide member benefits, a membership bought under it becomes active without benefits instead of plain active. This status is not treated as a current membership for renewal pricing. It also does not count as active for section participation. Only a plain Active membership can join a section or appear as an active member in that section’s own context.
Editing or deleting a membership type or package does not change memberships already sold under it. Existing membership records keep showing their prior type until they go through their own join or renewal cycle, so reports or dashboards built from those records can continue to reflect the prior type after you make the change.
If a package you use for renewals is retired and no longer offered, decide how members due to renew under it should be handled. Rhythm does not automatically move them to a replacement package unless the retired package’s own Renew this Package with setting points them to one. If you are retiring a membership offering entirely, set the package inactive, set its membership type inactive, set the related application process inactive, and update or remove that Renew this Package with setting so renewals route to a different package instead of continuing to offer the retired one.
Tip
Renew this Package with lets you point an existing package to a different package for renewal, so renewing members can transition into a newly created membership type without custom development; test the transition in your sandbox first. Rhythm applies this routing automatically, including when staff renew manually in Console, not only during self-service renewal. Because the target package is chosen for you, the renewal screen does not show a package selector when the member has only one eligible package or the package is assigned automatically. In that case, the renewal flow shows the membership type instead, and a selector appears only when the member must choose among more than one eligible package.
A membership discounted to a $0 total by a 100% coupon is still a successful renewal. Rhythm fulfills it and advances the membership term the same way it would for any other paid renewal.
Warning
If your account’s membership settings turn off add-ons, but the membership already has add-ons from before that change, a renewal on that membership can fail. If a renewal errors out and the affected member has add-ons on their record, check whether add-ons are still enabled in your account’s membership settings.
For a package that updates dates based on a percentage or amount paid, watch how that rule works with a Sell for Next Year After cutoff on calendar-year packages. An early renewal processed before that cutoff date can leave the membership in the current term, even when the package is configured to update dates right away. The cutoff decides which year a purchase counts toward independently of the dates rule. If you want an early renewal to land in the next year, process it after the cutoff date or adjust the package configuration.
The same kind of cutoff decides where a brand-new join lands. Set your Sell for Next Year After date earlier than the dates new members will actually join if you want those joins to receive the next calendar year’s expiration instead of the current year’s.
The same setting also controls the crossover point for renewals. If you want everyone who renews during your renewal window to receive next year's expiration, set Sell for Next Year After to the start of that window; memberships purchased on or after that date then expire at the end of the following membership year.
For an anniversary package, watch how the term length works with Sell for next month after. A 12-month anniversary package that cuts over at the end of the month can treat a January join or rejoin as starting in February, then extend 12 months from that shifted month. The resulting term and deferred revenue can appear to span 13 calendar months, even though the package is configured for 12. A 12-month anniversary term can also land on the day before the same calendar date the following year, rather than on that exact date, which is expected for a 12-month period rather than a fixed day count. Because the exact cutover day can shift the outcome by a full extra month in edge cases, such as a purchase made on the last day of a month, use your package’s Test/Reference Date and Calculate Expiration Date tools to confirm the expiration date before relying on it for an unusual purchase date.
A bundled purchase, such as a membership sold with an event registration, still follows the membership package’s own expiration configuration. For a calendar-year package, the resulting expiration can advance more than a single year when the package’s Sell for Next Year After and number-of-years settings call for it. The bundle itself does not use a separate expiration calculation.
Tip
The membership expiration date also drives deferred revenue timing, spread over the term the package defines starting with the purchase month. Avoid setting an expiration date unreasonably far in the future by hand. An excessive deferral period built from that date can disrupt financial batch processing.
Whether a billing run can generate deferral entries for the upcoming term also depends on the package's dates-update-timing setting. If a package updates dates immediately, its renewal invoices can produce deferral entries for the renewal term. If it waits until the invoice is paid in full, those future-term deferrals are not available at batch-post time for real invoices.
Warning
If you manually correct a membership’s expiration date, remember that the package’s own renewal rule still applies to whatever date the membership shows next. A later renewal advances from your manually corrected date, not from the date you overwrote, so the next automatic advancement follows your correction.
A membership record linked to an order can keep filling certain fields from that order on the edit screen until the link is removed. If you need to correct one of those fields by hand and your changes keep reverting, check whether the membership is still linked to an order. Remove the link before correcting the field.
The renewal date recorded on a membership generally reflects when the renewal was processed and fulfilled, not necessarily when payment was received. Rhythm sets it at fulfillment, even for a purchase still waiting on a payment rule for its other details. Order date, membership application date, renewal date, and Last Join or Renewal Date are lifecycle dates, not payment dates. If you need the actual date money was received, use your finance payment records instead of these membership dates. Rhythm does not currently offer a dedicated membership payment-date field for this purpose.
Tip
The Renewal Date field on a membership updates when a member renews. It is separate from the expiration date and the Last Join or Renewal Date, so compare the specific field you need instead of assuming one stands in for another.
Because a renewal extends your existing expiration date rather than resetting a term start date, a report or query filtered on term start date can miss a valid renewal whose start date did not change. If you are building a query to find renewals, filter on the expiration date or renewal activity rather than only on term start date.
An invoice template’s Term Start Date merge field shows the start date of the most recently purchased membership type. That is not the same as an upcoming renewal term or an expiration-based period, so keep the difference in mind if a printed invoice’s term dates look different than expected on a renewal.
Fulfillment is the step that applies these updates together. Once the applicable payment rule is met, fulfillment updates the expiration date and related statuses and dates, including the membership’s term, Last Order, renewal-related dates, and linked application and order details. A package configured to update dates only after its invoice is paid in full still depends on that later fulfillment step completing successfully. Full payment alone does not guarantee the change if fulfillment does not also complete.
A membership’s other status and date indicators, along with related dashboard figures, can take a short time to catch up after a qualifying payment. Rhythm updates some of these values in the background, so give it a little time before deciding the update failed.
Tip
A record you just finished processing can still be updated by background processing for a short time afterward. If the membership page prompts you to reload right after you process an order, or shows an error that the record changed when you try to edit it immediately, wait briefly and try again.
A completed membership renewal or reinstatement order is expected to be fully processed only after its payment was actually and successfully applied. An order marked complete with an invoice that never received a payment is not the expected outcome for a normal renewal.
If a paid order is stuck in Open or Awaiting Payment instead of Completed, its membership will not receive the new dates and details until the order is fulfilled. Have staff confirm the order’s status and fulfill it if payment has already gone through.
Rejoining a membership that was set up as a bundled purchase, such as a membership tied to a course or product, still renews the existing membership from its prior expiration date instead of resetting it. If you need that kind of purchase to count as a fresh, current-year join, terminate or drop the existing membership first so the person can go through the Join process.
A rejoin does not have its own reinstatement-style window the way a true reinstatement does. Set up rejoin using a join-type process with eligibility based on the membership’s inactive status, and configure its Sell for next year after and similar term settings to match your join package rather than your reinstatement settings.
Warning
If you need to move a lapsed member into a package that is available only to Active members, change the membership’s status to Active first. Then change the membership type or package. If you change the type or package before the status is eligible, the renewal order may not find the package you want.
A renewal rule built with broad matching, such as “any condition is true,” can match more members than you intend and reassign a renewing member to a different package, sometimes at a different price. If a renewal lands in an unexpected package, review the renewal rule’s criteria for overly broad matching before assuming it is a defect. Also check advanced eligibility rules when a renewal should land in a specific target package or add-on combination. The renewing contact’s field values must satisfy those rules. If they do not, update the contact record or the target package’s criteria so they match.
Required custom fields on a membership can block you from saving a correction. If you cannot save a membership after trying to fix a renewal issue, check whether a required custom field on that membership still needs a value.
Merging duplicate contact records does not change which membership record’s details survive. The record kept as the master keeps its own membership summary. From the record being merged away, only associated orders and invoices carry over, even if that record had a more recent membership purchase.
Tip
When you import or update memberships from a spreadsheet, include the membership package in the file. Leaving it out can keep the update from applying correctly.
Tip
If a membership shows a join date or Last Join or Renewal Date with no matching order, application, or audit history, the date likely came from a data import rather than a later edit. Standard order and membership history will not explain a date that originated that way.
Chapters, Sections, and Add-Ons
When an application is part of the purchase, Rhythm replaces your membership’s chapters and sections to match exactly what the application listed once the details are ready to apply.
Warning
If an application lists no chapters, Rhythm removes every chapter your membership previously held. Make sure an application you expect to keep your existing chapters actually lists them. This includes a renewal processed through the universal shopping cart: if you do not select a chapter at checkout there, none carries over to the renewed membership.
When Rhythm removes a chapter or section this way during a renewal, it moves into the membership’s chapter or section history instead of staying active on the record.
Rhythm adds add-ons from the application to your membership the same way. The exception is a change of affiliation, where Rhythm adds the application’s add-on quantities to what you already had instead of replacing them. Depending on your account’s configuration, a renewal’s next screen can also add an add-on as a line item automatically, even if you did not explicitly choose it. You can remove that line before submitting the order if you do not want it.
Warning
An add-on restricted to a specific membership package can stay attached to your record when you switch to a different package during a renewal. Rhythm can then refuse the next step because the new package does not allow that add-on. If a renewal errors out after you change the membership type, remove the incompatible add-on from the prior configuration first, then choose the new type. The same restriction can also block a group or bulk renewal until the incompatible add-on is removed from the affected records.
Making an add-on inactive, or hiding it from the Portal, does not necessarily remove it from memberships that already have it. It can still appear on that member’s renewal order. It stops appearing on renewal orders, including for other members who previously selected it, only after you also turn off that add-on’s own dues setting. Removing an add-on from Setup this way does not remove it from application or renewal forms that still include it as a form component. Update the form separately if you need to stop buyers from seeing or purchasing it there.
For a group membership renewal, members who were already assigned to the group and already had their own chapter affiliation keep that affiliation. A person treated as newly assigned to the group during the same renewal, including someone originally added by data import who is going through group renewal for the first time, inherits the organization’s own chapter affiliation. If the organization has no chapter affiliation, that can remove a chapter the person previously held.
Renewing an organization-based membership through an event registration path can keep the member’s existing chapter without charging the related chapter dues. If a renewal total from that path looks low on chapter dues, check whether it went through event registration instead of the standard renewal flow.
Warning
Renewing an organization-based membership online can sometimes create duplicate chapter dues line items when an assigned member contact is selected or receives flowdown from the organization. This has been observed specifically in manual renewal applications processed through the Portal or Console checkout, not in billing-run renewals. If an organization’s renewal total looks inflated with extra section, chapter, or add-on charges, check whether the assigned member contacts also carry their own dues-bearing memberships that could explain the extra lines before assuming it is a defect.
A staff-created renewal in the Console renews based on the member’s currently active chapters already on the record, including when the member has more than one. Staff can also add a chapter this way without charging the member a fee for it.
Buying a membership package in the online store without an application works differently. Rhythm drops any dues-bearing chapter your membership already held without changing the rest of your record.
After your membership is activated, Rhythm copies the application’s other choices, including custom field answers, onto the membership. If the application names no referrer, Rhythm clears your membership’s referrer to match. If it lists no seat holders, your existing seat assignments stay as they are. Any email address that comes through this same application or renewal process also overwrites the membership record’s stored email. Because of that, the membership can show a different email than the contact’s CRM record if the email was updated only on the contact and not through a membership transaction.
Warning
Rhythm does not currently support presenting an invoice for a bundled membership-plus-chapter purchase so that it shows only the chapter as its line item instead of the membership or package name.
If your account offers a donation prompt during the Individual Renewal Process, a suggested donation can appear on the order summary. If the contact has store credit applied, the donation may not remain selected through checkout. Seeing the donation listed is not confirmation that it will be included. If you need to confirm it was collected, check that it still appears as a paid line item after checkout completes.
Auto-Renewal and Saved Payment Methods
When you choose to renew automatically at checkout and pay by credit card or electronic check, Rhythm stores that payment method for future renewals. Paying by cash, check, or invoice never enables auto-renewal, regardless of what you chose on the form. Once auto-renewal is on for a membership, it renews the membership’s add-ons, sections, chapters, and package together, not just the base membership.
Auto-renewal can also be turned on later, separately from checkout. From a member’s Membership Overview in the Console, staff can use Setup Auto Renewal to enable it. This requires a payment method already on file. If none exists yet, add one first.
Warning
Turning off automatic renewal, either from the Portal or later in the Console, only stops the automatic charge. The card or bank account already on file for it usually stays stored on the membership record. If you do not want that payment method stored anymore, delete it separately, or replace it by setting up automatic renewal again with a different method.
For an organization membership, clearing the Renew Automatically option during the organization’s join or renewal process sets that field to No on the membership and removes the stored card from Membership Info, the same as it does for an individual membership.
Before mass-deleting stored payment methods, check which memberships rely on them for auto-renewal. Removing a card that a membership depends on for automatic billing can disrupt that renewal.
Auto-renewal billing works only when the membership is marked to renew automatically and a usable stored payment method is on the account for later charging. Having one without the other does not create a working auto-renewal. If a member selects Renew Automatically on an application but then unchecks the option to save the card for later use, the transaction can still complete, but no usable payment method remains stored for a future renewal billing run.
Selecting automatic renewal on a membership application can disable the checkbox to save the card for later use, so it cannot be unchecked after auto-renewal is chosen.
A membership package can default new applicants into automatic renewal unless they explicitly opt out. The application form can show the Renew Automatically field as optional, required, or not shown at all. To keep auto-renewal off by default, make sure the package does not default it on and that the form does not expose the field in a way that turns it on unintentionally. This package-level default applies only to joins or renewals completed after you turn the setting on. It does not change applications already submitted.
Tip
If you want more renewing members to end up on automatic renewal, turn on your package’s option to automatically renew unless the member opts out. This makes the checkbox start checked during the application or renewal process. Consider adding explanatory text near the field so members notice the preselection before they submit.
Renew Automatically depends on that setting and your package’s own defaults, not on whether a member received a renewal notice with a payment link. A saved payment method alone does not cause a charge unless Renew Automatically is turned on for that membership.
When an open invoice is paid, the Renew Automatically choice made at the moment that invoice is paid determines whether the membership ends up with auto-renewal on or off. That is true even if the member selected something different earlier in the application process. If the payer leaves the option unchecked while paying the invoice, auto-renewal is not enabled for that renewal. This has been observed specifically with a proforma invoice paid by a stored card when the invoice's own auto-renew option was left unchecked, which could reset an existing Renew Automatically flag from Yes to No during fulfillment; that behavior has since been corrected.
A pricing rule that depends on a membership already being marked Renew Automatically does not apply on the same transaction that first turns the setting on. The flag must already be set and saved before that later purchase is priced.
If your association changes payment processors, a card stored under the earlier processor may not appear as a usable stored payment method under the newer one. Have the member re-enter their payment details, or go through the renewal process again, so the card is saved under the new processor and appears in the newer payment-management experience.
A membership can show automatic renewal turned on while referencing a card from a payment-processor migration that no longer appears as a usable stored payment method in the Console. To get a current, usable stored payment method for that membership, have the member update their payment method in the Portal. It will then also appear under stored payment methods in the Console.
Warning
A membership’s auto-renewal setting can show a card on file even when the underlying link to a valid payment method is no longer good. If changing renewal settings for a member unexpectedly fails, check whether the referenced payment method is still valid before assuming the setting itself is broken.
Confirming that an auto-renewing membership still has a usable saved payment method, especially after a payments migration, may require a backend query rather than something you can confirm from standard query output alone. Involve support if you need this confirmed for several members at once.
For an organization’s own membership, there is currently no direct, self-service way to update the payment method used for its auto-renewal. A separate process is needed. Contact support for help updating an organization’s auto-renewal payment method.
Rhythm does not automatically send an incentive or reward when a member turns on auto-renewal. If you want to reward members who enroll, query for members with auto-renewal enabled and send them a discount code or similar offer directly.
Tip
If you need the exact date and time a membership’s Renew Automatically setting changed, check the member’s audit logs. They record the before and after value, along with when the change happened, which a standard query or the membership record itself will not show you.
“Linking” a saved payment to auto-renewal means Rhythm associates a payment method already saved with your account’s payment processor to the membership’s auto-renewal record. It does not create a new saved card from scratch.
Confirmation and Activation Emails
Rhythm sends a welcome or confirmation email once your membership is activated, if the application process has that email enabled. If your package details are held back until you pay enough, you receive the confirmation email first. The fuller activation email follows once the payment rule is met. If you make more than one payment toward it, you may receive that email again on each payment.
A membership join email is expected to go out only after payment has actually been made. When a package is configured so the membership is not technically active until the invoice is paid in full, no activation email is expected before that payment lands. Once activation happens, the activation email’s content should be sent, not the earlier submission email’s content. Leaving an activation email unopened does not trigger a second automatic send.
Join, renewal, and reinstatement or reactivation application processes each have their own activation confirmation email setting. Turning this email on for one process type, such as a new-member join process, does not turn it on for renewal or reinstatement processes. Check the setting on each process you care about.
A general order confirmation email and a membership-specific activation confirmation email come from two different configuration areas, and each can send independently for the same purchase. The order confirmation is set up under your Orders & Inventory settings, while the membership activation confirmation is a separate setting on the membership application process.
A payment receipt email sent when an invoiced renewal is finally paid is different from the membership confirmation or activation email. Do not assume the receipt a member receives at payment time is the same as their membership confirmation.
Rhythm can occasionally send two identical confirmation or activation emails for what should be a single join or renewal transaction, most often through Portal purchases. If a member reports a duplicate confirmation email, it does not necessarily mean they were charged twice. Check the order and payment records before assuming there is a billing problem.
A membership confirmation email is sent to whichever contact is on the order when the email is sent. If that order or membership is later relinked or merged to a different master contact, the email that already went out is not resent or reassigned to the new contact.
Any additional email address you enter at the final billing step of the membership order flow receives a copy of the order confirmation email. It does not also receive a copy of the invoice. For orders processed through the Membership Console order flow specifically, additional recipients also receive the activation email and payment receipt email, not only the confirmation email.
New members whose process creates or links a Portal login receive their welcome or set-password email under the same condition as the activation confirmation. It goes out only if the Membership activation confirmation email is turned on for that application process.
There is currently no built-in option on a member’s own record to manually send or resend a renewal confirmation email. If a member needs their confirmation resent, handle it outside that record.
Some merge fields used in membership emails have known limits. The membership type does not resolve reliably in a membership package confirmation email, and building content that depends on the membership type is not the intended use of that email. A membership-record merge field, such as a section or division, can reflect the value from before an application’s full details are applied if the confirmation email sends before that update lands. The order record may be a more reliable source when a merge field needs to match what the buyer chose. A first-name merge field in this kind of email can also resolve to the invoice’s bill-to contact rather than the applicant, especially on a join paid by or billed to an organization. Check whose name appears before relying on it.
A membership-related email address populated through the application or membership process, rather than the contact record, is what appears in membership emails and API responses for that membership. The contact record remains the primary source of truth for identity and duplicate-checking elsewhere in the product, but it does not automatically flow into an already-set membership email.
For a group membership, product-level add-on emails go to the billing contact who purchased the add-on, not to each individual member the add-on covers. There is currently no configuration to redirect those emails to the person receiving the benefit. If that person needs instructions, put the information in the membership application process’s own confirmation email instead, since that email goes to the person whose membership is being created or activated.
Mid-Term Changes and One-Off Purchases
A change of affiliation paid with a change fee updates your type, package, or holdings without waiting for a renewal. It also sends its own activation email, even if the process does not have that email switched on. If the order behind a change fee is later cancelled, the change itself is not undone.
A change of affiliation does not automatically add a renewal to the same order. If you want that order to also renew the membership, add the renewal package as a separate line during order review before completing the order.
Adding a chapter through a change of affiliation, without also buying a membership package or renewal on the same order, does not move the primary membership’s expiration date forward. Only a package or renewal purchase advances the main term.
You can buy a single chapter’s or section’s dues on their own, which adds or renews that chapter or section on your existing membership. You must already have a membership to attach it to. Buying an add-on on its own adds it the same way. If you renew an add-on you already had, the new purchase adds to its existing quantity instead of replacing it.
If a mid-term package upgrade needs to collect only the price difference rather than a full new order, create a standalone invoice for that difference, apply it, and then manually change the membership to the new package. You can also cancel the original order, issue a credit from that cancellation, and apply the credit to a new order for the upgraded option so only the difference is invoiced.
If an organization does not want a payment represented as a financial transaction in Rhythm, document the acknowledgment in the membership’s notes instead of creating a payment record.
Related
For how the order behind a purchase or renewal is priced, see How an Application's Order Is Priced. For how an organization’s own purchase can also update the memberships of its people, see How an Organization's Membership Reaches Its People.
If a Membership Doesn't Update as Expected
| What you're seeing | What to check first |
|---|---|
| An order, invoice, and payment all look complete, but the membership never updated | Confirm that an application record exists for the join or renewal. If it does not, contact support so the diagnostic details available on the back end can be reviewed |
| The expiration date advanced more than you expected, or advanced twice | Look for duplicate renewal applications submitted close together; each duplicate can be fulfilled and advance the term |
| The expiration date didn't advance, and the member was later billed again by auto-renewal | Check for a duplicate application tied to the same order. When the expiration date does not move, a later scheduled billing can still treat the membership as due and create another charge |
| A membership that requires approval shows its term advanced twice from one renewal | Check for a duplicated renewal application; this has been seen specifically on memberships that use an approval process |
| A paid invoice didn't update membership status or expiration, and the contact was recently merged with a duplicate | A merge by itself is not expected to activate or advance a membership. Check whether either merged record had prior membership history before treating the merge as the cause |
| You cancelled and refunded a renewal that should not have happened, but the old expiration date didn't come back | Contact support; cancelling and refunding an unintended renewal is expected to restore the prior expiration date |
| A renewal package you expect to see isn't offered as a renewal option | Compare the package’s purchasing or eligibility criteria with the renewing record’s own data before assuming the package is missing by mistake |
| A renewal or bulk renewal errors out over an add-on | Check for an add-on restricted to a different membership package that is still attached to the record, and remove it before renewing into the new package or type |
| A chapter disappeared unexpectedly after a renewal | Check the System Audit log to see what removed it, so you can tell a configuration effect from a support case worth escalating |
| You need to know exactly when auto-renewal was turned on or off for a member | Check the member’s audit logs, or the membership fulfillment audit log, for the before-and-after value and timestamp |
| A membership's own linked order looks wrong, so a renewal never lands where you expect | Staff can update the membership’s Linked Order ID field to point to the correct order |
| A membership's fields look incomplete right after a group or organization assignment | Check the Membership Fulfillment Agent’s audit log entry from when the order was placed. A later gap in the individual record can be a display or propagation delay rather than a failed assignment |
| A membership shows a join or renewal date with no order, application, or log to explain it | The date likely came from a data import rather than a later manual change |
| A membership record won't save after you try to fix a renewal issue | Check whether a required custom field on that membership still needs a value before it will save |
| A membership package stopped creating or renewing memberships | Confirm the package is still linked to an active membership type; a missing or broken link between the package and its type can stop fulfillment until you point the package at a valid type again |
| A member was billed twice around a renewal | Check whether an earlier renewal payment failed to advance the membership’s expiration date. When it does not advance, later auto-renewal or billing can still treat the account as unrenewed and bill it again |
| A membership record briefly won't let you save right after processing an order | Wait a short time and try again. The record can still be updated by background processing immediately after order processing |