How to prevent API from generating duplicate lines or invoices
Hi Everyone I have written and application that acts like a translator between InfinityPOS and MYOB AccountRight. It has been working for years and I have several clients using it. Lately some customers have complained about having duplicate invoices imported and also sometimes an additional line in the invoice. This interface imports Customer and Supplier Invoices and GL Journals and wanted to check with the community if there is anything I can do to fix it. It only happens 2 - 3 times a month at random and it can be any type of transaction. Sometimes it might be a extra line in an invoice sometimes an extra GL Journal. The system does check if invoices and lines are travelling OK and will not flag an invoice for example as being transferred if it does not get success codes along the way. I could build a delay loop in but I do not want to slow it down as it already takes a while to do everything during a daily transfer. My question is : 1). Does any one have issues with this type of problem ? 2). If you do have issues have you fixed them up or can anyone provide any ideas on how they could be fixed up. Thanks in advance David
Follow up on MYOB Developer Application
Hi, I am wanting to follow up on a developer account application I submitted approximately eight days ago. The confirmation message indicated that processing may take up to five business days, however I have not yet received an update. I have also submitted multiple support tickets and attempted to seek assistance via the MYOB Help phone line, but have not received a response through these channels. We are keen to gain access to the API and would appreciate any update you can provide on the status of our application.
OAuth2 invalid_scope error for sme-* scopes
I'm running into an OAuth2 authorization issue. When I include any sme-* scope in the OAuth2 authorization request, the flow fails immediately with: The requested scope is invalid, unknown, or malformed. The OAuth 2.0 Client is not allowed to request scope 'sme-company-file'. If I omit the scope entirely, the flow succeeds but the resulting token only contains offline_access and openid. Example authorization URL https://secure.myob.com/oauth2/account/authorize?client_id=&redirect_uri=&response_type=code&scope=sme-company-file%20sme-general-ledger&prompt=consent What I've confirmed API key was created after March 2025, so SME scopes should apply Redirect URI is correctly registered — a mismatch returns a different, distinct error Tested multiple sme-* scopes — all fail with the same message Registered a brand new application and reproduced the same error Tested directly in the browser (no SDK or middleware involved) Old-style scopes (e.g. CompanyFile) also fail with the same error Any help is appreciated.
