Follow the steps below to set up the transaction approval mechanism.

1. Log into the platform as a user with an Admin profile and set up the Expense approval flow.

2. After the Workflow setup, flag the cards you want the transaction approval mechanism to affect in one of three ways:

2.1 Flag cards on a company level (e.g., ALL the General Purpose cards). For this option, navigate to Company Settings >> Cards and Budgets >> Manage settings, check the 'Require transaction approval' checkbox, and click the 'Save' button to store your preferences. 

Note: We recommend using the transaction approval mechanism with General Purpose (GP) and Travel cards. If the checkbox is checked, all newly generated Travel and GP cards will be issued automatically as cards requiring transaction approval.

2.2 Flag existing cards one by one or in bulk. For this option, navigate to Card and Budgets >> Virtual Cards, click the 3 dots next to a card, and then click the Edit option. In the 'Edit Budget Request' form, type the Reasons for editing the card's settings, activate the 'Require transaction approval' toggle and click 'Submit'.  

Note: You can use the filters (e.g., Employee) to locate a specific card. 

Note: You can bulk edit several cards. To bulk edit, check the relevant cards >> click the 3 dots at the top right corner of the screen >> choose 'Bulk edit card settings' >> click the 'Requires approval' button >> click the 'Next' button and then the 'Update' button.  

2.3 Flag new cards when issuing new cards or approving card requests by checking the 'Require transaction approval' checkbox under the 'Settings' section. 

3. Check that the settings affect the selected cards. The card's details will display if 'Transaction approval' is 'Required'.

Notes:

• If you need to stop the 'transaction approval' process, you can change the settings at any time. If you disable a card's transaction approval, transactions already 'in the cycle' will go through the approval process; however, new transactions will not. 
• Transaction approvals and the syncing to the ERP happen in parallel and are not dependent on each other.