Skip to content
ISO/IEC 27001RazorERP is ISO/IEC 27001:2022 certified. View the certificate for your security review→
ISO/IEC 27001 certified · View the certificate →
RazorERP
AboutSupportRequest a Demo
Client reporting playbook

Give customers answers they can trace.

Clients ask the same three questions — did you receive it, what happened to it, and can you prove it. This playbook helps you plan reporting that answers them with references they recognize.

By the RazorERP team · Updated November 2026

Know who is reading

01Client ITWants proof of receipt and data destruction for specific assets.
02Procurement & financeWants settlements they can reconcile to the agreement.
03Compliance & securityWants custody history and evidence on demand.
04Your account teamWants to answer questions without searching three systems.

The questions clients ask

Receipt
Did everything arrive?
  • Was every asset on the manifest received?
  • What happened to items that were short or extra?
Status
Where is it now?
  • Has the asset been audited and sanitized?
  • When will processing finish?
Disposition
What happened to it?
  • Was it resold, harvested, or recycled?
  • Who received recycled material downstream?

Use references clients recognize

A report is only traceable if the client can match it to their own records.

  • The client’s asset tag alongside your asset ID
  • Serial number on every certificate
  • The client’s job or PO reference
  • Lot and settlement references that match the invoice

Cadence, access, and responsibility

ReportWhenAudienceOwner
Receipt confirmationWhen the receipt is closedClient ITReceiving lead
Processing statusAgreed cadence during processingClient ITAccount team
CertificatesAs assets are sanitizedClient IT, complianceAudit lead
SettlementAfter internal approvalProcurement, financeFinance
Open exceptionsUntil resolvedClient contactAccount team

An example report structure

A planning aid, not a screenshot. Switch perspective to see what each audience needs.

Disposition report · JOB-7712Planning aid · example structure
01
Header
  • Client and client reference
  • Job JOB-7712 and pickup date
  • Report period and owner
02
Receipt
  • Assets expected vs. received
  • Exceptions raised at receipt
03
Processing status
  • Audited
  • Sanitized with evidence
  • Graded
04
Disposition
  • Resale, parts, or recycling by asset
  • Downstream vendor for recycled material
05
Evidence
  • Certificate per asset
  • Custody history on request
06
Open exceptions
  • Item and reason
  • Owner and next step

Handling unresolved exceptions

  • List open exceptions on every report until closed
  • Name an owner and next step for each
  • Hold the settlement, or publish with exceptions flagged — decide which per client
  • Record how each exception was resolved

See client reporting for one job.

We will walk through what your clients would see.

Request a DemoClient portals