Set invoice defaults that make payment expectations clear

An invoice should not begin as a blank page every time someone in the office needs to collect money. The team usually already knows its normal payment options, terms, reminder cadence, title format, and partial-payment approach. Re-entering them over and over creates inconsistency where the business needs momentum.

This update gives Local Business Pro teams business-level defaults for eligible new invoices. The goal is a more reliable starting point for future billing without rewriting a record that has already entered the business’s history.

Set the invoice starting point once

Most shops have repeatable billing habits. They use the same payment-method options, payment terms, reminder cadence, title format, or partial-payment approach on a large share of invoices. Re-entering those choices on every invoice wastes time and makes it easier for the office to accidentally send mixed signals.

Business-level invoice defaults let an authorized team establish the starting configuration for eligible new invoices. Depending on the setting, that can include:

• accepted payment methods;
• payment terms and due-date behavior;
• reminder settings;
• invoice titles; and
• partial-payment settings.

The important phrase is eligible new invoices. These defaults are a starting point for future work. They do not reach backward and rewrite an invoice that was already created, sent, paid, partially paid, cancelled, or otherwise part of the business’s history.

That protects the practical record behind each transaction. An invoice needs to retain the commercial choices that applied when it was created—not inherit a later policy change that would make past communication harder to understand.

Keep the invoice lifecycle understandable

Local Business Pro also retains lifecycle snapshots around the invoice workflow so the office has better readback on the configuration and state that shaped the record. That is useful when a customer calls with a basic question: What terms applied here? Which payment options were offered? Was a reminder policy in effect when this invoice went out?

Snapshots do not turn every invoice into an accounting system of record or remove the need for ordinary operational judgment. They preserve workflow context so the team can investigate from a durable starting point instead of reconstructing a past decision from memory.

For the broader sequence—from finished work through collection—see the invoicing and payment tracking workflow and how to create and send invoices. This update makes the starting configuration more consistent; the office still owns the decision to review, send, adjust, collect, or follow up.

Payment choice gets its own story

Configured card, cash/ACH, and eligible Stripe surcharge behavior deserve a focused customer explanation instead of a paragraph inside invoice setup. Read clearer payment choices across supported documents and checkout for that separate update.

Accurate payment and refund context matters too

The update also strengthens payment and refund authority for Accounts Receivable and Customer Overview. Those views use the canonical invoice payment and refund information rather than allowing a reporting view to drift away from the record that owns the financial outcome.

That is deliberately unglamorous—and exactly the kind of product work that earns trust. A customer-facing payment choice is only useful if the office can later see the right payment and refund picture when it is answering questions, following up, or reviewing receivables.

What this update does not do

• It does not rewrite historical invoices when a default changes.
• It does not force a business to enable Card Pricing, cash/ACH pricing, or a surcharge.
• It does not guarantee that every payment provider, account, jurisdiction, or payment method supports every pricing configuration.
• It does not collect a surcharge without the supported quote and checkout acknowledgment flow.
• It does not replace the business’s accounting, compliance, processor, or customer-communication responsibilities.

That is the right boundary. The product can help a team be consistent and transparent; it should not pretend that a payment setting eliminates the business judgment behind it.

A cleaner revenue workflow starts with fewer surprises

Defaults handle the repeatable part of invoice setup, while canonical payment and refund readback keeps the office grounded in what actually happened. Together, those improvements remove a lot of small uncertainty from the revenue workflow without treating prior invoices as disposable drafts.

For revenue operations across estimates, jobs, invoices, and payments, start with the connected jobs-and-estimates workflow.

Frequently asked questions

Do new invoice defaults change invoices that already exist?

No. Defaults apply to eligible new invoices. Existing and historical invoices retain their own lifecycle and configuration context.

Where can I see payment and refund information after an invoice changes?

Accounts Receivable and Customer Overview use the canonical invoice payment and refund information so the office can review the appropriate financial context.