Skip to content

Understand posting approvals and pending results

5 min readBusiness

Use the original workflow’s own preview, submit, and saved receipt to confirm whether a posting is pending, verified, or failed. This page explains how to read those states and what to do next for Chart of Accounts corrections and FX Revaluation without replaying an uncertain write as a new request.

Before you start

  • You need to be signed in to a business workspace.
  • You need access to the accounting area for the original workflow you are reviewing.
  • For any recovery or follow-up, keep the original on-screen request, saved receipt, or batch reference shown in that workflow.
  • If the current workspace or connected ledger changed, reopen the original workflow before taking another action.

Read posting approvals and pending results

Use the original transaction workflow to review the result instead of looking for a universal batch browser. A pending or running result means the work is not finished yet; a verified result means the posting already has a saved outcome in the connected ledger.

  1. Open the original workflow that created the posting or correction.
  2. Check the visible status on that workflow first. Pending or running means the saved request is still in progress.
  3. If the workflow shows a verified receipt or submitted result, use that saved result instead of trying to create another posting.
  4. If the workflow shows an error or an unknown acknowledgement, treat it as unresolved until the same workflow shows a verified result or support confirms the saved receipt.

Expected result: you can tell whether the original request is still in progress, already verified, or needs follow-up on the same saved workflow.

Chart of Accounts corrections

Chart of Accounts corrections use the account detail view, the correction preview, and the same saved command. This workflow shows what will change before you confirm it, and it provides Resume same command when a saved correction is waiting or running.

  1. Open the account detail view for the posting you want to correct.
  2. Select Propose reclassification to start the correction review.Propose reclassification
  3. Review the preview carefully. Confirm the moved amount, effective date, and accounting reason before you continue.
  4. Select Confirm and submit correction to send the reviewed correction.Confirm and submit correction
  5. If the workflow later shows a saved correction in progress, use Resume same command instead of creating a new correction.Resume same command

Expected result: the reviewed correction is either submitted, or the same saved correction resumes from its current state.

FX Revaluation

FX Revaluation has its own Preview, Create Journal Entry, and Submit Journal Entry flow. The page can show a preview first, then create an export batch for the journal entry, and then submit the journal entry if that is part of the approved path.

  1. Open FX Revaluation and review the preview for the posting date you need.
  2. Select Create Journal Entry to create the reviewed journal entry when the preview is correct.CreateCreate Journal Entry
  3. Wait for the batch status to finish. A queued or running batch is still in progress.
  4. If the created journal entry is still a draft, use Submit Journal Entry from the same workflow.Submit Journal Entry
  5. After submission, use the saved submitted result shown on the page instead of creating another revaluation.

Expected result: you see either a created draft journal entry or a submitted journal entry tied to the same reviewed FX workflow.

What the visible states mean

Workflow state meanings
StateMeaningWhat you should do
pendingThe reviewed work is saved but not finished yet.Wait in the same workflow and check again.
runningThe work is currently being processed.Do not start a duplicate request.
succeededThe workflow reached a verified saved result.Use the saved result or receipt.
failedThe workflow ended with an error.Review the error shown on the original workflow and contact support if it cannot be recovered there.
unknownThe acknowledgement did not confirm the final ledger result.Keep the original reference and reopen the same workflow before trying again.

If the result does not match

If the company, ledger connection, account, or request shown on screen does not match the saved record, do not treat it as the same action. That protects your books from duplicate or conflicting writes.

  • If the workflow is still pending or running, wait for the same workflow to finish.
  • If the workflow already shows a verified receipt or submitted result, use that saved result and do not recreate it.
  • If the current workspace or connected ledger changed, reopen the original workflow before continuing.
  • If the result is failed or unknown and the workflow does not offer a supported same-request control, keep the original visible reference and contact support before another financial write.

Legacy association and support review

Some saved results can be reviewed or associated during support recovery, but there is no customer-facing universal association button for this. Use the original screen’s saved receipt or request reference when you contact support, and keep the uncertainty visible rather than replaying the write under a new request.

  1. Open the original workflow and note the saved request, receipt, or batch reference shown there.
  2. Confirm whether the workflow already shows a verified, submitted, or cancelled result.
  3. If the workflow does not provide a supported same-request control, stop there and contact support with the visible reference from the same screen.

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.