Recent Posts & Replies
Delay 15/03 - Southern Cross Credit Union
Hi all, we're aware that some customers are experiencing a delay when attempting to receive their bank feed data from Southern Cross Credit Union. Data has not been received since 14/03. This is being investigated with Southern Cross Credit Union. We will aim to update here once this has been resolved. Thanks!
Superannuation - clear from outstanding list
We entered into a payment arrangement with the ATO for outstanding superannuation guarantee for our employees. We lodge directly with the ATO and have not "paid" these through MYOB. How do we clear these outstanding figures now that they have been paid with the ATO directly? Do we generate a payment in MYOB? Does the system still talk to the super clearing house even though we pay directly to the ATO?
Developer Update March 2025
Developer Update March 2025 AccountRight 2025.2 has now been released. Please update your app to the latest version. You can find out more about the new version of AccountRight 2025.2 at our blog here. As new versions of AccountRight are released, we also decommission older versions. If you are currently on version 2025.1, you will need to update by March 25 2025**. You can find out more about updating to the latest versions here. ** All dates are indicative only and subject to change.
Issue when deleting bank statement
Hi I am experiencing an issue when trying to delete a bank statement. I have uploaded a statement that overlaps my bank feed and thus have duplicate transactions. when attempting to delete the statement i get the error message "Something went wrong. Please try again or refresh the browser." I have tried rolling back my reconciliation to before i uploaded the statement however the issue still persists. I am now in the process of un matching all transactions just in case that is causing the problem. Any advice or information would be greatly appreciated. Regards JoelHow-to: Reimbursements
This article provides a step-by-step guide for Solo users who need to manage client reimbursements efficiently. It explains how service providers can categorise purchases made on behalf of clients, ensuring smooth reimbursement. The process involves setting up two new categories—Reimbursement Expense and Reimbursement Income—and properly recording transactions. An example scenario of a virtual assistant buying a hairdryer for a client illustrates how to track expenses and invoice clients correctly. The article also highlights the importance of using the correct tax codes and consulting an accountant for personalised advice.Win $1000 with Solo & Triple M 💰
1 MIN READ Sole operators, we see you. You’re out there doing all the things—the boss, the worker, the admin, the finance team… Well, it’s time to take a breather, on us. What’s the deal? We’ve teamed up with Triple M and LiSTNR to give 10 lucky sole operators the chance to win $1,000—so you can take a well-earned day off (or treat yo self to whatever you like, no judgment) How to enter 1️⃣ Head over to the Solo ‘win’ page at triplem.com.au 2️⃣ Share your “work work” woes—the grind, the hustle, the moments that make you wish for a break 3️⃣ Sign up for a chance to win! To be eligible, you’ll also need to sign up to Solo using the code SOLODAYOFF, which gets you 12 months free on us. 🎉 Already signed up? Spread the love! Since you’re already part of the Solo crew (nice move 🙌), you might know someone who could use a day off and 12 months free Solo. Send them this post and give them the heads-up—it might just be their lucky break! When do winners get picked? Winners will be announced weekly throughout the campaign period, which runs from March 10 to April 30—so get in quick! This is your chance to step away from the work work and enjoy a well-deserved break. Go on, you’ve earned it. 🚀 Got questions? Drop them in the comments! ⬇️Issue with MYOB Business API: 409 Conflict when sending multiple POST requests
This is not a support request, it is more like an issue I recently encountered, and since I could not find any documentation about it in the API docs, I thought I'd post it here to save other developers time in the future. Undocumented limitation with MYOB Business API: 409 Conflict on sending multiple POST requests in parallel Issue Summary While integrating with the MYOB AccountRight API, I encountered an issue when creating new Bills via the API. When submitting multiple POST requests in quick succession, some of them intermittently fail with a 409 Conflict error. The error message returned is: "An Update operation requires the latest RowVersion for each of the existing entities being modified." This is unexpected behavior since this error message is typically associated with PUT requests (updates), not POST requests (new record creation). Expected vs. Actual Behavior Expected Behavior: Each POST request should successfully create a new Bill, returning the newly created Bill’s details. Actual Behavior: Some POST requests fail with a 409 Conflict error, while others succeed. Resubmitting the same failed request later often results in a successful response, without any changes to the request payload. Steps to Reproduce Send multiple POST requests to create Bills in rapid succession (e.g., five requests in parallel). Observe that some requests fail with a 409 Conflict error while others succeed. Resubmit the failed request later - it may succeed without any modifications. Analysis The error message suggests that MYOB is incorrectly treating some POST requests as PUT requests, possibly due to an internal concurrency issue. This behavior is undocumented, and no clear explanation is provided in the API documentation. Possible causes include: Concurrency limitations within the MYOB API when processing multiple requests simultaneously. Internal caching or sync delays causing some transactions to be misclassified as updates. Thread safety issues where parallel requests interfere with each other. MYOB API Support Response After raising this issue with MYOB API support, it was confirmed that the API does not handle multiple simultaneous POST requests to the same database correctly. Their recommendation was to add a delay between each request to ensure successful processing. "We have had requests to open this up, but we would need some significant updates to be able to do so. Going forward, you will need to provide space between each call." Workaround To avoid encountering this issue, implement the following workaround: Send requests sequentially, ensuring each request completes before sending the next. Introduce a delay of a few seconds between consecutive POST requests. Implement automatic retries with exponential backoff when encountering a 409 Conflict error. For example, in a microservices-based architecture, detecting this specific error and retrying after a short delay can help mitigate the issue. Conclusion This undocumented limitation can cause unexpected failures when batch submitting Bills via the MYOB API. Until MYOB updates their API to handle parallel requests correctly, developers should implement sequential request processing or introduce delays to ensure reliability. Hopefully, this post saves others time troubleshooting similar issues!
