How Voltrus works: records, approvals and the audit trail

Proposals, approvals, next actions and the audit log, and how people and AI agents share them.

Baca dalam Bahasa Indonesia

On this page
  1. Records and the record drawer
  2. Next steps: the flow, one click at a time
  3. Proposals and approvals: the governed flow
  4. Who can do what
  5. Discussion and activities
  6. The audit timeline
  7. Notifications and the dashboard
  8. Checklist

Voltrus works like any serious ERP: master data, documents with statuses, a stock ledger and a general ledger that every operational document posts to. On top of that it adds a layer most ERPs do not have: any change can travel as a proposal that a person approves before it is applied, and every action, approved or not, lands in one audit timeline. This is what lets people and AI agents work in the same system without anyone losing control of the books.

This article explains the pieces you will meet every day: records, next steps, proposals and approvals, discussion, and the audit timeline.

Records and the record drawer

Everything in Voltrus is a record: an item, a customer, a purchase order, a work order. Each sidebar entry opens a list of one record type. Lists can be filtered, sorted, paged and exported to CSV or Excel, and the filters and visible columns you last used are remembered in your browser.

Opening a record shows its drawer:

  • Fields, with the filled ones first and empty ones folded away.
  • Linked records: the documents it came from and the ones created from it.
  • Next steps: the actions its current status allows.
  • Discussion: comments, @mentions and follow-up activities.
  • Record info: its ID and when it was created and last updated.

Press Ctrl+K (Cmd+K on a Mac) anywhere to search items, customers, suppliers, orders and checklists, or jump to a page.

Next steps: the flow, one click at a time

You do not need to memorise the order-to-cash or procure-to-pay flow. Each record lists what can happen next from where it is:

Record and statusTypical next steps
Purchase order, draftApprove, cancel
Purchase order, approvedReceive goods (all or part of each line), return to supplier, cancel
Purchase order, receivedCreate bill, return to supplier, close
Sales order, confirmedShip, create invoice, create down payment, create work order, record a return, close lines
Sales order, closed with a leftover down paymentRefund or transfer the down payment

Steps that move stock, post to the ledger or cannot be undone are flagged and ask for confirmation. If a step fails a control, for example a credit check on confirming a sales order, a price check on issuing a supplier bill, or an amount above your approval limit, Voltrus can turn it into a proposal for an admin to approve instead of refusing outright, depending on the setting (see below). Purchase orders, sales orders and quotations can be printed from their drawer.

Proposals and approvals: the governed flow

A proposal is a change that has been described but not yet applied: "create this purchase order", "change this item's reorder point to 120", "confirm this sales order although it exceeds the credit limit". It carries who proposed it, why, and a before-and-after view of the change.

Proposals come from three places:

  1. AI agents and integrations with an agent token. They can read freely, but every write they attempt becomes a proposal. Agents can never change data directly.
  2. People who choose to ask. In the record editor, Submit for approval sends your change as a proposal instead of saving it.
  3. Controls that fail. With credit control or the bill price check set to approval (the default), a failing sales order confirmation or supplier bill becomes a proposal for an admin. The same happens when someone who is not an admin approves a purchase order, issues a supplier bill or pays above the company's approval limits.

Proposals wait in the Approval inbox. The approver reads the rationale and the diff, then approves or rejects. Rejecting requires a reason. You cannot approve your own proposal while someone else is able to; in a one-person company you may, and the audit trail records it as a self-approval. Approval applies the whole change in one atomic step, so either all of it happens or none of it. A proposal moves through pending, then approved and applied, or rejected; if applying fails (say the stock was used in the meantime) it is marked failed with the error and can be retried.

Proposals are validated when they are submitted, so a proposal that could never be applied is refused at once instead of sitting in the inbox.

Who can do what

Each person who signs in is linked by email to a user on Users & tokens, where an admin gives them a role. AI agents and integrations use tokens instead.

AccessCan readCan proposeCan approve, post and executeManages users, tokens and settings
ViewerYesNoNoNo
Agent (people or AI, or an agent token)YesYesNoNo
OpsYesYesYes, within the approval limitsNo
AdminYesYesYes, including above the limitsYes

Some actions are reserved for admins: posting manual journals, reopening closed periods, posting the opening balance, switching the costing method with stock on hand, approving proposals raised by failed credit or price checks, and approving anything above the approval limits. Until a company has at least one active Admin user, everyone with operations access keeps admin rights and the Users page warns you to assign one. Tokens are shown once when issued, stored only as a hash, and revoking one takes effect immediately.

See Internal controls and segregation of duties for how to use these to split duties sensibly.

Discussion and activities

Every record has a Discussion tab. Use it for the conversation that would otherwise happen in WhatsApp and get lost:

  • Comments with @mentions; the person mentioned gets a notification. A comment can be edited for 15 minutes.
  • Activities: a to-do, call, meeting or follow-up with an assignee and a due date, marked done or cancelled later.

Discussion never changes the record itself and does not need approval, but it is audited like everything else.

The audit timeline

Every write in Voltrus, from a person, an agent, an automation or the nightly jobs, is recorded in the Audit timeline: what was done, to which record, by whom (and which AI model, for agents), whether it came from a proposal, and whether it succeeded or was denied. You can filter it by record type and record ID, which makes "who changed this price and when?" a ten-second question.

Combined with immutable documents (journals are reversed, not edited; issued invoices are credited, not changed; the stock ledger is append-only), the audit timeline is what an external auditor needs to rely on your numbers.

Notifications and the dashboard

Operations users get in-app notifications for proposals waiting, decisions on their proposals, overdue invoices, low stock, mentions and assigned activities. The Dashboard shows the day's queues: pending proposals, items below reorder point, overdue maintenance, work orders due this week, purchase orders to receive and sales orders to ship.

Checklist

  • Open any sales order and read its Next steps and linked records.
  • Make at least one person Admin, then decide who on your team gets Ops, who should only propose and who only needs to look.
  • Set approval limits for purchase orders, supplier bills and payments in Settings → Inventory & trading → Approvals and limits.
  • Review the agent permissions in Settings before connecting any AI agent.
  • Agree that commitments made by phone or chat are logged as activities on the record.
  • Bookmark the Approval inbox and the Audit timeline.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP