Adfin Engager troubleshooting.

• If you log in to Adfin using Google or xero single sign-in, then you need to change it in the settings to log in with email and password. Adfin have not enabled the single sign-in option on link apis; this is being fixed in the coming days by Adfin.

• If you have linked Adfin to xero or qbo, then you must link xero or qbo in engager for the three-way sync to work.

• If you use invoice platforms such as Sage and Freeagent and upload invoices directly to Adfin, then the Engager integration will work fine
• Why do I need to link Xero or QBO to Engager if it is linked to Adfin? 
  
  The reason is a little bit complicated but I’ll try explaining it. we’ve done it this way after Adfin asked us to reduce the risk of creating duplicate clients. 
  
  Whilst if you add a client to Adfin, they push it to Xero, if you add it to Xero, Adfin doesn’t pick it up immediately as they have no way of knowing if it’s a customer or supplier straightaway.
  
  If, after adding client A directly to Xero, you added this client to Engager and tried to link with an existing client in Adfin, the client wouldn’t be there. So the natural thing to do would be to select "Create new client in Adfin”. That would create an Adfin client B that would not be linked to Xero because the Engager client is not linked to Xero; therefore, it cannot tell that client A in Xero is the same as client B being created in Adfin. All because Xero integration is not enabled in Engager.

• To request a direct debit mandate as part of the LOE process, you need to add the client to Adfiin and if using QBO or xero, then to them as well, a couple of clicks when setting up the prospect/client and press save. If you don't want to add them to Adfin and qbo/xero at this stage, you can not offer the DD mandate at signing the loe and send the request via email later on