Offering invoice terms without misdescribing payment collection

An invoice identifies the obligation and customer

Begin with the accepted invoice terms and the agreement they refer to. Record the named purchasing business internally, the due date or rule for calculating it, and the event from which that rule runs. Where the invoice and the agreement disagree, keep both references and resolve the discrepancy before describing one date as settled. An institutional buyer's purchasing process is not evidence that a particular collection step is enabled.

Stripe describes an invoice as a collection request for one specific customer. That documents the customer-specific object; it does not make invoice a payment method. Your requirements should name both the request and the method used to satisfy it. If your invoice is generated outside Stripe, identify that system and the actual provider instead of importing Stripe product behavior into it.

Say who performs the payment step

Read the payment instructions and the agreement to determine whether the buyer initiates payment or the merchant expects to initiate collection under an authorization. These are different operating requirements even when the invoice carries the same due date. Record the responsible party, the intended action and the document or configuration that supports it. Do not describe collection as automatic merely because the accounting system can issue an invoice.

For Stripe ACH Direct Debit specifically, the source requires customer authorization and bank-account verification for payments from US bank accounts. Neither an invoice due date nor a record that the buyer supplied bank information establishes those two requirements. Keep references to the authorization and verification status in the appropriate internal system; the preparation worksheet needs their status, not bank details or the authorization document itself.

If the chosen method or initiator is still undecided, that is a requirement to resolve. Ask for the documented collection behavior your provider and integration actually support. A description of Stripe ACH Direct Debit does not establish that another bank method works the same way, or that this merchant can use it.

Place fulfillment beside collection, not inside it

Copy the actual fulfillment commitment from the quote, order agreement or policy that applies. Determine whether the business promises shipment before the invoice is due, after a payment event, or at another documented point. Name that event precisely. An internal instruction to wait for payment can conflict with a customer commitment to ship earlier; the processing brief should expose that conflict rather than treating the due date as the shipping date.

Stripe ACH Direct Debit has delayed acknowledgement of success or failure and is not guaranteed. Therefore, an initiated debit cannot be treated as a guaranteed successful collection on the invoice due date. Payment confirmation, settlement into the provider balance and a later payout are separate events. If your fulfillment decision depends on one of them, identify which record the responsible person must read; do not turn a general payment-method description into a date promised for this order.

Choosing to offer commercial terms does not cause the processor to take responsibility for the unpaid balance. Record who in your business monitors that balance and reconciles payment records against the invoice. Leave questions of credit law, collection rights and remedies for appropriately qualified advice; this brief does not establish them.

Deliver requirements that someone can answer

A usable brief identifies the invoice system, chosen method, collection initiator, authorization dependency, fulfillment trigger and unpaid-balance owner. For each item, distinguish an agreed customer term, an enabled software behavior and an unanswered provider question. A workflow is still incomplete if it depends on an automatic collection step nobody has documented.

Prism's processing consultation can help organize the business description and provider questions. Include the website, research-only products and a plain-language description of the deferred-payment workflow. Scope, responsibilities, fees and terms are agreed before work; the provider decides eligibility and account terms. The public form is for the question, not invoices containing customer or bank records. Email follow-up does not constitute a booking, purchase or processing application.

Invoice-terms collection brief

Complete this for one real invoice workflow using the agreement, payment instructions and enabled configuration. Record a non-sensitive document reference rather than attaching private records. An unresolved method, authorization or trigger remains an open requirement; it is not evidence that collection will happen on the due date.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.