Menu
For digital agents

A guide for agents and the people directing them

Agent access to Ledgermast: browser workflows, MCP/OAuth delegation, and existing accounting approval policies.

Reviewed

Start with the right account and organization

Ledgermast is a double-entry accounting application for small businesses, bookkeepers, and teams with approval workflows. The public website describes the product; your accounting records live in the signed-in application.

Agents can work in the signed-in browser interface, or connect through the Model Context Protocol (MCP), authorized with OAuth.

Delegated access for personal assistants

An assistant connects through OAuth consent. You choose its permissions, the accounting books it can access, and an expiry. Its authority is also limited by your current organization permissions. You can inspect, narrow, or revoke connections in the application's agent settings.

The tools cover reports, customer and vendor records, invoice and bill drafts, approval workflows, posting and reversals, customer credit allocation, and document PDFs. Invoice delivery is a separate permission and operation. Cash receipts, vendor payments, banking changes, manual journals, and administrative settings are outside this delegated access.

An assistant can act within the permissions you delegate, with approvals required by Ledgermast's existing policies. There is no extra approval step for every assistant action. Two assistants acting for the same person cannot approve each other's work where a separate approver is required. See approvals and permissions.

Using the browser interface

The walkthroughs below describe the browser interface.

  1. Have the account holder sign in and complete any two-factor challenge in the browser session.
  2. Confirm the organization name shown in the application before reading or changing records. If the account belongs to several organizations, select the intended one first.
  3. Agree on the document, dates, amounts, currency, and intended outcome. An instruction to prepare a draft does not request its approval, issue, payment, or delivery.
  4. Use the visible links, labeled fields, and buttons. Navigation and available actions depend on the signed-in user's permissions.

Read a trial balance

  1. Open Trial balance in the application.
  2. Set the reporting period and apply it. Confirm the date range displayed above the report.
  3. Read the account activity and total debits and credits. Distinguish an empty reporting period from a failed request or a permission refusal.
  4. Report the organization, date range, and displayed figures with your answer so the account holder can reproduce it.

A report with no postings says so explicitly. It does not prove that a different period or another organization has no activity. If access is refused, ask the account holder to arrange the necessary report permission; changing a URL does not grant access.

Prepare an invoice for review

  1. Open New invoice. Select the intended customer and check the document dates.
  2. Enter the requested lines, quantities, prices, accounts, and applicable tax details. Read the calculated totals before saving.
  3. Choose Save draft. Wait for the saved document page and confirm its customer, totals, and Draft status.
  4. Return the document link for review. Use Submit for approval only when the user requested that next step.

Saving a draft does not issue an invoice or post it to the ledger. Submission, approval, issue, and sending are distinct steps. The application enforces the actor's permissions and segregation of duties. A refused approval needs an eligible approver, not another attempt with the same identity. See approvals and permissions.

Export the report you are looking at

  1. Open the trial balance and confirm its period and organization.
  2. Choose Export CSV. The trial-balance export link carries the displayed period.
  3. Confirm that a CSV file downloaded successfully; an HTML sign-in or error page is not an export.
  4. Check its headers and account rows, and retain the reporting period with the file when handing it back.

CSV exports remain available in the subscription's read-only state, subject to the user's permissions. Exports contain private accounting data: return them only through the destination requested by the account holder. See export formats and limits.

Recover from interruptions without duplicating work

  • Validation error: read the field-level message and correct the identified input. Check the saved result after resubmitting.
  • Session expired: return control for sign-in, then confirm the organization and current document state again.
  • Permission or approval refusal: stop that action and explain which authorized person needs to continue.
  • Timeout after saving: inspect the document or list before repeating the action. A missing response does not prove that the save failed.
  • Read-only subscription: continue permitted reading and exporting. An authorized account holder can restore editing through billing.
  • Incorrect posted document: use the application's supported reversal workflow with the appropriate authority. Posted history is not overwritten.

Pricing and bank feeds

$29 USD per month includes 3 active users; each additional active user costs $6 USD per month. See pricing for the full terms.

A 90-day free trial includes accounting workflows, approvals, reports, receipt scanning, and CSV exports. When the trial expires without a subscription, the organization becomes read-only and its records remain readable and exportable.

Automated bank feeds bring your bank activity in each day through Stripe Financial Connections. Feeds are included with a paid subscription at no additional Ledgermast charge. Without a feed, you can still reconcile by tick-off against your bank statement.

Product references

For public product research, start with the agent-readable index. Each public content page links to a Markdown version containing the same main content. These files describe the public product; they contain no tenant records or login credentials.