Invoice Methodology — Complete Guide

Tip: Need to create a professional invoice? Use our free Invoice Generator to draft, customize, and download your document in seconds.

CalculatorAI's reference for writing professional invoices that get paid. Every section covers what to include, why it matters, and the region-specific gotchas behind it. Used as the public guide AND as background context for the editor's AI Help mode.

What is an invoice (and what it isn't)

An invoice is a formal request for payment for goods or services already delivered. It exists for three reasons at once: it tells the buyer exactly what they owe and when, it's the document an accountant will match against the buyer's bank statement, and in most countries it's the legal record a tax authority demands if either party gets audited.

Three documents get confused with it constantly. A quote (or estimate, or proposal) is sent before work starts and lists expected costs — it carries no legal obligation to pay. A purchase order is sent by the buyer to the seller, authorising the seller to deliver and bill against it; the eventual invoice usually references the PO number on its face. A receipt is issued after an invoice has been paid, confirming the money arrived; on simple consumer transactions the receipt and invoice can be the same document, but for B2B work they're separate.

The practical rule: invoices flow from supplier to customer after delivery, name a payment amount, and either specify a due date or inherit one from agreed payment terms.

Required fields & what each one is for

A defensible invoice carries seven mandatory blocks. Skipping any of them turns the document into a request your customer's accounts team can legitimately bounce back to you.

Issuer block ("From"). Your business name, address, and tax identifier (VAT/GST/EIN/UTR/SIRET depending on jurisdiction). The address matters because it places your business in a tax regime; the identifier proves you're registered to charge tax in that regime.

Customer block ("Bill To"). Same shape as the issuer block. The buyer's accountant needs your invoice to address their legal entity exactly, not a colloquial nickname, or it won't book cleanly to their ledger. When invoicing a department of a larger company, include the PO number (next section) so the right cost centre absorbs the charge.

Unique invoice number. Sequential, gap-free, and unique to your business. "INV-2026-001" works fine. The "unique" and "no gaps" rules exist because tax authorities use number continuity as a signal that you're not hiding revenue between filed invoices. A missing number invites questions; duplicate numbers between two customers invite fraud accusations.

Issue date. When the invoice was created. Sets the start of any payment-term clock and, in VAT/GST regimes, fixes which tax period the sale falls into.

Due date. When payment must arrive. Either calculated from a payment term (see below) or stated as an absolute date. Both work; the absolute form leaves nothing to interpret.

Line items. One row per distinct deliverable. Description, quantity, unit price, line total. Vague descriptions ("consulting services" with no breakdown) are a leading cause of disputes — buyers won't pay what they can't reconcile.

Totals. Subtotal (sum of line items), tax breakdown, any discount or shipping, grand total, and balance due. List each component on its own line so the buyer can verify your arithmetic without re-running it.

Payment terms explained

Payment terms set the clock between the issue date and the due date. The short forms below appear all over freelance and B2B invoices — knowing what each one promises avoids surprise cash-flow gaps.

Whatever term you pick, write it on the invoice and in the contract that triggered the invoice. Buyers who claim to "have never agreed to Net 15" lose that argument when both documents say the same thing.

Tax handling: VAT vs sales tax vs GST

Three flavours of consumption tax dominate invoicing globally. They look similar on the face of the invoice but compute differently and land on different parties — getting the wrong one is the single biggest source of post-issue corrections.

Value Added Tax (VAT). Used across the EU, UK, and most of Asia and Latin America. Charged at every stage of a supply chain; sellers collect it and remit the net of what they collected minus what they paid on inputs. A typical line item carries the pre-tax price plus a VAT line at the standard rate (UK: 20%, Germany: 19%, Spain: 21%, etc.). Many regimes have a reduced rate for specific goods and a zero rate for cross-border B2B sales between VAT-registered parties — for the latter you write "VAT reverse charge: customer to account for VAT" on the invoice and charge nothing.

Sales tax. Used in the United States. Charged once, at the point of final sale to a consumer, by the state (and often city / county) where the buyer takes delivery. The applicable rate depends on where the buyer is, not where the seller is — and not every state taxes services. If you're a US-based freelancer billing US clients, check whether your service category is taxable in the buyer's state before adding a tax line. Sales tax never appears on a B2B invoice between two registered businesses on a resale transaction (the buyer presents a resale certificate).

Goods and Services Tax (GST). The Australian / Indian / Canadian cousin of VAT. Charged at 10% (AU), 18% (IN typical), or 5–15% (CA, varies by province) on most goods and services. Same accounting mechanics as VAT — collect, remit net of inputs.

The CalculatorAI editor leaves the tax label flexible (you can write "VAT 19%", "Sales Tax 8.875%", "GST 10%", or leave it blank for zero-rated work) because regional labels matter for buyer-side booking.

Payment details: IBAN, SWIFT, routing, sort codes

A common failure mode of a freelance invoice is forgetting the "where do I send the money" block. The buyer's AP team won't email you asking — they'll just delay the payment until you do. Include the payment details block on every invoice, formatted for whatever method you accept.

IBAN (International Bank Account Number). Used across the EU, UK, and most countries outside the US. A 15–34 character alphanumeric string that uniquely identifies a bank account globally — country code (2 letters) + check digits (2 digits) + bank account identifier. Example: GB29 NWBK 6016 1331 9268 19. Always write IBAN in groups of four for readability. Pair IBAN with the bank's BIC (also called SWIFT) — an 8 or 11 character code identifying the bank itself, e.g. NWBKGB2L.

US wire transfers. US banks use a routing number (9 digits, identifies the bank) plus an account number (varies by bank). A wire from outside the US also needs the bank's SWIFT/BIC — e.g. Chase is CHASUS33. Include the bank name and the account holder's name (the legal entity, not a nickname) so the wire clears without manual review.

UK bank transfers. UK accounts use a sort code (6 digits, formatted as XX-XX-XX) plus an account number (8 digits). For domestic UK payments only those two are needed. For international incoming payments, add the IBAN and BIC — UK accounts have both.

Alternatives that don't need bank details. PayPal (email address), Wise (email or "wisetag"), Revolut (@username), and Stripe payment links (a URL that opens a card-payment page). Including these alongside bank details widens the buyer's payment options; some AP teams pay PayPal invoices in 24 hours while wire transfers sit a week.

The CalculatorAI editor stores all of this in one free-text "Payment Details" block precisely because a single invoice often needs more than one method — your German freelance studio billing a US client needs both IBAN+SWIFT (for the EU wire route) and Wise or PayPal (for the faster US-side option).

Currency formatting nuances

Money doesn't format the same way in every currency, and a wrong- looking number is a credibility hit before the buyer even reads the total. Four rules cover most cases.

Decimal places follow the currency, not the locale. USD, EUR, GBP show two decimals. JPY, KRW, VND, ISK, CLP show zero — there is no "half-yen", so ¥1,500.00 looks broken to a Japanese buyer; it should read ¥1,500. KWD, BHD, IQD, JOD, OMR, TND, LYD show three, because those currencies divide into 1,000 fils/dirhams. The editor's currency catalogue carries the correct digit count for every currency and the PDF renderer respects it automatically.

Thousands and decimal marks follow the locale, not the currency. A Spanish reader expects 1.234,56, an American expects 1,234.56, a Swiss reader expects 1'234.56. The same dollar amount needs three different visual treatments. The editor uses the user's selected locale's Intl.NumberFormat for this, so the PDF reads naturally to whoever opens it.

Symbol placement varies. USD, GBP, JPY put the symbol before the amount: $1,234.56, £1,234.56, ¥1,234. CHF and SEK put it after in their own locales: 1,234.56 CHF. International invoices often write the ISO code instead of the symbol — USD 1,234.56 reads unambiguously where $1,234.56 could mean US, Australian, or Canadian dollars.

Cross-currency invoices. If you bill in a currency the buyer doesn't transact in, include an exchange-rate footnote on the invoice: "Amounts shown in EUR; payable in USD at the European Central Bank reference rate on the invoice date." Without this, the buyer guesses the conversion and you receive a different amount.

Late payments & disputes

Most freelance and small-business invoices get paid late at least once. Three preventative moves and one corrective protocol cover the common cases.

Set the consequence on the invoice itself. A line in the Terms block — "Late payments incur a 1.5% monthly fee on the outstanding balance" — gives you something to point at when chasing. The fee itself rarely gets collected; what it does is signal to the buyer's AP that you'll escalate, which moves your invoice up the queue.

Send a reminder one week before the due date. This isn't chasing — it's filing your invoice into the buyer's payment run for the correct week. Most AP teams batch payments; a polite "due next Wednesday" reminder gets you onto that batch.

Make the next step on Day +1 specific. Don't email "any update?" on the day after — that's information-free for the buyer's AP. Say "Invoice INV-2026-007 was due yesterday; please confirm the payment date." If they respond with a date, the conversation moves forward; if they don't respond at all, that silence is the dispute trigger for the next step.

Disputes follow a fixed escalation. Day +3 after due: second email, same precision. Day +7: phone the AP contact directly — voice contact resolves most stalls. Day +14: written notice from you to the buyer's senior contact (founder, CFO, whoever signed the original contract). Day +30: lawyer's letter, collection agency, or small-claims court depending on amount and jurisdiction. The escalation works because each step is one click higher in the buyer's org chart; few invoices need to go past Day +7.

If the buyer disputes the amount rather than refusing to pay, issue a credit note referencing the original invoice number and the disputed portion — adjust the balance, don't void the original document.

AI Fill — how the editor's AI works (and prompts that work well)

CalculatorAI's AI Fill turns a one-line description of billable work into structured invoice line items. It runs the user's text through the Claude API with a tightly scoped system prompt: classify the input, either parse it into items or answer the user's how-to question, never invent numbers that weren't in the input.

Prompts that work well are concrete about both the deliverable and the unit math. Compare:

• ❌ "Frontend dev work for last sprint" — no quantity, no rate. AI has nothing to extract and either skips it or asks for clarification.
• ✅ "Frontend dev, 40h at $90/hr" — one line, qty 40, rate 90.
• ✅ "5 design revisions at $200 each plus 1 onboarding workshop for $1,500" — two lines extracted, units and rates preserved.
• ✅ "Logo design — 1500 USD" — one line, qty 1, rate 1500 (AI infers it's a one-off when no quantity is given).

What AI Fill won't do. It won't invent a quantity or rate that wasn't in your text — better to skip a line than guess wrong. It also won't make up descriptions; if you write "stuff for Bob" it produces a line called "stuff for Bob" without padding. Maximum 10 lines per call (a hard limit so a verbose model can't explode the invoice).

The Help mode. If your input reads more like a question than a description ("how do I add tax?", "where do I put the logo?"), AI switches to help mode and answers in plain language pointing at the specific control. Same Claude call, different branch — there's no separate chat to open.

Common invoice mistakes

The mistakes below show up over and over in invoices that bounce or get paid weeks late. Skim once before you send.

The vague line item. "Services rendered — $5,000" doesn't tell the buyer's AP what they're booking. Split into actual deliverables even if the contract was for a flat fee: itemise the components so the amount has texture.

Missing PO reference. If the buyer issued a PO, write it on the invoice. AP systems route by PO; an invoice without one sits in a manual queue while someone figures out which cost centre absorbs it.

Wrong legal entity in Bill To. "Acme" versus "Acme Inc." versus "Acme Holdings, LLC" matters — the buyer's accountant matches your invoice to their entity's vendor record. Confirm the exact legal name before invoicing a new customer.

Tax line where there shouldn't be one. A US freelancer adding a sales tax line to a B2B services invoice between two US states where services aren't taxable creates a bookkeeping problem for the buyer. A UK freelancer not on the VAT register charging VAT is illegal. When in doubt, leave the tax line blank and write "VAT not applicable — supplier under threshold" in the notes.

Reusing invoice numbers. Two invoices to two customers with the same number make your filing look like duplicate-billing fraud. The numbering is per-supplier, gap-free, monotonic. If you void an invoice, mark it as such — don't reuse its number.

No payment details. You're inviting delay. Even if "the client knows how to pay you", an invoice with no payment block looks incomplete and gets routed to manual review.

Inconsistent currency. Choose one currency per invoice. If you need to bill in two (line items in a service currency, totals converted), use two separate invoices.

Country-specific gotchas

The fields above cover most invoices. Local jurisdictions add requirements that are easy to miss when working across borders.

United States. No federal invoice format — the IRS doesn't specify one. State sales tax rates and rules vary widely; check buyer-state taxability before adding a tax line on a B2B service. If you're paid more than $600 by a single client in a tax year, expect a Form 1099-NEC at year-end and reconcile your invoice total to it. Independent contractors should never charge sales tax on labour in most states; check the specific exemption code.

European Union. All VAT-registered businesses must show their VAT ID on every invoice. Cross-border B2B sales within the EU typically use the reverse charge mechanism: the supplier charges 0% VAT and writes "Reverse charge: customer to account for VAT" on the invoice. The customer reports the VAT in their own country at their own rate. For B2C sales across borders, the OSS (One Stop Shop) regime applies if the supplier's annual cross-border revenue exceeds €10,000.

United Kingdom. Since 2019, Making Tax Digital (MTD) requires VAT-registered businesses to file VAT returns digitally and keep electronic records of every invoice. Invoices themselves can still be PDFs, but the underlying data has to live in MTD-compatible software or a "bridging" tool. If you're under the £85,000 turnover threshold, you're VAT-exempt and shouldn't charge VAT at all.

Canada. GST (5% federal) plus PST or HST (provincial, varies) — Ontario uses HST 13%, BC uses GST + PST separately, Alberta uses GST only. Always show GST/HST registration number on the invoice if you're registered, or "Not registered for GST/HST" if you're under the $30,000 small-supplier threshold.

Australia. GST 10% charged on most domestic supplies. Tax invoices for sales above AUD 82.50 must include the supplier's ABN (Australian Business Number) and the words "Tax Invoice" prominently. Without those, the buyer can't claim the GST credit.

Japan. As of October 2023, the qualified invoice system requires registered businesses to include a 13-digit registration number; otherwise the buyer can't deduct input consumption tax. Consumption tax (CT) is 10% standard, 8% reduced for food.

India. GST registration is mandatory above ₹40 lakh annual turnover. Invoices need a GSTIN (15-digit Goods and Services Tax Identification Number), the HSN code per line item, and place of supply (state name + code) for both supplier and buyer.

When billing across borders, ask the buyer what their AP system expects — they'll tell you in one email, and you save weeks of back-and-forth.

Quick reference: the eight-check pre-send list

Before clicking Download or Send, run down the list:

1. Issuer block — your legal name + address + tax ID.
2. Customer block — buyer's exact legal entity name.
3. Invoice number — unique, sequential.
4. Dates — issue date present; due date or term explicit.
5. Line items — every deliverable has a description, qty, rate.
6. Tax line — correct for the regime; or absent if zero-rated.
7. Totals — subtotal + tax + discount + total + balance due.
8. Payment details — IBAN / routing / sort code / PayPal — at least one method, formatted readably.

Anything that doesn't pass these eight checks is paying you a guaranteed week of delay. Eight items, two minutes.