Bacs Processing Calendar 2015
As we head towards the end of 2014 we have inevitably started to think about making sure we’re ready to hit the ground running in 2015. To help you do the same we thought it would be helpful to share the 2015 Bacs Processing calendar.
The Bacs Processing Calendar shows the dates that Bacs will accept Direct Debit submissions throughout 2015 as well as the days it won’t (weekends, bank holidays etc.).
Bacs explain, “The Bacs processing calendars are a valuable tool to help you ensure you don’t miss those important processing dates over the holiday period. The Bacs processing calendars supply you with the all important Julian dates you need to process your payment files”.
Here at GoCardless, we automatically take the processing calendar into account so you don’t need to. We do still recommend making sure you’re aware of any non-processing dates which might affect your payment schedule so that you are either prepared for payment timings to change or can decide to move those payments to fit into your schedule (which we're more than happy to help with).
If you have any questions on the 2015 Bacs processing calendar or payment timings more generally our support team are always happy to help so get in touch at email@example.com.
Partner payout breakdown
If you have a partner account, you can now view the individual payments that make up each of your payouts from the dashboard (and export a CSV of these payments for your own records) much like you can for your merchant account.
Simply click through to the individual reference to see which payments and/or refunds are included in each payout - to be emailed a CSV of these details, you just have to hit the ‘Export’ button.
Clearer API Documentation
We’ve spruced up our API documentation, including clearer explanations and diagrams on payment flow and resource creation.
We’ve also added a new troubleshooting section to provide some answers for the most common API-related queries we receive.
Check out the updated docs here and see what you think. As always, if there’s anything you think is missing/incorrect, feel free to submit your own pull request on GitHub for review.