#PURPOSE:
 - Currently is the user is promoted as admin for accounting and he/she is try to generate/regenerate or view the gst report 
    following Error is thrown.
 - Access Error

    ```Uh-oh! Looks like you have stumbled upon some top-secret records.

       Sorry, Marc Demo (id=5) doesn't have 'read' access to:
         - Document (documents.document)```

#STEPS TO REPRODUCE
  1) Install necessary modules for indian accounting localization.
      (i.e accountant,l10n_in)
  2) Enable GST E-Filing & Matching Feature from account's configuration.
  3) Go to Settings -> User & Companies -> Users
  4) Click new if no user is there other then administrator else click on
     another user.
  5) Under Access Rights section , inside Accounting select Administrator & Save.
  6) Now log in as new user in another tab.
  7) Go to Accounting -> Reporting under 'India' section click on
     GST Return Period.
  8) Click on generate/regenerate or View option.
  9) The above shown error will be raised.

**Issue**
When modifying and reposting a vendor payment that does not have the highest sequence number, the payment's name (i.e., number) is regenerated using the next available sequence, rather than preserving the original. This issue only occurs when the Outstanding Payments account is configured for the journal.

**Steps to Reproduce**
1. Install the Accounting module.
2. Go to Accounting > Configuration > Journals, and open a Bank journal.
3. In the Outgoing Payments tab, set an Outstanding Payments Account.
4. Go to Accounting > Vendors > Payments.
5. Create and post two vendor payments (e.g., 00001 and 00002).
6. Reset the first one (00001) to draft, change any field (e.g., amount), and repost it.
7. The number changes to 00003 instead of preserving 00001.

**Root Cause**
When a vendor payment is modified and reposted, Odoo cancels and regenerates the associated account.move. If an Outstanding Payments account is configured — or was configured at any point — this triggers additional logic causing the move name to be reset to '/'. This placeholder indicates that the move is treated as if it were new, prompting Odoo to assign it the next number in the journal’s sequence. As a result, the payment loses its original number even though it conceptually refers to the same transaction.

**Fix**
The fix ensures the original number is preserved by restoring the payment's previous name only when it's clear that the move is being regenerated, not newly created. This is determined by checking that the move is linked to exactly one payment (i.e., a one-to-one relationship) and that its name is '/', indicating the move was regenerated.

Opw-4805870