Refund
The Refund object in Cloudy Inventory represents the process of returning funds to a customer or vendor when a Payment (or part of a Payment) needs to be reversed. Refunds may occur due to overpayments, order cancellations, product returns, service issues, or compliance requirements.
This object captures refund details, links them to the original Payment and Transaction, and ensures that financial records remain accurate, traceable, and auditable throughout the refund lifecycle.
Key Purpose of Refund
💰 Financial Reversal
Records full or partial refunds against customer or vendor payments while maintaining accurate financial records.
📋 Audit & Compliance
Maintains complete refund history, including Refund ID, Reference #, refund amount, and status for auditing and compliance purposes.
⚠️ Error Handling
Captures gateway or processing errors when refund attempts fail, helping administrators troubleshoot refund issues.
🌐 Multiple Refund Methods
Supports both Online (Payment Gateway) and Offline (Cash, Bank Transfer, Manual Adjustment) refund processing.
🔗 Payment & Transaction Traceability
Links every refund to the original Payment and Transaction records, providing complete end-to-end payment history.
Use Cases in Cloudy Inventory
💳 Customer Overpayment Refund
A customer accidentally pays more than the invoice amount. The excess payment is refunded through an Online or Offline refund.
❌ Order Cancellation
When a customer cancels an order before fulfillment, the payment is refunded and linked to the original Payment and Transaction.
🔄 Product Return Refund
After a customer returns products, the organization issues a full or partial refund based on the return quantity or approved refund amount.
💵 Partial Refund
Only a portion of the original payment is refunded, while the remaining amount stays allocated to the original invoice.
⚠️ Failed Refund Processing
If the Payment Gateway rejects the refund request, the Refund record stores the Status and Error Message for troubleshooting.
📊 Financial Reconciliation
Finance teams use Refund records to reconcile customer payments, refunds, and outstanding balances.
Refund Methods
🌐 Online Refund
- Processed through the configured Payment Gateway (such as Stripe or Authorize.Net).
- A unique Refund Id is generated and stored for traceability.
- The associated Payment and Transaction records are updated automatically.
💵 Offline Refund
- Processed manually outside Cloudy Inventory (for example, Cash, Bank Transfer, or manual accounting adjustment).
- The Refund record is still maintained for accurate accounting and audit purposes.
Refund Status Values Explained
- Refunded – Refund processed successfully.
- Refund Pending – Refund request is awaiting processing.
- Partial Refund – Only part of the payment has been refunded.
- Failed – Refund processing failed.
- Cancelled – Refund request was cancelled.
- Refund Pending For Settlement – Refund processed and awaiting settlement.
Example Business Scenario
- Test Customer Inc. purchases 10 Sedan Cars and pays USD 1,000 for Invoice INV-2026-0001.
- Later, the customer returns 2 Sedan Cars, and the organization approves a refund of USD 200.
- The finance team initiates an Online Refund from the related Payment record.
- Cloudy Inventory creates a Refund record with the following details:
- Refund Name: REF-2026-0001
- Amount: USD 200.00
- Refund Method: Online
- Status: Refunded
- Payment: PAY-2026-0001
- Transaction: TRN-2026-0001
- Refund ID: rfnd_7823kjh23
- Reference #: REF-20001
- Legal Entity: Gateway Entity LLC
- After the refund is processed:
- The Payment and Transaction records are updated.
- The refunded amount is reflected in financial reports.
- The Refund record provides a complete audit trail for future reconciliation.
Zoho books
Quickbooks
Shopify
Acumatica
SAP
Odoo
Sage
Agentforce Revenue Management
Agentforce Revenue Management + Billing
Salesforce CPQ
Salesforce Advanced Billing
Migrate from CPQ to Agentforce Revenue Management
Microsoft
Data Cloud
Tableau
