What Should Be on an Invoice? 10 Fields That Make It Legally Valid

Why Invoice Format Matters

An invoice is not just a receipt. It is a legal record of a transaction between a buyer and seller. In most jurisdictions, invoices are required for tax purposes, compliance audits, and dispute resolution. A poorly formatted or incomplete invoice can be rejected by a client's accounting system, flagged by tax authorities, or questioned in a dispute.

The good news: the required fields are standardized. Once you know what they are, every invoice you create will be compliant.

Field 1: Your Business Name and Details

The top of the invoice must clearly identify you (the seller). Include:

• Your full legal business name (as registered with tax authorities).
• Your postal address (city, state, postal code).
• Your tax registration number (GST number in India, VAT number in EU, ABN in Australia).
• Your contact details: phone number and email address.

For sole traders and freelancers, your legal name is your business name. For companies, it is the registered company name. If you are not registered for tax purposes, you still need to state this clearly on the invoice (e.g., "Not GST registered" in India).

Field 2: Client Name and Details

Clearly identify the buyer. Include:

• Full legal name (person's full name for individuals, company's registered name for businesses).
• Postal address (city, state, postal code).
• Tax registration number (if applicable and if they are a business).

For B2C invoices (selling to individuals), a simple name and address are sufficient. For B2B invoices, the buyer's tax registration number (GST number or VAT number) is often required by their accounting system. Ask corporate clients for their GST number before sending the invoice.

Field 3: Unique Invoice Number

Every invoice must have a unique sequential number. Start with "001" for your first invoice and increment by 1. This is a legal requirement in most jurisdictions. Why? Because it prevents duplicate invoicing and allows both you and the client to trace the invoice for payment and reconciliation.

Do not reuse invoice numbers. Do not skip numbers. Do not use non-sequential numbering (e.g., "Invoice-Alpha," "Invoice-Beta"). Sequential numbers are the standard.

Field 4: Invoice Date

The date the invoice is created or issued. This is different from the date of the work. An invoice issued on 15 May for work completed on 10 May should show 15 May as the invoice date. This date is used to calculate the due date and is required for tax compliance.

Field 5: Due Date

When the client must pay. This is typically 7, 14, or 30 days from the invoice date (depending on your agreed payment terms). For example: Invoice date 15 May, Due date 15 June (Net 30 terms).

A due date is legally required in most jurisdictions. It prevents disputes about when payment is actually due. State it explicitly as "Due date: 15 June 2025" rather than leaving it ambiguous.

Field 6: Itemized Description of Goods or Services

This is the core of the invoice. List each item, service, or deliverable separately. For each line item, include:

• Description: what was delivered or performed.
• Quantity: how many units, hours, or items.
• Rate: the price per unit.
• Amount: quantity × rate.

Example: "Brand strategy consulting — 8 hours at ₹5,000/hour = ₹40,000." This level of detail prevents disputes and helps clients verify the invoice matches what was ordered.

Field 7: Tax Calculation and Breakdown

If you are registered for tax (GST in India, VAT in EU), you must show tax separately on the invoice. In India, a GST invoice must show:

• CGST (Central Goods and Services Tax) — as a percentage and amount.
• SGST (State Goods and Services Tax) — as a percentage and amount.
• Or IGST (Integrated GST) for inter-state or international sales.

If you are not registered for tax, state "No tax applicable" or leave the tax field blank. A tax field showing 0% is correct.

Field 8: Subtotal, Tax Total, and Grand Total

Show the math clearly:

• Subtotal: sum of all line items before tax.
• Tax (CGST, SGST, or IGST): total tax amount.
• Grand Total: subtotal + tax.

A client's accounting system will verify these calculations. An error here delays payment. Double-check your math before sending.

Field 9: Payment Instructions

Tell the client how to pay you. Include:

• Bank account details (account number, account holder name, IFSC code).
• UPI ID (if you accept UPI).
• Payment gateway link (if applicable).
• Preferred payment method.

The easier you make payment, the faster the client pays. Missing payment instructions force the client to contact you for your bank details — a delay you want to avoid.

Field 10: Your Signature or Certification

In some jurisdictions and industries, invoices require a signature or a certification statement (e.g., "Certified that the above details are correct"). Check your local tax rules. In India, GST invoices do not require a signature. In other countries, they may. A browser-based invoice generator typically does not include this field, but you can add it manually by printing the PDF and signing it, or by using a digital signature.

Optional But Recommended Fields

• PO reference: If the client provided a purchase order number, include it. This helps their finance department match your invoice to their approved purchase.
• Project or contract reference: A reference code or project name that links the invoice to the agreement that triggered it.
• Notes: Any special terms, discounts, or follow-up actions (e.g., "Early payment discount: 2% if paid within 7 days").

Common Mistakes That Cause Payment Delays

• Vague descriptions ("Services rendered" instead of "8 hours of consulting on Q2 planning").
• Wrong due date (calculated from the wrong baseline date or omitted entirely).
• Missing tax ID (especially critical for GST-registered businesses in India).
• Incomplete payment details (bank account without IFSC, or UPI without clarity).
• Arithmetic errors in tax or total calculations.
• Missing client name or address (prevents matching in accounting systems).