Skip to content
ConsultEvo

Free Invoicing Software: Compare Plans, Payment Fees, and Limits

Choose free invoicing software by checking five things: invoice volume, client and user limits, payment methods, country availability, and the fee on a typical payment. A solo consultant sending 40 invoices a month, for example, needs to confirm that the plan supports that volume, whether a second user is allowed, and what card or ACH payments will cost.

This is a US-focused snapshot checked November 18, 2026. Plans, fees, feature access, and regional availability can change, so recheck the vendor’s current terms before signing up. Subscription prices, payment-processing fees, account or PCI fees, and add-on charges are separate cost categories. A free subscription does not necessarily mean free payment acceptance.

The comparison below is a use-case guide, not an independently measured ranking. It separates invoice creation from payment acceptance and identifies conflicting documentation instead of guessing.

What should you compare when choosing free invoicing software?

First decide whether customers need to pay online, and which methods they use. Next compare the free plan’s invoice, client, user, and project limits with your expected needs. Then calculate processing costs for your country, payment method, and typical invoice amount. Check recurring invoices, reminders, portals, exports, branding, and integrations only when they affect your actual workflow.

  • Volume: Check the limit and its period. A plan may allow unlimited invoices but restrict clients, users, projects, or storage.
  • Payment path: Confirm that the plan and country support the methods customers want.
  • Workflow: Check recurring billing, reminders, portals, time tracking, exports, and branding controls.
  • Upgrade trigger: Identify the first change that would require payment, such as adding a user, exceeding a client cap, or needing API access.

A free plan fits only when its operating limits and payment path match your business, not simply because its subscription price is zero.

Free invoicing tools at a glance

The table describes the reviewed US documentation. Payment-method availability and charges can differ by account, region, plan, and transaction type.

Product Free-plan fit or constraint Payment caveat
Wave Starter Free basic invoicing and accounting. Check the plan comparison for feature-specific limits and Starter versus Pro differences. Online payments are separate from Starter. US Starter rates include 2.9% + $0.60 for Visa, Mastercard, and Discover.
PayPal Invoicing No separate charge to create or send invoices. Processing fees apply when paid. US examples include 2.99% + $0.49 for cards and Apple Pay, and 3.49% + $0.49 for PayPal or Venmo.
Zoho Invoice $0 plan with two users, three projects, 500 invoices per year, and Powered by Zoho Invoice branding listed on the US page. Connect a supported payment gateway. The gateway may charge its own fees.
Square Free No monthly subscription cost for the Free plan. US rates differ for invoice or online cards, in-person cards, and ACH.
Bookipi The free document allowance is unresolved. The public pricing and support pages describe it differently. Bookipi uses Stripe. Confirm current country and payment-method fees and the allowance with the vendor.
Paymo Free lists unlimited invoices for one user and one client, with two projects. Time tracking is included. Integrations and API access are listed as unavailable on Free. PM Payments is for US paid accounts.
Invoice Ninja Free lists up to five clients, unlimited invoicing, and 11 invoice templates. Gateways are listed, but processor fees depend on the gateway. API access and removal of vendor branding are excluded from Free.

Quick fit guide: Square is a candidate when invoice and in-person payments belong in one system. Paymo can suit time-based billing when one client and one user are enough. Zoho Invoice offers a customer portal subject to its plan limits and gateway setup. PayPal may suit a business whose customers prefer PayPal or its supported payment options. These are starting points, not guarantees of regional or feature eligibility.

Separate invoice features from payment processing

Invoicing software creates, sends, tracks, and may remind customers about invoices. A processor or gateway handles a payment method and charges fees for processing it. One product may provide both layers, or the invoice product may connect to a separate gateway. An invoice feature does not guarantee that every card, bank transfer, wallet, country, or settlement option is available.

Before comparing fees, record four inputs: country, plan, payment method, and typical invoice amount. Do not compare a card rate with an ACH rate or an online invoice rate with an in-person rate.

  • Wave Starter: Published US online-payment rates include 2.9% + $0.60 for Visa, Mastercard, and Discover; 3.4% + $0.60 for American Express; and 1% for ACH, with a $1 minimum. Online payments are not included simply by choosing Starter. See Wave’s payment fees and timelines.
  • Square Free: The US pricing page lists 3.3% + $0.30 for online or invoice card payments, 2.6% + $0.15 for tap, dip, or swipe payments, and 1% for ACH invoice payments with a $1 minimum. Other payment types and plans can differ.
  • Zoho Invoice: Zoho says it does not charge its own fee for receiving online payments, but the selected gateway may charge one. Gateway availability depends on account setup and region. Its online payments documentation lists supported providers.
  • PayPal Invoicing: Current US examples include 2.99% + $0.49 for debit cards, credit cards, and Apple Pay; 3.49% + $0.49 for PayPal and Venmo; 4.99% + $0.49 for Pay Later; and 1% for Pay by Bank, capped at $10. Check current terms for international or other transactions.
  • Bookipi: Bookipi confirms Stripe processing, but the reviewed pages do not verify the card and ACH rates reported in older comparisons. Check the fees for the connected Stripe account and country.

Calculate the real cost on a typical invoice

For a percentage-plus-fixed fee, estimate the processing charge as invoice amount x percentage rate + fixed fee. Apply any minimum, cap, or additional charge that matches the plan, payment method, and country.

For illustration only, on a hypothetical $100 invoice:

  • A hypothetical rate of 2.9% + $0.30 produces a $3.20 fee.
  • Square Free’s reviewed US online or invoice card rate of 3.3% + $0.30 produces a $3.60 fee.
  • A hypothetical 1% ACH rate produces $1 before any minimum or cap. Square Free’s reviewed US ACH rate is 1% with a $1 minimum, so that minimum does not change this example.
Decision point

The fixed part of a fee takes a larger share of a small payment. Calculate against your real average invoice and payment mix, then compare card and ACH terms separately.

Keep transaction fees separate from subscription, gateway, account, PCI, and add-on charges. For example, Paymo describes PM Payments as available to US paid accounts and lists a $20 monthly account fee and a $69 annual PCI fee alongside transaction rates. Those are not Free-plan costs.

Check the limits that “unlimited invoices” can hide

Estimate the next 12 months of invoices, clients, users, and projects. Then compare those estimates with the plan’s documented limits and identify the first likely upgrade trigger.

  • Zoho Invoice: The US free-plan page lists up to two users, three projects, and 500 invoices per year, plus Powered by Zoho Invoice branding. Its customer portal lets invited customers view transactions and invoices, approve estimates, and make payments when the account is configured for payment.
  • Paymo: Free lists one user, one client, and two projects, alongside unlimited invoices and time tracking. Integrations and API access are listed as unavailable on Free.
  • Invoice Ninja: Free lists five clients and unlimited invoicing. API access, automatic payment reminders, and removal of Invoice Ninja branding are excluded.
  • Wave: Starter and Pro differ. Review the current plan comparison for online payments, branding, customization, and automated late-payment reminders rather than assuming every feature is part of Starter.
  • Bookipi: The public pricing page advertises up to three invoices and three eSignatures per month, while the support page says a maximum of five documents per month. The definitions conflict, so do not select one number as definitive.

A static invoice PDF can work for occasional manual billing. It does not itself track payment, send reminders, reconcile transactions, provide a client portal, or prevent duplicate invoice numbers. The Bookipi invoice template PDF is an example of a static template, not evidence of the app’s current plan features.

01Record requirementsRecord country, invoice estimate, client count, users, projects, and required payment methods. The business owner owns this record.
02Verify dated evidenceSave the vendor URL, plan, country, checked date, and exact limit or feature. Route conflicting claims, including Bookipi’s allowance, to manual review.
03Estimate payment costsCalculate the likely fee for the typical invoice and payment method, including any minimum or cap. Finance or the owner checks the assumptions.
04Test the workflowCreate a test invoice, check sending, payment options, reminders, exports, and customer-facing branding.
05Approve the fitRecord the selected plan, unresolved terms, and first upgrade trigger before migration. The business owner approves the decision.

Use automation only where the data path is documented

A product listing or general automation page does not prove that a specific API, webhook, field mapping, or free-plan integration is available. Square provides the clearest documented technical example in this comparison. Its Invoices API supports invoice operations and documents events including invoice.created, invoice.published, invoice.payment_made, invoice.canceled, and invoice.refunded. Square manages the hosted payment flow. Do not treat invoice publication as payment or assume that the API directly charges an invoice.

The following is a proposed architecture, not a Square-published workflow or schema:

  1. Receive and validate: An authorized Square connection receives a documented invoice event. Validate the event type, vendor invoice ID, account context, and required permissions.
  2. Preserve provenance: Store the original event or source snapshot before transforming it. Retain the provider event ID when the documented payload supplies one.
  3. Deduplicate at the database layer: Use a provider event ID as the preferred uniqueness key. If none is available, use a documented fallback such as vendor account ID, invoice ID, event type, and provider event timestamp. Enforce uniqueness with a database constraint or transactional upsert because lookup-then-insert can race.
  4. Write at the correct grain: Keep one invoice row per business invoice, one payment-event row per payment event or state transition, one reminder-attempt row per dispatch, one source-snapshot row per captured input, and one integration-run row per execution. Do not overwrite the invoice amount with payment-event data.
  5. Route exceptions: Send refunds, unmatched customers, unexpected status changes, missing identifiers, and failed writes to a person. Update a CRM or ledger only after the event and customer match pass validation.

AI should not decide numerical plan limits, fee arithmetic, event identity, payment status, or duplicate detection. It may summarize an exception for an operator. A proposed normalized processing record might look like this:

{
  "vendor_account_id": "illustrative-account-17",
  "vendor_invoice_id": "illustrative-invoice-42",
  "event_type": "invoice.payment_made",
  "provider_event_id_if_available": null,
  "source_snapshot_id": "illustrative-snapshot-08",
  "integration_run_id": "illustrative-run-03",
  "processing_result": "review_if_customer_match_is_ambiguous"
}

The fields above are illustrative editorial design fields, not a Square payload. Paymo is not an equivalent free-plan automation example: its current pricing page lists integrations and API access as unavailable on Free. For help planning a cross-app workflow or designing CRM processes around reliable records, document the verified source, access path, and review owner before promising an integration.

Choose a tool with a practical free-plan fit test

Shortlist only tools that pass your hard requirements: country, payment method, expected volume, and essential user or client limits. Then compare recurring billing, reminders, portals, time tracking, branding, exports, and integration needs. A product that fits today may still have a clear upgrade trigger, such as approaching a client or invoice cap, adding a user, requiring API access, removing vendor branding, or needing an unavailable payment method.

Before you sign up
  • Confirm product, plan, payment methods, and country eligibility.
  • Compare annual invoices, clients, users, and projects with documented limits.
  • Calculate fees for the typical invoice and actual payment mix.
  • Check branding, recurring billing, reminders, exports, and required integrations.
  • Name the first upgrade trigger and test sending, payment, reminder, and export steps.

Make the final choice from the actual workflow, not the feature list alone. Recheck the vendor’s pricing and payment terms immediately before purchase, especially where official documentation conflicts or fees depend on method and region.