Happy new year! 🥂
We took a short break for the festive period, so we've focussed most of our efforts recently on fixing the odd bug & making exciting plans for 2022.
Watch this space!
Hide paid invoices from invoice packs
If your company has the Automatic payment status check feature enabled, you can now choose to prevent paid invoices from appearing available to add to invoice packs. This ensures you’re never at risk of adding an invoice to a payment run when it’s already been marked as paid in your finance system. Handy, right?
To switch this feature on, just go to Configuration > Company management > Behavior settings, & switch on the Hide paid invoices when creating invoice packs toggle.
Order justification comment character limit
Some Compleat users were unable to submit orders for approval because there was no character limit for the justification comment, & longer justification comments were causing an error. We’ve added a character limit to stop this happening again.
Custom fields in multi line rich text format causing errors
Some Compleat users with custom fields set up in multi line rich text format were seeing an error page after entering text in the field, & then saving an order or invoice.
Incorrect payment reference number attributed to Sage Intacct transactions
A small number of customers connected to Sage Intacct were encountering incorrect payment reference numbers attributed to invoices marked as ‘Paid’ in Sage Intacct.
Sage 50 posting failures
Some Compleat users connected to Sage 50 were still seeing invoices in the Posting Failures tray after they’d been successfully posted.
Subscription payments filtering
The filtering & sorting options in the Payments grid within the Subscription area weren’t working.
Mobile app login issues
Some customers were unable to log in to the Compleat mobile app, but we’ve now fixed the issue causing the error.
Invoices per day report 'Date submitted' column missing
The ‘Date submitted’ column in the invoice grid in the Invoices per day report was blank. We’ve fixed it so that the report now shows you all the handy information you need to know when reviewing your invoice data.
Sage 50 overnight caching issues
A very small number of Compleat users connected to Sage 50 were experience caching issues overnight where certain data like suppliers & account codes weren’t being cached.
Invoice downloads not including PO numbers
The PO number field against invoices in invoice downloads was appearing blank even if the invoice was matched to a PO.
UK date format on US purchase orders
The date format on purchase orders was incorrectly displayed in the UK format (dd/mm/yyyy) rather than the US format (mm/dd/yyyy) for Compleat users in the United States.
Compleat Help button covering other screen elements in the new UI
The Help button in Compleat’s new UI was appearing over the top of other buttons & preventing users from interacting with them.
Supplier drop-down not auto-filled when manually matching
When using the Find a Po feature to search for a PO to match to an invoice from the invoice tray, the Supplier drop-down wasn’t automatically filled with the supplier name from the invoice.
Empty 'Supplier' list in the Supplier activity report in the new UI
When reviewing the Supplier Activity report in the new UI, some Compleat customers were seeing a blank grid. Other reports in the new UI were returning no results when a ‘Supplier’ filtering option was available.
Accounts IQ posting errors
Some customers connected to Accounts IQ encountered posting errors from Compleat. The cause of these errors has now been identified & resolved.
Single digit invoice numbers causing duplicate reference warnings
A small number of Compleat users with the ‘Supplier reference' feature enabled were encountering duplicate supplier reference warnings against invoices containing a single digit invoice number.
Caching Sage 50 closed projects
Compleat was caching closed projects from Sage 50 for a small number of users.
Error when deleting an action from an Event
When editing Events, some Compleat users were getting an error message when attempting to delete an action from the Event.
Please sign in to leave a comment.