- group by account code, not channel
- change description for batch & rows around date
Item 1 - There seem to be too many lines in the journal entries. We’ve noticed some where the date range, GL, department, funding, entity, currency, PSP, and activity type, date range are the same, but there are multiple lines split. One example you can check is CREV journal entry 120 in the sandbox. (edited)
2:27
Item 2 - Some journal entry lines seem to have incorrect date ranges. One example you can check is CREV journal entry 167 in the sandbox. Julie checked the donations for the journal entry, and both of the donations are from January 15, but the date range begins with December 2. We wanted to propose that PayPal can just have a single date (the day they settled). The intention of the memo date range was to provide the PSP’s batch settlement date range when we were planning weekly file transfers.
2:28
Request - We’d like to have the description on the batch journal entry changed a bit. Currently you are entering it as currency code, net amount, “Contribution Revenue”, batch date range. We would like to request: PSP name, currency code, “Contribution Revenue”, batch date range (remove the net amount and add the PSP). So for example this is what we would like:
Adyen EUR Contribution Revenue 12/31/2025 - 01/02/2026
Eileen McNaughton
Today at 4:40 PM
Thanks Tiffany
- yeah these are ones with different channels but the same account code - I can squash them
Thanks - just using the settlement date is good
Sure - I can get rid of the batch amount - I was including it in there because it made it really easy to eyeball what was settled in the bank was what was in the batch - but I'll get rid of it. Regarding the date range though - what is it a range of? Each batch has transactions that all settled to us on the same date. However, the received date could be over a period of months. We do have the date settled to the processor but I'm wondering if using that is adding more than just the date it settled to us - cos I'm not loving the settled-to-processor-date data that we are getting (either in the processor reconciliation report or in the re-formatted version of the same) - so unless the range adds clear value I wonder if the same settlement date as in 2 is good?
4:41
Oh I just re-read - you want a single date for Paypal & a range for Adyen. Note that Braintree, Dlocal are also being batched by daily account movement - so it would be only Adyen that would potentially get a range
Eileen McNaughton
Today at 4:55 PM
also we did talk about moving Adyen to daily? (note that is a configuration option within Adyen console that would need to be changed)
And from me
- process valid batches regardless of the presence of invalid ones - I think that now they are not wanting a single file for SFTP we can do this.
- maybe store the remote batch url?