Costs and account terms

An invoice correction has not appeared in the balance

Compare the original invoice, the correction or credit reference, the revised obligation, the original collection event and any actual return or offset. A changed document total shows a billing change; it does not by itself show money moving. Establish whether the original amount was collected and what the provider says the correction will do before expecting a balance credit or bank return. Keep any missing link explicit rather than creating an adjustment to force agreement.

For: A research-only merchant comparing a corrected processing or service invoice with its actual payment and balance records.

Updated 2026-10-01

Preserve the original and establish what changed

Keep the original invoice and the revised document together, including their identifiers, issue dates, account, service period and currency. Record which line or component changed and whether the provider’s document identifies a correction, replacement or credit. A different total without a reference back to the original leaves the relationship unconfirmed.

Use the correction’s stated amount and scope. Do not silently replace the original invoice in the history: that would remove the evidence needed to explain an earlier collection. If the document contains fee and tax components, retain those components as shown rather than treating the entire difference as the same type of fee.

Read any accompanying explanation for what is supposed to happen next. A reduction in an amount still to be collected, a return of previously collected funds and an offset applied elsewhere are different outcomes to establish from the actual documents. This page does not claim that any of them is automatically available or that a corrected invoice creates a particular refund entitlement.

Determine whether and where the original amount was collected

Locate the collection record for the original obligation before searching only for a return. Record the actual amount, currency, date, status and reference. If there was no collection, there may be no collected money to return; the open question is whether the remaining obligation reflects the correction. An invoice marked changed is not evidence that the original amount was paid.

Stripe’s general terms allow fees to be deducted, charged or invoiced, subject to the relevant agreement and regional terms. That distinction explains why an invoice and a balance report need not describe the same event. It does not identify the payment method or collection status of a particular merchant’s bill.

Follow the collection route the real records show. If collection appears in a balance record, retain that reference. If it appears in a bank or other payment record, keep a safe internal reference to that record. An absence from the provider balance alone cannot resolve a correction involving a different collection route. Keep full bank details and payment credentials out of the worksheet.

Match the correction to an actual funds or offset record

For Stripe balance movements, the transaction type describes the movement and the source identifies its originating object. Stripe recommends reporting_category for grouping. Inspect those fields, the amount, currency and dates when evaluating a candidate credit. A positive entry close to the invoice date is not enough to connect it to the correction.

Look for the correction or credit reference on the candidate event, or a provider explanation that connects them. If the provider describes an offset against another bill, locate the record showing that application and the obligation it reduced. Do not call the offset a cash return. If the provider describes returned funds, keep the actual movement reference and its recorded status separate from the instruction or promise to return them.

Where several events cover one correction, list their references individually. Where one event covers several corrections, use only a documented allocation. Match account and currency before comparing amounts, and retain the separate document, posting and receipt dates. A remaining difference is a trace gap until the missing event or allocation is established.

The balance-transaction documentation describes movement types; it does not promise the type, destination or timing of an invoice correction. Do not assign a label to an unexplained credit solely because it would make the totals agree.

State the unresolved link and choose the next action

If the invoice was uncollected and the remaining obligation matches the correction, record that document-level reconciliation without claiming a refund occurred. If a supported movement or offset matches the correction, connect the references and state what was actually recorded. If the provider has described an action but no matching event is available, record it as unverified and preserve the wording and date of that explanation.

For an unresolved case, ask the provider which event applies the named correction, where it should appear, what amount and currency it covers and how its status can be verified. Include the original invoice and collection references through the provider’s appropriate secure channel. Ask for a stated timing explanation if needed; this worksheet supplies no universal deadline.

For a Prism processing consultation, describe the website, research-only products and the specific missing link in ordinary language. Confirm any requested reconciliation assistance before work. The provider remains responsible for explaining its records and account terms. Leave invoices, bank records, card data and customer details out of the public inquiry. Follow-up is by email, and the request does not purchase a service or submit a processing application.

Invoice correction-to-funds trace

Complete one copy for a real corrected invoice. Keep the document change, original collection and subsequent application as separate entries. Use internal references rather than sensitive payment details. Classify the result as obligation reconciled, movement or offset matched, or a named link still unresolved.

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.

Invoice correction-to-funds trace. The last column is for temporary notes.
Trace stageEvidence to compareWhat this can establishYour record or unresolved link
Original invoiceOriginal reference, billed service period, account, amount and currency.The obligation the correction must refer back to; preserve the original document.
Correction or credit referenceRevised document identifier, date and explicit link to the original invoice.Which document or component changed, without establishing payment or return.
Revised obligationCorrected amount and components, plus the provider’s explanation of the intended effect.The documented billing position; leave unclear correction treatment unresolved.
Original collection referenceActual deduction, charge or payment reference, status, date, amount and currency.Whether and where the original amount was collected; an invoice total alone cannot establish this.
Actual return or offset eventMovement reference and status, or documented application to another obligation.Evidence that the correction was applied by that route; distinguish an offset from returned cash.
Stripe balance matchCandidate entry’s type, source and reporting_category, with matching account and currency.The nature and origin of a recorded movement; timing or amount similarity alone is insufficient.
Partial application or remainderEach supported event or allocation and the portion still unmatched.A traceable remainder rather than a fabricated balancing entry or assumed refund amount.
Provider follow-upSpecific missing link, provider reply reference and next action owner.A question about an identifiable event, destination or status; no invented completion date.

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.

Limits

  • A corrected invoice does not by itself prove payment, a return, an offset, entitlement to a refund or a deadline. Use the actual provider documents and collection evidence.
  • Stripe balance fields and collection clauses apply to Stripe. Other providers require their own definitions; exact agreements and regional terms must be read for the account.
  • This worksheet traces records. It does not determine tax treatment, legal liability, accounting recognition or the cause of an unseen discrepancy.
  • Do not put card numbers, authentication codes, private payment-link tokens, credentials, full bank details, identity documents or customer records into the worksheet or public inquiry.

Sources

  • Stripe Services Agreement general terms — checked 2026-09-29. Fees may be deducted, charged or invoiced under the relevant agreement and regional terms. Collection mechanisms are separate from the billing document; these clauses do not establish how an unseen invoice correction is applied.
  • Stripe balance transaction types — checked 2026-09-29. The transaction type describes a balance movement, source identifies the originating object, and reporting_category is recommended for grouping. These labels do not establish legal rights, accounting treatment or the timing of a correction.
  • Prism solutions — checked 2026-09-21. Published support is storefront review, processing preparation and help with provider website questions. Scope, fees and terms are discussed before work; the provider decides eligibility and account terms.
  • Prism contact — checked 2026-09-21. The form requests the website, products and question and excludes card details, passwords and customer records. Follow-up is by email; the request is not a purchase or processing application.

Discuss my processing options

Want to talk through your own processing situation?