Customers who paid on card still need a PDF for accounts payable. Use a form so they can request an invoice with a PO or job reference and a bill-to that includes ZIP or postcode, instead of tagging random people on LinkedIn.
Notifications to ar@, not sales@.
Unreferenced asks become archaeology.
‘Need a PDF invoice?’ should hit this URL.
Close the ticket in the dashboard when sent.
An invoice request is the customer asking you to raise or resend a bill: first issue, duplicate PDF, or a VAT-compliant original for a UK organisation that cannot pay on a card receipt. US AP teams need EIN-style vendor details on the PDF you send later; the web form only needs enough to find the job and the bill-to address.
This is not invoicing software. QuickBooks and Xero still raise the document. The form is the ticket that stops ‘please invoice us’ from dying in a salesperson’s mentions.
Wrong bill-to is how invoices bounce and days-sales-outstanding grow.
Never collect full card PANs here. You are issuing a bill, not taking a new payment method.
Portals help incumbents. First-time AP clerks still Google your domain.
Link it from every receipt email footer.
Great once the customer is in the system. This form creates the ticket before that.
The classic. Easy to miss when the thread is 40 messages.
Invisible to finance. Force the form so AR owns the SLA.
Even SaaS marketing sites are static. A /billing form posts to your form backend so finance is not waiting on a CMS plugin.
Mention VAT invoices for UK buyers and sales-tax exemption certificates for US buyers in the details placeholder—do not collect certificate images on an open form if you can send a secure link instead.
If you need that, add a textarea after copy. Most asks are ‘invoice job 441’.
Your PDF must be compliant. The form only collects who and which job.
Search the dashboard by email before you raise a second PDF.
No. Send your usual payment link on the invoice you raise.