Payment detail changes

The portal displays the masked description of the AP-owned verified payment profile. The actual bank or provider destination remains a protected reference. A supplier user does not need the buyer’s credentials or unrestricted raw account details to recognise which authorised profile is in use.

A proposed replacement is kept separate from the active profile. Submitting it cannot immediately redirect a scheduled payment. The request retains the current source profile revision, the requesting Supplier Admin and the proposed protected destination so the buyer can review the exact change.

AP Specialist verifies identity against the buyer’s existing known contact and relationship evidence. The new email address, telephone number or payment detail in the request cannot serve as its own proof. Record the verification evidence and the internal person who performed it.

The active vendor membership and applicable authentication controls must still be valid when the request is submitted. A forwarded invitation, shared mailbox or convincing support message does not create authority to change where the buyer sends money. Keep sensitive proposed details out of ordinary case-message bodies and supplier-visible notification text.

A different AP Manager reviews the verified proposal. The approver must be distinct from both the requester and the internal verifier. Approval applies to the recorded destination, reason, identity evidence and expected source profile revision. An edit after review invalidates the decision.

Admin may maintain the provider or vault connection but cannot mark a payee request approved through a technical role. Similarly, a supplier’s administrative portal role allows the request, not the buyer’s financial approval. Those responsibilities remain separate through UI controls and direct API calls.

The approved request goes to the owning AP system with its original command key. Pending AP and Unknown preserve an unresolved outcome. Applied requires the verified source acknowledgment and the new profile revision. Until that result exists, the portal keeps the earlier verified destination as current.

A timeout must not trigger another independent update or claim that the profile changed. Reconcile the same request against the expected source revision. If the buyer altered the profile while review was in progress, the stale request is rejected and a new checked proposal is needed.

Changing a verified destination does not retroactively modify an earlier payment instruction. Existing scheduled or submitted payments need the buyer’s own authorised reconciliation and execution controls. The portal cannot decide that a bank instruction was rerouted simply because its profile display changed.

Retain the old and new source references, reviewers and applied timestamp. A supplier or auditor can then identify the approved change without gaining access to unrestricted bank data. Revoking portal access stops subsequent requests and document reads but preserves the evidence behind actions already performed.

• Payee Changes Awaiting Approval — Review the work and supporting records for this module.