MIS Systems Thread, SIMS-FMS Remittance Advice/Office 365 in Technical; We use SIMS/FMS. When invoices have been paid, FMS can email a remittance advice to customers which used to work ...
19th June 2014, 09:51 AM #1
SIMS-FMS Remittance Advice/Office 365
We use SIMS/FMS. When invoices have been paid, FMS can email a remittance advice to customers which used to work fine with our Exchange Server. They we migrated to Office 365. Despite using a valid O365 account, remittance advice fails. Rang school support centre for advice on whether O365 client or smtp relay is used by FMS. Response came back that this is a "known problem" and has been referred to Capita...
Has anyone got FMS Remittance Advice working with Office 365 please? If so, please can you let me know if it is client or smtp relay based?
19th June 2014, 10:26 AM #2
We had the same problem, i've just checked how ours is set up for you.
go to Tools -> Establisment Details -> email tab.
edit BACS Address.
server for us is the pod****.outlook.com address.
port is 587
tick both boxes
enter a valid email address and password.
in the return to email address ensure its a vaild address that the user above can access.
Our finance officer says it works fine, we've not used our smtp relay for that, straight to Office 365.
Hope this helps
Thanks to dezt from:
kathabell (19th June 2014)
19th June 2014, 11:00 AM #3
Thanks, that's interesting as we've had more success with SMTP relay; at least it verifies the connection OK.
Is your Office 365 setup linked to AD, or do you run totally in the cloud?
19th June 2014, 11:20 AM #4
We use dirsync, we used to use ADFS but I ran into problems with it.
19th June 2014, 11:28 AM #5
Ours is working here too. Have you tried using the 'test' button to see if that sends?
19th June 2014, 02:25 PM #6
Thank you everyone, problem is now resolved; it was a lot easier once I knew that others had client based email working. Our issue was that Office 365 would not accept an email alias, it insists on true account details. We all have personalised staff accounts, but for systems we use generic aliases - particularly useful when a colleague leaves as the job function is protected; you just move "bursar@" alias to another personal account and for everyone else it is business as usual; nothing falls over or breaks if an individual is absent. This worked fine with our old Exchange server and was very easy to set up and maintain. It is more of a pain to create full delegate mailbox rights, but now this is done our bursar is happy and firms are once again receiving their remittance emails, from a generic "real" account that his personal one has access to!
By Kyle in forum Cloud Services
Last Post: 28th March 2013, 08:57 PM
By rob101 in forum Cloud Services
Last Post: 20th November 2012, 01:53 PM
By tj2419 in forum Cloud Services
Last Post: 1st November 2012, 04:40 PM
By MicrodigitUK in forum MIS Systems
Last Post: 14th June 2012, 11:12 AM
By SimpleSi in forum CLEO
Last Post: 3rd July 2009, 11:24 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)