--- title: Vendor Bill Payment Approvals (Intacct) slug: santander/vendor-bill-payment-approvals-intacct description: Use this guide to learn how to setup Payment Approvals, workflows, and integrate each step with your ERP. docTags: qsTTpmTCpLZnj3pL4Rz_Z createdAt: 2025-07-15T21:48:56.956Z --- :::hint{type="info"} **NOTE: **If you are interested in enabling this feature, please contact your Santander Treasury Service Sales Officer. ::: The Payment Approvals feature implements a multi-tiered approval workflow for payments made with the plugin, integrating the approval step directly into the ERP. This guide will walk you through setting up your approval workflows, ensuring that your payments are secure and properly authorized. *** ## Accessing Payment Approvals :::hint{type="info"} **NOTE: **To enable Payment Approvals, first update your plugin by following the guide on **Updating the Plugin**. ::: Once updated, follow these steps to access the Payment Approvals feature. ::::WorkflowBlock :::WorkflowBlockItem ### Log In to the Portal To begin, an ERP administrator or consultant with access to the portal needs to log in at [sys.fispan.live](https://sys.fispan.live/login). ::: :::WorkflowBlockItem ### Select Workflow Once logged in, select the **Payment Approvals** tile. You'll then be prompted to start creating your workflows. ::Image[]{src="https://app.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/TVUfASFJKitniVppgoVY--20250919-182534.png" size="80" width="1715" height="513" position="center" caption="Select Payment Approvals" darkWidth="1715" darkHeight="513" showCaption="true"} There are two main types of approval workflows you can set up: - **Global Workflow:** This is your default workflow. It applies to all payment types and bank accounts. - **Dedicated Workflow:** This workflow is more specific. It applies to a particular bank account and selected payment types. Dedicated workflows always take priority over Global Workflows. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/p4tU2aRp4XIM7_By6rgmD-20250919-182632.png" size="80" width="800" height="491" position="center" caption="Select Workflow" darkWidth="800" darkHeight="491" showCaption="true"} ::: :::: *** ## Setting Up Your Global Workflow To set up a global workflow, please follow these steps. :::::WorkflowBlock ::::WorkflowBlockItem ### Create Global Workflow First, give your workflow a descriptive name. This will help you easily identify it later. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-dXYsbi8JfZY1RX9neKR2X-20250721-185037.png" size="80" width="800" height="530" position="center" caption="Add Workflow Name" darkWidth="800" darkHeight="530" showCaption="true"} Here, you have the option to set thresholds. A threshold is the minimum payment amount required to trigger a specific approval tier. If a payment is less than the threshold amount, that approval tier will be skipped. :::hint{type="warning"} **IMPORTANT:** Each threshold amount must be equal to or greater than the previous tier's threshold. ::: :::hint{type="info"} **NOTE:** If your system supports multiple currencies for payments, you must first define a base currency for your workflow. Thresholds are only applied to payments in this base currency. Any payment submitted in a different currency will bypass the thresholds and automatically require approval from all tiers, as the system does not currently perform automatic currency conversion for this process. ::: :::hint{type="success"} **TIP: Best Practice for Multiple Currencies ** If you make payments from bank accounts with different base currencies, we highly recommend creating dedicated workflows for those accounts. This ensures that your thresholds are properly applied to payments in those specific currencies. ::: :::: ::::WorkflowBlockItem ### Add Approvers to Workflow You'll need to add approvers for your workflow. Enter the user's ERP email address exactly as it appears in their ERP user record. Approvers will receive an email notification when a payment meets the required threshold. :::hint{type="danger"} The approver email must ***exactly*** match the email in the user’s ERP record. Do not use an alternate or alias emails. Any mismatch may delay approvals and payment processing. ::: ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-8vDHnI6gmT2XnlRbqZo3q-20250721-185219.png" size="80" width="800" height="530" position="center" caption="Add Threshold Amount" darkWidth="800" darkHeight="530" showCaption="true"} :::hint{type="warning"} **IMPORTANT**: To approve payments, users in an approval workflow need both an ERP license and the necessary plugin permissions. ::: :::: ::::WorkflowBlockItem ### Add Multiple Tiers Add another Tier for approval and additional approvers, if needed. You can set up to three levels of approval. At each level, you can add up to five potential approvers. You can also decide how many individual approvals are required per tier. eg. Tier 1 requires 2 approvals, Tier 2 requires 3 approvals, Tier 3 requires 1 approval. :::hint{type="info"} **NOTE: Important Considerations** 1. **No Self-Approval. **You cannot approve your own payments. Keep this in mind if a single user frequently acts as both the payment creator and an approver. 2. **Best Practice for Approvers. **To avoid delays, we suggest: - Avoid having a single approver in a tier. - Adding more approvers than the required approvals (e.g., include 4 approvers in a tier that requires 2 approvals). This ensures the process can continue even if someone is unavailable. ::: :::: :::WorkflowBlockItem ### Complete Workflow Once you're satisfied with your settings, click **Confirm Selection**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-sJn4O8yYUdBvP3g60Bxgk-20250721-185252.png" size="80" width="800" height="530" position="center" caption="Select Confirm Selection" darkWidth="800" darkHeight="530" showCaption="true"} You can now review your workflow. Click **Create Workflow** to confirm creation. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-oEqGh7j125SMo5O2vwwea-20250721-185351.png" size="80" width="800" height="530" position="center" caption="Select Create Workflow" darkWidth="800" darkHeight="530" showCaption="true"} Your Global Workflow is now active! All payments made through the plugin will now follow this approval process. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-iYqKGwgRdicCHsBZpji-C-20250721-185433.png" size="80" width="800" height="530" position="center" caption="Click Close" darkWidth="800" darkHeight="530" showCaption="true"} ::: ::::: *** ## Creating a Dedicated Workflow If you have specific bank accounts that need different approval workflows, you can create a Dedicated Workflow. :::hint{type="warning"} **IMPORTANT:** Setting up a dedicated workflow means it will take precedence over the global workflow for this specific bank account and the chosen payment rail(s), affecting all future payments. ::: :::::WorkflowBlock :::WorkflowBlockItem ### Create Dedicated Workflow From the Payment Approvals page, select **click** **here** to create a dedicated workflow. ![](https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/lWKpyBnYB44nv1DWh3Hkm-20250919-182959.png "Created Dedicated Rule") First, enter a descriptive name for the workflow. ::: :::WorkflowBlockItem ### Add Source Account You'll then choose the bank account for which these approval workflows will apply. Click **Confirm Selection**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-d6_IMvEY3wYwX0o5rMJUD-20250721-201215.png" size="80" width="800" height="530" position="center" caption="Select Confirm Selection" darkWidth="800" darkHeight="530" showCaption="true"} ::: ::::WorkflowBlockItem ### Add Payment Methods Next, select the payment rail(s) that will be part of this workflow. **Payments not selected here will still be routed through your Global Workflow.** ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-VavG-VgS5YFY4kpePUy4V-20250721-201406.png" size="80" width="800" height="530" position="center" caption="Select Payment Rails" darkWidth="800" darkHeight="530" showCaption="true"} :::hint{type="info"} **NOTE: **This list displays all payment methods enabled for your **entire account**, not specific to individual bank accounts. ::: :::: :::WorkflowBlockItem ### Add Approvers and Tiers You can then set up the approval tiers, including thresholds, approvers, and the number of approvals required, just like with a Global Workflow. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-f-wxcxPCO4nAVuj9ceW0p-20250721-201434.png" size="80" width="800" height="530" position="center" caption="Click Confirm Selection" darkWidth="800" darkHeight="530" showCaption="true"} When you're finished, click **Confirm Selection**. ::: :::WorkflowBlockItem ### Complete Workflow Next, you will see an overview of your workflow. To enable the workflow, click **Create Workflow**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-wPqPqdV6KbsO1mdY1R6Is-20250721-201523.png" size="80" width="800" height="530" position="center" caption="Click Create Workflow" darkWidth="800" darkHeight="530" showCaption="true"} Your Dedicated Workflow is now active! Payments made with the selected combination of payment rails and bank accounts will now be routed through this workflow going forward. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-kDc3mDIuVlpMB59FzbVt6-20250721-201548.png" size="80" width="800" height="530" position="center" caption="Click Close" darkWidth="800" darkHeight="530" showCaption="true"} ::: ::::: *** ## Editing or Deleting Workflows You can edit or delete a workflow, but only if there are no pending approvals for that workflow. This prevents any confusion or errors with payments currently going through the approval process. In the event you need to edit a workflow with associated open payments, process or cancel any outstanding payments associated with the workflow. ### Editing a Workflow ::::WorkflowBlock :::WorkflowBlockItem **Select a Workflow to Edit** Click on the workflow you want to edit in the table. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/fWBvZGr_X7MDQEJjHHpPm-20250919-183019.png" size="80" width="800" height="355" position="center" caption="Select Workflow" darkWidth="800" darkHeight="355" showCaption="true"} An overview of the workflow will appear. Next, click **Edit Workflow. ** ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-TBVDCqzoas3hSbWL4l4W7-20250721-203318.png" size="80" width="800" height="689" position="center" caption="Click Edit Workflow" darkWidth="800" darkHeight="689" showCaption="true"} ::: :::WorkflowBlockItem **Edit Workflow** Make your desired changes to the workflow. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-aAK-FCw4V21rTvqVAgQCf-20250721-203634.png" size="80" width="800" height="530" position="center" caption="Make Changes" darkWidth="800" darkHeight="530" showCaption="true"} Verify your changes and then click **Save**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-B_bya9rl-yK59kLpFlzvU-20250721-203757.png" size="80" width="800" height="530" position="center" caption="Click Save" darkWidth="800" darkHeight="530" showCaption="true"} ::: :::WorkflowBlockItem **Confirm Changes** You will then see a confirmation of the changes. The updated workflow will now apply to all new payments. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-F0xOc18LNFkcyUsyK63t4-20250721-203700.png" size="80" width="800" height="530" position="center" caption="Click Close" darkWidth="800" darkHeight="530" showCaption="true"} ::: :::: ### Deleting a Workflow ::::WorkflowBlock :::WorkflowBlockItem **Select a Workflow to Delete** Click on the workflow you want to delete. ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/fWBvZGr_X7MDQEJjHHpPm-20250919-183019.png" size="80" width="800" height="355" position="center" caption="Select Workflow" darkWidth="800" darkHeight="355" showCaption="true"} Click **Delete Workflow**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-uQXG8U958ets5AbAZN9Qh-20250721-204031.png" size="80" width="800" height="689" position="center" caption="Click Delete Workflow" darkWidth="800" darkHeight="689" showCaption="true"} ::: :::WorkflowBlockItem **Confirm Deletion** Next, confirm you would like to proceed with the deletion. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-0Nq1GKJQbZAbgkD334FOl-20250721-204219.png" size="66" width="800" height="445" position="center" caption="Click Yes, Delete Workflow" darkWidth="800" darkHeight="445" showCaption="true"} Payments will no longer use this Workflow. If you still have a Global Workflow active, these payments will now be routed through your Global Workflow instead. You will then see a confirmation that the workflow was successfully deleted. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-o6I3O9kRhHbZqiKE2OWUN-20250721-204758.png" size="66" width="800" height="580" position="center" caption="Confirm Workflow Deletion" darkWidth="800" darkHeight="580" showCaption="true"} ::: :::: *** # Intacct Required Permissions To get access to the Payment Approvals page, please have your ERP Administrator navigate to the role for your bank's plugin and add permissions for **Payment Approvals**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-SD880qhwGofOcv70pPQU2-20250721-211418.png" size="80" width="794" height="607" position="center" caption="Add Payment Approvals" darkWidth="794" darkHeight="607" showCaption="true"} ## Payment Approval Request Page After creating Vendor Bill Payment Approval workflows, once you initiate a payment from within your plugin, its status transitions to **Waiting for Approval. **If the payment amount falls within a specific approval threshold, the designated approvers will receive an email notification with the subject: **"Action Required: Payments Requiring Approval"** ::Image[]{src="https://api.archbee.com/api/optimize/MM6nC_bKbIkwCRqiFZqEu/C1_VV_OjEkN0DJtm5PfIq-20260302-211955.png" size="80" width="1122" height="970" position="center" caption="Payment Approval Email Notification" showCaption="true"} Approvers can review these payments from the Payment Approval Request page, which serves as the central hub for all payments initiated for your company that are awaiting approval. The Approvals page table provides a comprehensive overview of each payment request, with the following key details: - **Request Date:** The precise date when the payment was initiated within the plugin. - **User/Requested By:** The name of the user who submitted the payment request. - **Payment Request ID:** A unique internal identifier generated by the plugin for this payment. This ID is crucial for any troubleshooting or support inquiries. - **Payee:** The name of the recipient (vendor or entity) to whom the payment is being sent. - **Amount:** The total value of the payment, after any applicable discounts or credits have been subtracted. - **Number of Bills:** The count of individual bills that are covered by this specific payment request. - **Payment Type:** The chosen method for distributing the funds (e.g., ACH, Check). - **Source Account:** The bank account from which the payment funds will be drawn. - **Expected Pay Date:** The date on which the payment is projected to be sent out to the recipient, assuming it receives final approval. - **Approval Progress:** A tracker that provides context for where a payment is within the approval process. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-_Wn9Sa_dShnwWCmsCWISj-20250717-205013.png" size="80" width="1413" height="615" position="center" caption="Approvals Page" showCaption="true"} To help you quickly find specific payment requests, the Approvals page provides filtering capabilities. Click on the **Filters **button to open the filter panel on the right side of the screen. You can filter by Amount, Payment Request ID, Payment Type, Request Date, Source Account, or Vendor. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-T_HFDsevM0av18fJIo0Kx-20250717-205408.png" size="80" width="1412" height="659" position="center" caption="Filter Approval Requests" showCaption="true"} *** ## Individual Approvals or Rejections For more granular control, or to provide unique rejection reasons, you can process payments individually. To approve or reject individual payments, simply click on the specific payment row in the Approvals table. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-Km3qteQ3--zk0qcaVJiR4-20250717-210314.png" size="80" width="1071" height="611" position="center" caption="View Approval Request" showCaption="true"} This will open a detailed dialogue for that payment. You can navigate through other payments directly from this dialogue using the provided navigation arrows, without returning to the main table. ### To Approve an Individual Payment ::::WorkflowBlock :::WorkflowBlockItem **Approve Payment** Click the **Approve** button. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-ymNMjdBkbF4xhf7FgHu12-20250717-210418.png" size="82" width="983" height="645" position="center" caption="Click Approve" showCaption="true"} You will then see an approval confirmation screen. This screen includes a countdown timer that will automatically advance you to the next payment in your list (if any) or close the dialogue. You can also click the navigation arrow to move to the next payment more quickly. ::: :::WorkflowBlockItem **Complete Approval** If your approval is part of a multi-tier workflow, the payment will proceed to the next required approver(s). ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-I2utMdKkSaCU0pX_9mOpt-20250717-210451.png" size="80" width="969" height="616" position="center" caption="Approval Confirmation" showCaption="true"} ::: :::: ### To Reject an Individual Payment ::::WorkflowBlock :::WorkflowBlockItem **Reject Payment** Click the **Reject** button. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-9uAozDEKbU48YZ3wdUOTh-20250717-210532.png" size="80" width="987" height="630" position="center" caption="Click Reject" showCaption="true"} ::: :::WorkflowBlockItem **Provide Rejection Reason** You will be prompted to provide a rejection reason. Once you have entered the reason, click **Yes, Reject Payment**. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-y4SmnSRMaQJgWyuvjtwOB-20250717-210658.png" size="80" width="1011" height="627" position="center" caption="Rejection Reason" showCaption="true"} ::: :::WorkflowBlockItem **Confirm Rejection** You will then see a rejection confirmation screen. Similar to the approval confirmation, this screen includes a countdown timer to automatically advance you or an arrow to move faster. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-UbRAm9AfkJzmttHdA9_3q-20250717-210546.png" size="80" width="1040" height="678" position="center" caption="Rejection Confirmation" showCaption="true"} If a payment is rejected, it will be voided within your ERP system. The associated bills will then reopen, becoming eligible for future payment. The payment status on the Payment History page will change to Cancelled. ::: :::: *** ## Bulk Approving or Rejecting Streamline your process by using bulk approvals and rejections for vendor bill payments. ::::WorkflowBlock :::WorkflowBlockItem ### View Payments Awaiting Approval To quickly focus on payments awaiting your direct action, click the **Show Assigned To Me Only** filter. ::Image[****]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-QRaY1syXcfQ7LPHVXAsby-20250717-233610.png" size="80" width="880" height="226" position="center" caption="Click Show Assigned to Me Ony" showCaption="true"} In this filtered view, you can efficiently manage multiple payments: - Select up to 1,000 payments for processing at once. - Your selections are saved across all pages of the table, letting you choose payments from your entire list without losing your place. - To see the total amount of selected payments, grouped by currency, simply hover over the **Selected** counter. ::: :::WorkflowBlockItem ### Select Payments Select payments with the checkboxes. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-utLBmao6uScPJQpgpUJ93-20250717-233723.png" size="80" width="1426" height="840" position="center" caption="Select Payments" showCaption="true"} Once you have reviewed and selected the desired payments, you can choose to **Approve** or **Reject** them using the corresponding buttons. ::: :::WorkflowBlockItem ### Bulk Approve or Reject After making your selection (**Approve** or **Reject**), you will be presented with a summary of your chosen payments for a final confirmation review. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-QrlXnwbQ6kL1IcLDzUJtp-20250717-233804.png" size="80" width="917" height="579" position="center" caption="Click Yes, Approve Payments" showCaption="true"} If you selected **Reject**, you will be prompted to provide a mandatory rejection reason. Please note that this reason will apply to *all* selected payments. If you require different rejection reasons for individual payments, you must process them separately. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-GN7-kFxl-ZRWlLMUrxtPw-20250717-234151.png" size="80" width="918" height="597" position="center" caption="Click Yes, Reject Payments" showCaption="true"} Once you confirm your selection, the system will begin processing your approvals or rejections. If a payment is rejected, it will be voided within your ERP system. The associated bills will then reopen, becoming eligible for future payment. The payment status on the Payment History page will change to Cancelled. If your approval is part of a multi-tier workflow, the payment will proceed to the next required approver(s). However, if your approval is the final one required, the payment will be sent for processing and will be transmitted to your bank. ::: :::: *** ## Payment Approval History Page The Approval History page provides a comprehensive record of all payments that have reached a definitive status: either rejected or approved. Payments still pending further approval will not appear here; they remain visible on the Approval Requests table. This page offers a detailed overview of past payment activities, including: - **Status:** The final outcome of the payment (e.g., Approved, Rejected, Paid). - **Payee:** The name of the recipient of the payment. - **Payment Request ID:** The unique internal plugin identifier for the payment, useful for reference. - **Number of Bills:** The count of bills included in the payment. - **Payment Type:** The method used for the payment (e.g., ACH, Wire). - **Amount:** The total amount of the payment after any discounts or credits. - **Source Account:** The bank account from which the payment originated. - **User/Requested By:** The user who initially requested the payment. - **Request Date:** The date the payment request was initiated. - **Total Approvers:** The total number of users who took action (approved or rejected) on the payment. - **Decision Date:** The date on which the final action (either final approval or rejection) for the payment was completed. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-Qu2CJqjipLSpsr_0-Kgnl-20250717-235621.png" size="80" width="1432" height="705" position="center" caption="Approval History Page" showCaption="true"} To view more details about a request, you can click **View** and see the following: - **Date and Time:** When the approval or rejection occurred. - **User:** The individual who approved or rejected the request. - **Reason:** Any comments or explanations provided for the decision. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-f2hIWwaS2XW6QcvuiW_0u-20250724-183124.png" size="80" width="2072" height="1448" position="center" caption="Approved History Record" showCaption="true"} ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-W4k0TdWbnLt-JTqnGozoA-20250724-183155.png" size="80" width="2078" height="1448" position="center" caption="Rejected History Record" showCaption="true"} *** ## Payment Approvals History Export You can export the Approvals History for record-keeping or analysis. The export file includes: - **Date:** The date the payment was processed. - **Vendor Name:** The name of the recipient of the payment. - **Total Bills:** The number of individual bills included in the payment. - **Amount:** The total value of the payment. - **Currency:** The currency in which the payment was made (e.g., USD, CAD). - **Payment Method:** How the payment was made (e.g., ACH, Check, Wire). - **Submitted By:** The user who initiated the payment request. - **Reviewed By:** The email addresses of all users who participated in the approval or rejection process. This gives you a clear view of the approval chain. - **Approval/Rejection Time:** The exact date and time when the final decision (either approval or rejection) was made by the last reviewer. - **Status:** The final outcome of the payment request, clearly indicating whether it was Approved or Rejected. - **Reason for Rejection:** If a payment request was rejected, this field will provide the specific reason. This field will be empty for approved payments. To generate this export, click the **Export** button on the Approvals History page. ::Image[]{src="https://api.archbee.com/api/optimize/LTm6J44NoHZKpyGlNLpLN-8Izk9MwXJYxit8pUBI6fe-20250729-215915.png" size="80" width="2548" height="584" position="center" caption="Click Export" showCaption="true"} *** ## FAQs :::ExpandableHeading **I have a user who has access to the portal, but I do not want to have permission to edit my approval Workflows. What can I do? ** Need to adjust user access to workflows (e.g., view-only or no access)? Please contact FISPAN Portal with the user emails for assistance. ::: :::ExpandableHeading **What if I accidentally reject a payment?** Rejection is a terminal action. If a payment is rejected in error, the initiating user will need to resubmit the request. :::