Extract Shred-it and Stericycle Invoices to Excel for AP

To extract a Shred-it invoice to Excel for multi-location AP, parse the consolidated PDF into one row per service event, with columns for location ID, service date, service category, container type, quantity or weight, and amount. Service categories run through the document-destruction side — scheduled-pickup base service, per-console and per-bin fees, on-call pickups and one-time purges, equipment rental, and environmental, fuel, and recycling recovery surcharges — plus, on Stericycle medical-waste invoices, the regulated medical waste, sharps, pharmaceutical waste, and weight-based lines that ride alongside. That single row shape supports per-location cost allocation, GL coding by service type, and certificate-of-destruction reconciliation in one extraction pass.

Stericycle and Shred-it are the same operational entity from the customer's invoicing perspective. After the merger that consolidated the two brands, customers commonly see both logos on a single statement, with document-shredding charges and regulated-medical-waste lines coexisting on one bill for healthcare networks. Two readers handle that monthly PDF for different reasons. The AP clerk processes the consolidated bill for a multi-site enterprise — a 30-office law firm, a 50-clinic healthcare network, a 200-store retail chain, a 500-branch financial services firm — and needs the data in a shape that lands cleanly in NetSuite, Sage Intacct, Oracle, SAP, or QuickBooks at line-item granularity. The compliance officer reads the same invoice quarterly to verify each scheduled pickup actually happened, that a certificate of destruction was issued, and that the chain of custody holds up to a FACTA, HIPAA, or state-records-destruction audit. Both readers are served by the same extraction shape; the only thing that changes is which filters and joins they apply downstream.

What's Actually on the Invoice: Line-Item Taxonomy for Shred-it and Stericycle

Before extraction logic makes sense, the line-item categories have to be named. A Shred-it / Stericycle consolidated invoice carries a stable taxonomy across National Accounts Program customers, even when the per-line wording varies between accounts. The categories below are what you should expect to see, in roughly the order they appear on a typical statement.

Document-destruction lines. The recurring shape on the shredding side runs through these categories:

• Scheduled-pickup base service. When the truck arrives at a location on its contracted route, the invoice fires a per-stop charge for the visit and a per-console or per-bin fee for each container actually serviced. The per-stop line is the route-arrival meter; the per-container line is the volume meter. On smaller accounts the two are sometimes combined; on National Accounts Program billing they are typically broken out so per-location detail is preserved.
• Per-container types. Containers carry different per-container rates depending on what was on site. The standard categories are the executive console (the locked office unit, usually placed near a copier or in a partner's office), the executive console with lock where the lock is metered separately, the security cart (the larger wheeled unit common in records rooms and back-of-house areas), and the mobile bin or shred bin (the toter-style container common in higher-volume accounts). The container category typically appears on the line label or in a service-detail column, and it carries to the spreadsheet because per-container density is part of what makes per-location cost reports useful.
• On-call pickups and one-time purges. Anything outside the contracted schedule lands here. An on-call pickup is an ad-hoc service request — the office filled a console early, a partner closed a matter, a clinic completed a quarterly purge. A one-time purge is the larger end of the same category, typically billed at a separate rate per box, per pound, or per truckload. Both should be visibly different categories from scheduled pickups in the extracted output.
• Equipment rental. Monthly rental on the consoles or bins themselves, often with a separate lock fee, billed every period regardless of whether a pickup happened. This is the steady-state line that fires even on quiet months.
• Environmental fee. A percentage-based surcharge applied to invoiced services. Shred-it's own customer documentation is the canonical source for the current formula; the percentage and the calculation base are the kind of detail vendor pages revise from time to time, so the extracted spreadsheet should carry the dollar amount as billed and reference the vendor page for the live formula rather than freezing a number in a comment.
• Fuel surcharge. A separate route-cost recovery line, typically formula-based against published fuel index rates. Like the environmental fee, it appears on most invoices regardless of pickup volume in the period.
• Recycling recovery surcharge. Where present on an account, this is a downstream-cost recovery on the destroyed material. Not every account sees this line, and the wording varies; the category fits alongside the environmental and fuel surcharges in the extracted output.

Stericycle medical-waste lines. On healthcare-network accounts and other regulated-waste generators, the same statement carries the regulated-waste side. The categories worth naming as distinct rows:

• Regulated medical waste (RMW) pickup. The per-pickup or per-container line that meters scheduled medical-waste collection at a generator location. This is the medical-waste analogue of the document-destruction scheduled-pickup line — recurring, route-based, and tied to a service date.
• Sharps containers. A separate line for scheduled sharps-container exchange, usually per container exchanged.
• Red bag waste. Where biohazard waste is metered as a distinct stream from general RMW, it appears on its own line, sometimes weight-based and sometimes per container.
• Pharmaceutical waste and chemotherapy waste. Regulated-stream-specific lines at typically higher per-pound rates than general RMW. These are the lines that drive the per-pound math on a hospital invoice.
• Weight-based or per-pound charges. Variable charges tied to the actual weight collected on the manifest. The manifested weight is the join key for compliance reconciliation on the medical-waste side.
• Manifest, transport, and treatment. The regulated-waste paperwork-and-disposal lines that ride alongside the pickup itself — uniform manifest filing, transport to the treatment facility, and the treatment cost itself, sometimes broken out and sometimes consolidated.

These categories survive consolidation. Even when a healthcare customer sees both the Shred-it and Stericycle logos on a single statement, the document-destruction lines and the regulated-medical-waste lines remain visually distinguishable on the invoice, and they need to land in different GL accounts downstream. Splitting the two streams in extraction is what makes the rest of the workflow possible.

ProShred and other regional document-destruction vendors invoice in a closely related taxonomy — per-stop, per-container, surcharge layer — so the extraction shape developed in this article generalizes to those vendors with vendor-specific naming variations the only material difference. Customers running parallel regional contracts alongside a Shred-it national account can use one schema across both.

Why Route-Based Billing Extracts Differently from Records-Storage Billing

Many of the same AP teams that handle a Shred-it / Stericycle invoice also handle an Iron Mountain invoice, often on the same desk in the same week. The two bills look broadly similar — multi-location, recurring, surcharge-laden — but the meter underneath is fundamentally different, and treating them the same way in extraction leaves data that doesn't roll up cleanly.

Shred-it is route-based. The truck arrives at each location on a schedule, services the consoles or bins it finds, and leaves. Every billable line on the invoice meters an event at a point in time: a stop, a container serviced, a pickup completed, a purge collected. That is why the line-item taxonomy from the prior section is dominated by per-stop, per-container, and per-event charges — the invoice is recording route activity, location by location and date by date.

Records-storage billing runs on a different model. The underlying meter is inventory: cubic feet or linear feet of stored records held at the vendor's facility, billed monthly on the inventory present in that period, with per-event activity charges (retrievals, refiles, destructions, file searches) layered on top. The recurring base is what is sitting on the shelf, not what happened on a route. Iron Mountain's storage-anchored invoice extraction workflow walks the same logic from the storage side.

The operational consequence is concrete. A route-based invoice extracts cleanly to one row per service event, tagged with a service date and a location. A storage invoice extracts to a recurring inventory row per location per period, plus per-activity rows for every retrieval and destruction. The two shapes do not merge into a single schema without forcing one of them into a structure that doesn't fit, so an AP clerk handling both vendors should keep them as separate extracts that consolidate at the GL-coding stage — same chart of accounts, same cost-centre mapping, two source schemas joining at the location level rather than at the row level.

This article focuses on the route-based side. Customers also processing storage invoices should run the parallel workflow described in the storage-side companion article and bring the two outputs together at the cost-centre summary, not at the line level.

The route-based shape generalizes well beyond Shred-it. Cintas uniform routes, multi-site janitorial contracts, multi-site pest control, and managed print services share the same per-stop and per-event billing structure, with the same per-location density questions and the same surcharge layers. The row shape introduced later in this article carries across those vendor categories with little adjustment; an AP team that already has the Shred-it extraction running can apply it to Cintas uniform invoice extraction for multi-location AP and to other route-based service contracts without rebuilding the schema for each vendor.

Where MyShred-it and MyStericycle Portal Exports Help, and Where They Don't

Most AP clerks reading this already log into MyShred-it or MyStericycle every month, and a fair share have already pulled an invoice export — for some accounts as a PDF, for others as a PDF plus an Excel file. Before the article goes further, it is worth being honest about what the customer portals deliver and where they leave gaps. The workflow below picks up exactly where the portal leaves off; what that means depends on which export the account receives.

The portals do real work. MyShred-it and MyStericycle offer multi-account drop-down navigation across National Accounts Program customers, per-account invoice download, statement history, scheduled-service visibility, and certificate-of-destruction download per pickup on the document-destruction side. For consolidated National Accounts Program billing, Shred-it's documented invoice format options include PDF only or PDF plus Excel, which means a subset of customers receive a structured Excel file alongside the PDF without doing any extraction work themselves. For those accounts, a portion of the work is already done.

The gap shows up at the point the export hits the accounting system. The portal Excel arrives in the vendor's reporting shape, not the customer's accounting shape, and the differences are predictable enough to name:

• No cost-centre or GL-account mapping. The portal export carries the location ID and the line-item label. It does not carry the customer's internal cost centre, the chart-of-accounts code, the partner-matter reference, or anything else that is specific to how the customer's books are organized. That mapping is always added downstream.
• Service-category split is absent or inconsistent. Scheduled and on-call charges may share a category column, equipment rental may be mixed with per-stop service in the same column, and environmental and fuel surcharges are often applied at the invoice level rather than allocated to the locations that triggered them. Splitting these into the GL-routing categories from the prior section is part of the reshape work.
• Per-location reshape is missing for cost reporting. The export is invoice-shaped — one row per line item as it appears on the invoice — rather than location-shaped, where each row represents a service event at a specific location with category, container detail, and amount. Per-location rollups still require a transform, even when the underlying data is already in Excel.
• Multi-vendor consolidation is not possible inside the portal. The same AP team often handles ProShred regional contracts, Iron Mountain storage, Cintas routes, and other multi-site service vendors. The MyShred-it portal cannot reach those, so any consolidated multi-vendor view of records-management spend is built outside the portal.
• PDF-only accounts still exist. For accounts that don't qualify for or haven't migrated to the National Accounts Program consolidated format, the portal output may still be PDF-only. Smaller-volume customers and newer accounts are the most common place this shows up.

The workflow from here starts wherever the reader's portal export ends. Customers with a PDF-only output extract from the PDF directly into the row shape the next section specifies. Customers with portal Excel use it as the input and reshape from there — same destination, less work to get there.

The Per-Location Row Shape That Drives Cost Allocation and Compliance Reconciliation

Every decision in the rest of this article hinges on a single output shape: one row per service event, with the columns that let the row be coded, allocated, and reconciled in one pass. Specifying the columns directly is more useful than describing them in the abstract, so here is what each column carries.

• Location ID or customer ID. The per-site identifier the invoice itself uses. Shred-it carries a location ID per service address; Stericycle uses a generator ID for medical-waste accounts, and the two identifiers may both appear on a consolidated statement for a healthcare customer. This column is the join key for everything downstream — cost centre mapping, per-location rollup, certificate-of-destruction reconciliation, multi-vendor consolidation. If a row does not have a location ID, it should not leave the extraction stage.
• Service date. The date the truck arrived and the event was billable. For lines that don't tie to a single date — equipment rental, environmental fee, fuel surcharge — the invoice period covers it, with a period-start or period-end date in the column.
• Service category. The line's GL-routing key. The values are the categories from the prior taxonomy: scheduled pickup, on-call pickup, one-time purge, equipment rental, environmental fee, fuel surcharge, recycling recovery surcharge, and on the medical-waste side RMW pickup, sharps, red bag waste, pharmaceutical waste, weight-based, manifest, transport, treatment. A row with an ambiguous category is a row that will be coded inconsistently downstream, so the extraction should resolve it.
• Container type. Where the line is per-container, the container category — executive console, locked console, security cart, mobile bin. Empty for lines that aren't per-container. This column is what makes per-location container-density reporting possible.
• Quantity or weight. Where the meter is a count or pounds — number of containers serviced, manifested weight on a regulated-waste line — the value the line was billed against. Empty where the line is a flat charge.
• Amount. The line total in dollars.
• Source page or reference. A pointer back to the page of the consolidated PDF the line came from. This column is what makes the extraction defensible in audit; any row in the output spreadsheet can be traced back to its source document in seconds.

Two rows worth distinguishing explicitly are the scheduled pickup row and the on-call pickup row, because the difference matters for both GL coding and compliance reconciliation. A scheduled pickup is recurring service tied to the contracted route schedule — Tuesday every other week at the Chicago office, the second Thursday of every month at the Phoenix clinic. An on-call pickup is an ad-hoc request outside that schedule, typically at a different rate and often coded to a different GL account. Both extract as rows in the same schema; they are distinguished only by the service-category column. Keeping that distinction visible at the row level is what lets the recurring run-rate stay clean and the ad-hoc spend remain visible.

This is also the shape worth standardizing because of what it enables in one extraction. Per-location rollup is a group-by on location ID. GL coding is a group-by on service category mapped through the chart of accounts. Per-pickup matching to the certificate-of-destruction log is a filter to scheduled-pickup or on-call-pickup categories with a service date and location ID, then a join. Multi-vendor consolidation is the same shape with vendor as one more column, so a Shred-it extract and a ProShred extract for the same period sit in one schedule for cost reporting. One extract, four downstream uses — that is the practical reason to set the schema this way.

For customers receiving the Shred-it portal Excel, the work in this section is reshape rather than extract. Adding location ID where it is not present on every line, splitting categories where the portal lumps them, and leaving cost-centre blank for the join stage are the typical moves. The destination is the same.

For customers without portal Excel, the work is one prompt-and-upload pass against the consolidated PDF. A natural-language prompt that names the columns above and the category split is enough to drive an AI extraction tool through a multi-page batch — Invoice Data Extraction's interaction model is a single prompt field with a file upload area, the same shape as a chat tool, with no templates to configure or rules engine to set up; the output is Excel in the row shape specified, typically within minutes for a multi-location consolidated batch. The permanent free tier covers up to fifty pages a month, which is enough for an AP team to test the workflow on a real invoice before deciding whether to run the recurring monthly extraction this way. If the article is a useful description of the workflow you actually run, you can automate Shred-it and Stericycle invoice extraction from the same row shape this section has specified.

GL Coding, Cost-Centre Allocation, and Multi-Office Chargeback

The row shape lands one decision short of accounting-system-ready: which GL account each row routes to, and which cost centre carries it. Both decisions follow patterns that vary by customer profile but stay stable enough across the AP teams running this workflow that they are worth naming as policy patterns.

GL routing by service category. The service-category column is the routing key. The typical splits, framed as patterns rather than prescriptions:

• Scheduled pickup routes to a standard recurring-service expense account, typically the records-management or document-destruction account. This is the recurring run-rate of the contract and stays consistent month to month.
• On-call pickup and one-time purge route separately, usually to an ad-hoc service or project expense account. Keeping these out of the recurring account preserves the run-rate for budgeting and forecasting; mixing them blurs the picture and surfaces variance that isn't actually variance.
• Equipment rental routes to a rental expense account, sometimes tracked separately for fixed-asset reporting purposes. Lock fees usually ride with the rental rather than getting their own account.
• Environmental fee, fuel surcharge, and recycling recovery surcharge route either rolled with the underlying service line — each surcharge attributed to the location it relates to — or held centrally in a single surcharge account by policy. The first approach produces more accurate location-level cost reports; the second is operationally simpler. Either is defensible if applied consistently.
• Regulated medical waste pickup, sharps, pharmaceutical waste, weight-based, manifest, transport, and treatment route to a separate expense account from document destruction. For mixed Stericycle invoices, the GL split between document-destruction lines and regulated-waste lines is the most consequential coding decision on the bill — these are different services governed by different regulatory regimes, and they need to land in different accounts even when the customer happens to receive both on one statement.

Cost-centre allocation by reader profile. The same row shape allocates differently across the multi-site customer profiles that read this article:

• Multi-office law firms allocate per office cost centre, with partner-matter chargeback layered on top where shredding is tied to a closed file. Records destruction at the end of a matter may be billable to the matter rather than the firm's overhead, and the on-call and one-time purge lines are where that chargeback most often shows up.
• Healthcare networks allocate per facility cost centre, with document-destruction and regulated-medical-waste lines routing to different expense accounts within the same facility cost centre. The split is upstream of the cost centre, not parallel to it.
• Retail chains and QSR HQs allocate per store cost centre. Whether environmental and fuel surcharges are pushed down to the store or held centrally is a policy call; pushing them down gives store managers visible costs they can manage, holding them centrally simplifies the close.
• Financial services networks allocate per branch cost centre, often with a centralized records-destruction account at HQ for compliance-driven destruction events that are not tied to a single branch — periodic purges of corporate records, regulatory-driven retention cleanups.
• Property management firms allocate per building or per tenant cost centre where shredding is part of a tenant service offering and chargeback is required. The location ID on the invoice maps to the building, and the tenant allocation rides on top through the cost-centre table.

The location ID join is the mechanism that makes any of this work at scale. The extracted row carries the location ID; the customer's chart-of-accounts mapping table converts location ID to cost centre and to the GL account where the surcharge policy applies. Keeping that mapping in a separate sheet rather than hard-coded in the extraction prompt is what makes it sustainable when locations open, close, rebrand, or reorganize between cost centres. The extraction stays the same; only the mapping table changes.

One thing AP teams routinely get wrong on these invoices is worth naming directly: applying the environmental fee or fuel surcharge as a single invoice-level adjustment rather than allocating it to the per-location services that triggered it. The all-in environmental fee on a 200-store retail chain's monthly statement might run several thousand dollars; held centrally, it disappears into a single line that no store manager sees. Allocated proportionally to each store's pickup activity, it becomes part of each store's actual cost of records destruction, which is the number that belongs in the per-store P&L. The same row shape supports either approach; the difference is whether the surcharge rows carry a location ID at extraction time or get assigned one through proportional allocation downstream.

For AP teams that handle these invoices alongside other multi-site service contracts, the same row shape is what makes centralised AP across multi-location and franchise businesses possible without a separate schema for each vendor. One extraction shape, one cost-centre mapping table, multiple vendors feeding into the same close.

Reconciling the Invoice to Certificate-of-Destruction Logs for Compliance

The compliance reader works the same invoice for a different question. The AP question is whether the bill codes correctly; the compliance question is whether the events the bill describes actually happened. Each scheduled pickup on the invoice should correspond to a certificate of destruction (COD) downloadable from MyShred-it, and on the regulated-medical-waste side to a manifest from MyStericycle. The chain of custody is only complete when every billed pickup has a matching COD or manifest with consistent date, location, and (where applicable) weight or container count.

The industry benchmark for vendor-side chain-of-custody is NAID AAA Certification, the standard that frames what a defensible destruction service looks like. i-SIGMA's NAID AAA Certification standard verifies secure data destruction companies' services' compliance with all known data protection laws through scheduled and unannounced audits by trained, accredited security professionals, fulfilling customers' regulatory due diligence obligations. That standard governs what the certified vendor is doing on its side of the contract. The reconciliation described below is the customer-side parallel: verifying that the certified vendor actually performed the contracted destruction events at the customer's locations, and that the documentation is in place when an auditor asks.

The reconciliation itself is a filtered join, not a complicated workflow. The steps:

• Pull the extracted invoice rows filtered to scheduled-pickup and on-call-pickup categories. These are the rows that should produce a COD; equipment rental and surcharge rows do not, so they drop out at this stage.
• Pull the COD log from the MyShred-it portal for the same invoice period. For healthcare customers with regulated-waste lines, also pull the manifest log from MyStericycle for the same period.
• Join on location ID and service date. Allow a small date tolerance — typically a day or two — because the billed date and the COD date can differ slightly on route-end pickups where the truck completes its run after midnight or where the COD is generated at the next-day office open.
• Surface unmatched rows in three buckets. Billed pickups with no matching COD go to an investigation queue — these are the rows that need the most attention. CODs with no matching invoice line go to a vendor reporting check; this often points to billing-cycle timing rather than a real problem, but it is worth confirming. Date or location mismatches go to a data-quality cleanup queue, where the resolution is usually updating a location ID after a relocation or fixing a typo on the COD side.
• For regulated medical waste, repeat the join against the manifest log. Add a column for manifested weight where weight-based charges apply, and confirm the billed weight reconciles to the manifested weight within the tolerance the contract specifies.

Unmatched rows almost never indicate a destruction event that simply didn't happen. The common causes are missed pickup events that were rescheduled but not noted on the invoice cycle, route-truck data-entry errors at the vendor's dispatch end, location ID drift after a relocation or a rebrand that the vendor's system caught up with on a different cycle than the customer's system, and mid-period schedule changes where the contract changed but the invoice cycle didn't catch up. Investigation rarely turns up dramatic findings. What investigation does produce is a clean, documented reconciliation — and that documentation is what satisfies a HIPAA audit, a FACTA disposal-rule audit, or a state-records-destruction audit when one comes.

This kind of reconciliation tends to get skipped when an AP team has no extraction to drive it from. Without rows tagged by location ID, service date, and category, the join is a manual task across PDFs and portals, and quarterly reconciliation becomes the project that always slips. With the row shape from the prior sections in place, the compliance reconciliation collapses to a filter and a join on top of work that has already happened — the same extraction that produced the AP run produces the compliance evidence.

For healthcare AP teams handling both shredding and regulated-waste streams from the same vendor, the same reconciliation pattern applies more broadly to GPO-contracted vendor relationships, where contracted pricing and contracted service performance are reconciled against invoiced events. The mechanics of GPO contract-pricing reconciliation for hospital AP teams are different in subject — pricing tier compliance rather than destruction-event verification — but the underlying logic is the same: extract the invoice into rows, join the rows to the contractual evidence, and surface the mismatches.