Cross-module workflow
Lead to Cash
A captured lead converts to an account and opportunity, progresses through a governed pipeline, becomes a publicly accepted quotation, converts to a credit-checked order, and posts a customer invoice.
- 01
Trigger
- 02
Work
- 03
Govern
- 04
Outcome
What it is
Lead to Cash is Vercentlabs ERP's real, cited sequence connecting CRM, Sales, and Accounting — the same system carries a captured lead through a publicly accepted quotation to a posted customer invoice, with no re-typed handoff between the three modules.
Execution sequence
- Steps
- 08
- Modules
- 03
- Approvals
- 02
The real sequence, step by step
The runbook shows trigger, participants, each module handoff, approvals, automated actions, exceptions, visibility and business value in one continuous operating document.
Trigger
A lead is captured from a public form, an import, or a signed webhook.
Participants
Sales rep · Sales approver (for over-threshold quotations) · Buyer (customer) · Finance/billing
- Capture and scoreCRM
The lead lands with source and campaign attribution intact, and is scored and SLA-tracked automatically.
- Qualify and convertCRM
Playbook-gated pipeline stage exit; one action creates the account, contact, and opportunity together.
- Build the quotationSales
A GST-aware quotation is seeded from the won opportunity, with automatic CGST/SGST vs. IGST tax splitting by state.
- ApproveSales
Under-threshold quotations auto-approve; over-threshold quotations route to an approval request.
- Accept publiclySales
The customer accepts or rejects via a public, single-use, hashed share link with a typed digital signature — no login required.
- Convert to orderSales
The accepted quotation converts to a sales order through an idempotent promotion — no duplicate orders on retry.
- Credit check and confirmSales
The order is checked against real-time aggregated customer credit exposure, under an advisory database lock, before confirmation.
- InvoiceAccounting
A customer invoice is generated from the confirmed order through an auditable, idempotent handoff.
Approvals
- 01Quotations above the approval threshold route to a designated sales approver, not an open-ended email thread.
- 02Order confirmation is blocked outright if the customer's credit check fails.
Automated actions
- 01Lead scoring and SLA due-date calculation
- 02Threshold-based quotation auto-approval
- 03Real-time aggregated credit-exposure check
- 04Idempotent invoice generation from the confirmed order
Exceptions & honest limits
- 01A quotation revision automatically cancels any pending approval on the prior version, so a stale draft can't get approved by accident.
- 02An order that would exceed the customer's credit exposure is held at confirmation, not silently accepted and discovered later at collection.
Visibility
- 01CRM's pipeline and forecast reports show stage-by-stage conversion by rep and team.
- 02Sales' quotation-conversion, expiring-quotations, and pending-approvals reports.
- 03Every quotation and order action writes an immutable, timestamped event row.
Business value
- 01A qualified lead reaches an invoiced order without a single re-typed handoff between CRM, Sales, and Accounting.
- 02Self-service, signature-backed quote acceptance removes a phone-tag round trip from the sales cycle.
- 03Credit risk is checked before commitment, not discovered at collection.
Handoff map
Every module involved, in operating order.
The workflow is deliberately shown as a chain of responsibility rather than a bag of features.
Buyer questions
Questions buyers ask about this runbook
Direct answers about how the sequence behaves, where controls sit and what a real deployment should expect.
Does confirming an order automatically deduct inventory?
Not for a standard sales order today — only Manufacturing and Point of Sale currently write to the stock ledger. Order lines carry a warehouse reference so fulfilment sees the same records, but the stock deduction itself is a separate, not-yet-automated step. See the Order to Fulfilment workflow for the honest detail.
What happens if a customer rejects the quotation instead of accepting it?
The public decision page records the rejection the same way it records acceptance — through the real API, with the event logged — rather than the quotation just sitting unresolved with no record of the outcome.
Is the credit check a hard block or just a warning?
It's enforced at order confirmation under an advisory database lock — an order that would exceed the customer's real-time aggregated credit exposure is blocked at that point, not flagged for someone to notice later.
Related runbooks