Skip to main content

Payment cycles have split

In this article, we explain why payment cycles may split into too many new cycles.

Y
Written by Yusef Abulaynain
Updated over 6 months ago

Mosaic has a system property named INV_PER_PAYMENT_CYCLE that sets the maximum number of invoices in a scheduled payment cycle. If the number of invoices generated exceeds this value, Mosaic splits them across multiple cycles and ensures:

  • No cycle has more invoices than the value of INV_PER_PAYMENT_CYCLE.

  • Invoice payees (Organisation or Person) aren’t split between payment cycles unless a single payee has more invoices than the maximum, in which case some splitting is necessary.

This method doesn’t always create the minimum number of payment cycles, so you may end up with more cycles than expected. This is normal, and each cycle can be processed like any other payment cycle.

Query your cycles

If you want to ask why your cycles split this way, or if you’re hosted and want to change INV_PER_PAYMENT_CYCLE, raise a new case online, reference the title of this article, and provide the new value you want for the system property.

Self-hosted customers can change the system property by running the following query, replacing 12345 with the value you need:

📌Note: The quotes are required because this is a text field, not numeric.

Update system_properties set value = '12345' where name = 'INV_PER_PAYMENT_CYCLE';
Did this answer your question?