Systems and connections

• Portfolio and custody systems. Configure the source of the household’s assets snapshot, including its USD basis and the supporting content the reviewer will inspect. Portfolio positions and investment execution remain in their responsible systems.
• Document and signature systems. If customer acceptance or review material comes from another system, agree how it reaches the opportunity’s attachments and how the team confirms the document belongs to the intended household. Test access to internal and shared material.
• Email and calendar systems. Configure any connection that creates relationship activities. Match the intended opportunity and preserve a useful activity outcome. Agree how repeat delivery is detected before enabling an import.
• Billing and accounting systems. Define the handoff for an accepted engagement if finance needs it. A Won opportunity does not itself create an invoice, payment or financial posting. The receiving system owns the actual financial result.
• Authoritative operation sources. When an operation receipt carries an external reference, name the source that can confirm its outcome and the person responsible for investigating a mismatch.

Treat each connection as setup work with a named owner, identity mapping and a rehearsal case. Keep credentials in the connection configuration and restrict access to the authorized organization. Compare a source result with the opportunity and its receipt before considering the action complete. An unavailable external source leaves an exception to investigate; it does not authorize a guessed result.

Start with the connection needed for the pilot assessment. Check its ordinary result, repeated delivery and unavailable-source case before expanding. Follow operation reconciliation when evidence disagrees.