Cost tracking · IT setup · 7 minute read

How to set up department and accounting codes for accurate cost tracking

A working guide to configuring per-department print volume tracking on office MFPs — from code scheme design through device configuration to monthly cost reporting.

Department and accounting codes on an MFP turn every print, copy, and scan into an attributable transaction. The finance team sees that Legal printed 18,400 pages in November while Marketing printed 28,100. The IT manager sees that the Madrid office costs €0.018 per page average while the Valencia office costs €0.024. The questions about who is consuming the print budget have answers instead of guesses. This guide walks through the setup that produces those answers.

Three code scheme levels

Simplest

Department only

One code per department. Marketing prints anonymously under code 100, Finance under 200, Legal under 300. No individual user tracking.

Standard

Department + user

Each user authenticates with their own ID linked to a department. Both individual and department-level tracking available from the same data.

Detailed

Department + user + project

Users enter a project code at print time for client billing. Print activity rolls up to user, department, and project for granular reporting.

Designing the code scheme before configuration

Before touching the device, design the code structure. The scheme should match how the finance team already categorises costs. If the chart of accounts uses three-digit cost centres, mirror that scheme on the MFP. If the firm bills clients by matter code, use those matter codes as project identifiers. The principle: the MFP code scheme should mirror existing accounting structures rather than introducing a parallel taxonomy.

Common Spanish SME scheme: three-digit department codes (100-999) covering all internal cost centres, with each user assigned a unique four-digit user code (1000-9999) linked to a department. For client-bill environments add a six-digit project code per active matter.

Device configuration step-by-step

Locate the account code settings

Common paths: HP Security → Account Policy, Konica Minolta Account Track Settings, Canon Department ID Management, Ricoh System Settings → Administrator Tools → User Code, Xerox Login/Permissions → Accounting, Kyocera Job Accounting Settings.

Enable account tracking mode

Set the master account tracking switch to On. Most devices require a reboot or service restart after enabling. The device now demands a valid code on every print and copy action.

Choose the code structure

Numeric codes only (most common, simplest input), alphanumeric codes (more memorable but slower to type on touchscreens), or pre-defined dropdowns (best UX but requires more setup). For typical office use, four to six digit numeric codes work well.

Define the departments first

Create department records: Marketing (code 100), Finance (200), Legal (300), Operations (400), IT (500). Set per-department print limits if the finance team has budget caps (e.g., Marketing capped at 30,000 pages monthly).

Create user records linked to departments

For each user enter a unique user code, link to a department, and optionally set per-user limits. Bulk import via CSV if the device supports it — most enterprise MFPs accept user lists in CSV format with columns user_code, name, department_code.

Configure print driver to prompt for codes

The workstation print driver needs to know the device requires codes. From the print driver properties on each workstation: Device Settings → Authentication or Accounting → enable "Use Account Codes" and configure default code or prompt-at-print behaviour.

Test with a pilot user

Have one user from one department run their normal workflow for a day. Verify their print and copy activity appears under the right code in the device's report. Fix any misconfigurations before announcing the system to all users.

Data schema the MFP captures per transaction

Record fields per print/copy/scan job

timestamp
datetime
When the job ran on the device
user_code
int
The authenticated user code
department
int
Linked from the user record
project_code
int|null
If project tracking is enabled and code entered
job_type
enum
print | copy | scan | fax
pages_mono
int
Monochrome page count
pages_color
int
Color page count
paper_size
enum
A4 | A3 | letter | other
duplex
bool
Whether the job ran duplex
finishing
enum
none | staple | hole | booklet

Sample monthly report

DepartmentMono pagesColor pagesMonthly cost
Marketing4,82023,240€1,489.40
Finance18,4002,100€312.20
Legal34,2001,800€397.50
Operations9,6504,200€344.30
IT2,1501,400€105.00

Report figures assume €0.008 mono and €0.062 color per page typical CPP. Most office MFPs generate this report automatically from the account tracking data, exportable as CSV or PDF for the monthly finance review.

Project code workflow for client-bill environments

Law firms, accounting practices, and consultancies that bill clients for print costs need project (matter) codes per job. The workflow: user authenticates, the device prompts for a project code before processing the job, the user enters the matter code, the job runs and is logged against the matter. The cost-per-page figure is then attached to client invoicing alongside billable time.

Setting this up requires the device's job-prompt feature enabled and the project code list maintained current. Most firms integrate the matter list with their practice management system via CSV export — when a new matter opens in the PMS, the next day's MFP code sync includes that matter. Closed matters disappear from the dropdown automatically.

Account code budgets and enforcement

Beyond tracking, account codes support budget enforcement. Set Marketing's monthly limit to 30,000 pages and the device refuses additional Marketing jobs once the limit hits. The user sees a message on the touchscreen explaining the limit was reached, with instructions to contact the budget owner for an increase. This catches runaway print volume before the monthly invoice surprises the finance team.

Enforcement is heavier-handed than tracking and produces more support calls. Start with tracking only and review the data for two to three months. Once consumption patterns are clear, consider whether enforcement is needed and at what threshold.

Common configuration mistakes

Three patterns recur. The first is code schemes too complex for users — six-level hierarchies with sub-codes and modifier codes feel rigorous but produce friction every time a user prints. Keep it simple: department code, user code, and optional project code. The second is forgetting to update the print driver — the device demands codes but the driver does not pass them, so every print fails with a generic error. The third is forgetting to provision new users when staff joins — they print using their colleague's borrowed code, pollute the reporting, and create no audit trail for their actual activity. Build user provisioning into the standard new-hire IT onboarding checklist.

Privacy and the GDPR consideration

Account code data is personal data under GDPR — it associates specific users with specific actions. The office's data processing register should include MFP account logs as a category of processing, with a stated purpose (cost tracking, audit), retention period (typically 12 to 24 months), and access controls (finance team and IT admin only). The data should not flow to unrelated systems without explicit purpose specification.

滚动至顶部