Record an Invoice as Sent
Not every invoice leaves through Flowtly. You might email one from your own mailbox, post it, or hand it over at a meeting. "Mark as sent" writes that delivery down, so the invoice is treated like any other sent invoice instead of waiting for a dispatch that already happened.
Recording a delivery sends nothing. No PDF is generated, no email leaves Flowtly, and nothing is submitted to KSeF or any other e-invoicing channel. It records a delivery that happened somewhere else.
Before you start
- You need the invoices manager role. The same role can undo the record.
- The invoice must be issued and awaiting payment. A draft cannot be recorded as sent — issue it first.
- An invoice Flowtly has already sent, or that has already been recorded as sent once, cannot be recorded again.
Record the delivery
- In the invoice list, click the "More Options" button on the invoice's row — or open the invoice's preview.
- Choose "Mark as sent".
- Optionally set "Delivered on". It defaults to today and cannot be in the future.
- Optionally add a "Note (optional)" saying how it went out, for example sent by email from the office mailbox. Up to 500 characters.
- Click "Record delivery".
The invoice's status becomes Sent, exactly as if Flowtly had emailed it.
Both dates are kept: the day you say it was delivered, and the day you recorded it. "It was posted on the 29th" and "it was written down on the 2nd" are different facts, and the invoice's history shows both, along with who recorded it.
What changes once it is recorded
- The invoice is chased for payment. It joins the overdue lists and the payment reminders — which is the reason to record the delivery at all.
- It shows as Sent in the invoice list.
- It now counts as issued for the accountancy exports, and appears in them.
- Its history shows the delivery was recorded by hand rather than emailed by Flowtly.
Undo a recorded delivery
If you recorded it by mistake:
- Open the invoice's preview — the undo is offered there, not on the list row.
- Choose "Undo mark as sent".
- Optionally give a "Reason (optional)".
- Click "Undo the record".
The invoice goes back to awaiting delivery and stops being chased for payment: it leaves the overdue lists and no further reminders go out.
The invoice stays in the accountancy exports
This is deliberate, and it is the part worth understanding before you record anything.
Recording the delivery is what makes the invoice count as issued, and undoing the record does not take that back. The invoice remains in the accountancy exports, with the original record still visible in its history.
The reason is that an export the accountant has already seen should not quietly lose a document. Flowtly keeps the correction visible instead of erasing the fact. This is also why a draft cannot be recorded as sent: that is the one case where staying in the exports would be wrong, because the invoice was never issued at all — so the action is refused up front rather than leaving you with a record you could not undo.
What the undo cannot do
- It works once. After an undo, the invoice cannot be recorded as sent by hand again. Flowtly can still send it normally.
- It only takes back a hand-made record. An invoice Flowtly really emailed cannot be put back to awaiting delivery — the client already has the PDF, and stopping its reminders would be wrong.
- It disappears once the invoice is edited. If you change the invoice after recording the delivery, the undo is no longer offered: the invoice then carries the "changed after the client saw it" signal, and the undo would erase it.
Example use cases
- An invoice emailed from your own mailbox: record it so it is chased for payment, without sending the client a second copy.
- An invoice handed over at a meeting: record it with the date it changed hands.
- An invoice posted on paper: record the posting date and note the method.
- A wrong row: undo the record the same day, before the reminders start, and the invoice goes back to awaiting delivery.