Provider evidence

After an instruction is approved, the Credit Officer can submit it to the provider. The instruction keeps the provider’s identifier, while the operation receipt keeps the stable operation key, expected revision, result state and effect references. Those records let the team distinguish an attempted action from one whose effect is known. A pending receipt needs investigation before anyone repeats an external request.

Provider statements, confirmations, settlement notices and corrections are recorded as evidence against the parent instruction. Each event may carry a provider event identifier, amount, receipt time and verified flag. A confirmation is useful only when the event can be attributed to the right instruction and its contents checked. The instruction reaches confirmed status on verified provider confirmation or settlement evidence.

• Submission identity. Keep the provider instruction identifier with the instruction and the operation key with its receipt.
• Supporting files. Store documents with title, uploader, upload time and visibility on the parent instruction.
• Provider events. Record the event type, amount, provider identity and verification result before treating an outcome as final.

Agree which provider system sends or receives instructions and which team member owns its connection. Define how provider instruction and event identifiers are captured, including retries or delayed responses. The external reference belongs to the operation that actually used the provider. If an operation was local, the team should inspect local records first rather than ask the provider for an event it never created.

Specify who verifies a provider statement and what document or source response supports that verification. Decide when attachments may be marked shared and who should see internal material. For a settlement notice received after the requested value date, keep its actual receipt time and amount; do not backdate the evidence to make the instruction appear timely.

Select an approved instruction with its reviewer decision and supporting attachment. Submit it through the agreed provider connection, retain the provider instruction identifier and inspect the resulting operation receipt. When the provider response is pending, keep the instruction visible in the provider submissions queue. A repeated request with the same operation key should be investigated against the existing receipt before any new execution.

Next, enter a provider confirmation and mark it verified only after checking the event identity, parent instruction and amount. Confirm that the instruction’s final state follows that evidence. If the response contradicts the requested scope, record the discrepancy and route it for review. A statement or correction may add useful history without proving that settlement completed.

• Provider submissions — Submitted and pending instructions with provider identifiers and dates.
• Provider evidence to verify — Incoming events that still need a person to check the source and amount.
• Operation exceptions — Failed or review-needed receipts with their reasons and parent instructions.

Follow provider outcome, then settlement reconciliation to verify the claimed effect.