Invoice Generator

• Unique invoice number — sequential or formatted (e.g., 2026-001, 2026-002). Required by tax authorities in most jurisdictions; non-negotiable for VAT-registered businesses.
• Invoice date and due date — explicit dates. "Net 30" with no issue date is ambiguous.
• Seller details — legal name, address, tax ID (VAT, NIP, EIN, ABN). For cross-border B2B sales in the EU, both VAT IDs are required for zero-rated invoices.
• Buyer details — legal name and address. For B2B EU VAT zero-rating, buyer's VAT ID is mandatory.
• Line items — description, quantity, unit price, line total. Detailed enough that the buyer's AP can verify against the PO or scope of work.
• Subtotal, tax breakdown, total — tax should be broken out by rate if multiple rates apply. "Total inc. VAT" without a breakdown fails most tax-audit requirements.
• Currency — explicit, three-letter ISO code (USD, EUR, PLN, GBP). "$" is ambiguous (USD vs AUD vs CAD vs SGD vs HKD vs MXN).
• Payment terms and methods — bank account (IBAN/SWIFT for international), payment-service IDs (PayPal email, Stripe link), or "see attached payment instructions". A vague "please pay" is the most common cause of delayed payment.

• B2B intra-EU services — reverse charge applies. Seller invoices €0 VAT; buyer self-accounts. Both VAT IDs required on invoice.
• B2B intra-EU goods — generally also reverse charge under certain conditions. Different rules than services; check.
• B2C intra-EU below thresholds — seller charges their own country's VAT.
• B2C intra-EU above OSS thresholds — seller registers under OSS (One-Stop-Shop) and charges buyer's country VAT.
• B2C non-EU buyer — outside EU VAT scope; usually no VAT, but specific rules for digital services (sold under OSS Non-Union if applicable).
• US sales tax — varies by state, by city, by product type. Nexus rules trigger collection obligations. Significantly more complex than EU VAT for cross-state sales.
• Poland JPK_V7 — invoices must be reported electronically with structured XML. Affects every Polish VAT-registered seller.

These rules change frequently. A tool can structure the invoice correctly; whether the tax treatment is correct is your accountant's call.

• You are a freelancer or small consultancy invoicing 1-50 invoices per month and a full bookkeeping suite (QuickBooks, Xero) is overkill.
• You need a one-off invoice on the road and want a clean PDF without paying for a subscription.
• You are testing what a "good" invoice template looks like before standardizing across your business.
• You are issuing a final invoice to a client and want to ensure all the legally-required elements are present before sending.

• It will not maintain your invoice numbering. Sequential numbering is your responsibility (and required for tax audits). For volume, use accounting software.
• It will not file VAT returns or report to JPK_V7 / Making Tax Digital. Generated invoices are PDFs; reporting requires structured XML/CSV submissions through your accounting software or directly to tax authorities.
• It will not collect payment. Embed Stripe / PayPal / bank transfer details; payment happens out of band.
• It will not give legal or tax advice. The structure is correct; whether your tax classification matches reality is a question for your accountant.