Esc

↑↓ move↵ openIndex · Pagefind
Accounting apps / Accounting Access

Accounting Access

Role presets, entity scope, a configurable segregation-of-duties library, access review campaigns and a control register for company books.

On this page

Accounting Access decides who can see and do what in company books, and records the evidence that someone checked. Access is granted separately from project access: a project role never grants accounting rights. Its tabs are Members, Access reviews, Segregation of duties and Control register. Open it from the company app launcher under Accounting > Accounting Access; it appears when your accounting access includes it.

Who uses it
Accounting owners and company admins; designated access reviewers; control owners; auditors with a read-only grant read the control register.
When
Onboarding and offboarding; quarterly or ad hoc access review campaigns; whenever a control objective falls due.
What it holds
Each member’s role preset, permission flags and entity scope; frozen access review snapshots and their decisions; the segregation-of-duties rules; control owners and evidence.

Key workflow

  1. Grant a role. Choose a preset: owner, controller, accountant, AP clerk, AR clerk, payroll admin, project manager view or read-only auditor. Individual flags override the preset.
  2. Limit the scope. Restrict a grant to some entities. A project manager view grant only sees its own projects and is refused entity-wide views.
  3. Check separation of duties. Every grant change is checked against the company’s rules on the person’s effective duties: their own flags plus any approval right a delegation lets them use. A warn conflict saves only with an audited reason; a block conflict is refused, reason or not. The default library includes construction pairs: creating vendors and entering bills with releasing payments, posting with approving journals, payroll setup with releasing payments, and changing vendor bank details with releasing payments. Administering access together with releasing payments is blocked by default.
  4. Tune the library. Change a default rule’s severity, wording or on/off (never its duties), or add your own rules of two to four duties. Each change needs step-up and a reason, and weakening a rule is flagged in the audit log. Raising a rule never strips anyone’s access: the save lists who already holds the combination, and they appear in the conflict report and the next review.
  5. Open an access review campaign. Run it quarterly or ad hoc, for the company or one entity, with a due date, a dormancy threshold (90 days by default) and one or more designated reviewers. Opening it freezes one item per person: role, flags, entity and project scope, expiry, MFA, accounting API tokens (never the token itself), delegations, last accounting activity, a dormant flag and their conflicts. Company administrators and expired grants are listed too.
  6. Decide every item. Keep, modify or revoke each item with a reason, after step-up. Modify and revoke go through the same grant-change path as the Members tab, so entity limits, segregation of duties and the audit trail all apply. Keep records a certification only when the live grant still matches the snapshot. The campaign completes only when every item is decided, and stores its counts.
  7. Record qualified reviews. On Qualified reviews (in the Accounting Admin group), a user who manages access with no entity or project limit registers CPAs, payroll specialists and tax advisors for the policy areas they may sign. A registered reviewer records a sign-off per area, jurisdiction and policy version, which expires after the area’s maximum validity or when its version changes. The page shows which pairs are covered and which are not reviewed.
  8. Keep the control register. The register lists ten control objectives, each with an owner, a frequency (monthly, quarterly, semiannual or annual), a procedure and its evidence. Some evidence is read live, such as completed access review campaigns, close reviews and integrity runs; owners append the rest, such as a recovery rehearsal report. Each objective shows as current, overdue (with days late), no evidence or no owner.

Controls

  • Nobody certifies their own access. The service and a database constraint both refuse it. If a reviewer’s own access is in scope, the campaign needs a second reviewer or cannot be opened.
  • An access review snapshot cannot change after it is taken, and each item is decided once: a database trigger refuses edits, second decisions and deletions. Recorded control evidence is append-only.
  • A delegation that would hand someone a blocked combination of duties is refused.
  • MFA can be required for payment release, vendor banking, payroll PII and grant changes, with an authenticator step-up for sensitive actions.
  • API tokens need the explicit accounting step-up scope for sensitive actions; an unscoped token is not enough.
  • Every grant change, review step, rule change, owner change and evidence record is audited.

Current boundaries

For the full procedure, exceptions and examples, read the Security and controls workflow guide.

API operations

26 operations · 12 read · 14 write · base path /rest/v1.0/companies/{company_id}/accounting

  1. GET /access_reviewsList access review campaigns
  2. POST /access_reviewsOpen an access review campaign
  3. GET /access_reviews/{id}Get an access review campaign with its snapshot
  4. POST /access_reviews/{id}/cancelCancel an access review campaign
  5. POST /access_reviews/{id}/completeComplete an access review campaign
  6. POST /access_reviews/{id}/items/{item_id}/decisionDecide one access review item
  7. GET /compliance/policy_areasPolicy areas and their qualified sign-off status
  8. GET /compliance/reviewersList registered qualified reviewers
  9. POST /compliance/reviewersRegister a qualified reviewer
  10. POST /compliance/reviewers/{id}/revokeRevoke a qualified reviewer registration
  11. GET /compliance/signoffsList qualified sign-offs
  12. POST /compliance/signoffsRecord a qualified sign-off
  13. GET /compliance/signoffs/{id}Show a qualified sign-off
  14. GET /compliance/signoffs/{id}/attachmentsList evidence on a qualified sign-off
  15. POST /compliance/signoffs/{id}/attachmentsAttach evidence to a qualified sign-off
  16. POST /compliance/signoffs/{id}/revokeRevoke a qualified sign-off
  17. GET /control_objectivesSOC 1 control register
  18. GET /control_objectives/{objective_key}Get a control objective with its evidence
  19. PUT /control_objectives/{objective_key}Assign a control objective's owner and frequency
  20. POST /control_objectives/{objective_key}/evidenceRecord control evidence
  21. GET /grantsList accounting access
  22. PATCH /grants/{id}Set a member's accounting access
  23. POST /grants/access_reviewCertify an access review
  24. GET /sod_conflictsSegregation of duties conflict report
  25. GET /sod_rulesList segregation of duties rules
  26. PUT /sod_rules/{rule_key}Create or change a segregation of duties rule

Parameters, request and response fields, errors and a generated example for each operation are in the REST reference for this app. Read scopes, step-up and permissions in the Accounting API guide.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file