Provider execution

Once an instruction is authorized, the Provider Coordinator sends its stable identity through the approved provider path. The instruction retains the external instruction identity and provider reference. Submission is an attempt, not proof of execution. The team waits for the provider’s actual receipt and evidence, then compares them with the authorized scope.

Each evidence line names its parent instruction, revision, provider event, occurrence time, executed quantity, price and fees. A unique provider event should not be counted twice. The provider coordinator verifies the source account, instrument, quantity and fees before marking evidence verified. Conflicts or rejected evidence go to review. Only authoritative evidence satisfying the required scope supports confirmation of the instruction.

• Authorized submission. The coordinator works from instructions already approved for the current revision and preserves the provider’s external reference.
• Event verification. Each provider event is checked against the original instruction and its expected scope before its evidence is accepted.
• Confirmed outcome. The instruction becomes confirmed only when required scope is satisfied by authoritative evidence, rather than by a local submission status.

Identify the provider connection and the owner of its acknowledgments. Agree how the external instruction identity is carried across retries, how provider event IDs are deduplicated and which source owns the account and execution facts. Define the required scope for a complete instruction, including how quantity and fees are interpreted. The local evidence line should preserve what the provider returned so reconciliation can explain a difference.

Set an exception path for unknown transport outcomes. A timed out request may have reached the provider. The team reads the operation receipt and external reference before any new attempt. Where the effect cannot be established, leave the receipt needing review and have the accountable person investigate at the provider.

A reviewed property operation is submitted once with its approved identity. The provider returns an event showing partial execution, an executed quantity and fees. The coordinator links that event to the instruction and verifies it against the source. The instruction stays pending while the remaining required scope is unresolved. A later unique provider event can complete the picture; then the owner can confirm the instruction.

Rehearse a duplicate event ID. It must not create an extra counted execution. Rehearse an event with a different instrument or an unexpected fee. It should be rejected or sent for investigation, while the original instruction and provider evidence remain available for the reviewer. The Operations Overview helps the team find such exceptions, but the provider’s evidence decides the result.

• Execution evidence to verify — Provider lines awaiting comparison with their parent instructions.
• Pending provider response — Submitted requests without a confirmed authoritative outcome.
• Rejected execution evidence — Conflicting provider lines that need investigation.

Verify provider execution and reconcile uncertain outcomes.