What should a CRM–ERP handoff test include?
Use a controlled order to check customer identity, document lines, stock choices, payment allocations, interrupted requests and permissions. Inspect supporting records, not only screen labels.
Six practical checks for customer identity, sales documents, stock, payments, interrupted requests and permissions—using evidence rather than a feature-list promise.
A CRM–ERP handoff is ready when another person can continue the work from the supporting records, without asking the first person to reconstruct the order. A shared customer name or a green integration status is not enough. Quantities, identity, document links, payment allocation and access must remain understandable when something changes.
This checklist answers the practical question behind CRM and ERP data ownership: how do you prove that the boundary works? It is for evaluating a connected workspace or an integration between separate products. It does not assume that Oxapher provides a connector to every other product. The CRM versus ERP comparison explains the categories; the ownership worksheet assigns responsibility. Here, the output is evidence from a controlled test.
Use an evaluation workspace with fictitious parties and no live messaging or payment collection. Give the tester the role they would actually use. An owner account can hide permission problems that stop ordinary staff.
Start with a fictional customer ordering ten units of an item at ₹100 each before tax. Record the intended customer, billing address, delivery address, item, unit, quantity and document reference. Use your configured tax rules; this example does not prescribe a GST rate or treatment. Write down the expected result before pressing Save.
Keep a short evidence sheet: scenario, source reference, expected result, observed result, tester role, time and unresolved exception. A screenshot helps explain a failure, but the underlying records establish whether the transaction is correct. Do not copy real customer identities into a publicly shared test report.
Create the inquiry or quotation using the existing customer reference. Ask a second tester to locate it from the next step. A matching display name alone is insufficient: two customers can have similar names, and one customer can have multiple addresses.
Now change the contact phone or add a separate delivery address. Check which value the next document proposes and whether a user can distinguish billing from delivery. The desired result is an intentional selection, not a silent replacement of the billing identity with the latest contact detail.
Record which customer fields are shared and which document details are snapshots. Agree how a correction affects future documents and how already issued documents are handled. Do not assume editing the master should rewrite every historical document.
Follow the supported path from quotation to the next relevant sales document. Check each item reference, unit, quantity, price, discount, tax context and customer-facing note. Check delivery and billing details separately. An internal comment must not become customer-visible merely because a document was converted.
Change the accepted quantity from ten to eight before the next step. The tester should be able to explain which document is current, how the change is represented and what happens to the earlier reference. Converting twice must not quietly create two orders that staff mistake for one.
This is not a requirement to launch every document type. Test the types your team actually uses. Oxapher supports quotations, proformas, sales orders and sales invoices; use the quotation workflow to decide which handoff belongs in your pilot.
An invoice and the movement of physical goods are related events, but they need not happen at the same moment. Test your supported receive/dispatch choice and inspect the resulting stock entries. The expected quantity must follow the choice made, rather than an assumption that every document immediately moves goods.
Include a partial delivery or receipt if your process supports it. Ask the tester to find what remains to be fulfilled. Refresh or reopen the document and confirm that displaying it again does not create another stock movement.
For a purchasing workflow, repeat the boundary with a supplier and the relevant purchase document. Do not treat a sales demonstration as proof that purchasing works identically. The purchase-order overview describes the separate workflow context.
In the fictitious example, record an advance of ₹300 using the supported receipt workflow, then prepare the related invoice. Inspect where the receipt is allocated. An amount displayed as paid is not enough: the receipt and the remaining balance must refer to the same customer and intended document.
If the invoice total is T and the only valid allocation is ₹300, the invoice's remaining balance should reconcile to T minus ₹300. Keep the original invoice amount separate from current paid and outstanding amounts. Add a second invoice for the same fictitious customer and confirm that the first receipt has not reduced both invoices.
Also test an unallocated advance and a partial allocation. The total of allocations plus the remaining unallocated amount must reconcile to the receipt. A quotation or proforma payment request is not evidence of a completed receipt. Use the accounts-receivable workflow to inspect the supporting collection context.
In an isolated test environment, interrupt a supported save or conversion and inspect the result before retrying. The user needs a clear success, failure or recoverable state. An endless spinner with no way to identify whether an invoice exists creates a duplicate-entry risk.
For separate systems, have the integration owner demonstrate a delayed or failed transfer and its recovery. For a combined workspace, test a failed request and reopen the existing record. The acceptance question is the same: can staff find the authoritative result without creating a second financial or stock effect?
Do not simulate interruptions by stopping a production server or repeatedly submitting live invoices. Fault testing belongs in a controlled environment with synthetic data.
Repeat the handoff with a role that can prepare commercial documents but cannot change accounting configuration. Verify both the visible controls and the response to an attempted restricted action. Hiding a navigation link is not proof that the underlying operation is denied.
If you use multiple companies or branches, include two records with similar names in different scopes. Confirm the selected company, permitted branch and currency before comparing totals. A combined view must not turn access to one company's customer into access to another company's records.
HRMS is a separate permission boundary. An employee's attendance or payroll information should not become visible to a sales tester just because both areas share a workspace. Include HRMS in this test only when the workforce handoff is in scope.
A useful completion rule is simple: the intended user can find the source, explain the current state and reconcile the result after an exception. List failures explicitly rather than averaging them into a dashboard score.
Before expanding, require a named owner for each unresolved issue and a retest of the same scenario after correction. Keep the exception records in the evaluation workspace. A new demonstration using only easy data does not establish that the original failure is fixed.
Oxapher connects CRM and sales, ERP and accounts, inventory and purchasing, manufacturing, and optional HRMS. Review the connected workflow overview, then start an Oxapher workspace to evaluate the boundaries that matter to your team. The current offer provides one-time 21-day free access; HRMS inclusion, paid add-on eligibility and other limits depend on the plan. Check the live public catalog and current signup offer rather than assuming every product area is included in every plan.
Use a controlled order to check customer identity, document lines, stock choices, payment allocations, interrupted requests and permissions. Inspect supporting records, not only screen labels.
Test the receive or dispatch choice supported by the selected workflow. Invoicing and goods movement may occur at different times; inspect the actual stock entries.
Reconcile the receipt, its document allocations and any unallocated remainder. Keep the original invoice total distinct from the current paid and outstanding balances.