Extract Iron Mountain Invoices to Excel for Multi-Site AP

To extract Iron Mountain invoice to Excel, build the spreadsheet at charge-line level. Capture the invoice number, invoice date, service period, customer account, division, department, site ID, PO, charge description, quantity, unit of measure, rate, amount, tax, and every location, department, box, file, order, or matter identifier shown on the invoice and supporting reports.

That row then needs an allocation path: vendor charge line to location or department, service category, GL code, cost center, and matter or client code where the cost is recoverable. A 40-page consolidated invoice is not useful as one summary row. AP needs one row per storage, retrieval, refile, receiving and entry, transportation, shredding, tax, late fee, or adjustment line, with the invoice header repeated on each row so the data can survive pivot tables, exception review, Excel review, NetSuite, Oracle, SAP, Sage Intacct, or a law-firm billing-system import.

This matters because Iron Mountain is not a fringe vendor in enterprise AP. Iron Mountain says it is trusted by more than 240,000 customers in 61 countries, including approximately 95% of the Fortune 1000, and reported $6.9 billion in 2025 revenue, according to Iron Mountain's scale across enterprise customers. For a law firm, hospital network, bank, university, or state agency, the monthly records-management bill can cover dozens or hundreds of departments.

The accounting problem is the same even when the invoice format changes. Monthly storage may be billed in Linear Footage. Receiving and Entry may relate to boxes entering storage. Retrieval and refile lines reflect records moving out and back. Transportation may be charged by stop or delivery. Scheduled shredding and purge projects may appear beside ordinary storage charges. Each line needs enough detail to answer two questions at once: does the billed activity match the records activity, and where should the cost land in the ledger?

Use every source in the invoice package, not just the PDF

The invoice PDF is the accounting document of record. Extract its invoice number, invoice date, customer, division, department, PO number, service descriptions, quantities, rates, amounts, tax, late fee, current charges, prior balance, and total due. Those fields tie the spreadsheet back to the bill AP must approve and pay.

The supporting reports explain what sits behind the invoice. A Billing/Activity Report can add activity detail by account or department. A Detailed Transaction Report can show retrievals, refiles, and other movement at a lower level than the invoice summary. A Rate Report CSV helps validate whether the billed rate matches the contract or schedule. Iron Mountain Connect inventory or search exports can add carton, file, department, retention, or location identifiers that do not always appear in the same way on the invoice PDF.

Use portal CSVs when they contain the right level of detail. They reduce extraction work and give you cleaner source fields. Do not assume they replace the invoice package for a consolidated account, because AP still needs the invoice presentation, tax and fee treatment, period totals, and the exact line structure being approved for payment.

The internal mapping table is a separate source, not something to bury inside a notes column. It should map Iron Mountain department IDs, customer-assigned codes, sites, or box identifiers to your location, department owner, cost center, GL code, and matter or client code. Keeping vendor-native fields beside accounting-enriched fields gives reviewers a trail from the PDF to the ledger instead of a spreadsheet that only shows the final answer.

Design the Excel schema before extraction

Start with column groups. That makes the workbook easier to review than a flat dump of every field the extraction process can find.

Invoice header columns should include invoice number, invoice date, due date, service period, customer account, division, department, PO number, remittance account, prior balance, total new charges, tax, late fee, and total due. Repeat these fields on every charge line so a filtered export or accounting import still carries the invoice context.

Charge-line columns should include source page, line number, service description, normalized service category, quantity, unit of measure, rate, extended amount, tax amount, adjustment amount, and net amount. For Iron Mountain records storage, the unit column matters as much as the quantity column, because Linear Footage, boxes, route stops, pounds, containers, and one-time project charges do not reconcile the same way.

Site, department, and records columns should include vendor department ID, customer-defined code, site ID, location name, box ID, file ID, retrieval order, refile reference, destruction order, and certificate reference where present. Keep these as evidence fields. Do not overwrite them with internal cost center names.

Accounting-output columns should include location, department owner, cost center, GL code, matter, client, allocation rule, import batch, review status, exception reason, reviewer, and notes. This is where the workbook connects to multi-location accounts payable automation, because the same vendor invoice may need an AP import view, a records-audit view, and a management review view from the same extracted rows.

For a one-site account, some columns will stay blank. For a national consolidated invoice, those same columns are what prevent AP from coding a records-center charge to the wrong office just because the invoice total looked correct.

Classify Iron Mountain charges before GL coding

Do not send every Iron Mountain line to a generic records-storage account. The invoice can contain several different services that belong in different cost buckets.

Build a classification table with these columns: vendor description pattern, normalized service category, unit type, default GL or cost bucket, allocation rule, and review flag.

Vendor description pattern	Normalized category	Unit type	Default cost bucket	Allocation rule	Review flag
Storage, Linear Footage, open shelf, vault	Storage	Linear Footage, carton, file	Records storage	Department or site mapping	Flag unexpected month-over-month movement
Receiving and Entry, intake, new carton	Intake	Box, carton, file	Records intake	Department receiving the records	Flag missing department or site
Retrieval, pull, file-out	Retrieval	Box, file, request	Records movement	Requesting department or matter	Flag unmatched request
Refile, re-shelving, file-in	Refile	Box, file, request	Records movement	Original retrieval owner	Flag refile with no related retrieval
Transportation, delivery, pickup, route stop	Transportation	Stop, delivery, mile	Records logistics	Site served by the route	Flag duplicate stop
Supplies, cartons, labels, materials	Supplies	Each, carton, pack	Records supplies	Ordering department	Flag unusual quantity
Scheduled shredding	Recurring shredding	Pickup, container, pound	Recurring destruction	Service location or department	Flag missing service location
Purge, project shred, one-time destruction	Project shredding	Box, container, project	Project destruction	Approved project, department, or matter	Flag missing approval reference
Tax	Tax	Amount	Tax	Follow taxable base line	Flag tax-only line
Late fee, finance charge	Late fee	Amount	Finance charge	Central AP or responsible owner	Flag for approval before import
Credit, adjustment, prior-period correction	Adjustment	Amount	Adjustment	Original charge owner where known	Flag all negative or prior-period lines
Data-center, colocation	Data-center services	Rack, space, service	IT or facilities	IT owner or site	Flag if outside records contract
ITAD, asset disposition	IT asset disposition	Asset, project, weight	IT asset disposition	IT owner or project	Flag if mixed with records storage

Storage lines usually use Linear Footage, carton, file, vault, or open-shelf language. Receiving and Entry belongs to intake. Retrieval and refile belong to records movement. Transportation belongs to route, delivery, pickup, or stop charges. Supplies belong to boxes, cartons, labels, or materials. Scheduled shredding, project shredding, taxes, late fees, adjustments, data-center services, and IT asset disposition should each keep their own category where they appear.

That table becomes the bridge between extraction and invoice GL coding. It lets AP assign a default code quickly while still flagging exceptions that need human review.

Scheduled shredding and one-off purge projects deserve special treatment. A recurring console pickup may belong to an ordinary departmental operating cost. A purge project, such as clearing 200 boxes after a retention review, may belong to a project code, legal matter, office move, or records-cleanup initiative. If both are collapsed into "shredding," the ledger loses the business reason for the charge.

Flag lines that are ambiguous, negative, duplicated, or prior-period. Also flag rate changes, duplicate route stops, charges with no site or department, and descriptions that do not match the classification table. A clean Iron Mountain invoice spreadsheet is not one with no exceptions. It is one where exceptions are visible before the import.

---

Reconcile Linear Footage, containers, retrievals, and shredding

Linear Footage is a records-storage billing unit, not a nuisance field to convert away. It represents occupied shelf space, so open-shelf storage, file-level activity, half-boxes, vault storage, and box-equivalent assumptions can all affect how the billed quantity relates to a simple carton count.

Preserve quantity, unit of measure, rate, service period, activity type, and department on separate columns. If the invoice says Storage - LF, the workbook should not turn that into a generic box count unless the records team has a documented conversion rule. The safer review is to trend Linear Footage by department or site over time, then compare the movement to intake, destruction, and transfer activity.

For storage reconciliation, look for departments whose Linear Footage rises without Receiving and Entry activity, boxes or files still billed after a destruction order, and departments with storage charges but no current owner in the mapping table. A box-level billing audit should also identify billed records that do not appear in the internal inventory and inventory records that appear active but have no current storage charge.

For retrieval and refile lines, keep the retrieval order, request date, box or file ID, requesting department, delivery location, and refile date where the source package provides them. The point is not only to verify the amount. It is to show whether the billed movement matches a real request and whether the refile charge relates to the same record that was pulled.

For shredding, split scheduled service from purge work before review. Scheduled pickup lines can be checked against route frequency, containers, or service location. Purge projects should be checked against destruction orders, certificates, department ownership, box or container counts, and the cost bucket approved for the project. Sites that also receive console pickups or medical-waste service from a dedicated destruction vendor can apply the same row model to Shred-it and Stericycle consolidated invoice extraction, keeping per-console, per-stop, and surcharge lines distinct from Iron Mountain records charges.

Allocate the same invoice differently for law firms, healthcare, and finance

A law firm may need the Iron Mountain department code, office, practice group, client, matter, and chargeback status on the same row. The vendor department code is not the same thing as a client-matter code, even when a records box was created for a specific matter. Keep both fields, then let the mapping table decide whether the charge is billable, non-billable, office overhead, or subject to review. That discipline fits the broader control needs in law firm accounts payable workflows.

Healthcare finance teams usually care less about matter billing and more about facility, department, retention category, destruction hold, and request history. The invoice spreadsheet should help the records manager see whether billed storage and activity make sense against the inventory, without turning an AP article into a clinical records compliance guide. The useful AP output is still location, department, GL code, cost center, exception status, and support for approval.

Financial-services teams often process consolidated records bills for branches, corporate departments, lending operations, wealth teams, or compliance archives. The same charge-line model lets finance split central billing across branch, department, and cost-center owners while preserving enough records detail for the RIM team to review retention and destruction activity.

The lookup table is the control point: vendor department ID to location, department owner, GL code, cost center, client, matter, exception owner, and effective date. The final workbook can then produce several views from the same rows: AP import, records audit, matter chargeback, and management review. That is the same reason professional services invoice processing needs line-level detail rather than a total-by-vendor export.

---

Use AI extraction where portal exports stop

Use Iron Mountain Connect exports when they give you clean CSV detail. They are source data, not competition for the workbook. The gap usually appears when AP has a mixed package: invoice PDFs, scanned pages, Billing/Activity Reports, Detailed Transaction Reports, rate exports, inventory exports, and an internal allocation table that needs to be joined to the vendor data.

That is where Invoice Data Extraction fits the workflow. The product converts invoices and financial documents into structured Excel, CSV, or JSON files. Users upload documents, describe what to extract in a natural language prompt, and download the structured output. For an Iron Mountain package, the prompt can ask for one row per charge line, repeated invoice header fields, preserved vendor department and box/file fields, normalized service category, allocation columns from the mapping table, and review flags for missing site IDs or ambiguous descriptions.

A practical prompt should name the row model rather than asking for a generic invoice export. Tell the system to keep vendor fields separate from accounting fields; classify storage, receiving and entry, retrieval, refile, transportation, supplies, shredding, tax, late fee, and adjustment lines; preserve quantity, unit of measure, rate, service period, and source page; and export the result to Excel or CSV. That is the difference between invoice-to-Excel extraction for AP teams and a spreadsheet that only captures invoice totals.

For monthly Iron Mountain processing, save the prompt and reuse it against the next invoice/report package. The SaaS spec supports saved prompts, mixed-format uploads including PDF, JPG, and PNG, and output as Excel, CSV, or JSON. The repeatability comes from a clear extraction instruction and a consistent allocation table, not from pretending that every portal export already contains every accounting field AP needs.

Put review controls around the monthly process

Treat the Iron Mountain spreadsheet as a monthly close control, not a one-time conversion. Collect the source package first: invoice PDF, supporting reports, portal CSVs, current mapping table, and any request or destruction logs the records team uses for review. Extract charge-line rows from the invoice and reports, then join the mapping table only after the raw vendor fields are visible.

Run the workbook through the same sequence each month: classify service categories, assign default GL codes, allocate by location and cost center, reconcile storage and activity, review exceptions, approve allocations, and import. A stable sequence makes month-over-month differences easier to spot, especially when Linear Footage changes, a department code disappears, a purge project appears, or transportation charges rise for one site.

Exceptions should have named reasons. Use separate flags for missing site ID, unmapped department, consolidated account, one-off purge project, rate change, duplicate charge, prior-period adjustment, tax-only line, late fee, and manual review. That lets AP decide whether a line is ready for import, needs records-manager review, or should be disputed before payment.

Archive the evidence with the approved workbook: source PDFs, portal CSVs, extracted Excel or CSV, mapping table version, exception notes, reviewer name, approval date, and import batch. Six months later, the team should be able to explain not only what Iron Mountain charged, but how each charge moved from the invoice package to the ledger.