I'm trying to resolve an issue for a customer with a document that uses SEQ formula operators.

I've created an invoice document template and the table uses some SEQ formula operators to calculate the invoice total, amongst some other things, but the template doesn't work correctly on my clients machine. When the fields are updated using F9, the dollar symbols are repeated and decimal places are introduced even when these are zero.

To be clear, the template works correctly on my computer. It also works correctly on my client's colleagues computer too.

I'm confused as to what the problem is. We're both using Windows 11 and we're both using the latest version of Microsoft Office 365 but there must be something different between the two installations? Here's some things I've already tried to resolve the problem:

• Client was previously on 'Microsoft Office Mondo 2016' which was thought to be the source of the problem but we've now installed a trial of the latest Microsoft Office 365. Before they updated from Mondo, we were getting messages about the contents of the file being unreadable, but these now don't appear.
• Verified that 'Protected View' or anything to do with the Trust Centre is blocking the formulas.
• Disabled any Add-Ins.
• Ran the Word Document in safe mode.
• Stripped all formatting from the document to rule out other conflicts
• The document was sent to the client via email, I tried sending via WeTransfer instead, incase email was corrupting the file.

Does anyone have any suggestions?

Here's what formula code I'm using in one of the cells. I'm not an expert in these SEQ operators but I built this based off some other formulas I found on StackExchange, basically it multiplies three cells together to create a total for the row, it works relatively so the same code can be used in all total cells and it won't break if other rows above or below are deleted.

Here's a video of what happens, we're using a stripped back version of the template in that example. I've also uploaded an anonymised version of the file to WeTransfer if anyone wants to test the file directly.