Your invoicing
Link the system you already issue invoices from and they sync in on their own, PDFs included, and keep syncing as you issue more.
Enter the workspace name you chose when you signed up.
One click ages every invoice against its sent date, decides who gets chased, and writes each reminder from your own inbox — first, second, final notice — until the money lands.
Payloopy needs two things: somewhere to read your invoices from, and a mailbox to write from. Both are yours, and you pick them in about two minutes.
Link the system you already issue invoices from and they sync in on their own, PDFs included, and keep syncing as you issue more.
Not using invoicing software? Keep the list in a spreadsheet and Payloopy reads it. Nothing to migrate.
Reminders go out from your own address, so they land in the inbox and look like you wrote them.
Enter invoices directly in the app when there is nothing to connect. A direct connection only saves you the typing.
Missing yours? A direct connection only saves you the typing — a spreadsheet works today either way. Ask for the one you need and it goes straight to the person who writes the code.
No spreadsheets to maintain, no calendar reminders, no mail merge. Four moves and you are done.
Connect the system you already invoice from, point it at a spreadsheet, or type the list in by hand. Payloopy pulls everything in and keeps pulling as you issue more.
Every run re-ages every invoice against its sent date, so "23 days overdue" is current the moment you look. You never recalculate anything, ever again.
Say it plainly: over 7 days gets the friendly nudge, over 14 gets the firm one, over 30 gets the final notice. Filter on amount, client, status or date too.
Payloopy writes each reminder from your own email account with the invoice number, amount and days overdue already filled in. Every run is logged and exportable.
Reminder logic is built from modules on a canvas — source, variable, router, email. You can see the whole chain, run a single module on its own, and read every message before it goes anywhere.
You write the wording once, in any language. Payloopy fills in the details per invoice.
Organisations hold scenarios, scenarios hold runs, runs hold every message. Nothing happens that you cannot go back and read.
One pass re-ages every invoice, applies your rules and writes every reminder that is due. Run it as often as you like — there is no per-run or per-message charge. Today you start each run yourself.
Every run, every message, every outcome — kept and downloadable. Your accountant can have the file.
Everything lives at yourname.payloopy.com — your organisation, your scenarios, your data, on your own subdomain.
Push too hard and you strain the relationship. Push too softly and you get ignored. Decide the ladder once, calmly, and let it climb itself.
7, 14 and 30 days is where most people start — it is a suggestion, not a setting you are stuck with. Choose your own days, add as many reminder stages as you need, and filter on amount, client, status or date too.
A short note that assumes the best: it probably slipped past. Most invoices never need anything more than this.
Facts, plainly stated: the number, the amount, the date it went out, and a direct request for a payment date.
The message you would never get around to writing. It goes out on time, in your words, without you having to feel anything about it.
Nobody pays an invoice that stopped being mentioned. The reminder that never got written is the one that costs you the most.
A gentle nudge at day seven. A firmer one at fourteen. A final notice at thirty. The same three emails, retyped for every client.
€29 a month against a single invoice that would otherwise have gone quiet. The maths stops being interesting very quickly.
One pass, in your own workspace. Sources in, ageing applied, rules resolved, messages written into your mailbox, the whole thing logged.
Leave sending switched off and every reminder is written into your own drafts folder instead. Nothing reaches a client until you turn sending on yourself.
Permission to create drafts and send mail is granted through your email provider's own sign-in screen. Revoke it there and Payloopy stops sending immediately.
Invoices come from your own systems and mail goes through your own account. Payloopy does not own or keep anything.
There is no sales team, no call centre, and no wall of logos — it is new, and pretending otherwise would be a bad way to start.
What you get instead: the person who writes the code answers your email. If something breaks, it gets fixed by the one who built it. If you need it to do something it does not do yet, that request goes straight to the top of the list — because there is no list above it.
It is also why nothing here is designed to trap you. It bills monthly with no minimum term, your reminders go out through your own mailbox, and your whole history downloads as a file the day you decide to stop.
Because there is nobody to quote yet, and invented praise is the cheapest thing on the internet.
The founder reads every message sent to support. That is not a service promise, it is just arithmetic.
You pay first. So here is exactly what protects you, right next to the price.
Billed monthly. VAT may apply depending on your country and VAT number.
One invoice paid on time covers the year.
Leave sending switched off and Payloopy writes every reminder as a draft in your own mailbox instead. You read them, you decide. Nothing reaches a client until you turn sending on yourself.
Every run and every message is exportable to CSV whenever you want it. Leaving is a download, not a negotiation.
A monthly subscription with no minimum term. Cancel and you keep access until the end of the period you already paid for.
Set your reminder rules once. After that, chasing every overdue invoice you have is one click.
Draft mode on by default · monthly, no minimum term · cancel anytime