How to fix Error: An error occurred during processing of the field Balance: Object reference not set to an instance of an object.

I forgot to attached the trace. Please see below, thank you.

Up

Hi ​@Novstat,

Based on the trace and similar cases, there are a few common reasons why this type of Object reference not set error can occur:

1. Cache or interrupted process related issue
These errors can sometimes be caused by corrupted cache or an interrupted background process.
👉 As a first step, I recommend restarting the instance during non-working hours and re-testing.

2. Previously known issue in older versions
Similar behavior has been observed in earlier Acumatica builds. Most recent builds include fixes for this, but the behavior may still surface depending on build level and customizations.

3. May require a corrective script from Acumatica Support
If the restart does not resolve the issue, it would be best to log an Acumatica Support case so Support can review the environment and, if needed, provide a corrective script and guidance.

Additional troubleshooting step:
Please try importing and running the Generic Inquiry referenced in the KB article below as a troubleshooting step.

Known issue: In rare cases, the AP payment could not be released or opened on the Checks and Payments form due to the following error: 'An error occurred during processing of the field Balance: Object reference not set to an instance of an object.' | Community

⚠️ I strongly recommend testing this in a sandbox/test tenant first before applying anything in production.

Thank you! Hope this helps clarify!

Hi ​@OshadhiJayasundara82  ​@DipakNilkanth 

Thanks for the response. Sadly, I don’t have access to the links you provided.

​@Novstat , if possible ​@Chris Hackett can help you into this.

Hi ​@Novstat - This is a question asked several times on the community. The answer is that your community account is controlled by your account in Acumatica Portal. That account must be attached to a known business account giving you customer/partner access. Your account isn’t attached to a business account, so you only have guest access. You would need to work with your account administrator to have that changed. Regards, Chris

Hi,

If the issue still occurs even after unpublishing all customizations, it is most likely not customization-related and may be caused by a data inconsistency or system-level configuration issue for that specific payment record.

I would recommend reviewing the full error details from the Trace window and checking the application logs under App_Data\Logs to identify the exact source of the exception. In many cases, this type of issue can be resolved by running Validate Data Integrity (SM203015) for the relevant modules (Accounts Payable, Cash Management, and General Ledger) to correct any missing or broken references.

If the error occurs only for one record, it may indicate that the payment record has an incomplete or corrupted link to related transactions (such as vendor, cash account, adjustments, or GL batch).

Please share the full stack trace from the Trace window (and the payment reference number if possible) so the root cause can be confirmed and the appropriate fix can be suggested.