Source: [Approvals and permissions — Ledgermast](https://www.ledgermast.com/product/approvals/)

Product guide

# Preparation and approval have different responsibilities

Ledgermast separates document preparation, approval, and issue, with role permissions, approval ceilings, and segregation-of-duties rules.

Reviewed October 6, 2026

## Dashboard and inbox

Open Ledgermast to the state of the business, and to the approvals that are waiting on you.

-   Cash balances, receivables and payables aging
-   Current-period profit and loss
-   Recent activity across the organization

## The invoice workflow

1.  **Draft:** prepare the customer, dates, line items, and accounting details. Saving a draft does not post it.
2.  **Submit:** send the document for approval. Submission locks the document details and captures the organization and customer addresses used for review.
3.  **Approve:** an eligible user reviews the submission under the organization's permissions and segregation-of-duties rules.
4.  **Issue:** an authorized user issues the approved invoice, assigning its number and recording the accounting entry.

Sending the invoice to a customer is an additional delivery action. The interface also offers an explicitly labeled issue-and-send action where permitted. Preparing, posting, and delivering a document should each match the account holder's intended outcome.

## Permissions apply to the signed-in identity

Organization roles grant specific permissions, including which books a member can access. Segregation of duties is separately configurable for receivables, payables, and payments; it is not enabled by default. When enabled, it bars document contributors from approval, including owners. The same checks apply when an agent uses that member's browser session. A role name by itself does not promise access to every operation, and a visible document is not permission to approve, issue, pay, or void it.

Bill approvals can also carry role-based amount ceilings. When segregation is enabled, the person preparing work cannot bypass it by running the next action through an agent. If a transition is refused, an eligible person needs to continue the workflow.

## Return work for correction

Where the document's state and the user's permissions allow it, submitted work can be withdrawn or returned to draft with a reason. Read the resulting state before editing and resubmitting. Issued documents follow the correction and reversal process rather than being silently rewritten.

## A practical handoff to an agent

“Prepare an invoice draft for this customer and return its link” gives an agent a clear stopping point. The result should include the organization, customer, document state, total, and saved link. The reviewer can then check the document and arrange the next authorized step.

See [the invoice-draft walkthrough](https://www.ledgermast.com/agents/#drafts) and [how posted corrections retain history](https://www.ledgermast.com/product/ledger-integrity/).