Lead Management is where ERP discipline either begins or breaks.
Lead Capture and Qualification looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: ≥90% of qualified leads converted within 24 hours of qualification; source attribution preserved for pipeline reporting; duplicate contact creation rate <2%
The control flow a finance team actually needs.
Step 1
Auto-Deduplication Against Existing...
Step 2
Lead Scoring Rules Configurable By...
Step 3
Mandatory Disqualification Reason On...
Step 4
Conversion Creates Opportunity With...
Step 5
End-To-End Conversion Time Tracked
The ERP surface involved.
Module
Lead Management
Actors
Marketing System, SDR (Sales Development Rep), Lead Scoring Engine
Tier
Tier 3
Finance area
Sales, CRM & Customer Management
Region lens
US and UK finance teams
Publication date
May 19, 2026
Auto-deduplication against existing contacts and accounts on email/phone; lead scoring rules configurable by admins without code; mandatory disqualification reason on rejection; conversion creates opportunity with inherited lead source; end-to-end conversion time tracked; lead assignment respects territory rules; GDPR consent flag carried through conversion
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Auto-deduplication against existing contacts and accounts on email/phone | Given a marketing system with active campaigns |
| Control 2 | lead scoring rules configurable by admins without code | when a web form submission arrives with UTM parameters, then a lead record is created with source attribution, a numeric score assigned by the scoring engine, and the lead appears in the SDR queue sorted by score |
| Control 3 | mandatory disqualification reason on rejection | when the SDR qualifies the lead, then opportunity, contact, and account records are created inheriting lead source and score history |
| Control 4 | conversion creates opportunity with inherited lead source | negative) when a duplicate email already exists on an active contact, then the system surfaces the match for review before creating a new record and returns a 409 conflict with error code DUPLICATE_LEAD_DETECTED. |
| Control 5 | end-to-end conversion time tracked | ≥90% of qualified leads converted within 24 hours of qualification; source attribution preserved for pipeline reporting; duplicate contact creation rate <2% |
| Control 6 | lead assignment respects territory rules | ≥90% of qualified leads converted within 24 hours of qualification; source attribution preserved for pipeline reporting; duplicate contact creation rate <2% |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | An inbound inquiry arrives via web form, email, or marketing campaign integration and is automatically created as a lead record with source attribution. The lead scoring engine evaluates firmographic and behavioral signals and assigns a numeric score. An SDR reviews the queue sorted by score, researches the account, and either qualifies the lead into an opportunity or disqualifies it with a reason code. Qualified leads convert to opportunity, contact, and account records, preserving the original source and score history. |
| Control rules | Auto-deduplication against existing contacts and accounts on email/phone; lead scoring rules configurable by admins without code; mandatory disqualification reason on rejection; conversion creates opportunity with inherited lead source; end-to-end conversion time tracked; lead assignment respects territory rules; GDPR consent flag carried through conversion |
| Acceptance proof | Given a marketing system with active campaigns; when a web form submission arrives with UTM parameters, then a lead record is created with source attribution, a numeric score assigned by the scoring engine, and the lead appears in the SDR queue sorted by score; when the SDR qualifies the lead, then opportunity, contact, and account records are created inheriting lead source and score history; (negative) when a duplicate email already exists on an active contact, then the system surfaces the match for review before creating a new record and returns a 409 conflict with error code DUPLICATE_LEAD_DETECTED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`lead` { id: string (lead_*), external_id: string, source: string, utm_campaign: string, score: int, status: enum(NEW, NURTURE, QUALIFIED, DISQUALIFIED), gdpr_consent: bool, disqualification_reason: string, converted_at: timestamp, created_at: timestamp, currency_code: char(3) }; converts to `opportunity`, `contact`, `account` on qualification; (reference, product may differ).API and events
`POST /v1/leads` { external_id, source, utm_campaign, email, phone, company_name, gdpr_consent } -> 201 { id, score, status }; `PATCH /v1/leads/{id}` { status, disqualification_reason } -> 200; `POST /v1/leads/{id}/convert` -> 201 { opportunity_id, contact_id, account_id }; `GET /v1/leads/{id}`; emits `lead.qualified` and `lead.converted` events; idempotent via `external_id`.State transitions
`NEW -> NURTURE -> QUALIFIED -> CONVERTED`; terminal `DISQUALIFIED`; guard: DISQUALIFIED requires non-null disqualification_reason; CONVERTED requires prior QUALIFIED status; re-qualification of DISQUALIFIED is blocked without manager override.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.