Invoice vs Pay Stub vs Receipt: Which Document to Use for Employees and Contractors

Overview

Here is the short version: an invoice asks for payment, a pay stub explains payroll that has already been processed, and a receipt confirms that payment was made or received. Once you separate those three jobs, most paperwork confusion becomes much easier to solve.

An invoice is generally used before payment. It is a billing document. A contractor, freelancer, or vendor sends it to your business to request payment for completed work, products, or services. In some businesses, the company itself also issues invoices to customers. In the context of worker payments, invoices are most often tied to independent contractors rather than employees.

A pay stub is usually connected to payroll. It shows how gross pay became net pay by listing earnings, taxes, deductions, reimbursements, and sometimes paid time off balances. A pay stub is commonly issued to employees as part of a payroll record. It is not a request for payment. It is a statement of how payroll was calculated.

A receipt is a confirmation document after payment. It proves that a transaction took place. A receipt may show the amount paid, date paid, payment method, and reference number. It does not replace an invoice or a pay stub. It closes the loop on the payment side of the transaction.

For many small businesses, the most common mistake is using employee-style payroll documents for contractors or expecting contractors to submit payroll-style documentation. Another common mistake is treating a receipt as if it contains all the detail needed for accounting, approvals, or tax records. Usually, it does not.

A simple way to remember the differences is this:

• Invoice: “Please pay this.”
• Pay stub: “Here is how this payroll payment was calculated.”
• Receipt: “This payment happened.”

If your business manages both W-2 employees and 1099 contractors, you need all three concepts clear in your workflow. For more on worker classification and payment treatment, see 1099 vs W-2 Payroll Rules: Worker Classification, Taxes, and Payment Differences.

How to compare options

The easiest way to decide which document to use is to compare them across five practical questions: who creates it, when it appears, what it communicates, what records it supports, and who should receive it.

1. Who creates the document?

Invoices are commonly created by the party requesting payment. In a contractor relationship, that is often the contractor. Pay stubs are created by the employer or payroll system as part of the payroll run. Receipts are created by the seller, service provider, payment system, or payer depending on the workflow.

If your bookkeeper is asking whether a worker should “send a pay stub,” that is usually a sign that the process needs to be corrected. Employees do not normally send pay stubs to ask for wages. Contractors generally do not receive employee pay stubs through payroll just because they completed a project.

2. At what point in the process is it used?

Think in sequence:

1. Work is agreed and completed.
2. An invoice may be submitted to request payment.
3. The payment is approved and sent.
4. A receipt or payment confirmation may document that the payment occurred.
5. If the worker is an employee, payroll also generates a pay stub explaining the compensation details.

This timing matters. A pay stub cannot replace an invoice because it comes after payroll calculation, not before approval. A receipt cannot replace an invoice because it does not ask for payment. An invoice cannot replace a receipt because it does not prove the funds were actually sent.

3. What information does each document communicate?

An invoice communicates billing details: what was done, for whom, when, for how much, and under what payment terms. A pay stub communicates payroll details: wage type, hours, earnings, taxes, deductions, and net pay. A receipt communicates transaction completion: amount paid, date, payment method, and reference.

If your main concern is how the amount was calculated, use a pay stub for employees and supporting billing detail for contractors. If your main concern is whether the money changed hands, use a receipt or payment confirmation. If your main concern is what needs to be paid, use an invoice.

4. What records does it support?

Invoices help support accounts payable, approval workflows, contract billing, and contractor documentation. Pay stubs support payroll records, employee communication, and wage detail records. Receipts support payment reconciliation, bookkeeping, and audit trails.

One document can support more than one function, but none of these documents should be expected to do every job by itself. Clean operations usually rely on a chain of documents rather than a single catch-all file.

5. Who should receive it?

Invoices go to the party responsible for payment approval and processing. Pay stubs go to employees and payroll recordkeeping systems. Receipts may go to the payer, the payee, or both, depending on how the transaction is recorded.

That means the right answer often depends on the worker type:

• Employee: time records, payroll approval records, pay stub, payment confirmation as needed
• Contractor: contract or statement of work, invoice, approval record, payment confirmation or receipt, year-end tax documentation as applicable

If you need a broader process for contractor billing and year-end tracking, review Independent Contractor Payment Process: Invoices, Approvals, 1099 Tracking, and Year-End Prep.

Feature-by-feature breakdown

This section breaks down the practical differences in more detail so you can map each document to the correct workflow.

Invoice

Main purpose: request payment.

Best fit: contractors, freelancers, consultants, agencies, and vendors. In some internal reimbursement or intercompany contexts, businesses may adapt invoice-style documents, but contractor billing is the most common use in this topic.

Typical contents:

• Business or contractor name and contact details
• Client or payer name
• Invoice number
• Invoice date
• Service period or project dates
• Description of work or deliverables
• Quantity, rate, and total amount due
• Payment due date and terms
• Tax treatment if relevant to the transaction structure
• Payment instructions

What it is not: an employee wage statement, proof of payroll withholding, or proof that payment already happened.

Common confusion: Some businesses ask contractors for pay stubs because they want backup for hours or tasks. In reality, what they usually need is either an itemized invoice, a timesheet attachment, or a milestone approval form. A contractor can invoice by project, by milestone, by retainer, or by hours, but that is still invoicing rather than payroll.

Operational tip: If you routinely question contractor invoices after they arrive, your issue may be weak intake standards. Create a standard invoice requirement list: approved vendor name, matching purchase order or contract reference, service dates, clear descriptions, and approver signoff.

Pay stub

Main purpose: explain payroll results.

Best fit: employees paid through payroll.

Typical contents:

• Employee name and identifying information
• Pay period start and end dates
• Pay date
• Hours worked, when relevant
• Regular, overtime, bonus, commission, or other earnings categories
• Gross pay
• Taxes withheld
• Benefits deductions or other authorized deductions
• Employer or employee contributions where shown
• Net pay
• Year-to-date totals in many systems
• Leave balances in some systems

What it is not: a bill from the worker to the company, a contractor invoice, or a receipt.

Can contractors get pay stubs? In a standard setup, a contractor is not paid through employee payroll as though they were a W-2 employee, so the answer is generally no in the normal employee-payroll sense. If a business creates a remittance advice or payment summary for a contractor, that may look somewhat similar to a pay statement, but it is still not the same thing as an employee pay stub. The safer practice is to use invoice-based documentation for contractors and payroll-based documentation for employees.

Operational tip: If employees frequently ask questions about their checks, review whether your pay stub includes enough detail to reduce confusion. Pair it with a clear payroll cutoff and approval process. Related reading: Payroll Cutoff Dates Explained: How to Set Deadlines for Timecards, Approvals, and Corrections.

Receipt

Main purpose: confirm payment or transaction completion.

Best fit: both employee-related reimbursements and contractor or vendor payments, depending on context.

Typical contents:

• Date of payment
• Amount paid
• Who paid and who received payment
• Payment method
• Reference or transaction number
• What the payment was for, at a high level
• Status such as paid, completed, or settled

What it is not: a detailed earnings breakdown or a formal billing request.

Common confusion: A bank confirmation, payment processor email, or accounting system note may function as payment evidence, but it may not contain all of the business context needed for your records. If you rely only on those confirmations, you may struggle later to match payments back to the correct invoice, contract, or worker file.

Operational tip: Store receipts and payment confirmations with the originating invoice or payroll batch, not in a separate inbox that nobody audits. Your records become much more useful when the request, approval, and proof of payment stay connected.

At-a-glance comparison

• Before payment: invoice
• During payroll processing: pay stub generated as part of payroll output
• After payment: receipt or payment confirmation
• For employees: pay stub is central; invoice usually is not
• For contractors: invoice is central; employee pay stub usually is not
• For reconciliation: receipt helps prove completion

If hours are part of the dispute, the real missing document may be a timesheet or approved hours report rather than any of the three documents in this article. In that case, your process should connect time records to payroll or contractor billing approval. See How to Calculate Payroll Hours Correctly: Breaks, Rounding, Travel Time, and Training Time.

Best fit by scenario

The right document becomes clearer when you test it against real business situations. Use these scenarios as a decision guide.

Scenario 1: You pay hourly employees every two weeks

Best document: pay stub.

Your employees should submit time through your approved timekeeping process, not send invoices. After payroll is run, they receive a pay stub showing hours, pay rate or earnings categories, deductions, and net pay. A payment confirmation may also exist in the background, but the employee-facing explanation document is the pay stub.

Scenario 2: You hire a freelance designer for a one-time project

Best document: invoice.

The designer completes the work and sends an invoice according to your agreed terms. Your business reviews and approves it, then pays it. Once payment is sent, a receipt or transaction record can confirm completion. There is usually no employee pay stub involved.

Scenario 3: A contractor bills by the hour every week

Best document: invoice, often with timesheet support.

If you need detail, ask for an itemized invoice or attach an approved timesheet. Do not convert the contractor into an employee-style payroll workflow just because the billing is hourly. Hourly billing does not automatically mean payroll.

Scenario 4: An employee says their net pay looks wrong

Best document: pay stub, plus payroll records.

The pay stub should show the earnings and deductions that explain the result. If there is an actual error, correct it through payroll rather than issuing a receipt or asking the employee for an invoice. If corrections are needed, see Payroll Error Correction Guide: Missed Hours, Overpayments, Underpayments, and Tax Fixes.

Scenario 5: Accounts payable wants proof that a contractor was paid

Best document: receipt or payment confirmation, linked to the invoice.

The invoice explains what was billed. The receipt confirms the payment happened. Together, they form a stronger record than either document alone.

Scenario 6: You reimburse an employee for a business expense

Best document: receipt for the expense and a reimbursement record.

This is a useful reminder that not every payment document is one of the three discussed here in a strict sense. The employee may submit a purchase receipt, and your business may reimburse through payroll or accounts payable depending on policy. If the reimbursement runs through payroll, the pay stub may also show it. The original store receipt still does a different job from the payroll pay stub.

Scenario 7: You run a mixed workforce with employees and contractors

Best setup: two distinct tracks.

Use a payroll track for employees and an invoice-and-approval track for contractors. The more your business grows, the more important this separation becomes. A practical monthly control is to review worker lists and make sure nobody is sitting in the wrong process. For a broader operational framework, see Payroll SOP for Small Businesses: A Standard Monthly and Per-Pay-Run Workflow.

When to revisit

This topic is worth revisiting whenever your payment workflows change, your workforce mix changes, or your systems create overlap between payroll and accounts payable.

Review your documentation rules again if any of the following happens:

• You hire your first contractor after previously paying only employees
• You convert contractors to employees or employees to a different engagement model
• You add new accounting, payroll, or payment software
• You start requiring purchase orders or formal approval chains
• You see repeated confusion about who should submit what document
• You have year-end cleanup issues, missing approvals, or unmatched payments
• You expand into more complex pay arrangements such as milestone billing, commission, reimbursements, or mixed hourly and project work

A practical update routine is to audit one recent employee payment and one recent contractor payment side by side. Ask these questions:

1. Was the worker classified correctly for the payment method used?
2. Did the business receive the right initiating document: invoice, time record, or internal payroll input?
3. Did the approval happen before payment?
4. Was the worker given the right closing document: pay stub, payment confirmation, or both as appropriate?
5. Could a future reviewer understand the transaction without digging through email?

If the answer to any of those questions is no, your business likely needs a simple SOP and a document checklist. Keep it short. For example:

• Employees: onboarding records, time records if applicable, payroll approval, pay stub, payroll archive
• Contractors: contract, invoice, approver signoff, payment confirmation, year-end tax tracking file

The goal is not to create more paperwork. The goal is to use the right paperwork at the right moment so payment records stay clear, defensible, and easy to reconcile.

As a final action step, document these three rules for your team:

1. Never ask employees to invoice for wages.
2. Do not use employee pay stubs as a substitute for contractor invoices.
3. Always connect proof of payment back to the originating invoice or payroll record.

That simple distinction will prevent a large share of common admin confusion around invoice vs pay stub vs receipt. And if your business is outgrowing manual methods, it may also be time to review whether your current payroll and payment tools still match your operations. A useful next read is Manual Payroll vs Payroll Service: When Small Businesses Should Switch.