Known Issues
This documentation will highlight common errors which users might come over when using Eftsure inside D365 F&O.
In most of cases, the errors are due to configuration or process is not processed correctly. With this document, we will propose alternate solutions which can be performed either by end user or system administrator.
See Troubleshooting for more infos on how to troubleshoot your issue.
Dynamics 365
Onboarding
Missing GST group
Error: "Field 'GST group' must be filled in"
When: Accept new onboarding after Review
Background:
Tax group field is setup as mandatory field for vendor master and no default tax group is set for vendor group. Since onboarding create vendor automatically and from default onboarding, GST group is not identified, this will create an error.
For more information, please refer to Data integrity.
Solution:
- Set default GST group for vendor group(s).
- Select GST group for each vendor.
Select correspondence GST group per vendor before Accept new onboarding.
- Remove Mandatory tax group.
infoIf this option is removed, vendor will be created without GST group
Onboarding business without ABN
Error: "ABN must be specified"
Background:
Business set ABN as mandatory for all vendor
Solution:
Change ABN requirement mandatory field.
Vendor Master
Invalid ABN when modify existing record
Error: "Invalid ABN '12 345 678 900' : ABN doesn't satisfy validation rules"
When trying to change any field for existing vendor with invalid ABN.
Background:
ABN validation is switched on meaning a vendor can only have either a valid ABN or no ABN. The configuration will not accept invalid ABN.
Solution:
-
Input valid ABN or leave ABN as Blank Modify ABN number before modifying any other fields.
-
Change configuration - disable ABN look up (system admin)
ABN lookup will be disabled and any value should be accepted by the system.
-
Change configuration - disable ABN look up (Customer) If business wishes to leave ABN lookup on for AP and only turn off Customer and Sales Orders, configuration can be done in Parameter.
Vendor Payment
GST check vendor journal
Error: "GST Group mandatory for vendor AU-11111 voucher VPA0000"
Background:
Vendor payment journal has GST validation switched on for all the journal line.
Solution:
-
Set default GST for each journal line.
noteBefore changing the default setting, please take into consideration business process.
For more information, please refer to Payments -
Remove GST group validation for vendor payment journal and leaving only GST validation for vendor invoice check.
Simulating posting
Error: "Eftsure validation 1 line(s) have invalid Eftsure verification status. Please validate and review journal before posting again"
Background:
Vendor has been excluded from daily Eftsure synchronization but has default method of payment with Eftsure enabled.
Solution: Create new method of payment with Eftsure disabled.
Payment journal line with disabled Eftsure.
Access configuration
For any new user, you should receive an activation email. Please ensure to test all portal login directly using below respective hyperlinks before configure in D365 F&O.
Eftsure Portal environments
Sandbox - UAT: sandbox.eftsure.com.au/
Production: portal.eftsure.com.au/
Generic account
Error: Eftsure cloud: Incorrect PartnerId (UpgradeRequired)
Background:
Generic account is used for au-batches synchronising between D365 and Eftsure portal.
Solution:
Review Generic Username and Password before sending request to support using link provided.
Once the username is assigned to the correct PartnerId, successful Login message will be as below.
Personal account
Error: Eftsure cloud: Login failed (Unauthorized)
When trying to sync new onboarding from portal.
Background:
Wrong username or Password per user or user does not have correct access including API or username hasn't been assigned to correct partnerId.
Solution:
This should be single user access which is the same access to Eftsure portal. Please click in the recommended hyperlink, action item to contact support directly for API access and assign to correct partnerId.
Review auto-save PW in internet browser to ensure new PW is updated accordingly.
User Interface
Icon size
If user accidentally increase the size of icon column
To resolve the issue, user will need to resize the column to original size and perform a hard refresh.
The icons size should be reset to original size.
Synchronisation
Self-certified - vendor payment
Vendor self-certified in D365 vendor master but not yet verified in payment journal.
Background:
Bank account is newly created and not yet synchronised to Eftsure portal correctly or Eftsure portal has not been setup accordingly.
Solution:
-
ensure the vendor bank account is synchronized to Eftsure portal
-
Ensure legal entity is setup correctly in portal which should be the same with D365 legal entity.
Once all checked and synchronized correctly, once vendor payment journal is validated again, all should reflect correct status.
None - Grey vendor
Vendor bank account is Grey in D365 F&O.
Vendor is not synchronized to Eftsure portal.
Background:
Vendor bank account hasn't been synchronised to Eftsure portal. Main reasons include:
-
Vendor is manually created in D365 with Excluded vendor group (vendor group not schedule for synchronizing to Eftsure portal)
-
Vendor is created manually in D365 with normal vendor group but not auto sync due to user account not validated
Solution:
Update user access
Manually sync to Eftsure portal
Vendor bank account will be synchronized to Eftsure portal.
Bank account verified but vendor is grey
Vendor verification status shows Grey but vendor bank accounts is already self-certified.
Background:
Eftsure verification status is for default vendor bank account only. If no default bank account is selected/vendor has no default bank account or bank account with no valid bsb, bank account number, there will be no verification status.
If vendor is manually created without Eftsure onboarding process, default bank account must be selected.
Solution:
Select default bank account in main vendor master form
Once default bank account is selected and saved, verification status will be populated.
Phone number validation errors
Message: Phone number 'XXX XXX XXXX' is invalid for country YY
This message has 2 different causes:
- the phone number is invalid, please find a phone number matching country rules and formatting.
- the phone number is valid, but the phone number validation version is obsolete as new country specific rules have been added. In this scenario, disable phone number validation temporarly to proceed with the current valid number, re-enable phone number validation, and update eftsure to the latest version.
If the issue persits, you can disable phone number validation in Eftsure parameters > User interface > Extend > Phone: Phone number validation.
Please choose a contact from the list
Message: Please choose a contact from the list
While saving a vendor, a warning message prevents from saving a vendor. This message usually occurs when the vendor has an inccorect Primary contact value.
Go to the matching vendor > Purchasing demographics > Primary contact and enter the appropriate value.
Once the value is appropriate, you should be able to retry the current action.
If using record templates to create vendors, make sure to empty the Primary contact field on the template.
UpdateConflict
Message: Cannot edit a record in [Table Label] ([Table Name]). An update conflict occured due to another user process deleting the record or changing one or more fields in the record.
As much as we do our best to avoid them, Update conflicts do occur in a highly distributed environment, especially if the customer is running batches during daily user activities or while other related batches run. Please retry later.
We do not comment/investigate on update conflicts occuring a single time. If you are experiencing high volumes of repeated update conflicts, please reach out to support.
Webservices
Webservice errors are usually common client/server errors as described here The most common appearing in this extension are described below, in the form of 4XX or 5XX error codes and descriptions.
Error 401 - Unauthorized
Either a token expiration or a user without the appropriate permissions.
Error 403 - Forbidden
Insufficient permissions
Error 408 - Token Timeout
Either a timeout, please retry later.
Either an Eftsure user that is expired, in which case the error message is misleading.
Error 500 - Internal Server Error
Likely an outage, please retry later or contact support if situation doesn't improve quickly.