Skip to content

Free planner

Invoice cash flow timing planner

To see when invoice money could arrive, add each invoice's payment terms to its issue date to get the due date, add the delay you expect, and total what is still owed by week or month. This planner does that for up to 200 sent and planned invoices and shows the same plan with every invoice paid on its due date beside it, so you can see how much money the delay pushes into later weeks or months.

The invoices, dates and delays in the planner are an example. The payment dates it shows come from the terms and delays you enter: they are assumptions, not predictions of when a client will pay, and nothing on this page sends an invoice or requests a payment.

Plan settings

The plan filled in is an example for a small agency. Replace it with your own invoices, or clear it and start empty.

One currency per plan. Amounts are not converted, so make a separate plan for each currency you invoice in.

Usually today. The timeline starts with the week or month that holds this date.

Cash on hand at the plan start. Leave it empty to count invoices only.

Your own estimate for every invoice. Enter 0 for paid on the due date. Any invoice can have its own delay below.

Group the timeline by

Invoices

Add the invoices you have sent and are still waiting on, and the ones you plan to send. Due dates count calendar days from the issue date. Enter any part already received under “Already paid”, so only the rest goes on the timeline.

  1. Invoice 1

    Leave empty to use the plan's delay.

    Due Sat, Nov 14, 2026. Assumed paid Tue, Nov 24, 2026, 10 days late.

  2. Invoice 2

    Leave empty to use the plan's delay.

    Due Mon, Nov 16, 2026. Assumed paid Thu, Nov 26, 2026, 10 days late.

  3. Invoice 3

    Leave empty to use the plan's delay.

    Due Fri, Nov 27, 2026. Assumed paid Mon, Dec 7, 2026, 10 days late.

  4. Invoice 4

    Leave empty to use the plan's delay.

    Due Wed, Dec 16, 2026. Assumed paid Sat, Dec 26, 2026, 10 days late.

  5. Invoice 5

    Leave empty to use the plan's delay.

    Due Tue, Dec 29, 2026. Assumed paid Tue, Jan 19, 2027, 21 days late.

5 of 200 invoices.

Cash flow timeline

USD 24,500.00 is still to collect on 5 invoices. With your delays, the last of it is assumed to arrive on Jan 19, 2027, against Dec 29, 2026 if every invoice were paid on its due date.

Still to collect5 invoices with an amount left to collect
USD 24,500.00
Starting balanceOn Nov 2, 2026
USD 8,000.00
Running total after the last receiptStarting balance plus everything still to collect
USD 32,500.00
Last receipt, with your delays
Tue, Jan 19, 2027
Last receipt, paid on the due date
Tue, Dec 29, 2026
Largest difference in running totalDecember 2026
USD 7,500.00

Invoices are assumed to be paid 10 days after the due date, except 1 invoice with its own delay. The payment dates are the terms and delays you entered, not a forecast. The second scenario uses the same invoices with no delay at all, so the difference column shows how much less has arrived by the end of each row under your assumption.

Expected receipts by month in USD, two scenarios
MonthReceipts, with your delaysRunning total, with your delaysReceipts, paid on due dateRunning total, paid on due dateDifference
Starting balanceMon, Nov 2, 20268,000.008,000.000.00
November 2026Mon, Nov 2, 2026 to Mon, Nov 30, 202610,500.0018,500.0012,500.0020,500.002,000.00
December 2026Tue, Dec 1, 2026 to Thu, Dec 31, 20266,500.0025,000.0012,000.0032,500.007,500.00
January 2027Fri, Jan 1, 2027 to Sun, Jan 31, 20277,500.0032,500.000.0032,500.000.00

The gap is largest at the end of December 2026, when USD 7,500.00 less has arrived than if every invoice were paid on its due date.

Invoices, due dates and assumed payment dates
InvoiceIssuedTerms and delayDue dateAssumed paymentStill to collect (USD)
INV-0101 Website redesign, milestone 2SentOct 15, 2026Net 30, 10 days lateSat, Nov 14, 2026Tue, Nov 24, 20266,000.00
INV-0102 Retainer, NovemberSentNov 1, 2026Net 15, 10 days lateMon, Nov 16, 2026Thu, Nov 26, 20264,500.00
INV-0103 Brand workshopSentOct 28, 2026Net 30, 10 days lateFri, Nov 27, 2026Mon, Dec 7, 20262,000.00of 3,200.00
Retainer, DecemberPlanned, not sent yetDec 1, 2026Net 15, 10 days lateWed, Dec 16, 2026Sat, Dec 26, 20264,500.00
Website redesign, final paymentPlanned, not sent yetDec 15, 2026Net 14, 21 days late (this invoice)Tue, Dec 29, 2026Tue, Jan 19, 20277,500.00
Total24,500.00
Totals by status in USD
StatusInvoicesInvoicedAlready paidStill to collect
Sent313,700.001,200.0012,500.00
Planned212,000.000.0012,000.00
All invoices525,700.001,200.0024,500.00

The CSV files hold plain amounts in USD with dates as YYYY-MM-DD, for a spreadsheet. The plan starts Monday, November 2, 2026 with a starting balance of USD 8,000.00.

A planning aid built from the dates and delays you entered. It is not a prediction of when any client will pay, and nothing here sends an invoice, a reminder or a payment request.

How the planner works out payment dates and the timeline

Each invoice has an issue date I, payment terms of N days, an amount A and an amount already paid P. L is the delay, in days after the due date, that you assume for it: the plan's delay, or the invoice's own when you enter one. The planner works out three figures per invoice:

  • Due date: D = I + N, counted in calendar days. Due on receipt is N = 0, Net 30 is N = 30, and a custom term can be any number of days up to 365.
  • Assumed payment date: T = D + L.
  • Still to collect: O = A − P. An invoice with nothing left to collect is listed but not placed on the timeline.

The timeline is a row for each week or calendar month, starting with the period that holds the plan start date and ending with the last period any payment lands in. A row's receipts are the sum of O for every invoice whose date falls in it, and its running total is R = S + receipts so far, counting this row and every row before it, where S is the starting balance, or zero if you leave it empty.

The same invoices are laid out twice. The first scenario places each amount on T, with your delays. The second places it on D, as if every invoice were paid on its due date. The difference column is the second running total minus the first. It can never be negative, because a delay is zero or more days, and it falls back to zero once the last delayed payment is in.

A payment date before the plan start cannot go in a period, so those amounts go on one line at the top of the timeline, for example “Before Nov 2, 2026”, and still count toward the running total. In the paid-on-due-date scenario that line holds invoices that were due before the plan start and would have been paid by then. In your own scenario the planner also shows a warning, because an invoice still unpaid after its assumed date needs a longer delay.

Amounts are added exactly, without rounding. An amount cannot have more decimal places than its currency uses, two for USD or EUR and none for JPY, so the timeline, the totals and the exported files add up to the same figures.

Worked example: five agency invoices in USD from Nov 2, 2026

The planner opens with this example. A small agency starts its plan on Monday, November 2, 2026, with a starting balance of USD 8,000.00. It has 3 sent invoices with USD 12,500.00 still to collect and 2 planned ones worth USD 12,000.00. It assumes clients pay 10 days after the due date, except the final payment on the website project, which it gives 21 days. The references and figures are made up for the example, and the delays are not typical values for any client.

Worked example: five invoices in USD, with due dates and assumed payment dates
Invoice (example)StatusIssuedTerms and delayDueAssumed paymentStill to collect (USD)
INV-0101 Website redesign, milestone 2SentOct 15, 2026Net 30, 10 days lateSat, Nov 14, 2026Tue, Nov 24, 20266,000.00
INV-0102 Retainer, NovemberSentNov 1, 2026Net 15, 10 days lateMon, Nov 16, 2026Thu, Nov 26, 20264,500.00
INV-0103 Brand workshopSentOct 28, 2026Net 30, 10 days lateFri, Nov 27, 2026Mon, Dec 7, 20262,000.00
Retainer, DecemberPlannedDec 1, 2026Net 15, 10 days lateWed, Dec 16, 2026Sat, Dec 26, 20264,500.00
Website redesign, final paymentPlannedDec 15, 2026Net 14, 21 days late (this invoice)Tue, Dec 29, 2026Tue, Jan 19, 20277,500.00
Total still to collect24,500.00

INV-0103 Brand workshop was for USD 3,200.00 and USD 1,200.00 of it has been paid, so USD 2,000.00 goes on the timeline. It is due Nov 27, 2026, and with the 10-day delay it is assumed to arrive on Dec 7, 2026, which moves it from November 2026 into December 2026. The final payment is due Dec 29, 2026 and assumed on Jan 19, 2027, which moves USD 7,500.00 from December 2026 into January 2027. INV-0101 Website redesign, milestone 2 is due Nov 14, 2026 and stays in November 2026 either way.

Worked example: receipts and running totals by month in USD, with the delays and paid on the due date
MonthReceipts, with the delaysRunning total, with the delaysReceipts, paid on due dateRunning total, paid on due dateDifference
Starting balance8,000.008,000.000.00
November 202610,500.0018,500.0012,500.0020,500.002,000.00
December 20266,500.0025,000.0012,000.0032,500.007,500.00
January 20277,500.0032,500.000.0032,500.000.00

With the delays, USD 10,500.00 arrives in November 2026 and the running total reaches USD 18,500.00. Paid on the due dates, it would be USD 12,500.00 and USD 20,500.00. The gap is largest at the end of December 2026, at USD 7,500.00. By the end of January 2027 both running totals reach USD 32,500.00, the starting balance plus the USD 24,500.00 still to collect.

Grouped by week instead, the same plan has 12 rows, from the week of Nov 2, 2026 to the week of Jan 18, 2027, and 4 of them have nothing arriving in either scenario.

Weeks, month ends and leap years in the timeline

Weeks run from Monday to Sunday and are named after their Monday. A week that spans the new year stays one row: the week of Dec 28, 2026 runs to Sun, Jan 3, 2027, so a payment assumed on Jan 2, 2027 is counted in that row rather than in a separate row for the first days of 2027. A week can also span two months: a payment on Tue, Dec 1, 2026 falls in the week of Nov 30, 2026 when you group by week and in December 2026 when you group by month. Calendar months run from the 1st to the month's last day.

Due dates add calendar days, so a term never jumps to a month end on its own. Net 30 on an invoice issued Jan 31, 2027 is due Tue, Mar 2, 2027, because February 2027 has 28 days. Issued Jan 31, 2028, it is due Wed, Mar 1, 2028, because 2028 is a leap year, and Net 30 from Jan 30, 2028 lands on Tue, Feb 29, 2028 itself.

A due date or payment date that falls on a weekend stays where it is. If your terms move a due date to the next business day, or count business days, work the date out with the payment due date calculator, then set that invoice's payment terms to Custom number of days and enter the number of days from its issue date to that due date. The delay is then added to the date you worked out, in both scenarios.

Choices to make before you rely on the plan

  • The delay. The planner knows nothing about your clients, so the delay is your own estimate, for example from how late each client paid its last few invoices. A delay of 0 makes both scenarios the same. Give a client who usually pays later its own delay on each of its invoices.
  • Which invoices count as sent. Mark an invoice as sent once the client has it, and as planned when you expect to issue it, with the date you expect to issue it. A monthly retainer is one planned invoice per month.
  • What has already been paid. Enter a deposit or part payment under already paid, so only the rest is placed on the timeline. Money already received belongs in the starting balance, not on the timeline.
  • The starting balance. Leave it empty to see invoice receipts alone, or enter the cash available on the plan start date to see a running total that includes it.
  • Weeks or months. Weeks show the gaps between payments more clearly, while months are easier to read over a longer plan.
  • The currency. Make one plan per currency. Amounts are never converted, so a plan in USD should only hold invoices issued in USD. Listing a currency in the planner does not mean Hanko can invoice in it. Invoices can be issued in USD, EUR, GBP, CAD, AUD, AED, SGD or INR.

Assumptions and limitations

  • Every payment date is an assumption built from the terms and delays you enter. A client can pay earlier, later, in parts or not at all, and the planner cannot tell which.
  • The plan counts money coming in from invoices only. Bills, payroll, tax and other payments going out are not included, so the running total is not a forecast of a bank balance.
  • Amounts are counted as invoiced. Payment processing fees, bank charges and currency conversion are not deducted. The net payment calculator estimates what arrives after fees you enter.
  • Days are calendar days. Weekends, holidays and the time a payment takes to reach your account are not considered.
  • The planner does not work out late fees or interest. The late payment calculator models a charge under the terms you enter for an invoice that is already overdue.
  • Limits: up to 200 invoices per plan, terms up to 365 days, delays up to 365 days, and issue dates up to two years after the plan start.
  • Nothing you enter leaves your browser, and the plan is not saved: reloading the page brings the example back. If analytics are on, the page records that the planner was used, that a result was copied, printed or downloaded, and the currency code. References, amounts and dates are never sent.

Due dates and reminders on Hanko invoices

Hanko invoices have an issue date, a payment term (Due on receipt, Due in 7, 15 or 30 days, or a custom number of days) and an editable due date. Choosing a term fills the due date by adding calendar days to the issue date, and a workspace can set a default payment term.

After an invoice has been sent, Hanko can email its contact a reminder from the invoice, if the contact has an email address. A workspace admin can turn on automatic reminders in the invoice settings, sent a chosen number of days before the due date, on it, or after it. Scheduled reminders are skipped once the invoice is paid or closed.

The planner does not read or change anything in Hanko. Once the real invoices are out, compare their due dates with this plan and adjust the delays to what you now expect.

Keep the real invoices and due dates in Hanko

Sign up or sign in to create and send invoices from a Hanko workspace (a new account sets up its workspace first). Nothing from this planner is carried over, so the dates and amounts here stay a plan until you enter real invoices there.