Every member now (optionally) has a second “ScoutBucks” wallet that can be used to track funds that aren't real money (those are tracked in the original “Top-Up” wallet). The types of members (i.e., Youth, Youth & Scouters, Everyone, No one) that have this new wallet can be configured under “Account” | “Payment tracking”. E.g., a Section can offer it only to Youth, or disable the “ScoutsBuck” wallet entirely, if they want.

The ScoutBucks wallet functions identically to the original Top-Up wallet. E.g., amounts can be deposited into a member's ScoutBucks wallet, and they can then use it to pay for events. However, the ability for a member to self-pay for an event when RSVP'ing using the funds in their ScoutBucks wallet is an event-specific option (found under “Signup & Fee options”), and also has a default value (under “Account” | “Event defaults”). Some Sections may want to restrict the use of fundraising dollars to just marquis events (e.g., Jamborees), whereas other Sections might be happy if their members use their ScoutBucks in whatever way the families find helpful.

The Section also has a ScoutsBuck wallet, this means that a Section can put aside money (e.g., that was given a donation) into a separate wallet, and use it for their own NOLB program or saving up for expensive gear acquisition, without having that balance muddled with the Section's general operating funds.

Members who have a ScoutBucks wallet (and the troop) now see a second column of Money IN/OUT and Balance when viewing their statements (e.g., “Home” | “My Wallet”, or “Account” | “Wallets” | “Troop”.

There is now also better support for fundraising activities. Of note, after a fundraising event is complete, the Section can now record a fundraiser's proceeds in the event's wallet (including doing the behind-the-scenes double-entry accounting so that the Group's Treasurer can follow along).

And, there is now the ability to share a fundraiser's profit amongst some/all members. E.g., the profits can be shared across all members of the Section, or just select members (e.g., those that participated in the fundraiser). There are flexible ways to specify how much money is to be shared, so it's easy to do things like share one portion of the profits amongst all members, and another bonus share among the participants, and reserve a portion to be put towards the Section's “new canoe fund”.

Note that the Profit (or loss) sharing isn't just for fundraisers. If an event encounters some unanticipated expenses and you want to recoup the losses from all the participants, then the same sharing mechanism can be used to distribute the loss across the selected members' wallets. When sharing a profit (or loss), you are able to specify which of the members' wallets are impacted. Profit/Loss Shares can be edited, so if you realize that you overlooked one participant, or if an after-the-fact donation towards your fundraiser came in, you can go back and re-jig the numbers and all impacted members' wallets will be appropriately credited.

Now that there is a fully-supported ScoutBucks wallet, and built-in support for tracking fundraisers, the old “Targeted Fundraising” pseudo-badge has been deprecated, and any credit towards that badge has been migrated to a ScoutBucks balance.

• Can now claim/reimburse expenses from an event wallet (e.g., useful for events with $0 fees, but which have expenses such as craft supplies)
• Upcoming meetings with fees but no signup now have a “Manage Payments” option
• Reworded “Add Entry” transaction types to be more task-oriented
• Only show the options for member debt write-off and/or overpayment claim if they apply to one or both of the members wallets
• Improved presentation of event wallet statement for transactions involving deleted members
• Added “ScoutsTracker Skills” topics for all the new functionality
• Memory of members' preferred ledgers for deposits/withdrawals/reimbursements are no longer scrubbed during a “reload from server”
• Bulk payment of members' outstanding fees using “We've already received the money” now supports “Via what Method” option

• Deleting a transaction didn't clear the sync of other other affected ledgers (if any)
• Go to “Account” | “Wallets” | “Event Wallets” | <event>, then delete payments and delete the event, and go back, and the deleted event still shows in the list of wallets
• Fixed incorrect label in member wallet statement when itemizing member profit claim by troop
• Editing a member transaction for an event correctly updates the DB, but on the next reload, the old cached amount was re-used (until the next reload, or the next edit to the event)
• SS-6875: In the payment history of Manage Signups, show fees as $0 for any members who are ineligible, or who signed up NO, or if the event is cancelled
• Bad HTML encoding when describing wallet sharers in confirmation dialog

• SS-6791: Blank space was being added to Personal Journey Cards for training “skills”
• SS-6794: Incorrect text displayed in “Back” link on “My Path” report
• SS-6815: HTML entity code being shown in email subject (date range) if the event is more than a year in the future
• SS-6815: HTML entity code being shown in email subject (date range) if the event is more than a year in the future
• SS-6805: Zero per-member costs shouldn't be shown in the quick event overview, in some situations (emails, newfeed post view on /hello)
• SS-6867: If you pick a joined Scouting Date in the future (e.g., next month), it could say that they'd joined Scouting 11 months ago
• SS-6825: Navigating to old link of “https://scoutstracker.ca/sc/main” wasn't redirecting to “https://scoutstracker.ca/sc/info”
• SS-6889: When pasting content from 3rd-party apps into event descriptions, Scouter-only notes, etc., strip out CSS that could muck up subsequently display
• “Manage Signups” didn't have a bottom border for consent and signup notes cells