Skip to content

Review and cancel linked postings or payments

3 min readBusiness

Review the linked original posting or invoice-payment reversal before cancelling it. If a reversal is pending, keep the same saved request and use its check or continue controls to read the status again. Treat it as cancelled only when a verified cancellation result is shown.

Before you start

  • You must be signed in to the correct workspace.
  • You need the current editor role.
  • The undo and accounting features required for your transaction type must be available in your workspace.
  • For posting reversals, the connected ledger and connector features for the original posting must be available.
  • For invoice-payment reversals, the ledger invoices and connector features must be available.
  • The transaction must already be linked to the original posting or payment you want to review.

Review the linked original record first

Before you cancel anything, open the transaction and confirm which original posting or payment it is linked to. The cancellation flow checks the current linked record and keeps the original request identity while it is pending.

  1. Open the transaction you want to review.
  2. Look for the linked original posting, payment, or reversal status shown on the page.
  3. Confirm that you are working in the correct workspace and on the correct transaction before you continue.

Check whether the cancellation is already pending or complete

If a cancellation request already exists, the page can show it as pending or confirmed. A pending state means the original request is still waiting for confirmation, and a confirmed cancelled result appears only after the receipt is verified.

  1. Open the cancellation panel for the transaction.
  2. Use Check original reversal to re-read the saved request status.Check original reversal
  3. If the panel says the original reversal has not been accepted yet, keep the same request and check it again later.
  4. If the panel shows a cancelled receipt, review the amount, currency, and reference before making any further changes.

Continue the same pending request

Use Continue original reversal only for the same saved request. This keeps the same saved request in place and avoids starting a duplicate cancellation.

  1. In the cancellation panel, select Continue original reversal.Continue original reversal
  2. Wait for the app to check the saved request again.
  3. If the app shows a pending message, leave the request in place and return later.
  4. If the app confirms cancellation, review the amount, currency, and reference shown on screen.

What happens when the cancellation is authorized

When the request is accepted and verified, the app confirms the cancellation with the saved request details and updates the transaction state. For both supported workflows, the visible result is a verified cancelled receipt, not a broad deletion of journal history.

  • The original request stays tied to the same transaction while it is pending.
  • The app verifies the receipt before marking the reversal complete.
  • In the normal success path, the stored request is cleared after confirmation; pending or replay states may leave it in place.

If something blocks the cancellation

Common issues and what to do next
What you seeMeaningWhat to do
The original reversal has not been accepted yetThe original reversal is still waiting for confirmationKeep the same request and use Check original reversal or Continue original reversal
The request does not matchThe saved request no longer matches the current workspace or transaction contextReturn to the original workspace and re-check the same request
The app says the receipt could not be verifiedThe receipt or current state could not be confirmedKeep the original request and review the transaction again before retrying
The button is disabledThe app is busy or the action is not availableWait for the current step to finish, then try again

Important limits

Updated

Related guides

We can help

Still need a hand?

Tell us which workspace and page you were using, what you expected, and what happened. Include the time and any request reference shown on screen.

Keep passwords, access tokens and private bank details out of your message. Review screenshots before sharing them.