Connections
The Connections area links your D365 F&O environment to the Eftsure database via the Eftsure API v2. From version 5.0 onwards, authentication uses OAuth 2.0 Client Credentials (aclientId and clientSecret) rather than basic authentication. You generate these credentials in the Eftsure customer portal under Partner API Credentials, then enter them in Eftsure parameters in D365.
Once credentials are configured, use the Ping and Login buttons to validate connectivity. Additional API settings let you select the TLS security protocol (1.2 or 1.3), configure a request timeout in seconds, and set a UserAgent string that matches your environment URL to assist with API log tracing.
TLS 1.3 is only available on Windows Server 2022 and later. Some development
boxes may require IIS Crypto to enable TLS 1.3 cipher suites manually.
Batches
Eftsure ships with a set of background batch jobs that keep D365 and the Eftsure cloud in sync. The Batches tab in Eftsure parameters is where you configure alerts, incremental batch reset dates, and the service account that receives notifications. Use the Check Batches function (available in Eftsure parameters or Eftsure Workspace > Admin > All batches) to let Eftsure read your configuration and automatically schedule the appropriate jobs. Run Check Batches after every deployment to ensure new jobs are created and obsolete ones are removed. Key recommended recurrences:Always assign a dedicated service account (one that never expires or resigns)
as the User ID for batches and alerts.
License
The Eftsure for D365 F&O license is independent of your Eftsure portal license. To check or renew your license, go to Eftsure parameters > License or System Administration > Setup > Eftsure > License. Click the License button to trigger an automatic renewal. A batch job created during Check Batches handles monthly license renewal automatically.License file updates no longer require a deployment and are independent from
Microsoft Dynamics 365 F&O license artefacts.
Go-Live checklist
The Go-Live tab lets you enable Eftsure protection per legal entity. Work through the steps from left to right for each entity you want to protect:1
Exclude vendors
Run the Exclude task to mark vendors (such as those in excluded vendor
groups like employees) as outside Eftsure verification scope. These vendors
can be re-included at any time.
2
Init
Run Init to calculate all
supplierCode values on bank accounts, giving
Eftsure a single identifier per vendor-bank combination. Use multi-thread
mode for larger data sets.3
From Eftsure
Run From Eftsure to download the latest verification data from the
Eftsure cloud, including any verifications completed before Go-Live.
4
To Eftsure
Run To Eftsure to push any vendors created since the vendor master file
was originally sent to Eftsure, ensuring D365 and the Eftsure cloud are fully
in sync before Go-Live.
5
Enable
Click Enable to activate Eftsure verification for the legal entity.
Eftsure will check that Init has completed first; if not, it will complete
Init in a single thread before enabling.
Configuration best practices
Before going live, review the following D365 General Ledger setting:- Allow multiple transactions within one voucher — Eftsure recommends keeping this off in General Ledger Parameters. Enabling it can create voucher-numbering inconsistencies that affect payment processing. See the Microsoft Docs — One voucher article for full details.