Tasks and systems

How do you handle credit note and refund requests automatically at a post-seed startup?

Handle SaaS credit notes and refunds with contract context, clear approval, correct billing actions and reconciliation across payments and accounting.

Automate credit and refund requests by matching the customer, invoice and payment, checking the contract, sales promises, usage and policy, then preparing the correct billing action for human approval. Separate invoice corrections, future credits and cash refunds. Bombos supplies the account history and company rules the agent needs, so the founder need not reconstruct every decision.

Abstract oil painting with layered ivory planes, a looping antique-gold thread and a small yellow-and-black bee against deep forest green.

By Bombos. Published November 16, 2026. Sources checked November 16, 2026.

Example: a customer requests an outage refund in Slack Connect. Support finds the incident, billing finds a paid annual invoice, and the founder remembers a promise made before signature. The useful result is one supported decision that respects all three facts, followed by the right document, payment action and accounting treatment.

The scenarios, operating rules and templates below are proposed designs, not customer cases or measured Bombos results. Start with one recurring request type, and keep a person on every decision that needs judgment.

What is the difference between a credit note, a refund and a chargeback?

A credit note documents a billing reduction; a refund returns a payment; a chargeback follows a cardholder’s dispute through the payment network. They can concern the same sale while requiring different actions. Stripe’s credit-note guide explicitly separates reducing an open invoice from refunding a paid one or crediting the customer’s invoice balance.

Use this classification table before selecting an action. Its routing advice is our proposed starting point; product-specific behavior follows below.

Request or concept What it means for this workflow Decision to record
Invoice correction The billed price, quantity, service period or tax needs correction Which original lines are wrong and what replaces their economic effect
Credit note or credit memo A document recording a reduction, using the billing system’s terminology Origin invoice, credited lines, reason, tax and application
Cash refund Returning a previously collected payment Original payment, refundable remainder and settlement status
Customer balance credit Value held for application against invoices What it may pay, when it applies and whether it is refundable
Service or SLA credit Compensation under service terms or an authorized exception Incident, eligibility, formula, cap, claim window and settlement form
Proration A calculation for part of a service period Effective date, calculation basis and separately authorized settlement
Write-off Treatment of a receivable that will not be collected Finance’s reason and accounting classification; no assumed refund
Chargeback A formal payment dispute Processor case, evidence, owner and response deadline

These distinctions have practical consequences. Chargebee uses adjustment credits for unpaid invoices and refundable credits for paid invoices. Its promotional credits do not generate credit notes and cannot be refunded as cash. A customer-level credit is therefore not automatically a refundable claim.

Example: an invoice charges for seats removed before the agreed billing date. If unpaid, the desired result may be a corrected receivable. If paid, finance must also decide whether the customer receives a refund or an available credit. The word “credit” alone does not specify either outcome.

A credit memo does not necessarily cancel an invoice. In Stripe, a credit note preserves the original invoice. Fully crediting an open invoice can even change its status to paid without a payment being recorded. Read the document and payment history together before interpreting “paid” as cash received.

When your team says “give them a credit,” would everyone choose the same document and payment action?

What account context must an AI agent know before deciding?

A credit request needs both current transaction facts and the commitments that explain them. Our recommendation is to assemble one decision record from the contract, approved exceptions, service evidence and account history. Context engineering means preserving each fact’s source, scope and validity, then supplying the relevant part when the agent prepares the decision.

The record should make the account understandable to the next colleague, including why an earlier exception applied. Bombos’s role is the memory layer for that company context. The billing system remains responsible for its financial records; the payment processor supplies the current payment state.

Use this example context map:

Question Designated source What the decision record keeps
Who bought and who may request the change? Customer master, authenticated support identity, billing account Legal entity, requester authority and mapped customer identifiers
What was agreed? Executed contract, order form, amendments Relevant clause, version, effective date and precedence rule
What did sales promise? Approved deal exception and its original correspondence Exact commitment, approver, conditions and unresolved conflicts
What service was delivered? Usage ledger, entitlement history, incident record Affected units or period and supporting evidence
What has already been corrected? Billing and processor records Credit, refund, balance allocation and dispute identifiers with status
What policy applies? Finance-owned policy register Version, eligibility window, exclusions and approval authority
What changes the relationship decision? Authorized account history and renewal record Previous resolution, champion concerns and active negotiation
How should it be booked? Finance-approved accounting and tax mapping Entity, original tax lines, service period and review owner

Example: the public refund policy excludes mid-term cancellation, but an approved order-form exception permits it for a particular service. Retrieve the exception and its conditions. A recent support email repeating the general policy should not silently erase the signed agreement. Equally, an unapproved sales note is a conflict to resolve, not automatic permission to refund.

Keep eligibility, interpretation and authority separate. A source can establish what someone said without establishing that they could bind the company. Ask the commercial owner to resolve conflicting promises and finance or legal to confirm the applicable treatment. Record that resolution with its scope.

Restrict shared knowledge to the permissions of its sources. An agent serving one account should not expose another account’s negotiated terms. Preserve access restrictions in summaries and learned rules, and propagate corrections or deletion requirements to the knowledge derived from those sources.

The wider method is explained in giving AI agents your company context.

Which promise would disappear from the decision if the founder were unavailable tomorrow?

How do you turn email, support and Slack requests into one case?

Credit-request intake should identify the commercial event before authorizing a financial action. We recommend one case with linked messages, a named owner and verified customer, invoice and payment identifiers. Multiple channels may contain different evidence about one request, or genuinely separate requests from the same account.

Example: the billing contact emails finance while the champion posts in Slack Connect. Match the legal entity, subscription, affected service period and requested remedy before merging their threads. Retain both messages. An account match alone is insufficient because two issues can affect the same invoice.

Use an intake template: case ID; source messages; authenticated requester; customer and legal entity; invoice and line references; original payment; request category; affected period; requested outcome; prior action search; owner; next update. Leave unknown fields explicitly unresolved. Do not create a new customer merely because a familiar email address has changed.

Before proposing action, retrieve the current invoice, payment, existing credit notes, pending and completed refunds, balance applications and any dispute. Check whether the payment actually succeeded. Stripe distinguishes canceling an uncaptured payment from refunding a successful one in its refund documentation.

A disputed invoice needs a resolution owner and a clear scope for any collection hold. Keep unrelated, undisputed balances visible. The separate guide to payment reminders and collections covers that follow-up; this workflow supplies its approved credit and remaining-balance facts.

An upset customer can need both a financial correction and service recovery. Link the credit case to the customer complaint and escalation rather than expecting a refund to resolve the underlying incident. One owner should coordinate the explanation so support and finance do not promise different remedies.

What do Stripe, Chargebee, Maxio, Recurly and Paddle actually do?

Billing platforms already provide credit and refund operations, but their objects and settlement rules differ. Select the operation from the platform’s documented financial meaning. A generic “issue credit” action should never conceal whether it reduces a receivable, creates future value or returns cash.

Platform Documented behavior What to verify in your setup
Stripe credit-note API Reduces the unpaid remainder first; post-payment value can create or link refunds, credit invoice balance or record an outside credit Allocation between outcomes, existing refunds and original invoice lines
Chargebee credit notes Adjustment and refundable notes differ; standalone refundable credits need not reference an invoice Correct type, auto-application settings and line service-period configuration
Maxio Advanced Billing Credit-note origin and application can be different invoices; service credits wait on the subscription until applied Origin invoices, applications, discounts, taxes and any Maxio Core synchronization
Recurly credit invoices Distinguishes standalone credit, refund and write-off invoices; credits may settle future invoices or be refunded Credit origin, remaining balance, linked transactions and enabled feature configuration
Paddle adjustments Creates a separate adjustment beside the unchanged transaction and sends a credit-note PDF Refund versus invoice credit, adjustment status and payment outcome

Chargebee says standalone credit notes require contacting support and are not supported with Chargebee RevRec. Its credit-note service-period setting can use the original invoice line’s billing period or the note’s generation date. Confirm that setting with finance before relying on downstream period allocation.

Stripe’s API requires the post-payment refund, invoice-balance credit and outside-credit allocations to add up to the post-payment part of the note. It can link an existing refund. Use that link when money has already been returned instead of requesting another refund. Stripe also keeps its customer invoice balance as an immutable transaction ledger; it is distinct from the cash-refund operation.

Partially paid invoice example: an approved credit exceeds the invoice’s outstanding balance. In Stripe, the note first reduces that outstanding balance to zero. Only the excess requires the specified post-payment allocation. Do not turn the whole correction into a cash refund merely because some payment was collected.

In Maxio, the original invoice and the invoice consuming a credit need not be the same. Its documentation describes prorations, partial voids, invoice refunds and service-credit application, with discounts and taxes carried through. Preserve both sides of that relationship when reconciling an account.

Recurly’s failed-refund behavior is particularly useful to understand: by default, a declined refund transaction can leave value on a refund credit invoice as account credit. A document exists, but the cash refund has failed. Its write-off credit invoice is another distinct event, not evidence that the customer received money.

Paddle says most live refunds begin as pending_approval, although some are automatically approved. Your company’s approval and Paddle’s approval are separate states. Neither a submitted adjustment nor a generated PDF establishes that a bank has credited the customer.

Worked routing example: an approved correction concerns a paid invoice, and the customer has chosen a refund. Prepare the platform-specific note and refund allocation. Check its resulting identifiers and status, then reconcile the accounting record. If approval is pending or the transaction fails, retain the unresolved case and its owner.

Can existing support connectors handle this without another AI layer?

Existing connectors can be enough when they supply the necessary data, actions and controls. Intercom’s November 3, 2026 release lists ready-made billing connectors for Stripe, Chargebee, Paddle and Recurly, and specifically lists issuing refunds in Stripe. This is an existing alternative, not a capability that necessarily requires a new implementation.

Intercom’s template documentation names full and partial Stripe charge refunds. It requires the Stripe app for those templates and advises identity verification, protected email fields and control over response fields visible to Fin. Installed templates are independent copies; subsequent template updates do not automatically change your connector.

The Stripe app synchronizes selected billing attributes and events. That is valuable account data. It does not by itself demonstrate that the agent has the relevant signed exception, incident attribution or accounting decision. Our advice is to inspect the actual decision inputs before buying additional software.

There is substantial vendor evidence against assuming humans must execute every routine refund. Intercom’s September 8 action-agent article reports a 76% average support-conversation resolution rate and describes refund actions. The number is vendor-reported across support conversations. It does not establish refund-specific policy compliance, accounting accuracy or incremental retention.

Example selection rule: if one verified subscription, a clear policy and a native refund action answer the request completely, configure that route first. If the remaining work is repeatedly asking the founder what was promised, address the missing company memory. If requests are infrequent and unusual, a prepared case plus manual billing action may be the better approach.

How do you calculate SLA credits, usage corrections and prorated refunds?

Credit calculations should reproduce the applicable agreement and billing basis. Proration determines a portion of a charge; it does not decide whether that portion becomes cash, future credit or a reduction of an unpaid invoice. Stripe explicitly states that negative prorations are not automatically refunded.

Use these illustrative calculation records, with your own approved terms:

Case Calculation and evidence Separate decision
SLA credit Eligible service-fee base multiplied by the contractual credit percentage; apply the contractual cap Whether the claim qualifies, including exclusions, attribution and claim window
Seat overcharge Incorrectly billed seat quantity compared with the contracted billable quantity for that period Correction of the original charge versus a newly effective seat reduction
Usage correction Billed usage reconciled to the corrected usage ledger under the agreed aggregation and pricing rules Which invoice lines and tax treatment require correction
Mid-term downgrade Approved reduction multiplied by the unused fraction under the contract’s time basis Immediate change, next-renewal change, balance credit or permitted refund
Cancellation inside a refund window Eligibility checked against the applicable start event, deadline and exclusions Cancellation date, access termination and refund scope

Worked example: an annual service allows a mid-term reduction using actual days. The approved change leaves 90 days of a 365-day term. The unused fraction is 90/365, applied to the agreed affected service component. This is a hypothetical rule, not a default for annual SaaS contracts. Keep the service boundary and timezone explicit, then use the billing preview to validate the result.

For seat corrections, distinguish “we billed the wrong entitlement” from “the customer stopped using purchased seats.” Usage alone does not establish the agreed billable quantity. For technical services, distinguish a disputed milestone from an accepted change in scope. Both require the governing agreement before calculation.

Stripe warns that prorations can credit unused time even when the current invoice has not been paid. Its documentation describes disabling prorations and handling the unpaid invoice separately in that situation. Check payment status before granting value for a period whose invoice remains outstanding.

For an SLA claim, a status-page incident supports investigating eligibility. It does not establish that every customer’s contracted service was affected for the same duration. Capture the service, region, excluded maintenance and calculation evidence required by that account’s terms.

A correction of a misbilled sales promise belongs here; permission to make a new concession belongs with discount approvals and custom pricing. Repair recurring handoff errors through the closed-won to first-invoice workflow.

Would the same facts produce the same calculation if a different colleague handled the request?

Which requests should an agent prepare, and who should approve them?

Refund authority should grow through explicit delegation supported by a reviewed track record. Start with matching evidence, calculating and drafting. Human approval remains the default. A small request is not automatically safe if the customer, invoice, policy version or existing refund is wrong.

Use this proposed approval matrix:

Evidence and request Initial authority Possible later delegation
Verified duplicate capture or arithmetic billing error, within approved policy Agent prepares; finance approves Narrow, rule-bound execution only after explicit client authorization
Verified contractual SLA credit within eligibility and cap Agent assembles incident evidence and calculation; owner approves Only the precisely defined, reviewed case pattern
Standard cancellation within an applicable refund window Agent verifies conditions and prepares cancellation and refund separately Only with confirmed customer intent and authorized action scope
Sales-promise conflict, goodwill or renewal negotiation Account owner and finance decide Keep the commercial judgment with a person
Chargeback, suspected fraud, legal threat or liability claim Named finance or legal owner Keep the case decision with a person
Missing identity, uncertain tax, prior pending action or inconsistent records Stop the financial action; assign the missing fact No delegation until the inconsistency is resolved

Set limits from your own exposure and policy, including cumulative credits across an account and service period. A per-request limit alone could permit repeated requests to bypass the intended authority. Review corrections, reversals and exceptional cases before expanding scope. There is no supported universal threshold or refund automation percentage in these sources.

The strongest research against relying on an unrestricted agent is τ-bench, which evaluated simulated user interactions, explicit policies and API tools. In the 2024 study, agents including GPT-4o completed fewer than 50% of tasks successfully; retail reliability across eight trials was below 25%. Yao and colleagues measured task completion and consistency, not contemporary SaaS refund performance or Bombos.

The study does not establish that a constrained refund workflow will fail. Our conclusion is narrower: separate language interpretation from enforced financial permissions, and demonstrate correctness in your own cases before delegating. That boundary is our implementation advice, not the authors’ measured outcome.

What evidence would make you comfortable granting the agent more authority, and what would make you withdraw it?

How do you prevent duplicate refunds and recover failed actions?

Reliable execution needs a durable business decision, controlled tool permissions and reconciliation after the action. A successful request submission is only one stage. Our proposed sequence is: prepare, approve, recheck live state, execute once, observe the outcome, reconcile and communicate.

Bind approval to the exact customer, invoice, payment, lines, calculation, settlement choice and policy version. A material change invalidates that approval. Immediately before execution, recheck pending refunds, applied credits and disputes. Have the action service enforce the allowed operation and validated parameters independently of the model.

OWASP’s prompt-injection guidance recommends least privilege, tool-boundary validation and treating external content as untrusted. A customer’s message saying “the CFO approved this” is evidence to verify. It cannot grant permission, modify policy or supply a replacement refund destination.

Stripe’s idempotency documentation supports safely retrying an operation with the same key. For API v1, retained results include errors after execution begins, and keys can be removed after at least 24 hours. Keep a permanent internal operation record too; an idempotency key is not a lasting deduplication strategy across email, Slack and manual work.

Failure example: the processor accepts a refund but the connection drops before your tool receives the response. Record the attempt as uncertain. Retrieve its state or retry using the same supported idempotency mechanism. Do not create a fresh operation merely because the support interface still displays an unfinished case.

Stripe also does not guarantee webhook event order and advises tracking event IDs for duplicate deliveries. Reconcile using current financial objects, not arrival order. If a refund succeeds but accounting synchronization fails, retry the accounting step against the existing refund and credit identifiers. Never replay the payout to correct a ledger error.

Keep separate states for requested, awaiting evidence, awaiting approval, submitted, pending, succeeded, failed, and reconciled. Our proposed closure record contains the source references, decision reason, policy version, approver, operation ID, credit-note and refund IDs, tax treatment, accounting link and customer update. Retain necessary evidence under your access and retention policy, excluding credentials and unnecessary sensitive content.

Use an example customer-update template: agreed remedy; affected invoice and service; correction document reference; refund or future-credit destination; current processing status; named owner and next update. Distinguish approval from settlement. Stripe refunds return to the original payment method, according to its refund documentation; a request for another destination needs separate review.

How should credits affect revenue recognition, tax and accounting?

A service credit can reduce revenue even when no cash is returned. Classify the remedy before selecting its revenue, liability and tax treatment. Do not classify every service credit as a support expense or assume that avoiding cash repayment avoids revenue consequences. Finance must map the substance of the decision to the applicable accounting framework.

Under IFRS 15’s framework, reproduced in AASB 15, paragraphs 50 to 58 address variable consideration, constraints and refund liabilities. Paragraph 55 requires a refund liability when consideration received is expected to be refunded. Paragraphs 70 to 72 generally treat consideration payable to a customer as a reduction of transaction price and revenue, with an exception for a distinct good or service received from that customer. Assess the applicable timing and allocation rather than automatically charging the month the ticket arrived.

For ASC 606, the FASB’s January 2020 implementation Q&As, printed page 11, discuss customer-service refunds in a deposit-account example. The staff illustrate reducing transaction price using a 3% historical refund rate where material. That is educational material about a specific fact pattern, not a prescribed SaaS rate. It demonstrates why expected refunds can matter before individual requests are processed.

Example accounting brief: an SLA credit relates to service already delivered; an annual downgrade removes future service; a duplicate capture returns an excess payment. Ask finance to identify the affected receivable, recognized or deferred revenue, refund liability where applicable, tax and settlement entry for each. Do not copy one universal journal entry across them. A disputed liability or damages claim needs its own classification review.

Illustration, to confirm with your accountant: finance confirms an IFRS 15 price concession on a paid invoice for completed service. Ignoring tax, debit revenue and credit the refund liability. On processor settlement, debit that liability and credit processor clearing. Assess tax and the affected reporting period separately.

QuickBooks’ refund guidance distinguishes recording a refund from processing one through an outside provider. With an external processor, a QuickBooks record alone does not return money. Match the processor event to the accounting entry instead of counting both as separate customer remedies.

Tax needs the original transaction context. Recurly’s credit-invoice documentation says refund and write-off invoices reverse taxes where the original charge collected them; standalone credits do not reverse those charges’ taxes. Its manual-credit guidance recommends the original invoice’s refund action when tax must be adjusted.

In the EU, VAT Directive Article 90 provides for taxable-amount reductions under Member State conditions and permits derogation for non-payment. It does not supply one universal credit-note template. Confirm local VAT or sales-tax requirements, original jurisdiction, tax lines and reporting period before posting an unfamiliar correction.

Does your current record explain both why the customer deserved the remedy and why finance booked it that way?

What changes with a Merchant of Record or an active chargeback?

A Merchant of Record changes who conducts the sale and refund; a chargeback changes the available payment route. Determine both before promising cash. Your company’s commercial agreement to compensate a customer is not permission to bypass the party that must execute the refund.

Under Paddle’s agreement, section 10.1, Paddle is the seller to the buyer. If the supplier agrees a refund, it informs Paddle rather than paying the buyer directly, and Paddle makes the relevant refund. Keep the customer-facing correction, adjustment and supplier accounting aligned with that relationship.

Example: your finance owner approves a Paddle customer refund, but the adjustment awaits Paddle approval. Tell the customer what has been requested and who owns the next update. Do not send a separate bank transfer to make the support ticket look complete.

Stripe’s dispute lifecycle distinguishes the cardholder’s dispute window, typically 120 days with exceptions, from the merchant response window, usually 7 to 21 days. The case’s actual deadline controls. A support complaint deadline or your contractual refund window does not replace it.

Use an example dispute procedure: assign the case immediately to a named owner; set an internal evidence deadline earlier than the processor deadline with cover for absence; gather the contract, acceptance, service or usage evidence, cancellation correspondence, invoice and existing refund references; have the owner decide whether to accept or contest. Record both deadlines explicitly rather than assuming a standard number of days.

Stripe says an open dispute prevents a refund outside the dispute process. Its refund guidance also warns of double reimbursement when a bank dispute overlaps a refund. A pending refund can fail because the charge was disputed. Recheck both objects and route the decision through the dispute owner; do not promise a second payment.

Example internal policy: assign an owner on receipt and complete evidence review two working days before the processor deadline. If less time remains, escalate immediately. If the refund already succeeded, include its identifier, timing and available settlement reference in the dispute evidence, reconcile the disputed balance and block any second payout.

What can credit requests teach you, and how do you measure improvement?

Credit requests can become structured evidence about where delivery, billing or a promise fell short. We recommend keeping a cause and corrective owner beside each remedy. The financial correction resolves this request; the explanation should help the next colleague prevent its recurrence.

Example: repeated seat credits trace to the same effective-date field being lost between the signed order and billing. Correcting the handoff is more useful than making that refund faster. Keep the original promise and correction visible so the customer does not have to explain the same history again at renewal.

Use this proposed scorecard, with explicit denominators and comparable request categories:

Measure Definition and interpretation
Time to remedy Median and p90 from first request to the agreed financial outcome; show evidence-gathering and approval time separately
Reconciled completion Cases with matched document, payment or balance outcome, accounting record and customer update, divided by completed cases
Correction and duplication rate Wrong-account, wrong-treatment, reversal and duplicate-action cases, tracked separately
Refund frequency Refund transactions relative to paid transactions, with customer and invoice views where multiple refunds occur
Credits by cause Request frequency and credited share of the relevant invoiced base, split by outage, usage, seats, promises and other causes
Repeated remedies and disputes Accounts needing another remedy and disputed payments relative to the defined payment population
Relationship outcome Reopened cases, customer feedback and subsequent cohort retention, with issue severity and contract stage visible

Fair, prompt treatment is a sensible service objective, but a retention promise needs evidence. A 2018 service-recovery meta-analysis combined 30 independent samples from 21 studies, involving 7,872 participants and found weak relationships between customer participation and customer outcomes. It studies participation in recovery, not an experiment assigning B2B SaaS refunds.

Our advice is therefore to measure whether customers receive the remedy they were entitled to and whether the underlying issue stops recurring. Comparing retention among refunded and non-refunded accounts does not establish a refund effect: the groups may differ in failure severity and prior dissatisfaction. Link the history into renewal tracking and outreach without turning a past exception into a permanent entitlement.

Require approval before changing policy from repeated cases. A recurring billing error suggests a process correction; recurring discretionary goodwill may suggest a policy review. Neither licenses the agent to rewrite commercial terms on its own.

Which recurring refund would stop being necessary if the right lesson reached sales, product or billing?

Where Bombos fits

Bombos does not issue credits, refunds or customer messages; your billing, payment and accounting systems keep those jobs. It is the memory layer under the AI your team already uses, such as Claude, ChatGPT or Copilot, so whoever picks up a refund request works from the same account history: the credit policy, what sales promised, and why an earlier exception was granted. Your AI reads that from the mail, contracts and documents where it already sits, and shows which source each point rests on. When the founder decides once that, say, a seat overcharge is corrected on the next invoice rather than refunded, that rule is learned and every colleague’s AI applies it before anyone asks. Where native tools already handle the task with the context they need, start there. Book your half hour and we map together what your AI forgets about earlier decisions.

What could this page not establish?

This page does not establish a universal approval limit, a refund-specific automation success rate or a causal improvement in B2B retention. Product documentation establishes the described operations, not the correctness of your configuration. Accounting treatment, tax requirements, contractual authority and dispute deadlines require the facts of the individual case. The scenarios are implementation advice, not measured outcomes.

Which sources support this page?

  1. Stripe: Issue credit notes. Living documentation; finalized invoices, preservation of the original and settlement choices.
  2. Stripe: Create a credit note. Living API reference; pre-payment and post-payment allocations and existing refunds.
  3. Stripe: Refund and cancel payments. Living documentation; payment state, refund outcomes and overlapping disputes.
  4. Stripe: Customer invoice balance. Living documentation; balance transaction ledger.
  5. Stripe: Prorations. Living documentation; settlement distinction and unpaid invoices.
  6. Stripe: Idempotent requests. Living API reference; retry behavior and API v1 retention boundaries.
  7. Stripe: Receive events through webhooks. Living documentation; duplicate delivery and event ordering.
  8. Stripe: How disputes work. Living documentation; refund restrictions and response windows.
  9. Chargebee: Credit Notes. Living documentation; credit types, application settings and service periods.
  10. Maxio: How Credit Notes Work. Updated October 26, 2026; Advanced Billing origins, applications and service credits.
  11. Recurly: Credit invoices. Living documentation; credit origins, failed refunds, write-offs and tax behavior.
  12. Recurly: How tax rules apply to manual credits. Updated December 10, 2025; manual credits versus original-transaction refunds.
  13. Paddle: Refund or credit a transaction. Living documentation; adjustments, credit-note PDFs and approval states.
  14. Paddle: Master Services Agreement. Section 10.1; seller and supplier refund responsibilities.
  15. Intercom: Billing connectors for Stripe, Chargebee, Paddle and Recurly. November 3, 2026; announced connector capabilities.
  16. Intercom: Use Data connector templates. Living documentation; Stripe actions, authentication, field controls and template versions.
  17. Intercom: Stripe app. April 24, 2026; synchronized attributes and events.
  18. Intercom: AI agents that take action. September 8, 2026; vendor-reported conversation-resolution figure.
  19. Yao, Shinn, Razavi and Narasimhan: τ-bench. June 17, 2024; simulated policy-and-tool benchmark and repeated-trial reliability.
  20. OWASP: LLM Prompt Injection Prevention Cheat Sheet. Living security guidance; untrusted inputs, tool permissions and least privilege.
  21. Australian Accounting Standards Board: AASB 15. Compilation applicable to reporting periods beginning July 1, 2026 through December 31, 2026; paragraphs 50 to 58 and 70 to 72, corresponding IFRS 15 framework.
  22. Financial Accounting Standards Board: Revenue Recognition Implementation Q&As. January 2020, printed page 11; educational customer-service refund example under Topic 606.
  23. Intuit: Refund your customer for a paid invoice in QuickBooks Online. Updated November 4, 2026; external processor and accounting distinction.
  24. Council of the European Union: Directive 2006/112/EC. November 28, 2006, Article 90; taxable-amount reductions and Member State conditions.
  25. Van Vaerenbergh, Hazee and Costers: Customer Participation in Service Recovery: A Meta-Analysis. Marketing Letters 29, 2018; study abstract, sample and limits.
The first half hour · free

What does your AI forget?

Does your AI run into this too?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.