# Printing Batches: Activating, Re-printing & Queue Limits

### Abstract <a href="#e9myf3esd7m6" id="e9myf3esd7m6"></a>

Check batches are automatically created during the print process in **Charted** and can be reactivated if reprinting is needed. Administrators can manage batch activity, address print failures, and stay within queue limits. For example, if a printer error interrupts check printing, administrators can reactivate the entire batch for reprinting. It’s important to use the designated reprint process rather than relying on the *File Cabinet*.<br>

This guide explains how to access, reactivate, and reprint check batches and highlights key behaviors such as PDF rendering, print queue limits, and batch ownership visibility.

### Viewing, Reprinting, and Managing Check Batches <a href="#jfq6yrbhfc83" id="jfq6yrbhfc83"></a>

Once checks are printed, the system creates a batch and marks it inactive after rendering. If issues occur, such as printer errors, administrators can reactivate the batch for reprinting and monitor activity using the available batch management tools.

Follow these steps to view, reprint, or activate check batches:<br>

1. To access existing check batches or create a new one, hover over the **Setup** menu, go to **Check Printing**, and select **Check Batches**, which will take you to the **CPB Check Print Job List** page:\ <br>

   <div align="left"><figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FMGoZvQT6TNDylCEemvTr%2F0.png?alt=media&#x26;token=6369abdf-d667-42ae-9c02-56630f880593" alt="" width="536"><figcaption></figcaption></figure></div>

   \
   \&#xNAN;**\[SW TO PROVIDE SCREENCAP OF CPB CHECK PRINT JOB LIST PAGE]**\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FhPjsMQH3v4JP1mXkA6m5%2F1.png?alt=media&#x26;token=77d2cced-c650-44ef-a344-5522dad16279" alt=""></div>

   \
   \
   A batch is created automatically when checks are printed or queued through the print checks page. You can print a single check or select large quantities like 100 or 500. While some customers print more, it’s recommended not to exceed 500 — especially when logos are included in the output.\ <br>
2. Next, select a batch from the list and click the **View** button to open and review its details:\
   \ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FPV30pA1L67Y58VPP5JsR%2F2.png?alt=media&#x26;token=7ddbeeab-0a52-4368-923c-32048e2893c6" alt=""></div>

   ![](https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2F4wDM8P5W5EGzcprfvPh3%2F3.png?alt=media\&token=1b722581-bf96-4b58-8804-2200279ce94e)

   \
   \
   The system marks the check batch as inactive once the checks are printed and the PDF is rendered. This is why test mode is useful — it keeps the batch active while testing templates. In production, rendering the PDF marks the batch inactive.\ <br>
3. If a printer jam or error occurs and the entire batch needs to be reprinted, an administrator can reactivate it. To do this, open the batch and check the **READY TO PRINT** box:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FaILgpICzh5ohn6BXo6bE%2F4.png?alt=media&#x26;token=48bf1a47-07b9-4a7a-90dc-683590c8ff9e" alt=""></div>

   <br>
4. To locate the batch for reactivation, hover over the **Transactions** menu, then go to **Check Printing**, and click **Status**, which will take you to the **Print Checks Status** page:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FC9f9iZaIVwpGrVaEpFvo%2F5.png?alt=media&#x26;token=f3dce59f-9cb9-4f04-857d-7480a34dd1f0" alt="" width="416"></div>

   <br>

   <figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FnBypI1yaqsiN6sz8Q7mz%2Fimage.png?alt=media&#x26;token=8d61ae99-aae9-4db6-8ba2-26d66d6cd6eb" alt=""><figcaption></figcaption></figure>
5. If the user does not own the batch, they may need to select **Show All Owners**, provided they do not have restrictions on viewing others’ batches:\ <br>

   <figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2F5wmaGGdpvGWpEmQ6IbpY%2Fimage.png?alt=media&#x26;token=3a2afc1c-88d3-490b-8251-9a195cf8fd28" alt=""><figcaption></figcaption></figure>

\
Reactivating a batch will return it to the print queue, but it’s important to note that this reactivates the entire batch, not just a single check. Some users may mistakenly attempt to print directly from the **File Cabinet**, but that is not the intended process. Reprinting must occur by making the batch active again.

This concludes the process of printing, reactivating batches, and managing queue limits in **Advanced Check Printing**.
