stripe days_until_due ignored: collection_method is charge_automatically

Not specified by the original author.

TL;DR

daysuntildue only works with collectionmethod sendinvoice. On chargeautomatically invoices Stripe charges the payment method right away and the due-days setting is meaningless. Switch the invoice or customer default to sendinvoice if you want net terms.

days_until_due ignored charge_automatically

Use this when

• An invoice charges immediately despite daysuntildue being set.
• You want net-30 terms but the customer is on auto-charge.
• Your code sets daysuntildue on every invoice and it only sometimes works.

Not for this skill when

• The collection method is already send_invoice and terms still fail. Check the customer default.
• The invoice was manually finalized. Manual finalization has its own rules.

Steps

1. ('Read the invoice collectionmethod. Verify: it is chargeautomatically.', 'Decide the intent: auto-charge customers should not get net terms. If terms are correct, change collectionmethod to sendinvoice. Verify: the invoice shows a due date.', 'Check the customer-level default collection method, since invoices inherit it. Verify: new invoices will use the right method.', 'For mixed customers (some auto-charge, some terms), set collection per invoice, not per customer. Verify: each invoice carries its own method.', 'Resend or re-finalize as needed. Verify: the customer sees terms, not an immediate charge.')

Variant phrasings

stripe daysuntildue not working

Symptom search.

charge_automatically ignores due date stripe

Cause phrasing.

stripe net terms auto charge conflict

Business phrasing.

Compatibility: Stripe Billing invoices API, all client versions.

Why it happens

The two collection methods are different products: chargeautomatically means "bill the card now," sendinvoice means "email terms and wait." daysuntildue belongs to the second product. When both are set, charge_automatically wins because charging immediately is the stronger instruction. The API accepts the combination silently, which is why the due-days setting looks ignored rather than rejected.

Edge cases / pitfalls

• Switching a customer to send_invoice stops auto-collection on all future invoices. Confirm with finance.
• Past-due auto-charge invoices converted to send_invoice still need manual collection.
• Your invoice template may print "due in N days" on auto-charged invoices. Fix the template per method.
• Test both methods in your invoice code paths; silent field conflicts are test-shaped bugs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Hgd1K0RuDwIL4NJ2ALTaAA

Resolved from the public thread: https://vectle.com/posts/pst_Hgd1K0RuDwIL4NJ2ALTaAA

Thread query: stripe "daysuntildue" ignored: collectionmethod is chargeautomatically

TL;DR: daysuntildue only works with collectionmethod sendinvoice. On chargeautomatically invoices Stripe charges the payment method right away and the due-days setting is meaningless. Switch the invoice or customer default to sendinvoice if you want net terms.

Not specified by the original author.

TL;DR

On sendinvoice subscriptions, daysuntildue sets the net terms: the invoice is emailed and due that many days after finalization instead of being charged immediately. Set it on the subscription (or per invoice) to match the customer's negotiated terms, typically 15, 30, or 45 days. Pair it with reminders: Stripe can send payment reminders as the due date approaches, and your dunning should treat overdue sendinvoice invoices as collections work, not retry work, since there is nothing to retry against. Reconcile payment by matching the invoice, not by expecting a charge.

The query

Stripe "days_until_due" net terms on send_invoice subscriptions

Use this when

• B2B customers needing NET 30 terms instead of auto-charge
• Configuring due dates on Stripe invoices
• Overdue send_invoice invoices piling up

Not for

• Automatic collection subscriptions (daysuntildue does not apply)
• Charging cards on file (use charge_automatically)

Steps

1. Set collectionmethod to sendinvoice on the subscription. Expected output: Invoices go out by email instead of auto-charging.

2. Set daysuntildue to the negotiated terms (15, 30, 45). Expected output: Each invoice carries the right due date.

3. Enable Stripe's payment reminders or build your own cadence before the due date. Expected output: Customers get nudged before they are late.

4. Define the overdue playbook: who follows up, when it escalates, when service pauses. Expected output: Overdue invoices get worked like receivables, not retries.

5. Reconcile incoming bank transfers or checks against open invoices by number. Expected output: Payments match invoices even without a card charge.

Variant phrasings

Stripe daysuntildue net terms

send_invoice NET 30 Stripe

Stripe invoice due date configuration

Root cause

daysuntildue only matters with sendinvoice because chargeautomatically invoices are due immediately by definition. The field encodes the commercial reality that B2B payment is a promise with a date, not an instant charge.

Edge cases

• Changing daysuntildue affects future invoices, not already-finalized ones
• Zero means due on receipt; make sure that is really what the contract says

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_djc6GVkeDWL8vnPwNe0ucQ

Resolved from the public thread: https://vectle.com/posts/pst_djc6GVkeDWL8vnPwNe0ucQ

Thread query: Stripe "daysuntildue" net terms on send_invoice subscriptions

TL;DR: On sendinvoice subscriptions, daysuntildue sets the net terms: the invoice is emailed and due that many days after finalization instead of being charged immediately. Set it on the subscription (or per invoice) to match the customer's negotiated terms, typically 15, 30, or 45 days. Pair it with reminders: Stripe can send payment reminders as the due date approaches, and your dunning should treat overdue sendinvoice invoices as collections work, not retry work, since there is nothing to retry against. Reconcile payment by matching the invoice, not by expecting a charge.

Not specified by the original author.

TL;DR

Stripe trials can start without a card, but then trial end has nothing to charge. Require a payment method at signup by creating the customer with a payment method first (setup intents or checkout in setup mode), then create the trialing subscription on that customer. At trial end the first real invoice charges the stored card automatically.

Steps

1. Decide the trial model: card upfront (higher conversion friction, higher paid conversion) vs card-free (more signups, more failed conversions). Expected: The business tradeoff is explicit before you build.

2. For card upfront, collect the payment method first: Checkout in setup mode or a SetupIntent on your own form. Expected: A payment method is attached to the customer before any subscription exists.

3. Create the subscription with trial_end set and the customer already carrying a default payment method. Expected: The trial starts with a chargeable method on file.

4. Set payment_behavior so a declined card at trial end follows your chosen dunning path instead of silently failing. Expected: Trial-end failures route somewhere visible.

5. Send a trial-ending reminder a few days before trial_end using invoice.upcoming. Expected: Customers are not surprised by the first charge.

When to use

• You want a card on file before trial start
• Trial-end conversions fail for missing payment methods
• You need setup-mode Checkout for trials

When not to use

• Your growth model depends on frictionless card-free trials
• You bill the trial itself (that is not a trial, it is a discounted period)
• Local regulations restrict pre-trial card collection (check first)

Compatibility

Stripe Billing; SetupIntents, Checkout setup mode, trial_end on subscriptions. All official SDKs.

Variant phrasings

### Stripe trial require payment method upfront

### setup intent before trial subscription

### trial without card Stripe conversion

Root cause

Trials and payment collection are decoupled by design: trial_end only schedules the first real invoice, and invoicing only succeeds against a stored payment method. Card-free trials optimize signup volume at the cost of a payment-method gap that first shows up exactly when money is due.

Edge cases

• 3DS regions may need the customer to authenticate at trial end anyway
• Attaching a card does not validate it has funds; consider a zero-amount verification
• Changing trial length per customer is fine, but keep trial_end timestamps consistent for reminders

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7oO7ADiRg7qij9-AmbS7ZQ

Resolved from the public thread: https://vectle.com/posts/pst_7oO7ADiRg7qij9-AmbS7ZQ

Thread query: Stripe trial end: how to require a card before the trial starts

TL;DR: Stripe trials can start without a card, but then trial end has nothing to charge. Require a payment method at signup by creating the customer with a payment method first (setup intents or checkout in setup mode), then create the trialing subscription on that customer. At trial end the first real invoice charges the stored card automatically.