Frequently asked questions

Register your organization, choose a workspace slug, and sign in within minutes. Then onboard vendors, employees, and policies at your own pace.

No. ProcureDesk runs in the browser. Point NEXT_PUBLIC_API_URL at your backend (or use our hosted API) and your team signs in with workspace slug + email.

Yes. Organization settings support logo, primary colors, and sidebar styling so the workspace reflects your company identity.

Procurement teams, finance, operations, compliance, and vendors who need one transparent procure-to-pay system—not email and spreadsheets.

Yes. The platform acts as a neutral liaison: structured communication, standardized documents, and shared status for both sides.

Quotations, invoices, payment receipts, and optional purchase orders—using your templates and tied to the underlying request or contract.

It is your procurement command layer—standardizing P2P while complementing ERP, accounting, and inventory systems you already run.

Organization, Procurement, Inventory, Accounting, Governance, and Analytics—opened from one home grid with per-app sidebar menus.

Every significant action is recorded with user, timestamp, and record context. Approvals, documents, and payments link back to a single transaction story.

Each workspace is scoped at the API and session layer. Users authenticate to one tenant; cross-tenant access is blocked by design.

Yes. Governance includes roles, policies, approval limits, and an audit trail—see the Security page for more detail.

Yes. Payment gateways, accounting exports, analytics, and inventory workflows can be rolled out in phases. Talk to us about your integration map.

The backend exposes versioned REST endpoints for auth, tenants, organization, and procurement operations—suitable for custom integrations.

AI-assisted vendor recommendations, deeper payment gateway integration, and expanded mobile access—without changing the core P2P model.