> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/reporting-and-integrations/reporting/filter-and-export-the-invoice-payments-report.md). # Filter and export the Invoice payments report The Invoice payments report gives you one row for every payment or checkout attempt linked to an invoice. If a customer makes two payments on the same invoice, the report shows two rows. Each row shows the invoice, customer, property, invoice status, payment status, method and reference, notes, created date, paid date, and payment amount. > **Where to find it:** In the left navigation, click **Reports**, then open **Invoice payments** under Financial. The **Payment method** column includes the saved reference, for example **Business Check (Check #: 1042)** or **Zelle (Confirmation #: Z-1042)**. CSV exports include the same value. Renaming or removing a payment method in Settings does not change the method name or reference shown for recorded payments. If your business records payments in goods or services, the **Payment method** filter finds them under the name they were recorded with (see below), and whether a payment counts as paid in trade can follow the method's current setting (see [Payments in goods or services](#payments-in-goods-or-services)). The **Payment speed** report also includes these references and lists all successful payment methods when an invoice has more than one payment. ## Filter the report 1. Click **Filter** above the table. 2. Choose one of these filters: * **Payment status** — select one or more payment statuses. * **Customer** — search for and select one or more customers. * **Created date** — set a From date, a To date, or both. * **Paid date** — set a From date, a To date, or both. * **Payment method** — search for and select one or more methods, such as **Cash** or **Zelle**. Card and bank payments made online appear as **Card** and **Bank**. * **Settlement** — **Paid in money** or **Paid in trade**. It matches succeeded payments only: a payment that failed, was canceled, or is still processing settled nothing. **Payment method** and **Settlement** appear once your business has recorded a payment with a method marked as paid in goods or services (see [Payments in goods or services](#payments-in-goods-or-services)). 3. Close the filter menu. The table and payment count update immediately. You can combine filters. For example, select **Succeeded**, one customer, and a Paid date range to see that customer's successful invoice payments during the period. Both ends of a date range are included and follow your business's time zone. The Created date is when the payment record was created. The Paid date is the day the customer paid: for card and bank payments made online or charged to a method on file, the day the payment was started; for payments you recorded yourself, the payment date you entered. A bank payment can take several business days to clear; when it cleared on a later day, that day appears under the paid date as **Cleared**. Sorting, the Paid date filter, and the CSV export use the paid date. The Paid date stays blank for payments that have not succeeded. The payment amount excludes a separately collected processing fee. It reduces the invoice balance only when the payment succeeds. Each active filter appears above the table. Click a filter pill to remove it. When it appears, the **Payment method** filter lists each name saved on the report's payments once, so a method appears there after its first payment. Once a renamed method has payments under both its old and its new name, choosing either name finds all of that method's payments; until a payment is recorded under the new name, they are found under the old name. Two methods with the same name (for example a custom **Cash** method and the standard one) filter together. Older online payments without a recorded card or bank choice are listed under **Stripe**, and payments that can't be matched to a method under **Unknown**. The toolbar keeps **Filter**, search, **Review mode**, and CSV export together. Click the search icon to find payments by invoice number, customer, property address, status, payment reference, notes, displayed date, or amount. Search covers all pages and combines with your active filters. ## Payments in goods or services A payment counts as **Paid in trade** when it was recorded with a method that has **Customers pay with goods or services (barter / trade)** turned on (see [Customize manual payment methods](/administration/settings/customize-manual-payment-methods.md#mark-a-method-as-paid-in-goods-or-services)). Once your business has recorded one, the report adds the following. Until then the report looks exactly as it always has, and its CSV has only the columns shown in the table. * the **Payment method** and **Settlement** filters, described above; * **Succeeded payments by paid date** above the table, with **Paid in money** and **Paid in trade** totals for the rows that match your filters. Only succeeded payments count, each once, so set **Paid date** to the period you want. A payment marked unpaid later is no longer succeeded and drops out of these totals; the [Tax Remittance Report](/revenue/invoices/run-the-tax-remittance-report.md) is the figure to file from, because on a cash basis it shows a payment in its own period and its reversal in the reversal's period; * **Tax share** and **Amount excluding tax** columns, filled in for trade payments only. **Tax share** is the part of the payment that went to sales tax on your sales-tax reporting basis, as of when you open the report, net of any refund of the payment. **Amount excluding tax** is the payment amount, less any refund, minus the tax share, so each row adds up net of refunds. It includes any late fee or overpayment the payment covered, so it isn't always the pre-tax price of the work. A trade payment that failed or was later marked unpaid shows $0 in both columns. Essential splits every payment on an invoice between sales and tax in proportion, so a trade payment carries part of the tax even when the partner paid the tax in money. ## Understand the two statuses **Invoice status** is the same overall status shown when you open the invoice. **Payment status** describes this individual attempt; an unpaid invoice can have an incomplete checkout attempt. * **Unpaid**: this checkout attempt has not paid the invoice. The invoice's payment history explains when checkout is incomplete. This replaces the earlier label **Requires confirmation** and does not mean the bank needs verification. * **Checkout started** or **Payment details needed**: the customer has not completed checkout. These statuses do not mean the bank needs verification. * **Action required**: the customer needs to finish an additional step on their invoice payment page. For bank verification, the invoice's payment details explain that step. * **Processing**: payment has been submitted and is still processing. Bank payments can take several business days. No customer action is currently requested. * **Succeeded**: the payment counts toward the paid balance. * **Failed** or **Canceled**: this attempt does not count toward the paid balance. Open the invoice to see payment attempts alongside successful payments. Hover over a payment status in the report for an explanation. ## Sort, open, or export payments Click any column header to sort the report, then click it again to reverse the order. Click a payment row to open its invoice. Use the page controls below the table to browse payments, 20 at a time. Changing a filter or sort returns you to page 1. Filters and sorting apply to every payment, and CSV exports include every matching row across all pages. Click the download icon above the table to export a CSV. The export contains the same filtered rows in the same sort order shown on screen. Money is exported as plain numbers so a spreadsheet can sum and format it. Once your business has recorded a payment in goods or services, the CSV ends with four more columns: **Payment method name** (the method without its reference), **Settlement** (**Paid in money** or **Paid in trade**, and blank for a payment that did not succeed), **Tax share**, and **Amount excluding tax**. They come after all the earlier columns, so spreadsheets that read columns by position keep working. The two tax columns are blank for payments made in money. ## Related guides * [Export, filter, and drill into a report](/reporting-and-integrations/reporting/export-filter-and-drill-into-a-report.md) * [See and browse all your invoices](/revenue/invoices/see-and-browse-all-your-invoices.md) * [Record a payment on an invoice](/revenue/invoices/record-a-payment-on-an-invoice.md) --- # 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://learn.withessential.com/reporting-and-integrations/reporting/filter-and-export-the-invoice-payments-report.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.