Procurement Reference Public

Daily Operations

The routine operating manual for staff who run Procurement day to day — the core screens, records, and workflows to use once setup is complete.

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-22 Estimated time: 2 min 1 views
User Manual

Daily Operations

The routine operating manual for staff who use Procurement after setup is complete.

Slug: procurementVersion: 1.0.0Category: ProcurementReviewed: 2026-07-11

Main Workspaces

Procurement

Use this sidebar area for the module workflow associated with Procurement.

Purchase Orders

Use this sidebar area for the module workflow associated with Purchase Orders.

Purchase Returns

Use this sidebar area for the module workflow associated with Purchase Returns.

Vendors

Use this sidebar area for the module workflow associated with Vendors.

Vendor Groups

Use this sidebar area for the module workflow associated with Vendor Groups.

Purchases Journal

Use this sidebar area for the module workflow associated with Purchases Journal.

Bir Form 2307

Use this sidebar area for the module workflow associated with Bir Form 2307.

Atc Codes

Use this sidebar area for the module workflow associated with Atc Codes.

Standard Operating Procedure

  1. Open the module workspace from the sidebar or the route your team normally uses.
  2. Search or filter before creating a new record so duplicate records are not introduced.
  3. Open the create form, fill required fields, attach supporting information when the workflow expects evidence, then save.
  4. Review the saved record from the detail or list view and confirm ownership, dates, status, and linked records.
  5. Move the record through the next workflow step only when the supporting data is complete.
  6. Use reports, dashboards, or export screens for review rather than manually editing calculated totals.

Record Handling Rules

Create carefully

Use one source document or one real-world event per record. Avoid bundling unrelated items into a single record just to save time.

Review before action

Check status, ownership, dates, amounts, attachments, and related records before approving, publishing, posting, or closing.

Use update actions intentionally

If the module has separate approve, issue, post, sync, export, or close actions, use those instead of editing database-style fields directly.

Keep auditability

Prefer correcting records with comments, revisions, status changes, or replacement files so the business history remains understandable.

Daily Quality Review

  • New records have clear owners, dates, statuses, and related records.
  • Required documents, comments, attachments, or references are added before approval or closing.
  • List filters and report date ranges match the period being reviewed.
  • Users can only see and act on records appropriate to their role.
  • API data matches the intended tenant, permissions, filters, and response schema.
Was this guide helpful?

Report a content problem