Invoice Generator

TL;DR

Use this generator to create a simple invoice PDF (via print/save as PDF) for common contractor workflows. It’s ideal for drafts and quick client documents.

If you also need a proforma or receipt, use:

Who this is for

• Freelancers/contractors who need a quick, clean invoice layout.
• People who want to sanity-check totals (subtotal + VAT).
• Teams that want a consistent invoice format without exporting from accounting software.

How to use it

1. Fill issuer (your company/PFA) and customer details.
2. Add items (description, quantity, unit price).
3. Toggle VAT on/off and set the VAT rate if needed.
4. Click “Print / PDF” and save as PDF in your browser.

What makes a good invoice (practical checklist)

Clients reject invoices for boring reasons: missing details, mismatched totals, unclear payment terms. Before you send an invoice, double-check:

• Supplier / issuer details are correct (name + address + identifiers as applicable)
• Customer details match what your client expects (especially legal name)
• Invoice number and issue date are present and consistent
• Payment terms are clear (due date, bank details, currency)
• Line items are understandable (“what is being billed?”)
• VAT presentation matches your agreement (net vs VAT vs gross)

This tool helps you produce a clean PDF, but it can’t know your exact legal/contract requirements — validate with your accountant if you’re unsure.

Invoice vs proforma vs receipt (Romania)

These documents are often mixed up:

• Invoice: the billing document for payment (what most clients require for payment processing).
• Proforma: a “pre-invoice” / quote-like document used before payment, depending on client workflow.
• Receipt: proof of payment collection (used in specific scenarios).

If your client asked for “a proforma first”, use Proforma template. If you need a receipt layout, use Receipt PDF (quick). For a deeper explanation, read: Invoice vs proforma vs receipt : when to use each.

Worked examples

Example 1: fixed monthly retainer

One line item: “Software development services – monthly retainer”, qty 1, unit price = your monthly fee.

Example 2: day-rate invoice

Line item: “Development services”, qty = working days, unit price = day rate.

Example 3: mixed services

Separate line items for dev + consulting + expenses so the client can approve and account for them separately.

Example 4: multi-currency contracts

If your contract is in EUR but you have expenses in RON:

• invoice in the contract currency
• avoid mixing currencies across line items
• use your accountant’s guidance for FX handling and recordkeeping

Edge cases & gotchas

• Always confirm what fields your client requires (purchase order, contract reference, etc.).
• If you’re VAT registered, align VAT rate and wording with your accounting setup.
• Currency should match what you agreed with the client; avoid mixing currencies across line items.
• This generator does not validate legal compliance for every edge case.

FAQ

Is this e-Factura compliant?

Not by itself. For e-Factura XML handling, use:

Can I add my logo?

Yes. You can upload a logo (PNG/JPG/SVG) in your browser: it shows in the preview and when you Print / Save as PDF. The file stays local (it’s not uploaded to the server).

What should I read next?

See Invoice vs proforma vs receipt : when to use each.

What should I use for VAT math?

Sources

• ANAF: https://www.anaf.ro/
• Romanian legislation portal: https://legislatie.just.ro/

Next steps (IT Jobs List)

For documents (invoice/proforma/receipt), consistency beats “perfection”: numbering rules, correct data, and complete fields.

Related tools

Related guides

Quick recommendation

• Save your assumptions (rates, breaks, thresholds) so you can reproduce the result.
• If you use the output in an invoice/offer, include a short explanation (what’s included and what’s not).

Practical checklist (IT Jobs List)

• Verify required fields (issuer, client, number, date, description, totals).
• If you charge VAT, include base + VAT + total and the VAT rate.
• Keep consistent numbering and clear line-item descriptions.