Jump to the page text

PaidSmith

How to get an invoice paid

Recurring invoices: how 5 apps handle charging

PaidSmith Editorial Team · Published · 13 min read

Five apps describe a way to repeat an invoice on a schedule, but they differ on sending and charging.

Key takeaways

  • Square, FreshBooks, Invoice Ninja, and Stripe describe distinct methods for repeating invoices and charging customers. They differ on when the invoice is created, whether sending and charging are separate actions, and how failed payments are handled.
  • Schedule timing varies by product. FreshBooks notes that recurring setups start creating and sending invoices at around 1 AM EST on the day they are set to run, according to FreshBooks. PayPal explains that following invoices in a series are issued around 7:00 AM in your time zone according to a frequency you set, according to PayPal.
  • Automatic charging is not always automatic. Square specifies that it will not automatically attempt to re-process declined payments, according to Square. FreshBooks describes a Retry status where the payment is attempted again on the original saved payment in the next 24 hours, according to FreshBooks.
  • Verify missing details in the product. The PayPal and Invoice Ninja pages quoted here do not state retry limits for failed payments, so those details remain UNKNOWN. Check each product’s current help page to confirm which features are available in your specific plan and region before relying on automatic charging.

Which invoicing apps can repeat an invoice and charge the customer automatically?

Square defines recurring invoicing as a way to charge a customer’s credit card for goods or services on a prearranged, recurring schedule, according to Square. FreshBooks describes creating a recurring setup that generates invoices automatically based on the frequency you choose, according to FreshBooks. Invoice Ninja uses a Remaining Cycles setting to tell the system how many invoices to generate before considering the job done, allowing a specific number for fixed-term engagements or Endless for open-ended retainers, according to Invoice Ninja. PayPal states that when you start a recurring series of invoices, the customer will immediately receive the first invoice, according to PayPal. Stripe notes that when you create a subscription, it automatically generates invoices, attempts payment collection, and manages the subscription status throughout its lifecycle, according to Stripe.

These definitions show that each product handles the repetition differently. Square focuses on the charging aspect of the schedule. FreshBooks focuses on the setup generating the invoice. Invoice Ninja focuses on the number of cycles. PayPal focuses on the immediate delivery of the first invoice. Stripe focuses on the automatic management of the entire subscription lifecycle. The pages do not all use the same terms for the feature; some say recurring invoice, some say recurring setup, and some say subscription. This difference in terminology reflects how each product structures the feature within its broader toolset.

How we compared: the official help pages we read and what we looked for

We read one Square page, two FreshBooks pages, one Invoice Ninja page, two Stripe pages, and one PayPal page. For every page, we looked for three specific details: how the repeating schedule is set, whether the invoice is sent and charged in the same step or separate steps, and what the page says happens when a payment fails. We did not look at pricing, plan tiers, or user reviews.

For Square, the page states that recurring invoices will follow an ID convention similar to 000001-R-0001, according to Square. This tells us how the system labels the invoices, but it does not describe the schedule frequency or the charge timing on that specific line. We noted what the page explicitly said and marked everything else as unknown.

Schedules: how each page says a repeating invoice is set up and sent

Not every product’s help page describes a specific moment when the recurring series begins or when subsequent invoices are generated.

Square’s page states that if you schedule a recurring payment for a future date with the Card on File feature, your customer’s card will be automatically charged at 10:00 AM in your local time zone on the date you’ve selected, according to Square. This specific time applies to the automatic charge event described in that section.

FreshBooks notes that recurring setups start creating and sending their invoices at around 1 AM EST on the day they are set to run FreshBooks. The page uses the phrase "around 1 AM EST," indicating this is an approximate system time rather than a precise minute-by-minute guarantee.

Invoice Ninja distinguishes between saving a draft and starting the series. Saving on its own only stores the draft; starting is what puts it on the billing calendar Invoice Ninja. The page does not specify a particular time of day for the creation of subsequent invoices in this quoted section, only that the start action initiates the calendar entry.

PayPal explains that when you start a recurring series of invoices, the customer immediately receives the first invoice PayPal. You can also schedule the recurring series to start at a future date. For the following invoices in the series, PayPal states they will be issued around 7:00 AM in your time zone according to the frequency you set PayPal.

The pages differ on how they handle the duration of the series. Invoice Ninja uses a setting called "Remaining Cycles" to tell the system how many invoices to generate before considering the job done Invoice Ninja. You can pick a specific number for a fixed-term engagement or choose "Endless" for open-ended retainers and subscriptions that run until you stop them Invoice Ninja. The other pages quoted here do not specify a cycle limit field in the provided text.

The Stripe quotes used here state no clock time or frequency.

Automatic charging: what each page says about cards, banks and failed payments

Four of these pages distinguish between sending an invoice and charging a customer, though they define the boundary differently. FreshBooks describes recurring payments, also known as AutoPay, as a feature that allows you to automatically charge a client's credit card or bank transfer (ACH) details on a regular basis through a recurring invoice or a retainer, according to FreshBooks. Invoice Ninja uses the term Auto Bill to decide whether generated invoices are charged automatically against the client's saved payment method, set up through one of your payment gateways, or simply emailed for manual payment, according to Invoice Ninja. Stripe specifies that for subscriptions with collection_method set to charge_automatically, it creates an invoice with the status open when you create the subscription, according to Stripe. Square states that if you schedule a recurring payment for a future date with the Card on File feature, your customer’s card will be automatically charged at 10:00 AM in your local time zone on the date you’ve selected, according to Square. The PayPal page does not state how automatic charging works, so that detail is UNKNOWN.

When a payment fails, the pages state different retry behaviors. Stripe re-attempts payment using Smart Retries or based on your custom retry rules, according to Stripe. You can set the Smart Retry policy to retry payment a specific number of times within a time period: 1 week, 2 weeks, 3 weeks, 1 month, or 2 months, according to Stripe. FreshBooks states that if a payment fails, it will go into Retry status automatically, where the payment will be attempted again on the original saved payment in the next 24 hours, according to FreshBooks. Square explicitly states that it will not automatically attempt to re-process declined payments, according to Square. The Invoice Ninja and PayPal pages do not describe what happens when an automatic payment fails, so those details are UNKNOWN.

The filled reference table: one row for each product, from its own page

Each row below is built strictly from the quoted help-page statements. The publisher is named in each row, and every cell traces back to that specific product's own help page. Where a page does not state a detail, the cell is marked UNKNOWN. Pages change, so anything not stated here must be verified directly in the product.

Publisher Schedule Setup Automatic Charging Failed Payment Handling
Square Future date with Card on File: charged at 10:00 AM local time Square Charges customer’s credit card on prearranged schedule Square Will not automatically attempt to re-process declined payments Square
FreshBooks Creates and sends invoices at around 1 AM EST FreshBooks AutoPay charges credit card or bank transfer (ACH) FreshBooks Retry status attempts payment again in next 24 hours FreshBooks
Invoice Ninja Remaining Cycles sets number of invoices; Endless for open-ended Invoice Ninja Auto Bill charges saved payment method or emails for manual Invoice Ninja UNKNOWN
Stripe Automatically generates invoices and attempts collection Stripe Creates invoice with status open for charge_automatically Stripe Re-attempts using Smart Retries or custom rules Stripe
PayPal First invoice immediate; following issued around 7:00 AM PayPal UNKNOWN UNKNOWN

The table shows that Square describes a 10:00 AM charge for a future-dated Card on File payment, while FreshBooks notes invoices are sent at around 1 AM EST. PayPal states the first invoice is immediate and subsequent ones issue around 7:00 AM. Stripe describes automatic generation and collection attempts, and Invoice Ninja uses Remaining Cycles to define the series length.

For failed payments, Square explicitly states it will not automatically re-process declined payments. FreshBooks describes a Retry status where the payment is attempted again in the next 24 hours. Stripe mentions re-attempts using Smart Retries or custom rules, with specific retry periods available in its documentation. The Invoice Ninja and PayPal pages provided do not describe failed payment handling, so those cells remain UNKNOWN.

Check each product's current help page to confirm these details before relying on them for your billing workflow.

Checks before you rely on automatic charging

Map your specific billing workflow to the official documentation before selecting a tool. If a page does not state a detail, mark it UNKNOWN.

If you require manual review before sending, check if the page offers a choice between automatic sending and manual drafting. The FreshBooks page states: "Delivery Options - Choose between Send invoices automatically or Create draft invoices and send manually" according to FreshBooks. This specific option allows you to create draft invoices and send them manually rather than having them sent automatically.

If you need a deposit or a partial payment, read Deposits and partial payments in 5 invoice tools.

Identify the specific sentence in the help article that addresses your requirement. If the article is silent on a point, such as retry limits for failed payments or specific time zones for sending, mark that point UNKNOWN. Do not infer behavior from other products or general knowledge.

Illustrative example: mapping a 30-day repeat

Picture one bill for 100 that repeats every 30 days. On day 1 you send it. On day 30 the same 100 is due again. Sending the bill and charging a saved card are 2 separate steps. If the charge fails, you allow 1 further try. If that try fails, you stop after 2 misses instead of letting the repeat continue toward 6 bills. These round figures are illustrative, so you can rehearse 3 checks: how the repeat is set, whether sending and charging are separate, and what a failed payment does.

Today, check each product's help page for the specific retry limit and payment method support before relying on automatic charging.

FAQ: recurring invoices and automatic payments

What is a recurring invoice?

A recurring invoice repeats the billing cycle without manual re-entry each time.

Can the app send the invoice and charge the customer automatically, and are those the same step?

Sending and charging are not always the same step. Invoice Ninja lists Auto Bill as the setting that decides whether generated invoices are charged automatically against the client's saved payment method or simply emailed for manual payment according to Invoice Ninja. This separation implies sending and charging are distinct actions within that tool. Stripe describes a process where it automatically generates invoices and attempts payment collection as part of creating a subscription according to Stripe. FreshBooks notes that AutoPay allows you to automatically charge a client's credit card or bank transfer details through a recurring invoice according to FreshBooks.

What does each page say happens when an automatic payment fails?

Square, FreshBooks, and Stripe describe a failed payment, while Invoice Ninja and PayPal are UNKNOWN.

FreshBooks explains that a failed payment goes into Retry status automatically, where the payment will be attempted again on the original saved payment in the next 24 hours according to FreshBooks.

Square states that it will not automatically attempt to re-process declined payments, according to Square.

Can I review a repeating invoice before it goes to the customer?

Yes. FreshBooks offers a 'Create draft invoices' option within its recurring setup according to FreshBooks. Invoice Ninja requires you to 'start' a recurring series to put it on the calendar, according to Invoice Ninja.

Why does this guide not say which app is best or what they cost?

This guide uses only official help pages, and the quotes gathered here contain no prices or rankings. Because product pages change, any item not explicitly stated remains UNKNOWN until you check the product directly. We recommend verifying current pricing and feature availability on each vendor's site before making a selection.

Sources