Sending a PayPal Invoice, and What Happens After Someone Pays It
To send a PayPal invoice, open Pay & Get Paid in your PayPal account or app, choose Create Invoice, add your line items and a due date, then send it by email or share the link directly. The customer can pay with a card, a bank account, or their PayPal balance, often without needing a PayPal account of their own. Sending the invoice isn't the part we automate. What happens the moment one gets paid, or doesn't, is, instead of someone checking the dashboard to find out.
How PayPal invoicing actually works
Every invoice starts from the Create Invoice screen under Pay & Get Paid, where you add a customer's email, line items with quantities and prices, any tax or discount, and a due date. PayPal generates a hosted invoice with its own link, which you can send through PayPal's email or copy and send yourself through whatever channel you'd use anyway.
A customer doesn't need a PayPal account to pay it. They can pay as a guest with a card directly on the invoice page, which is a real difference from a standard checkout button that nudges people toward signing up first. That guest option is a big part of why invoicing gets used for one-off business-to-business payments where the customer isn't a PayPal regular.
You can save an invoice's details as a template and reuse it, which covers most of what people mean by 'paypal invoice template' or 'invoice generator' searches, a faster starting point, not a blank form every time. It doesn't, on its own, send that invoice again automatically on a schedule. Each one still gets created and sent as its own action unless something's built to trigger it.
Paying a PayPal invoice is treated the same as any other commercial payment. The standard transaction fee comes out before the money lands in your account, the same as a regular Goods & Services sale, not a separate invoicing charge billed afterward.
Where a paid invoice stops being PayPal's problem and becomes yours
PayPal marking an invoice as paid doesn't tell your accounting system a payment came in, doesn't close the matching order or job in whatever tracks your work, and doesn't tell anyone an overdue invoice needs a nudge. Those are separate, real steps that still wait on a person noticing unless something's watching PayPal's side directly.
Recurring work is the clearest gap. A monthly retainer or a repeat client invoice has to be rebuilt and resent by hand every period, since PayPal's own invoicing tool doesn't run a repeating schedule for you the way a few of its competitors do. That's exactly the kind of flat, repeatable task that's easy to automate once something's talking to the invoicing side of the account directly, generating the invoice on schedule with the right line items instead of someone recreating it from memory.
What we build on top of PayPal invoicing
An invoice that generates itself on schedule
A recurring client or retainer invoice gets created and sent automatically on its own cadence, with the right line items pulled from wherever that data actually lives, instead of someone rebuilding the same invoice from last month's copy.
A paid or overdue invoice that updates everything else
The moment PayPal marks an invoice paid, the matching job or order record updates and the books get the credit, and an invoice that goes quiet past its due date triggers a reminder on its own instead of someone noticing weeks later.
What happens in your business once a PayPal invoice actually gets paid?
Tell us what you're still updating, re-entering, or chasing by hand after the money lands, and we'll look at whether it needs a person at all.
Sending PayPal invoices and still rebuilding the same one every month?
A PayPal invoice getting paid is rarely the last step. Someone still has to update the books, close out the job, or chase the ones that go quiet, and most of that doesn't need to wait on a person remembering. Invoicing's just this page's example. The same question is worth asking about anything else in the business that still runs on someone recreating the same task from memory.
Let's talk