Tools represent payment timing through installment terms, due-date inputs, invoice schedules or subscription billing anchors. Reusable Payment Term records combine into a schedule for sales and purchase transactions, according to Frappe.
Invoice payment schedules: how four tools define timing
The four mechanisms differ in structure and purpose. ERPNext uses installment percentages paired with due-date rules to split a single invoice into multiple payments. Odoo documents payment term naming with Due and After fields to calculate a specific due date. Square presents the invoice payment schedule alongside accepted payment methods and recipient delivery methods. Stripe uses a billing cycle anchor to align future recurring billing periods.
Each tool defines timing differently based on its core function. ERPNext structures multi-part payments within one invoice document. Odoo uses Due and After fields to determine the due date within named payment terms. Square groups the schedule with how the customer pays and receives the invoice. Stripe aligns recurring charges to a specific calendar anchor point.
Write down whether the next client bill needs installments, a calculated due date or recurring billing dates, then identify the corresponding documented control in the tool you already use.
Key takeaways for how do invoice tools define payment schedules?
- ERPNext: Each term defines an installment percentage and its due-date rule, requiring portions to total the full invoice amount according to Frappe.
- Odoo: Users name a payment term and complete Due and After fields to determine the specific due date for the invoice according to Odoo.
- Square: The invoice schedule is documented alongside the list of payment methods accepted on the payment page and the delivery method for recipient communication according to Square.
- Stripe: The billing cycle anchor serves as the reference point that aligns future billing period dates for recurring subscriptions according to Stripe.
- Action: Write down whether the next client bill needs installments, a calculated due date, or recurring billing dates, then identify the corresponding documented control in the tool you already use.
Payment schedule reference table from the tools' own documentation
| Publisher | Documented Schedule Mechanism | Key Documented Inputs or Rules |
|---|---|---|
| Frappe | Percentage and due date | Each term defines an installment percentage and its due-date rule, according to Frappe. |
| Odoo | Due date calculation inputs | Due fields, then fill out the After fields to determine the due date, according to Odoo. |
| Square | Invoice schedule configuration scope | The payment schedule for the invoice, list of payment methods accepted on the invoice payment page, and delivery method that Square should use to communicate with the recipient, according to Square. |
| Stripe | Future billing period alignment | The billing cycle anchor is the reference point that aligns future billing period dates, according to Stripe. |
Verify which specific controls your current tool exposes for setting payment timing.
ERPNext pairs installment percentages with due-date rules
ERPNext structures payment timing by defining each term with an installment percentage and its corresponding due-date rule, according to Frappe. This structure allows a single invoice to be split into multiple payment events, each governed by a specific percentage of the total amount and a distinct date calculation.
To create a schedule, you add one row for each installment and make sure all Invoice Portions total 100%, according to Frappe. This requirement ensures that the sum of all scheduled payments equals the full invoice value. The documentation illustrates this with two distinct examples. For Nova Industries, an electronics manufacturer and distributor, a Net 30 term contains one term for 100% due after 30 days, according to Frappe. This represents a single payment event where the entire balance is due at one specific time.
In contrast, a 50% Advance, 50% Net 30 schedule contains two installments, according to Frappe. This setup requires two separate installment rows. The first row defines the advance payment percentage and its due-date rule, while the second row defines the remaining balance percentage and its due-date rule. The distinction between these examples highlights how the tool handles both single-payment and multi-payment scenarios through the same underlying structure of percentage and date rules.
When setting up your own payment terms, identify whether the client agreement requires a single due date or multiple partial payments. If multiple payments are required, determine the percentage for each portion and the specific rule that calculates its due date. Enter each installment as a separate row in the schedule, verifying that the percentages sum to 100%. This approach aligns the tool’s configuration with the specific terms agreed upon in your client contract. For broader context on how different platforms handle partial payments, see Deposits and partial payments in 5 invoice tools.
Odoo exposes payment term and due-date inputs
Odoo documents a specific workflow for creating payment terms that centers on naming the term and defining how the due date is calculated. The documentation for "Payment terms and installment plans — Odoo 19.0 documentation" instructs users to begin by entering a name in the Payment Terms field according to Odoo. The Payment Terms field is where users enter a name for the payment term.
Following the naming step, the documentation outlines the inputs required to determine the actual date by which payment is expected. Users must complete the Due fields, then fill out the After fields to determine the due date according to Odoo. Complete the Due fields and then the After fields to determine the payment due date. This approach allows the system to calculate specific calendar dates based on the parameters set by the user.
Square documents the invoice schedule alongside payment and delivery methods
Square's documentation for the "Create and Publish Invoices" API lists the payment schedule, accepted payment methods and recipient delivery method together. The first element is the payment schedule for the invoice itself. The second element is the list of payment methods accepted on the invoice payment page. The third element is the delivery method that Square should use to communicate with the recipient, according to Square.
This grouping indicates that the schedule is not isolated from how the client pays or how they receive the bill. The payment schedule, accepted payment methods and recipient delivery method appear alongside one another in the invoice creation documentation. Accepted payment methods are an invoice configuration element listed alongside the payment schedule. The delivery method for communicating with the recipient is another invoice configuration element listed alongside the payment schedule.
It defines the scope of the configuration as the payment schedule, the accepted payment methods, and the delivery method. You cannot infer specific installment rules or mandatory payment splits from this documentation alone. The text confirms that these three components are part of the invoice schedule configuration scope.
To apply this scope, verify that your invoice setup includes the intended payment methods and delivery channel before finalizing the schedule. Confirm that the payment schedule aligns with the accepted payment options listed on the invoice payment page. Ensure the delivery method matches how you intend to communicate with the recipient.
Stripe fits recurring billing dates; ERPNext fits installment schedules
Stripe’s documentation describes a billing cycle anchor as the reference point that aligns future billing period dates, according to Stripe. This anchor sets the day of week for week intervals, the day of month for month and year intervals, and the month of year for year intervals, according to Stripe. The default value is either the subscription creation date or the trial end date (if you’re using a trial period), according to Stripe.
Consider a scenario where a free trial is 7 days and the billing renewal is monthly on the 1st, according to Stripe. In this case, the anchor aligns the recurring charges to that specific monthly date. For a different alignment, if you have an existing monthly subscription with a billing_cycle_anchor timestamp that contains the day of the month, hour, minute, and second of 15, 12, 30, and 0, you can align a new monthly subscription with it, according to Stripe. This mechanism is distinct from installment structures because it manages the timing of recurring subscription periods rather than splitting a single invoice amount into multiple payments.
Stripe also documents how initial periods function within this framework. There’s an initial, prorated period from subscription creation until February 28 (or 29 during a leap year), followed by a full two-month billing period, according to Stripe. This example illustrates how the anchor interacts with calendar boundaries to define the first billing cycle. The documentation focuses on aligning future dates for recurring services, which differs from the approach used by tools that structure single invoices into multiple payment installments.
In contrast, ERPNext defines payment timing through installment percentages and due-date rules. While the current section focuses on Stripe’s recurring billing anchor, the distinction lies in the nature of the obligation. Stripe’s anchor aligns future billing period dates for subscriptions, whereas ERPNext’s structure involves splitting an invoice total into portions that must sum to the full amount. A subscription billing anchor is not equivalent to an installment due date; the former sets the reference point for recurring cycles, while the latter specifies when a portion of a single invoice is due.
Related guides
FAQ: choosing a schedule for your client billing
How do invoice payment schedules differ across these tools?
ERPNext structures schedules using installment percentages paired with due-date rules, as documented in its payment terms examples. Odoo calculates due dates by completing specific "Due" and "After" fields within named payment terms. Square groups the payment schedule with accepted payment methods and the recipient delivery method in its invoice creation documentation. Stripe aligns future billing period dates using a billing cycle anchor, which serves as a reference point for recurring subscription renewals.
Which documented schedule fits a deposit followed by a balance payment?
The ERPNext documentation describes a "50% Advance, 50% Net 30" schedule that contains two installments, according to Frappe. This structure explicitly splits the invoice into an initial advance portion and a second portion due after a specified period. The documentation notes that invoice portions must total the full invoice amount when using such examples. This example provides a documented structure for splitting a bill into two distinct payment events.
What does Net 30 mean in the ERPNext example?
In the Nova Industries example, "Net 30" contains one term for 100% due after 30 days, according to Frappe. This contrasts with multi-installment examples that split the total amount across different dates. The term defines a single payment event where the full balance is due at the end of the 30-day period. The documentation uses this to illustrate the difference between a single-payment term and a multi-installment schedule.
How does Stripe determine the default billing cycle anchor?
This anchor acts as the reference point that aligns future billing period dates. The default billing cycle anchor is the subscription creation date, or the trial end date when a trial period is used. Users can adjust this anchor to align billing with specific calendar dates or business cycles.
Does Square's documentation specify an installment limit?
Square's documentation documents the payment schedule alongside the list of payment methods accepted and the delivery method for communication, according to Square. It defines the scope of the schedule configuration within the invoice creation process. Square lists the invoice payment schedule, accepted payment methods on the payment page and delivery method for communicating with the recipient.