Internal controls and segregation of duties

Who may create, approve and pay, and how the system enforces it.

Baca dalam Bahasa Indonesia

On this page
  1. The idea behind segregation of duties
  2. Access in Voltrus
  3. Controls the system enforces
  4. Controls that need a habit
  5. A small-company example
  6. Checklist

Internal controls are the rules that stop honest mistakes and dishonest ones from reaching the books. Auditors test them, banks ask about them, and the larger a company grows, the more its owners depend on them, because they can no longer check every payment themselves. In a spreadsheet company the only control is usually the owner's eye. An ERP makes most controls part of the flow: the system refuses, asks for approval, or at least records who did what.

This article explains the classic controls, how Voltrus supports each one today, and where you still need a manual habit.

The idea behind segregation of duties

Segregation of duties (SoD) means no single person should control a transaction from beginning to end. The textbook split has four roles:

RoleExample in purchasingExample in sales
AuthoriseApprove the purchase orderApprove credit above the limit
RecordEnter the supplier billIssue the invoice
Hold the assetReceive goods into the warehouseShip goods out
ReconcileMatch the bank statement, review GRNIReview aging, match receipts

If one person can create a supplier, raise a PO to it, receive the "goods" and pay the bill, fraud needs no accomplice. Split those steps across two or three people and it needs collusion, which is much rarer and easier to detect.

Small companies cannot always separate everything; three people cannot fill twelve roles. Auditors accept that when there are compensating controls: a manager reviews the reports that would reveal a problem, regularly and visibly.

Access in Voltrus

Every person who signs in is linked by email to a user on Users & tokens, and an admin gives each one a role:

  • Viewer can read everything and change nothing. Useful for owners, auditors and the external accountant.
  • Agent access (people signed in as agents, AI agents and integrations with an agent token) can read everything and propose changes. Every write it attempts becomes a proposal in the Approval inbox.
  • Ops can read, propose, approve proposals, execute next steps and post, within the company's approval limits.
  • Admin can do everything Ops can, above the limits too, and manages users, tokens and settings.

Some actions are reserved for admins: posting manual journals and the opening balance, reopening closed periods and years, switching the costing method with stock on hand, approving the proposals raised when a credit check or bill price check fails, and approving anything above the approval limits.

Two rules make segregation of duties real:

  • Nobody approves their own proposal. The Approve button is disabled on your own proposals while someone else can approve them. A one-person company may self-approve, and the audit trail records it as such; set Approving your own proposal to Never if you want no exceptions at all.
  • Approval limits by amount. In Settings → Inventory & trading → Approvals and limits, set an IDR amount per kind of document: approving a purchase order (lines plus freight, before PPN), issuing a supplier bill (including PPN), and money going out (a supplier payment, a refund, a payment batch or a whole payment run). Above the amount, only an admin may act; anyone else's action becomes a proposal that an admin approves. Foreign-currency documents are compared in IDR. Leave a field empty for no limit.

How to set it up

  1. Give Ops to few people, Admin to fewer. Staff who enter documents (purchasing clerks, sales admins, warehouse staff) can work with agent access: they draft, and their changes reach the inbox for a decision. Supervisors who decide get Ops; the finance manager and a director get Admin.
  2. Set approval limits that match your signing authority. If today a director signs every PO above Rp 50 million, enter 50,000,000 as the purchase order limit.
  3. Review high-value documents after the fact. Once a week, a manager filters purchase orders and payments above a threshold and checks each has a reason. The list export to Excel makes this a ten-minute job.
  4. Review the audit timeline. The Audit timeline records every write with the actor, including approvals made above a limit and self-approvals. Spot-check changes to supplier bank details, item costs and customer credit limits, the three favourite targets of fraud.

Controls the system enforces

These work without anyone remembering them.

ControlWhat it preventsWhere it is set
Immutable documentsChanging posted numbers. Journals are reversed, issued invoices credited, payments reversed; the stock ledger is append-only.Always on
Period closeBack-dating into a month already reported. Posting into a closed or locked month is refused; reopening needs an admin.Settings → Ledger → Periods
Three-way match on billsPaying for more than was received, or at a price above the PO beyond a tolerance. The bill quantity is always capped at received minus already billed.Settings → Inventory & trading → Bill price check
Credit controlSelling to customers on hold, with overdue invoices, or above their limit.Settings → Inventory & trading → Credit control
No negative stockShipping or consuming stock that is not there.Always on
Blind cycle countsCounters copying the book quantity. Large differences need a second count or an admin override.Settings → Inventory & trading → Inventory control
Adjustment reasonsUnexplained write-offs. Reason codes can be made mandatory on manual adjustments.Settings → Inventory & trading → Inventory control
Approval limitsA single person committing or paying large amounts. Above the limit an admin must approve.Settings → Inventory & trading → Approvals and limits
No self-approvalApproving a change you proposed yourself.Settings → Inventory & trading → Approvals and limits
Budget checkApproving a purchase order beyond its cost centre's budget. Off, warn, or block.Settings → Inventory & trading → Approvals and limits
PPN on non-PKP suppliersClaiming input PPN from a supplier who cannot charge it.Supplier record (PKP flag)
Governed agentsAI agents changing data unsupervised.Settings → Access & integrations

For credit control and the bill price check you choose the mode: off, warn (or block for bills), or approval, where the failing document becomes a proposal an admin must approve. Approval is the default and the right choice for most companies: business keeps moving, and every exception has a name and a reason attached.

Controls that need a habit

ControlHabit
Supplier master changesOnly the purchasing owner changes suppliers; finance verifies new bank details by phone to a known number before the first payment.
Payment releaseThe person who prepares the payment run is not the one who releases it in internet banking. Voltrus exports the bulk-transfer file; the bank's own dual authorisation is the second key.
Bank reconciliationReconcile the bank statement at least weekly, by someone who does not post payments.
GRNI reviewMonthly, review goods received but not billed; old items are either missing bills or wrong receipts. The month-end checklist flags old ones.
Manual journalsAnyone can draft; an admin posts. Require a description and supporting document for every one.
Stock countsCount high-value items monthly, everything at least yearly. See Transfers, stock counts and cycle counting.
User access reviewEach quarter, list users and tokens on Users & tokens, deactivate leavers, revoke unused tokens.

A small-company example

A manufacturer with eight office staff sets up:

  • Purchasing clerk and sales admin: agent access. They draft POs and sales orders and submit them.
  • Purchasing manager and sales manager: Ops. They approve their teams' proposals; the system stops them approving their own.
  • Approval limits: purchase orders Rp 25 million, payments Rp 50 million.
  • Finance manager: Admin. Closes periods, posts manual journals, prepares payment runs and approves POs above Rp 25 million.
  • Director: Admin. Approves payment runs above Rp 50 million, releases payments in internet banking, and reviews the audit timeline for supplier changes once a week.
  • External accountant: Viewer.

Nobody can create, approve and pay alone, and the limits route every large commitment to a second, more senior person.

Checklist

  • Assign at least one Admin, decide who gets Ops, and give everyone else agent or Viewer access.
  • Set approval limits for purchase orders, supplier bills and payments that match your signing authority.
  • Keep self-approval at Only when nobody else can approve, or Never once you have two approvers.
  • Set credit control and the bill price check to approval.
  • Close each month in the ledger as soon as it is reported.
  • Schedule a weekly review of high-value documents and supplier changes, and a quarterly access review.

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