Skip to content

postings: the journal entry created at Issue is not refreshed when the document is amended and re-issued (Confirm → Reject → edit lines → Issue keeps the old amounts) #7071

Description

@delchev

What happens

SalesInvoice SI00000003 on sta: issued at 1 200.00 → journal entry 8 created (Dt 118 1200 / Ct 213 1000 / Ct 144 200, status DRAFT, Post task in Inbox). At the Confirm task I chose Reject → invoice back to DRAFT, added a line (total 1 260.00), Issue again (number kept, PDF v2 minted with 1 260.00).

Journal entry 8 still carries 1 200 / 1 000 / 200. No second entry was created (good), but the pending posting no longer matches the document it references; when the accountant posts it the ledger is 60.00 short.

Expected

The posting rule fires on the Status == 3 transition; on a re-issue it should either refresh the DRAFT entry's items (entry not yet posted) or create a correcting entry (entry already posted), like the snapshot generator mints a new copy version.

Why it matters

The amend path (Confirm → Reject → fix → Issue) is a documented, tested flow (QA scenario 5) and the ledger silently diverges from it.

Found 2026-09-06 on sta (14.46.0 train: dirigible 14.46.0 / rhea 2.87.0), QA data prefixed QA, walked as an end user through the Billing and Timesheets lenses; recorded in businessintents-catalog/scenarios/.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions