NetSuite "RCRD_HAS_BEEN_CHANGED" error when saving the bank reconciliation a second time

TL;DR

RCRDHASBEEN_CHANGED is NetSuite optimistic concurrency doing its job: the reconciliation record changed on the server after you loaded it, so your save would overwrite someone else's work - often your own second browser tab or an integration updating statement lines. Do not keep retrying the stale page. Note which lines you had matched, close the stale copy, reload the reconciliation fresh, and reapply the matches against the current version. Then check who or what else is editing the rec: a second user, an Account Reconciliation sync, or a SuiteScript job touching the same statement. One active editor per reconciliation removes the error entirely.

NetSuite "RCRD_HAS_BEEN_CHANGED" error when saving the bank reconciliation a second time

Use this when

• Saving a bank or credit card reconciliation in NetSuite fails with RCRDHASBEEN_CHANGED, typically on the second save.
• The same rec was open in two tabs, two users, or alongside a bank statement sync.
• Matches made earlier in the session saved fine before the error started.

Not for this skill when

• Every NetSuite record save fails this way across modules. That points at a deployment or script fault, not one stale reconciliation.
• The error appears on first open before any edit. Look at statement import corruption instead of concurrency.

Steps

1. Write down the matched and cleared lines from your stale screen before closing it, since the reload will not keep unsaved selections. Verify: your match list is captured outside the browser tab
2. Close every tab and window holding that reconciliation, then reopen it fresh from the reconciliation list. Verify: the rec loads with the server's current matched state visible
3. Compare the fresh state with your list and reapply only the matches that are still missing. Verify: the fresh copy shows the same intended matches without duplicates
4. Check the audit trail and active sessions for another user, sync or script that modified the rec during your session. Verify: the other editor or process is identified by name and time
5. Save the reconciliation and agree a single-editor rule or lock window for future closes on this account. Verify: the save succeeds and the rec balance ties to the statement

Variant phrasings

NetSuite RCRDHASBEEN_CHANGED bank reconciliation save

The verbatim code with the rec context.

record has been changed NetSuite reconciliation second save

The plain-English form of the same concurrency error.

NetSuite optimistic locking reconciliation two users editing

When coordinating a shared close.

Compatibility: NetSuite OneWorld and standard NetSuite with Match Bank Data and bank reconciliation, SuiteScript 2.x customisations, and Account Reconciliation syncs.

Why it happens

NetSuite stamps each record with a version and refuses a save based on an older version, because blindly overwriting would erase matches another process saved in between. Reconciliations are long-lived, heavily edited records, so they collide often: statement imports add lines, teammates clear items, and scripts update statuses while a user still holds the first loaded copy on screen.

Edge cases / pitfalls

• Browser back buttons resurrect stale copies; always navigate from the list after a concurrency error.
• If a script keeps touching the rec during business hours, schedule it outside the matching window instead of fighting it daily.
• A rec that changes with no user or script in the audit trail may have an in-flight import; wait for the import to finish before matching.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_RUZu7q8UGk5OE7m4oikAtg