> 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/revenue/invoices/bulk-actions-on-invoices.md). # Bulk actions on invoices When the same thing needs doing to a stack of invoices — a check that covers several of them, a batch of bad debt to write off, a run of paperwork to print — you can do it from the Invoices page in a single pass instead of opening each invoice one at a time. **Bulk Actions** at the top of the Invoices page offers six actions: | Action | What it does | | --------------------- | ------------------------------------------------------------------------ | | Record a payment | Enters one manual payment per invoice, sharing a payment method and note | | Charge payment method | Charges one customer's saved card or bank account once per invoice | | Mark as uncollectible | Writes off the remaining balance on each invoice, with one shared note | | Void | Voids each invoice so the customer can no longer see or pay it | | Download PDF | Downloads each invoice's PDF (one file, or a zip for several) | | Print | Merges the invoices' PDFs into one document and opens your print dialog | ## Before you start * You need permission to edit invoices to see the Bulk Actions button. * Bulk actions are available on desktop only. The mobile invoice list has no selection checkboxes — use each invoice's own page there. * Every action has its own eligibility rule, so the invoices you can pick change with the action you chose. While you're selecting, the list only shows invoices that qualify — anything the action can't take is left out until you cancel or finish. * Invoices created by your payment provider (for example, one billed through a Stripe-managed subscription) are left out of Record a payment, Mark as uncollectible, and Void — the provider collects on those, so recording or cancelling them here would put the two out of step. This excludes any invoice carrying a provider invoice id, not only ones set to charge automatically. You can still download and print them, and you can still act on them individually from the invoice's own page. * One batch can hold up to 100 invoices (25 for Charge payment method). If you need more, run it in several batches. ## How selecting works 1. Open the Invoices page and choose an action from **Bulk Actions** (top right, between Tax Report and New Invoice). 2. Click each invoice you want — anywhere on its row, not just the checkbox; clicking again deselects it. While you're selecting, a click never opens the invoice. Use the status tabs, search, and filters first if that makes them easier to find — the banner's **Select all** and the checkbox in the table header both pick every eligible invoice currently in the list, across all pages, up to the 100-invoice limit. If more than 100 qualify, Essential selects the first 100 **in the order the list is showing** — so sorting a column first (oldest due date, largest amount) decides which 100 you get. The banner's Select all tells you it capped the selection; the header checkbox caps the same way but without that notice. Narrowing the list with filters works too. 3. The banner above the table shows how many invoices are selected and the button that runs the action. 4. **Cancel** in the banner leaves selection mode and clears the ticks — it's also the only way to switch to a different action, since Bulk Actions is hidden while you're selecting. ## Record a payment Use this when one check (or one cash drop-off) covers several invoices, or you simply have a stack of manual payments to enter. **Eligible invoices:** Unpaid, Overdue, or Partially Paid, and still with a balance owing. Draft, Paid, Void, Uncollectible, and Payment Processing invoices can't be included. An invoice with a card or bank payment already in progress can still appear in the pick list — Essential names it and rejects the whole batch when you confirm, instead of filtering it out beforehand. Everything in the batch shares one payment date, one payment method, one reference field (when configured), and one note. If the payments were collected on different days or in different ways, do them in separate batches. 1. The banner shows the selected invoices' combined balance, so you can check it against the amount you received. 2. Select **Record payment** in the banner to open the window. 3. Each invoice appears with its balance due and an amount box pre-filled with that full balance. Change any amount to record a partial payment, or use the **✕** next to a row to drop that invoice from the batch. **Total payment** at the bottom of the list is what you should be matching against your check. 4. Set the **Payment date** — the day the check cleared or the cash arrived. It defaults to today and can be back-dated to any past day, never into the future. It may be earlier than some invoices in the batch (an invoice written up after the check arrived); the window tells you how many invoices are dated after the payment date so you can double-check. This one date applies to every payment in the batch and is the date QuickBooks books them on, so it lines up with your bank statement. 5. Choose one of your business's configured payment methods. Fill in its reference field if one appears, such as **Check #**; a field marked **\*** must be filled before recording. Admins manage the choices, field labels, placeholders, and required fields in [Settings → Invoicing → Manual Payment Methods](/administration/settings/customize-manual-payment-methods.md). 6. Add **Internal Notes** for your team if useful. Notes are included in accounting journal-entry memos sent to QuickBooks, but not on customer receipts or invoices. Use the payment method's reference field for customer-visible details such as a check number. 7. Select **Record … Payments of …** to confirm. When the selected manual payment method has multiple GL accounts, choose the required **GL account** before recording the batch. Every payment in the batch uses that account. With one mapped account, it is used automatically. GL account details and Internal Notes remain internal. Each invoice gets its own recorded payment for the amount you entered. An invoice paid down to zero moves to Paid; anything with a balance left moves to (or stays) Partially Paid, or Overdue if it's past due. Every payment is written to its invoice's timeline like a single Record Payment would be. If an admin changes the payment method's name, reference field, or GL destination after a batch starts recording, Essential preserves payments already recorded and stops recording the remaining invoices with those changed details. Refresh and record the remaining invoices in a new batch. Retrying the original batch still recognizes its recorded payments without duplicating them. Essential saves each payment together with the invoice status, timeline, payment-reminder stop, and accounting work that describe it. It also prepares the paid PDF before reporting that invoice complete; delivery of the saved accounting entry to QuickBooks may finish just after the confirmation appears. If the payment is saved but the paid PDF cannot finish, Essential keeps it out of the ordinary payment selection and shows **Payment processing needs attention** with **Retry finishing up**. The same safe prompt appears if the browser loses the result and Essential cannot tell whether the payment landed. Essential saves the exact recovery request in this browser before sending the payment, so the prompt remains available after a page refresh or browser restart when you return as the same user. Use that button to replay the exact original request — do not start another payment. Essential either finishes the payment that already exists or records it once if the first request never arrived. To correct a recorded payment, open that invoice and use [Mark as Unpaid](/revenue/invoices/can-i-reverse-a-payment-i-recorded.md). This undoes all manual payments on that invoice; it is not a bulk action. ## Charge payment method Use this when a customer wants to pay several invoices with the card or bank account on file, or reads you a new card over the phone for a stack of invoices. It is the bulk form of [Charge a customer's saved card for an invoice](/revenue/invoices/charge-a-customers-saved-card-for-an-invoice.md), and it needs the same permission to charge payment methods (the action is hidden otherwise). **Eligible invoices:** the same as Record a payment — Unpaid, Overdue, or Partially Paid with a balance owing, and not collected by your payment provider. A charge is for **one customer at a time**: once you tick the first invoice, the list reloads with only that customer's invoices until you cancel the selection. The previous list is hidden while it reloads, so another customer's invoice cannot be added during the wait. Opening the Invoices page from a customer (the amount-due link on the customer page) already filters it to them. 1. The banner shows the selected invoices' combined balance and the customer's name. Select **Charge payment method** to open the window. 2. Each invoice appears with its balance due and an amount box pre-filled with that full balance. Change any amount to charge less, or use the **✕** next to a row to drop that invoice from the batch. 3. Optionally enter a **Receipt email**. Every receipt in the batch is emailed there as each charge succeeds; leave it blank and each invoice's receipt goes to that invoice's contact, as a single charge does. 4. Pick one of the customer's **Saved payment methods** (shown first, with a count), or switch to the **New payment method** tab to enter a new card or bank account. A customer with nothing saved goes straight to the new-method choice. **Fee** and **Total to Pay** under the list show the processing fee for the whole batch, priced per invoice the same way a single charge is (an invoice whose fees are waived adds none). 5. Select **Charge**. With a saved method, Essential charges each invoice in turn and then lists the result for every invoice: **Charged**, **Processing** (bank transfers settle later; invoice payment reminders stop while the transfer processes), or the reason it was not charged. With a **new** method, the first invoice in the batch is charged through the payment form you fill in, which also saves the method on the customer. The remaining invoices are then charged with the saved method straight away, and the same result list appears. If the form is declined, nothing has been charged. Receipts work as they do for any card or bank charge: when a charge succeeds, Essential emails that invoice's receipt automatically — to the **Receipt email** you entered, or to the invoice's contact — and each payment card on the invoice keeps its **Send Receipt** and **Download Receipt** actions for a resend to anyone else. Each invoice gets its own charge: the customer sees one line per invoice on their card or bank statement, each invoice records its own payment and receipt, and a processing fee applies per invoice. If a charge is declined partway through, the invoices before it are already paid, the declined one and every invoice after it are reported as not charged, and those stay selected so you can try them again with another method. Retrying the same batch after a lost connection never charges an invoice twice: Essential recognizes the charges it already made for that batch and reports them instead. If you reopen the charge window after an interrupted payment, retry with the same amount and saved method so Essential can recover the pending charge. If the interrupted attempt is 23 hours old or more, Essential asks you to review the original payment before starting another. Check the payment provider's record before trying again. When retrying a batch, completed charges still appear in the results if another invoice has since become unavailable. A retry also preserves a later write-off or other change to an invoice that was already charged. ## Mark as uncollectible Use this to write off balances you've given up on collecting — the same thing as [Mark as Uncollectible](/revenue/invoices/mark-an-invoice-as-uncollectible-write-off-the-balance.md) on a single invoice. **Eligible invoices:** Unpaid, Overdue, or Partially Paid. Drafts are deliberately excluded — an invoice the customer has never seen isn't a write-off. An invoice with a card or bank payment in progress can still appear in the pick list, but if that payment goes through afterwards it would put the invoice straight back to paid and undo the write-off — so Essential names it and rejects the whole batch when you confirm instead. Wait for the payment to succeed or fail, then decide. 1. Select **Mark uncollectible** in the banner. The window lists the invoices you're writing off. 2. Enter **Notes**. A note is required, and the same note is saved on every invoice in the batch — write the reason you'd want to read a year from now ("customer out of business", "sent to collections"). 3. Select **Mark … Uncollectible** to confirm. Each invoice moves to Uncollectible, the note is saved on it, and the write-off is recorded in accounting. **This can't be undone** — if you only want to stop the invoice reaching the customer, void it instead. ## Void Use this to pull invoices back — a duplicate run, a batch raised against the wrong property, paperwork that shouldn't have gone out. **Eligible invoices:** Draft, Unpaid, or Overdue, with no payment received. An invoice that has taken any money can't be voided (there's no refund path on void) — mark it uncollectible instead. An invoice with a card or bank payment still in progress can't be voided either: the payment could settle a moment later and reinstate the invoice as paid. The invoice may still appear in the pick list in that case — a payment that hasn't gone through yet isn't shown in the list — so Essential names the invoice and blocks the batch when you confirm. 1. Select **Void** in the banner. The window lists the invoices you're voiding. 2. Select **Void … Invoices** to confirm. A voided invoice is no longer visible to the customer or editable, and any scheduled reminder emails for it stop. Unlike a write-off, you can re-open a voided invoice later from its own page — see [Void an invoice (and reopening a voided one)](/revenue/invoices/void-an-invoice-and-reopening-a-voided-one.md). ## Download PDF **Eligible invoices:** any invoice that already has a PDF — that is, one that has been sent or finalized. An invoice that has never left Draft has nothing to download yet. Select **Download PDF** in the banner. One invoice downloads as a single `Invoice-I….pdf`; several download as a single zip named `invoices.zip`, with the files in the same order they appear in your list. ## Print All invoices matching your filters can be printed, including unpaid invoices. Essential reuses an invoice’s associated PDF when it matches the selected template and is current with its payments. Otherwise, it generates a temporary PDF for that print request without attaching it to the invoice. Printing does not finalize an invoice or change its payment status. Choose **Invoice date to print** to narrow the list to one day. Invoices for that day matching your other active filters are selected automatically, across pages, up to the existing 100-invoice limit. If more than 100 match, a notice explains that only 100 are selected. You can deselect any you do not want. The date uses your business timezone. If the existing invoice-date filter already covers one day, entering Print selects that day’s matching invoices. If your business has multiple invoice templates, choose **Print template** beside the date picker. Your business’s default invoice template is selected initially. The selected template is used for every invoice in the batch. This only affects the printed copies; it does not change saved templates or the invoice PDFs shown to customers. Select **Print** in the banner. Essential merges the selected invoices' PDFs into one document, in the order they appear in your list — including whatever sort you have applied to the table — and opens your browser's print dialog on it. Print the whole batch in one go rather than opening each invoice. ## When something is skipped or fails * **Download and print** skip any selected invoice whose PDF cannot be prepared or retrieved and tell you how many were skipped. Printing also skips invoices that cannot be prepared before the request deadline. The rest still download or print. If not one of the selected invoices can produce a PDF, nothing downloads or prints and Essential says so; if that happens to an invoice you know has been sent, re-send it to regenerate its PDF. * **Record a payment, mark uncollectible, and void** check the whole batch before changing anything: if one invoice isn't eligible, nothing is changed and Essential names the invoice and the reason. * Each invoice is re-checked again at the moment it's written. If something changed while the batch was running — a customer's card payment landed, or a colleague voided the invoice — that one invoice is skipped with a reason and the rest of the batch still goes through. This is what stops a bulk payment from overpaying an invoice that was settled seconds earlier. * If a batch is interrupted partway, Essential tells you which invoices were affected and keeps **only** those whose payment was not recorded selected, so you can retry without re-running the ones that already went through. If the same response also contains a payment whose paid PDF still needs repair, Essential closes the ordinary selection and makes you finish that saved repair first; afterwards, start a new batch for any invoices that remain unpaid. This prevents the new batch from replacing the saved repair for money already recorded. If a payment was recorded but its paid PDF failed, or the browser loses the response before it can confirm the result, a separate **Retry finishing up** banner preserves the exact submission even after paid invoices leave the ordinary selection or you refresh/reopen this browser. Use that safe replay instead of starting another payment. * If the browser loses the response entirely after part of a Void or Mark uncollectible batch committed, retrying the original selection is safe: Essential recognizes invoices already in the requested status, does not repeat their history, automation, or accounting entries, and continues with the remaining invoices. > **Where to find it:** Invoices page, Bulk Actions (top right) ## Related guides * [Record a payment on an invoice](/revenue/invoices/record-a-payment-on-an-invoice.md) * [Mark an invoice as uncollectible (write off the balance)](/revenue/invoices/mark-an-invoice-as-uncollectible-write-off-the-balance.md) * [Void an invoice (and reopening a voided one)](/revenue/invoices/void-an-invoice-and-reopening-a-voided-one.md) * [See and browse all your invoices](/revenue/invoices/see-and-browse-all-your-invoices.md) * [Filter invoices by status](/revenue/invoices/filter-invoices-by-status.md) * [Invoice statuses and what each one means](/revenue/invoices/invoice-statuses-and-what-each-one-means.md) * [Can I reverse a payment I recorded?](/revenue/invoices/can-i-reverse-a-payment-i-recorded.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/revenue/invoices/bulk-actions-on-invoices.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.