Developer Update August 2025

Hello fellow developers,

I’m adding this note here in case others are encountering similar behaviour. We’ve identified a separate issue to what is primarily being discussed here. Certain endpoints, such as /GeneralLedger/JournalTransaction, fail to return complete data when paging is involved (i.e. using $top and $skip parameters). Through support case #46197, MYOB has confirmed the issue is reproducible internally.

Hello MYOB team,

I appreciate the ongoing engagement here, and through the support cases we have open, however I question why there is still no public acknowledgment of this on the MYOB status page under Developers -> API (https://status.myob.com/).

As developers, we’re on the front line with customers who expect clear communication about what’s broken and when it will be fixed. This issue has now been active for over a week. My first report from a customer came through last Thursday and it’s becoming increasingly difficult to maintain trust when the only message we can offer is “we’ve escalated it to MYOB,” while the official status page shows no indication of a problem.

I’d like to respectfully request that confirmed issues are publicly acknowledged and backdated on the status page. Otherwise, it undermines the purpose of having a status page at all. Transparency is key, not just for technical teams, but for the businesses relying on us to give them honest, timely updates.

Thanks again for your support, and I hope this can be addressed soon.

Cheers, Shem

Hey Stuart - we're getting reports from customers that our integration is missing transactions. We heavily use /GeneralLedger/JournalTransaction endpoint and my initial investigation that started yesterday suggests some transaction data is not being returned when paging is involved. If we narrow the filters to ensure no paging then problem transactions are returned but as soon as we have to use $top and $skip there are some transactions not being returned. 

I'm preparing a support case with more details now. 

Cheers Shem

Hi Shem,

Thanks for letting me know. Please raise a support ticket via the below form and we'll take a look.

MYOB Business (AccountRight) API Support

Ticket submitted. It's a difficult one to show with evidence since it is about missing data and there are no errors reported. I've put together a video to highlight what I can. Can you please ensure this ticket is looked at with urgency. 

Appreciate your help!

Cheer Shem

Hello Stuart - unfortunately the support team have pickup up an older unrelated support case. The case that is urgent is the one submitted today with Id #46197. Can you please check if somebody has picked this one up.  

We are using the API hosted locally and since yesterday we have been unable to create Invoices via the API.

We are using c# and the latest MYOB.AccountRight.API.SDK 2025.5.658

When Adding a new invoice:
    ServiceInvoice newInvoice = _serviceInvoiceService.InsertEx(_companyFile, invoice, _companyFileCredentials, ErrorLevel.WarningsAsErrors);

Receiving errors:
    Invoice Exception: Encountered a communication error (http://localhost:8080/AccountRight/xxx-xxx/Sale/Invoice/Service/?warningsAsErrors=true&returnBody=true)
    Inner exception: The remote server returned an error: (500) Internal Server Error.

We are using a self hosted instance of AccountRight SE.

Since upgrading to version 2025.7 from 2025.6 the API interface is throwing a 500 Internal Server Error on invoice creation, which sounds like the same issue Martic has reported.

End point: POST /AccountRight/[retracted]/Sale/Invoice/Service/ 

API Error Log:
C:\Program Files (x86)\MYOB\AccountRightServerEdition\app-2025.700.10005\API\logs\logfile.txt

Unexpected Exception of type 'System.ArgumentNullException' was thrown with the following details:
Details : System.ArgumentNullException: Value cannot be null.
Parameter name: authority
   at Myob.IdentityModel.Clients.LiveDirectory.AuthorizationServer..ctor(String authority)
   at Myob.IdentityModel.Clients.LiveDirectory.AuthenticationContext..ctor(String authority)
   at MYOB.ARLive.BusinessLayer.Implementation.Services.OnlinePayments.MerchantConfigService..ctor(IExecutionContext executionContext)
   at MYOB.ARLive.Services.MerchantConfigContainerService.InitializeNewBusinessOperationTree(IExecutionContext executionContext, IMerchantConfigContainer container)
   at MYOB.ARLive.Services.ContainerService`2.ProcessContainer(TContainer container, IExecutionContext executionContext, Boolean ignoreWarnings)
   at MYOB.ARLive.ServiceBridge.ServiceBridge.InvokeGetOnlinePaymentSettings(ICompanyFile companyFile)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at MYOB.Huxley.Services.ARLiveBridge.RunNewStack.Execute[T](String methodName, Object[] parameters)
   at MYOB.Huxley.ApplicationServices.Container.OnlinePaymentSettingsContainerService.GetOnlinePaymentSettingsContainer()
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceRepositoryCommandHelperBase`2.GetOnlinePaymentSettings(ApiCompanyFile apiCompanyFile, TInvoice apiEntity, ISaleEvent huxleyAggregate)
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceRepositoryCommandHelperBase`2.MapApiEntityToHuxleyAggregate(ApiCompanyFile apiCompanyFile, TInvoice apiEntity, ISaleEvent saleEvent, Object[] args)
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceServiceRepositoryCommandHelper.MapApiEntityToHuxleyAggregate(ApiCompanyFile apiCompanyFile, InvoiceService apiEntity, ISaleEvent huxleyAggregate, Object[] args)
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceRepositoryCommandHelperBase`2.<>c__DisplayClass15_0.<ProcessContainer>b__1()
   at MYOB.AccountRight.API.Adapter.Common.CommandHelperBase4`4.ProfileOperation[TX](Func`1 profile, String message)
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceRepositoryCommandHelperBase`2.ProcessContainer(ApiCompanyFile apiCompanyFile, TInvoice apiEntity, OperationContext context, ISaleEvent existingAggregate)
   at MYOB.AccountRight.API.Adapter.Version2.InvoiceRepositoryCommandHelperBase`2.InsertInternal(ApiCompanyFile apiCompanyFile, TInvoice apiEntity, OperationContext context, Func`2 newItemFactory, Object[] args)
   at MYOB.AccountRight.API.Adapter.Common.CommandHelperBase4`4.<>c__DisplayClass17_1.<Insert>b__1()
   at MYOB.AccountRight.API.Adapter.Common.HuxleyCallHelper.Call[TApiEntity,T](Func`1 func, Func`3 validationResultTranslator, TApiEntity passedObject, IApiRequestLogWriter requestLogWriter)
   at MYOB.AccountRight.API.Adapter.Common.CommandHelperBase4`4.DoHuxleyCall(Func`1 func, TApiEntity apiEntity)
   at MYOB.AccountRight.API.Adapter.Common.CommandHelperBase4`4.<>c__DisplayClass17_0.<Insert>b__0(ApiCompanyFile accountRightCompanyFile)
   at MYOB.AccountRight.API.Adapter.Common.ApiCompanyFileExtensions.ExecuteOperation[TResult](IApiCompanyFile companyFile, Func`2 operation)
   at MYOB.AccountRight.API.Adapter.Common.CommandHelperBase4`4.Insert(IApiCompanyFile companyFile, TApiEntity apiEntity, OperationContext context, Func`2 newItemFactory, Object[] args)
   at MYOB.AccountRight.API.Adapter.Common.RepositoryEx4`3.Insert(IApiCompanyFile companyFile, TApiEntity apiEntity, Boolean returnEntity)
   at MYOB.AccountRight.API.Adapter.Common.RepositoryEx4`3.SaveByUid(IApiCompanyFile context, TApiEntity instance, Boolean returnEntity)
   at MYOB.AccountRight.API.Core.Controllers.Version2.MutableControllerProxy`1.<>c__DisplayClass12_0.<SaveOrUpdate>b__0()
   at MYOB.AccountRight.API.Core.Extensions.ProxyExtensions.HandleUnexpectedException[T](Func`1 makeCall)
Base Details : MYOB.AccountRight.API.Core.Base.AccountRightApiUnexpectedExceptionException: An exception was thrown that was not handled correctly. If this situation persists please contact developers@myob.com for further assistance.

Hi Martic and PlainUser,

Please raise a support ticket via the below form and we'll take a look.

MYOB Business (AccountRight) API Support

When submitting the ticket, please include the full API error logs from your local machine, as well as the API key you are using if any. You can find the API error logs at the below file paths:

AccountRight Server Edition: 
C:\Program Files (x86)\MYOB\AccountRightServerEdition\app-2022.XX\API\logs

AccountRight PC edition:
C:\Users\{user name}\AppData\Local\Programs\MYOB\AccountRight\app-2022.XX\AddonConnector\logs

https://apisupport.myob.com/hc/en-us/articles/6217129882255-LocalHost-log-files

I have received a reply from support:
---------------------

We’re aware of an issue introduced in 2025.7 where some users encounter a System.ArgumentNullException during invoice POST, specifically when the API attempts to read Online Payments configuration. We’ve raised this internally with our engineering team and are tracking it closely.
 
In the meantime, the steps we recommend are:

1. Rebuild your project against the 2025.7 SDK so the client and server versions are aligned. After updating, restart the MYOB AccountRight API and Server services.
2. Test with a minimal invoice payload (one line, no attachments or payment flags) to rule out payload-level causes.
3. Open the file in the desktop app, visit Online Payments settings, and re-save or confirm the configuration before retrying. This refresh can sometimes clear the null reference.

-------------------

Currently there is no 2025.7 SDK, but I have tried using POST & PUT requests via Powershell and have the same issue.

We don't use online payments so will not be going through that process.

We also don't use online payments nor do we even have a Online Payment settings option.

It seems the error within the API service is originating within MYOB.ARLive.BusinessLayer.dll during the call to the MerchantConfigService when it attempts to create a new AuthenticationContext. There are null fields in the IdamConfigurationSettings, which appear to be triggering the System.ArgumentNullException resulting in the API's 500 error.