> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/commerce-data-models/financial-models.md). # Financial models Chord gives you three OMS explores for financial, refund, and return analysis. The Transactions explore covers cash movement (sales, captures, and refunds) and books refunds on the date they were issued. The Refund Line Items and Return Line Items explores break refunds and returns down to the order line, so you can read them by product. These explores are available to OMS tenants. ## Quick reference, which explore should I use? | Business question | What you want to understand | Explore | | --------------------------------------------------------------- | ----------------------------------------------- | ------------------------------- | | How much revenue moved in this period, including refunds? | Cash-basis revenue and refund dollars by date | Transactions | | Which products are getting refunded, and for how much? | Refund dollars and refunded units by product | Refund Line Items | | Which products are getting returned, and why? | Returned units and return reasons by product | Return Line Items | | Were these refunds tied to a customer return or a cancellation? | Restock type behind each refunded line | Refund Line Items | | When was the return opened versus when was the refund issued? | The two date axes (return date and refund date) | Transactions, Return Line Items | ## Key dimensions and metrics ### Transactions One row per successful cash-moving transaction (sale, capture, or refund). Refunds book on the date the refund was issued rather than the original order date, which keeps month over month revenue stable. Common metrics: Gross Sales, Net Sales, # Refunds, # Refunds (distinct), Refunded Amount Sum, # Returns (distinct), Returned Quantity Sum. Common dimensions: transaction date (cash basis), transaction kind (sale, capture, refund), Refund Created At, Return Created At, Return Status, Return Closed At. Use this explore for revenue reporting and for refund or return dollars grouped by date. ### Refund line items One row per refunded order line. Join to the order line to group refunds by product (product title, SKU). Metrics: # Refund Lines, Refunded Quantity, Refunded Subtotal, Refunded Tax, Refunded Amount (incl tax). Dimensions: Restock Type, Refund Created At, plus product fields from the joined order line. Use this explore to see refund dollars and refunded units by product. A note on coverage: the line-item amounts cover merchandise only. They do not include shipping refunds or order adjustments such as restocking fees, because those are not attributed to a product line. The sum of per-line refund amounts will be lower than a refund's full amount by that non-product portion. ### Return line items One row per returned order line. Join to the order line to group returns by product. Metrics: # Return Lines, Returned Quantity, Refunded Quantity, Refundable Quantity. Dimensions: Return Reason, Return Reason Note, Return Created At, plus product fields from the joined order line. Use this explore to see returned units and return reasons by product, and to find returns that are not yet fully refunded (Refundable Quantity greater than zero). ## Glossary | Term | Definition | How to use it | Where you'll see it | | -------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Return Created At | The date the return was opened | Matches your OMS Total Sales and Net Sales reporting, which book a return when it is opened | Return Line Items, Transactions (Return Created At) | | Refund Created At | The date the refund was issued | Matches your OMS Finance and Refunds reporting, which book on the refund date | Transactions (Refund Created At and transaction date), Refund Line Items | | Restock Type | How the refunded items were handled (no restock, cancel, return, legacy restock) | Tells you whether a refunded line was a cancellation before fulfillment (cancel) or a customer return (return) | Refund Line Items | | Returned Quantity | Units returned on the line | The volume of product coming back | Return Line Items | | Refunded Quantity | Units that have already been refunded | Compare against Returned Quantity to see how much of a return has been settled | Return Line Items | | Refundable Quantity | Units on a return still eligible to be refunded | Find returns that are open and not yet fully refunded | Return Line Items | | Refunded Amount (incl tax) | Refunded subtotal plus refunded tax for a line | Product-level refund value. Does not include shipping or restocking-fee refunds | Refund Line Items | ## Choosing the right date Returns and refunds sit on two different dates, and they can be weeks apart. A return is opened first (Return Created At), and the refund is issued later (Refund Created At). Group by Return Created At when you want to match your OMS Total Sales view. Group by Refund Created At (or the Transactions explore's transaction date) when you want to match your OMS Finance and Refunds view. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/model-your-data/commerce-data-models/financial-models.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.