If you've paid the invoices outside of Mosaic and haven't reconciled them in the system, Mosaic will keep offering up those commitments in every new payment cycle.
That’s because Mosaic doesn’t know what’s happened outside of it, it still thinks those commitments haven’t been processed or paid to the supplier. So, it’ll keep trying to help you pay that money.
Until Mosaic certifies those invoices and completes a payment cycle, it’ll continue generating them every time you reject and regenerate a cycle.
Here’s what we suggest:
Put those invoices into a cycle on their own, complete the cycle, and receive the AP interface file for that specific cycle ID. Then, instruct your internal team to discard the AP file so it never reaches your corporate system. This way, Mosaic will be reconciled with what’s happened outside the system, and those commitments will stop reappearing.
Alternatively, you can set the dispatch method on those invoices to something starting with ‘NON’. Once the cycle is completed, the interface is hardcoded to ignore invoices with that dispatch method, so no file data will be generated. Mosaic will reconcile the invoices without exporting them. If you do receive a file, check to make sure those invoices aren’t included. If the file contains only data for that one cycle ID, discard it. If it’s mixed with other cycle IDs, please raise a new case with us.
Whichever method you choose, it’s best to hold off completing these cycles until there are no other legitimate cycles you need data for. That way, you’ll know the export file you receive is only for that cycle ID and can confidently discard it.
If you’ve got questions about how your interface is set up to export data or if you’re not sure whether you have a ‘NON’ dispatch method configured, please raise a new case with us. Let us know which cycle the invoices are isolated on, and we’ll check your interface and export configuration for you.