As long as paper and toner come out of one common budget, every department prints like it is free. Shared accounts change the psychology completely: each job is billed to a department, and each department head gets a monthly statement with their own total on it. This guide builds the accounts, the per-page maths and the charging routine.
A shared account in PaperCut is a cost bucket - a department, a project, a client - that print jobs can be charged to instead of (or alongside) the user's own balance. The user picks the account when printing, or you set a sensible default per group so nobody has to think. At month end, each account gets a statement. The maths must be honest and visible, or departments will dispute every line - so this guide starts with the cost calculation, not the software clicks.
Build the page prices from real bills, and publish the working. Take last quarter's paper cost plus toner and drum cost, divide by the pages actually printed in that period (PaperCut's printer report gives you the count), and you have a defensible mono cost per page - in many Indian offices it lands near Rs 1 to 2. Colour costs several times more because colour toner and coverage are heavier; price it from the colour cartridge yields the same way. Add nothing for the printer purchase unless management wants a depreciation share - and if you do, say so on the statement. A price nobody can interrogate will be interrogated forever.
Create one shared account per department, project or client, using the same names and codes your accounting already uses. If finance calls it CC-204 Sales, PaperCut should call it CC-204 Sales too - statements then drop straight into the existing bookkeeping without translation arguments. Set each account's behaviour: most departments run as tracked budgets (print always allowed, cost recorded), while grant-funded projects or client-billable work may carry a real balance that can run out. Resist creating hundreds of accounts; every account is a choice a user may have to make at print time, and long lists breed wrong charges.
With the PaperCut user client installed (or at release on MF devices), the user sees a prompt: charge this job to my department, or to a project? For staff who print for several projects, this prompt is the system working as intended. For the majority who print only for their own department, set their group's default shared account so the charge lands correctly with no prompt at all. Review the default when someone changes teams - a transferred employee charging their old department for six months is the most common shared-account error, and it is an admin error, not user fraud.
For professional firms - advocates, CAs, architects, design studios - shared accounts named per client turn printing into a recoverable cost. The monthly account statement lists every job for that client with pages and amounts, ready to attach to the client's bill. PaperCut can format this as client-ready invoicing. Offices that start charging clients for the printing done on their matters often find the PaperCut licence pays for itself from this one report - and clients rarely dispute it, because the statement shows document names and dates, not a round figure.
Statements must arrive like clockwork and be checkable. On the 1st: run the shared account summary for the closed month, send each head their own statement, and keep the master copy. Give heads a simple challenge route - any line can be traced to the job log entry with user, document and time. When a charge is genuinely wrong (wrong account selected), correct it in the open and note the correction. A billing system that admits and fixes its rare errors is trusted; one that insists it is always right is routed around within a quarter.
The video shows shared accounts being created and a job charged to a department - watch it before setting up your account list.
▶️ Watch Full VideoThat is a configuration choice. The common office design: jobs charged to a shared account do not deduct the user's personal balance, because the department is paying. Personal printing, where allowed, charges the user. Mixing both deductions on one job double-charges and is the fastest way to make staff hate the system - pick one owner per job.
The job charges to their default - normally their department account - and the monthly review catches it: the project statement is short, the department's is fat. An administrator can reassign recorded jobs to the correct account before statements go out. Repeated forgetfulness from one team usually means the account list is too long; shorten it.
No. Shared account reports are generated by the administrator and sent to each head separately. Within the admin console, you can also restrict which administrators manage which accounts if your organisation is large enough to need that separation.