Provider evidence

A provider reports that an instruction was received and later sends a confirmation. Operations records the provider event identifier, occurrence date, amount and evidence type on the parent instruction. A supporting file can be attached with an internal or shared visibility choice and the team member who uploaded it. The reviewer checks the actual confirmation or settlement evidence before the instruction is treated as confirmed.

• Attach the source. Operations Analyst links the provider event and any supporting file to the instruction that prompted it.
• Check authority. Independent Finance Reviewer distinguishes an acknowledgment from verified confirmation or settlement evidence.
• Keep corrections. Preserve the earlier event and its later correction so the outcome can be reconstructed.

Agree which provider messages are authoritative for submission and which are authoritative for final confirmation. Establish how corrections are retained alongside earlier messages, including a changed amount or event date. Decide which supporting files may be shared and who can see internal material. Provider identifiers should remain stable through reconciliation so a repeated message is recognized as the same event.

Take a submitted instruction with a provider acknowledgment but no confirmed effect. Leave the outcome open while the team checks the provider. Add a verified confirmation with the event date and amount, then trace it to the instruction and receipt. Add a correction and make sure the earlier evidence is still visible. A receipt that claims completion without its effect references should remain under investigation.

Use an acknowledgment and a later confirmation with different occurrence times. Check the provider event identifier and amount on each. If the later message corrects the amount, keep both entries and explain which event supports the final outcome. An attachment marked shared may reach a wider audience than an internal file, so rehearse access with an auditor before using that visibility in live cases.

A provider statement can document what the provider reported without proving a final effect. Compare the evidence type, verification choice and occurrence date before moving the instruction to a confirmed outcome. Keep the source file attached so an auditor can inspect the original message.

• Verified provider evidence — Find source events already checked by a reviewer.
• Provider response pending — Follow instructions still waiting for authoritative evidence.
• Receipts needing review — Investigate claims of completion that lack persisted effects.

See instruction review and provider reconciliation for the full handoff. Implementation sets out the pilot sequence.