The payment log is “barely” useable. It’s great for logging transactions for people to see, but that’s it.
- If you create an invoice, say unit dues. There is no notification of any type to inform the family they need to pay.
- If the family clicks on an invoice, it becomes initiated which then cannot be deleted… simply by opening it.
- Your log can have money on the account (scout account) but you can’t use it at all. The only form of payment is credit card.
I think barely is an overstatement. I don’t understand how opening an invoice (that then shows credit card entry fields) now locks the transaction into an initiated status forever (unless of course you submit payment). There isn’t even a warning showing what you’re about to do.
Further issue with “initiated” status. When a charge is created, Scout Book displays the amount as a negative number with red font on the computer screen. When a user simply clicks on the charge entry and does nothing else, the status changes to initiated and the amount displayed changes to a positive number with black font. I have posted in other streams that the running balance displayed on computer screens considers the initiated transaction as just initiated but not completed (as not paid). However, Scoutbook’s reports and exports considers the charge as if it was completed. (as paid). A more technical question; is the change to a displayed positive number the cause of the reports/exports not handling the “initiated” transactions correctly?
@John_Kevin_Hickey - here is an initiated payment (done by clicking the pay button)
They still actually owe the 71 as the payment was not processed. When i run the payment log report csv and filter on that person it shows as 71 still owed to the unit.
I was incorrect in saying it changed the charge transaction. When a user clicks on the charge it is adding an initiated payment transaction to the list of the scout’s transactions, but initiated transactions are not being added to the running balance shown on the screen. However, I am getting different results than you are when it comes to reports. The Scout I am looking at initiated a payment for his March dues on May 5, 2026. The Scout’s detail log report includes the initiated payment transaction with a date of May 6, 2026. There is nothing on the detail report that indicated the transaction’s status. The Scout’s summary log report must be including the initiated payment as if it was completed because the summary figure shown as owing is lower by the amount of the initiated payment. I find this to be the case if the Scout has just a single initiated payment or if a Scout has a few initiated payments.
@John_Kevin_Hickey - ok.. here is a scout page where it was all manual payments
and the csv of his payment log report
This is a completed on-line payment
The date range you use is key
What does the report look like if the payment was not completed? If it was left with an initiated status? I run a date range for all scouts with the intent of the reports capturing all transactions.
JohnKevinHickey@msn.com
757-395-0439
@John_Kevin_Hickey - here is an initiated but not completed
