Requirements
REFERENCE / VERIFIEDA structured, filterable checklist built from Vercentlabs' retained 991-requirement capability model — usable as a neutral evaluation framework for any ERP decision, not just this one.
70
capability groups / 991 source requirements
This checklist is organised by module and platform capability area, mirroring the real structure of an ERP evaluation — not a flat, undifferentiated list. Use the filter below to focus on one module or capability area at a time, or work through the full list. Checking an item marks it for your own reference only; nothing is transmitted anywhere, and nothing requires an account or a form.
This is a genuinely reusable evaluation framework: the module/capability breakdown below reflects real ERP domains (CRM, sales, accounting, procurement, inventory, manufacturing, and more), so it's structured to be useful whether or not Vercentlabs ends up being the right fit.
Progress stays in this browser. Nothing you check is transmitted.
The ledger core — draft, approve, and post, with the year-end close computed automatically.
See how Vercentlabs implements this →Accounting
Customer invoices, generated from Sales, and the aging/collections work that follows.
See how Vercentlabs implements this →Accounting
Vendor bills that can only be created once they're actually matched.
See how Vercentlabs implements this →Accounting
Bringing the bank statement and the ledger into agreement.
See how Vercentlabs implements this →Accounting
A GL-mapped depreciation subledger — a separate data model from the EAM Assets module (see Honest Limitations).
See how Vercentlabs implements this →Accounting
India-specific tax compliance as part of the ledger, not a bolt-on.
See how Vercentlabs implements this →Accounting
The governed monthly close, plus multi-entity planning.
See how Vercentlabs implements this →Accounting
The governed path from a request to an issued purchase order.
See how Vercentlabs implements this →Procurement
Choosing and qualifying who you buy from.
See how Vercentlabs implements this →Procurement
What arrives gets checked against what was ordered before a bill can move forward.
See how Vercentlabs implements this →Procurement
Live visibility into what's blocking the chain, and a defensible record of every exception.
See how Vercentlabs implements this →Procurement
A 12-report registry covering spend, risk, and cycle time.
See how Vercentlabs implements this →Procurement
How a quotation gets its price and tax figures — automatically, not by memory.
See how Vercentlabs implements this →Sales
Discounts and terms that cross a threshold don't just go out the door.
See how Vercentlabs implements this →Sales
From an accepted quote to a confirmed, shippable order.
See how Vercentlabs implements this →Sales
The auditable bridge from a confirmed order to a posted Accounting invoice.
See how Vercentlabs implements this →Sales
A customer can accept or reject a quotation without a login.
See how Vercentlabs implements this →Sales
The governed spine of the module: leads convert to accounts, contacts, and opportunities in one step, and pipeline stages can't be skipped without qualification.
See how Vercentlabs implements this →CRM
How leads get in, get scored, and get worked before a human ever touches them.
See how Vercentlabs implements this →CRM
Every touchpoint with a prospect stays attached to their record instead of living in someone's personal inbox.
See how Vercentlabs implements this →CRM
The core of the module — a race-safe, row-locked movement ledger.
See how Vercentlabs implements this →Stock
Every way stock changes, each permission-gated.
See how Vercentlabs implements this →Stock
How the stock value on the books is calculated.
See how Vercentlabs implements this →Stock
Following a unit through its life, and knowing when to reorder it.
See how Vercentlabs implements this →Stock
Stock
The versioned product structure production is built against.
See how Vercentlabs implements this →Manufacturing
The sequence of operations and where they happen.
See how Vercentlabs implements this →Manufacturing
From plan to completed production, with materials and operations locked in at release.
See how Vercentlabs implements this →Manufacturing
Where the shop floor becomes a real, auditable inventory transaction.
See how Vercentlabs implements this →Manufacturing
Forward visibility instead of reacting to a stoppage.
See how Vercentlabs implements this →Manufacturing
Knowing what a work order actually costs, not just what it was planned to cost.
See how Vercentlabs implements this →Manufacturing
How a project is defined and connected to the commercial record that funds it.
See how Vercentlabs implements this →Projects
Breaking the project into trackable pieces.
See how Vercentlabs implements this →Projects
The raw actuals that feed cost and billing.
See how Vercentlabs implements this →Projects
Projects
The live financial picture of the project.
See how Vercentlabs implements this →Projects
The core record of what you own and how it's classified.
See how Vercentlabs implements this →Assets
Moving an asset from draft to available, with a governance guard.
See how Vercentlabs implements this →Assets
Who currently has the asset, enforced as a single source of truth.
See how Vercentlabs implements this →Assets
Planned and reactive maintenance with real cost capture.
See how Vercentlabs implements this →Assets
Retiring an asset with a computed, auditable financial outcome.
See how Vercentlabs implements this →Assets
The data model exists; today these are read-only views, not a create workflow — an honest, current limitation.
See how Vercentlabs implements this →Assets
Point of Sale
Controlling who's operating a terminal and reconciling the drawer.
See how Vercentlabs implements this →Point of Sale
Handling a return without losing control.
See how Vercentlabs implements this →Point of Sale
Configuring how a store and its terminals operate.
See how Vercentlabs implements this →Point of Sale
Point of Sale
Reusable inspection definitions typed by where they apply.
See how Vercentlabs implements this →Quality
Where the segregation-of-duties control actually lives.
See how Vercentlabs implements this →Quality
What happens automatically when something fails.
See how Vercentlabs implements this →Quality
Turning a defect into a tracked, verified fix.
See how Vercentlabs implements this →Quality
Holding suppliers accountable with structured evidence.
See how Vercentlabs implements this →Quality
Quality
How a ticket moves from open to genuinely resolved.
See how Vercentlabs implements this →Support
Support
Named policies that actually reflect business reality.
See how Vercentlabs implements this →Support
Keeping the conversation and the internal notes both in context.
See how Vercentlabs implements this →Support
Reusable answers, versioned and published deliberately.
See how Vercentlabs implements this →Support
The schema exists; automated escalation triggering is not yet live — an honest current limitation.
See how Vercentlabs implements this →Support
The organizational scaffolding employee records sit inside.
See how Vercentlabs implements this →HR & Payroll
Daily attendance and leave, kept in sync automatically.
See how Vercentlabs implements this →HR & Payroll
Pay structure and India-specific statutory compliance.
See how Vercentlabs implements this →HR & Payroll
The governed run itself, from draft to posted.
See how Vercentlabs implements this →HR & Payroll
Expense records, exposed through the generic resource API.
See how Vercentlabs implements this →HR & Payroll
Organizations, companies, branches, departments, cost centers, and teams with granular, membership-scoped access — company, branch, or department, not all-or-nothing.
See how Vercentlabs implements this →Platform Architecture
12 seeded system roles, time-bound role assignments with start/expiry dates, and framework-neutral permission-key packages per module.
See how Vercentlabs implements this →Security & Governance
A generic approval-requests system plus a governed command registry with reusable decision and separation-of-duties primitives, reused across Accounting, Sales, CRM, HR, Assets, Projects, POS, and Support.
See how Vercentlabs implements this →Workflow Automation
A database trigger makes the audit table immutable — UPDATE/DELETE are rejected at the Postgres level, not just the application level.
See how Vercentlabs implements this →Security & Governance
Injection-safe CSV export with hard-capped pagination; MIME/size-allow-listed, SHA-256-hashed, quarantine-lifecycle document storage; India-default localization (en-IN, Asia/Kolkata, INR, April-start fiscal year).
See how Vercentlabs implements this →Reporting & Analytics
Device-bound mobile authentication (fingerprint-required login, secure-store tokens, biometric re-lock after 15 seconds background) and an idempotent, HMAC-verified, replay-protected subscription billing webhook pipeline.
See how Vercentlabs implements this →Mobile ERP
Yes — your checked items are saved to your browser's local storage, not to a server, so they persist across visits on the same device and browser but are never visible to Vercentlabs or transmitted anywhere.
Yes — the Print button opens your browser's print dialog with a layout suited for printing; the filter and checkbox controls are hidden in the printed version so you get the clean requirement list.
This checklist operates at the same capability-group granularity Vercentlabs' own module pages use — 70 groups summing to 991 documented requirements — rather than presenting each requirement as a separate feature claim.
See it on your workflow
30-minute working session