Setup
Eftsure Setup Card
Update API URL and credentials received from Eftsure.
Origin ID : This is to indicate the type of environment e.g. Sandbox, UAT, LIVE. The same value needs to be updated in the Eftsure portal depending on the environment.
Entity ID : This is a unique identifier for the companies. The same value needs to be updated in the Eftsure entities.
Log API Calls : Enable to log API calls made to Eftsure.
Developer Mode: Enable to check the raw responses from Eftsure APIs to assist developers in debugging. If Log API calls is enabled, it also stores the API response in the API log table.
Manual Mode: Enable to make Eftsure actions visible on pages that otherwise would be run using job queues in the background. This is to facilitate on-demand requests.
User Setup
Every Business Central user can use the Eftsure related functions. However, most of them will be done by automation through Job Queue Entries. Specific sensible functionality requires additional setup in the User Setup. These are to control administrative actions like Self-Certification, Activation and De-Activation of Vendors in Eftsure.
Setup Vendor/Supplier Onboarding forms
Multiple vendor onboarding forms can be created and customised in Eftsure depending on the category of vendors, country etc.
Eftsure Job Queue
This action creates a job queue called Get Updates from Eftsure to run the Eftsure API calls in the background. This fetches the onboarding information, verification status, supplier information etc. from Eftsure.
The user must have permissions to create and run scheduled tasks.
Eftsure API Timestamps
Logs the timestamp for API calls to Eftsure. Used in job queues to only retrieve changes since the last update.
Eftsure API Call Logs
Logs the API calls made to Eftsure and records number of updates from onboarding and supplier information. It can be enabled from Eftsure setup.
If developer mode is enabled in Eftsure setup, API response can be stored and downloaded as well.
Workflows [Planned]
This feature has not yet been released.
Workflows can be created and set up to automate the manual actions like Send Onboarding Invite, Get Onboarded Info, Send Payment Verification Request etc. These manual actions are covered in the processing section.
Examples:
Supplier Onboarding:
If a vendor is created/changed in Business Central and mandatory fields like Name, Email, Payment Method Code etc. are filled in, a workflow can be configured as below to send an onboarding request to the supplier automatically.
Payment verification:
Payment journals are created by the user and once the entry is completed, the user can trigger the below workflow by an action to verify the payment.
Note: A manual action is required in this scenario so that user can confirm that he has entered all the journal lines and is ready for verification.
