Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.

Bookkeeping & finance

A Stripe invoice PDF and payment page show different line prices

Compare tax-inclusive and tax-exclusive presentation before treating a difference between the PDF and hosted invoice page as a billing calculation error.

By Institution5 minute readPublished View sources
In this guide

Compare the same invoice and the same kind of amount

A line price can differ between an invoice PDF and its payment page even when both show the same total due. First confirm that you are comparing the same invoice identifier and version. Then identify whether each line displays a price including tax or excluding tax. Do not issue a credit or change the customer's obligation until the difference is understood. A presentation setting can look like a calculation defect when the labels are overlooked.

Stripe documents that, for inclusive tax, its option to display line prices excluding that tax applies to the invoice PDF, while the hosted invoice page and invoice emails show tax-inclusive prices. It also describes customer-level settings taking precedence over account defaults. Check those settings for the affected customer. This documented behavior explains one possible difference; it does not establish that the actual tax treatment, rate or invoice content is correct for your transaction.

References: Stripe: Customize invoices

Build a small presentation bridge

Write the underlying line amount, tax amount, discounts and final total in a comparison that the billing owner can follow. Use the invoice's actual tax calculation and line details. Where the tax is inclusive, distinguish the amount embedded in the stated price from an additional charge added afterward. A report that subtracts tax again from a tax-exclusive figure can create a genuine error while attempting to reconcile an innocent display difference.

For a deliberately simplified example, a service has a tax-inclusive price of $120 at an illustrative 20 percent rate. The pre-tax amount is $120 divided by 1.20, or $100, and the included tax is $20. One view can display a $100 line plus $20 tax while another displays a $120 inclusive line. The payable total remains $120. This arithmetic illustrates presentation only; it does not say that this rate or treatment applies to any particular sale.

Extend the comparison carefully when there are several rates, discounts, credits or quantities. Identify whether the discount applies before or after the relevant calculation under the configured system and applicable treatment. Do not force a complex invoice into the simplified example. Ask the billing specialist to explain each component and the tax adviser to resolve substantive tax questions. The practical test is whether both views describe the same obligation after their labels and calculations are interpreted correctly.

Check the configuration that actually governed this invoice

Record the account default, customer setting and any invoice-specific configuration relevant to the displayed prices. Identify when those settings changed relative to invoice creation and finalization. A screenshot of today's default may not explain a document generated earlier. Preserve the customer-facing versions being compared and the underlying record references. This prevents the investigation from comparing a fresh preview with an older PDF that the customer already downloaded.

Use a safe test invoice or the vendor's supported preview to reproduce the configuration. Include the same pricing behavior and relevant tax setup without copying private customer details unnecessarily. Verify the PDF, email and hosted page separately. A successful preview in one channel does not establish the appearance of another. Record the labels and totals that a customer sees, especially where the screen uses compact formatting that makes the tax basis easy to miss.

Look beyond the line price when a difference remains. Confirm currency, quantity, discount, credits applied, shipping and amount already paid where those components exist. A payment page may emphasize the remaining balance while the PDF emphasizes the original invoice total. Those amounts answer different questions. The reviewer should explain each difference with an identifiable component, not assume that every discrepancy is caused by the documented tax-display setting.

Decide whether the remedy is explanation or correction

If the record is correct and only the presentation differs, give the customer a concise explanation using the invoice's own amounts. Show the pre-tax amount, included tax and unchanged total. Avoid telling the customer that the system is working as designed without explaining the numbers. If the display repeatedly causes confusion, review permitted presentation settings and wording for future invoices with the billing owner and relevant adviser.

If a rate, customer status, address, tax treatment or underlying amount is wrong, follow the supported invoice correction process. Do not edit a downloaded PDF independently and leave the platform record unchanged. That creates competing documents and can complicate payment and tax records. Identify whether a credit, replacement or another authorized correction is required for the specific transaction and jurisdiction. Preserve the relationship between the original document and the corrective record.

Separate customer communication from changes to the ledger. An explanation of two equivalent views does not require a financial adjustment. A real correction may require both an updated customer document and an accounting change. Have the responsible owner approve each. If the customer has already paid, compare the received amount with the final valid obligation before deciding whether any refund or additional collection is appropriate.

Prevent the same misunderstanding in reports and support

Tell the reporting team which fields represent gross price, pre-tax amount, tax and remaining balance. Do not scrape a displayed line price from a PDF and assume it has the same meaning as a field exported from the billing system. Use the documented source fields and reconcile the final totals. Include the relevant configuration in the billing procedure so a later template change does not silently alter how staff interpret the document.

Keep a sanitized example showing the permitted difference and the calculation behind it. Add it to support guidance with a clear escalation path for amounts that do not reconcile. Review the example when Stripe changes the relevant product behavior or the business changes invoice settings. The useful outcome is that staff can distinguish an understandable presentation difference from a tax or billing defect and can explain the customer's actual amount due without guessing.

Sources

Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.

Related reading

Need help with this work?

General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.