...
|
|---|
Enhancements
Statement View
Statement views have been redesigned to allow Statement detail to be grouped by AR and by Member.
Use Case: Previously, Statement data was shown grouped together. Now, under System and Club Settings then Statements, Users can check settings to group Statement details by Member or group Statement details by AR Account. Grouping by Member shows statement charges grouped by primary Member, spouse, and dependent(s). Grouping by AR Account facilitates the display of charges for Clubs with Multi-A/R.
Please Note: Users can have both grouping categories checked or just one or the other. Additionally, groupings display on desktop and mobile devices. See statement view below with both grouping items checked.
Member Name and primary/spouse/dependent level
AR Account
Aligned Statement and Current Activity page displays.
Use Case: Previously, Statement view and Current Activity tabs displayed results in a different grid format. Now, statement and current activity tabs display data in similar format and grid, and also consistently display within Mobile views.
Improved UI/UX on Mobile Statement and Current Activity views.
Use Case: The Mobile Statement Detail view has been adjusted to show a breakdown of all charges below the main total (with click to access for chit detail for each charge). Further, each charge will breakdown the fees or taxes associated, and will display additional payment details when a portion of a line item was paid with Credit Book or Gift Card. The Mobile view (as indicated above) also displays the Group by Member or Group by AR account setting.
Seamless Pay
Updated Integration for Seamless Pay initiated API changes.
Use Case: Seamless Pay (epay, Newtek, Premier Payments) has continued to update their API. As such, Paycloud integration to Seamless API needed updated to reflect the most current version/changes.
Website Integrations
Added ability to store Event Payment details within PayCloud
Use Case: Previously, Event payment details were not stored or synced to the Website, and therefore, Paycloud was not a feasible option for integration with the Website Product. With this enhancement, Event payment details (event ID and registration ID) are stored in Paycloud, to allow for additional sync features (between Paycloud and the Website) to be added in the future. This functionality is part of our longer-term Paycloud migration plan, and helps lay the groundwork for future Website development that will allow a true sync and reconciliation of Event Registration(s) made on the Website when Paycloud is the integrated Payment platform; enabling Clubs to see paid and unpaid event registrations.
Added ability to store Third Party ID from the Website when a Member signs on.
Use Case: Previously, unique identifying Member single sign on (SSO) data was not stored in Paycloud. By adding this field to store, information to identify a unique member will now be available even if changes occur to the Member number, name, and/or address. This will improve general syncing/reconciliation between the Website/Paycloud and will further support the event payment integration highlighted in the previous item.
Changed method of determining Minimums for Website Snippets using PayCloud data to work better for clients with non-standard minimum date ranges.
Use Case: Previously, Website snippets that relied on PayCloud data for minimum information did not account for non-standard minimum date ranges (date ranges that did not cut off at the same time frame as the statements). In these cases, the Minimum snippet would not display the proper Minimum amount. Now, snippet will display proper balance for Minimums with nonstandard date ranges.
Bug Fixes
...
Fixed an issue with CE Payments where the transfer type for Reversals was not designated correctly in Paycloud and therefore was not properly batching in Office.
...
Fixed a bug where grouped Credit Book activity could be duplicated on the Credit Book page.
...
Fixed a Third Party Integration that prevented Plastiq syncs when a payment was made with a JCB card.
...
Payments
Added Audit Log Details for Scheduled Payments.
Use Case: Within Club Admin Reports > Scheduled Payments grid there are now columns for ‘Created On Date Time’ and ‘Created By User ID’ that can be added to the Grid. Also, within the Scheduled Payment details a Club Admin can view ‘Scheduled on Date Time’ and ‘Scheduled By’ fields, as seen below.
Axis Integration
Created a new tab in Club Admin > System > Club Settings for Axis Member Sync to manage Sync settings.
Use Case: Club Admins can select to only sync changes for Members that are already in PayCloud or can choose to ‘Create New Members’. See Axis Member Sync menu below. This serves to ensure member numbers exist in Paycloud before an SSO attempt is made from Axis and will be utilized by clubs using 3rd party accounting vendors or with future enhancements such as event or form payments.
Club Admins will need to select the Member Number Format for when Spouses/Dependents will be synced. See various Spouse/Dependent Member Number options below.
Dash Letters: 100-A, where A stands for the Spouse.
Dash Numbers: 100-1, where 1 stands for the Spouse.
Letters: 100A, where A stands for the Spouse.
Space Letters: 100 A, where A stands for the spouse.
Bug Fixes
Fixed an issue with OpenEdge allowing Members to submit the payment form multiple times.
Fixed the ability for Club Member’s to hide and unhide fields from their profile from view in the Member Roster.
Fixed an issue with duplicate Third Party IDs being created when a Club Member’s name or member number is changed in Office it does not create a new entry for that Member in the database when synced to PayCloud.
Fixed an issue with “Show Summary Breakout on Statement” in Office. When set, gratuity, taxes, and service charges on the header row are correctly added to the total.
Fixed an issue with PayCloud and Website Snippets where a Date Snippet would also show the time, when not needed.