Build your pipeline. Grow your customer relationships.

Qualify

Review the customer need and supporting evidence before opening the opportunity.

Negotiate

Check the final pricing and contract terms before asking the customer to accept.

Quote approvals

MigrationBatches imports source namespaces, cutoff watermarks, original IDs/hashes and reviewed maps. Two-pass identity resolution handles Users/Managers/Territories/CommissionPlans and all child parents. The supported receivable baseline loads original gross invoice/credit/receipt amounts plus exact effective historical applications once; never load already-net outstanding and deduct the same history again. Explicit baseline fields are reconciled summaries of MigrationHistory rows, with only Native effects added afterward; MigrationItems retains partial ordered/fulfilled/billed/cash/credit amounts, accepted versions, source owner/territory and current remaining scope. Historic ClosedWon/Active/Paid/Sent records are nonposting evidence and must not generate new commissions, orders, invoices, renewals, messages or payouts. Already pending/uncertain external requests retain their identifiers/reservations for reconciliation before new actions. Sales Manager, AR Clerk and Marketing Manager independently review their commercial/financial/suppression totals and representative lifecycle cases before activation. Every guarded action validates actual user, entity, parent ownership, eligible role, effective policy, source version, amount/currency and conflict rules within the same atomic transaction as any reservation or effect. Qualification and known within-threshold quote self-release are explicit Sales Rep decisions; final contract, technical exception, protected master, bulk campaign, commission statement and payout decisions follow their independent-owner rules. Approved/accepted/issued/paid data is immutable; a successor version invalidates stale pending authority and unsent intents while retaining executed evidence. This specification states requirements to implement and test, not verified runtime behavior. All money records name currency and basis. CurrencyRecord is authoritative where the original selector remains; it cannot disagree with the selected code. Missing rate, tax, authority, configuration, recipient identity or source proof blocks the dependent action. Rounding applies at the approved precision and final allocation remainder only; a substantial discrepancy is review, not rounding. Net offer/contract/billing values exclude tax; tax-inclusive source prices must be normalised to net with explicit tax evidence before final commercial approval. Subscription term end is exclusive; cadence/proration must reconcile accepted total, cycle totals and invoices. Usage beyond an accepted minimum bills only validated measured scope under the agreed price policy. Forecast, quota, attribution and commission snapshots retain dated conversions instead of using today's rate. Receipts, cash applications, credits and refunds are separate. A ReversalOf record consumes a bounded remaining portion of its original effect and never counts as another forward application/allocation/fulfilment. Net balances retain the original contribution and subtract each effective compensation once; do not both exclude an original by its Reversed display state and subtract the same reversal again. Partial and repeated reversal claims use current source version and remaining scope. Credits on a paid invoice preserve cash history; cross-currency applications preserve both cash and document quantities and external accounting settlement evidence. An application reversal releases its claim without implying money left the bank; a bank return/refund requires its own evidenced cash effect. No reserved amount may be used by concurrent invoice/credit/refund/payout operations. Reversing fulfilment/usage/accepted scope requires downstream billing/credit/commission resolution and cannot erase what was delivered or paid. CRM does not maintain a general ledger, payroll salary engine or unrestricted bank-payment rail merely because it stores payout and receivable records. Suppression is evaluated on canonical recipient identity and all applicable lead/contact/merge aliases. Exactly one live recipient target is required per member/message, and historical snapshots retain prior identity. Conversion, new owner or record merge cannot clear restrictive preferences. A new version or queued replay cannot send a message without current authority and dispatch-time checks. Provider opens/clicks remain observed signals, deduplicated and aged under policy, rather than proof of purchase intent.