Explanation of point-of-charging and automatic refunds

When does PaperCut charge users for printing? What happens if I delete a job from the queue?

Windows Print Servers:

PaperCut will charge the user the moment the print job completes spooling to the server. This may also correspond to the time the job prints, however if the job is 2nd or later in the queue, then the point-of-charging will be before printing starts while the job is waiting. If the job is subsequently deleted form the queue the job will be refunded according to the following logic:

  1. If the job has not started printing (e.g. was placed 2nd or later in the queue), the full amount of the job will automatically be refunded.
  2. If the job has started printing or is in the process of printing, the job is not refunded, but instead is marked as a candidate for manual refund (e.g. Canceled but not Refunded). The reason for this is security - that is it's not possible to tell how many pages have actually printed due to buffering in the printer memory and network connection. The safest approach is to manually handle these exceptions using the one-click refund link listed next to the job in the admin interface. (A behind the scenes comment: In the very early days at PaperCut our software would automatically refund, but the kids at one school worked out that if they deliberately stuck a paperclip in the printer at the right moment, they could get a free or discounted job! Hence we now take a more secure play-it-safe approach.)

Linux and Mac Print Servers:

Due to the method of integration with CUPS, the point-of-charging is when the job is positioned number 1 in the queue and is about to print (On the technical level this is because PaperCut hooks in at the CUPS backend layer). If an error occurs prior to printing, or the job is deleted form the queue early, again the job will automatically be refunded.

The Windows method offers the advantage of immediately notifying the user that they have exceeded their quota/credit when the job completes spooling to the print server. Sites with Mac and Linux servers should be aware that users will not receive the "Print Denied" message (generated as a result of no available credit) until the job is ready to print. This will not be a problem on small sites with lightly loaded queues, however, large sites with heavily loaded queues may require some additional user education.

How do I perform a manual refund?

A manual refund can be performed quickly by any nominated administrator. Simply locate the job in the print log (either the global print log under Printers -> Print Log or under the user's of printer's Recent Jobs list), and click on the one-click Refund link next to the appropriate job. The user's or the shared account will automatically be refunded and the job flagged appropriately.

Partial refunds, if applicable, should be handled via the Adjustments & Charges tab on the appropriate account.


Categories: Administration


keywords: refunds, refunding, failed or cancelled prints, paper jams, errors, charge time

Page last modified on May 26, 2008, at 08:36 AM