When will the money actually arrive?

A due date is the day you wrote on the invoice. It is not a promise the client's bank will keep. Net 30 on a $12,000 invoice issued 1 January is 31 January. A client who pays in 41 days sends it on 11 February. If you planned rent, a contractor, or your own tax payment for 31 January, you planned against a sentence, not against their habit.

The gap between those two dates is the whole point of a forecast. Adding up unpaid invoices and calling the sum "expected this month" treats every client as if they pay when asked. Some do. Many pay when their own cycle allows, which is a number you can already see if you look back at the last invoices they settled. This page puts that number on the row, next to the due date, so the two dates stay visible and stop being treated as the same day.

The running total is what you will have received by each arrival, not what you are owed. Owing $12,000 and holding $12,000 are different facts. A forecast that only shows the amount owed will always look healthier than the week you are about to live through.

Take the invoices they have already paid. For each one, count the days from the invoice date to the day the money hit your account, not the day they said they had "sent it." Drop the fastest one if it was a rush, and drop a single disaster if you already know why it happened. What is left is the number to type in. Six invoices that land between 36 and 48 days are a 41 day client. They are not a Net 30 client who had a bad month.

A brand new client has no history. Use the lag of the closest client you already have, or the terms you wrote, and mark it as a guess. Replace the guess the first time they pay. One data point is thin. It is still better than pretending the due date is a forecast. If they pay the deposit on time and the balance late, those are two lags. Do not average them into a number that describes neither invoice.

Write the lag down where you will see it next time, next to the client, not in a note you will not open. The days field on this page is that note made useful. Change it when the pattern changes. A client who used to take 20 days and now takes 50 has told you something. The forecast should move with them.

A stretch of more than ten days with nothing arriving is the week that hurts. The tool marks it because a quiet calendar is easy to miss when every invoice still looks "due soon." Once you can see the empty stretch, you have a few ordinary moves, and they work better before the gap starts than during it.

Ask the slow client, before the gap, whether the next invoice can be paid on the date you actually need, and say the date. Offer a smaller invoice now for the part of the work that is already done, instead of one large invoice that lands in the empty stretch. Bring a deposit forward on the next job so the gap is funded by money you already hold. Move your own bill, if the vendor will let you, to the week after the arrival rather than the week of the due date you no longer believe.

None of that is a collections step. It is scheduling. If the gap is larger than your savings, the next proposal should not be a single invoice at the end. A deposit, then a midpoint, then the balance, spreads arrivals into the weeks that are currently empty. The deposit calculator is the arithmetic for that split. A statement is what you send when several invoices are open and you want one date for the whole balance, instead of hoping each due date will save a different week.

You just typed all of that in. Incusia already knows when each client pays and forecasts this on its own, updating every time an invoice is paid.