How to remove company & software metadata from excel before regulatory submission
- Step 1Complete the regulator's template — Fill every required cell in the regulator's
.xlsx(RegData, EDGAR schedule, EBA template). Do the wipe last so no further edits re-stamp metadata. - Step 2Review what is embedded — Right-click → Properties → Details (or File → Info). Note
Company,Manager,Author, program/version, and any draft labels in Tags/Subject. - Step 3Drop the file onto the tool — Upload one
.xlsx. ExcelJS loads it locally; the submission file is never uploaded to a server. No options to set. - Step 4Run the wipe —
company,manager,creator,lastModifiedBy,description,subject,keywords,categoryare blanked; ExcelJS writes a genericApplication/AppVersion. - Step 5Clear Title and confirm cell content — Clear
dc:titleseparately if it carries a firm/period label (Excel File → Info or office-doc-property-wiper). The tool does not redact cell data — re-check figures and any free-text cells manually. - Step 6Submit the verified clean file — Validate the cleaned
<name>-clean.xlsxopens correctly and passes the regulator's template checks, then upload it through the official portal.
Submission metadata fields and their fate
What a regulator's tooling could read from the file, before vs after.
| Field | Risk if left | After this tool |
|---|---|---|
Company | Discloses firm's registered Office name | Blanked |
Manager | Reveals internal reporting line | Blanked |
creator / lastModifiedBy | Names the preparing analyst | Blanked |
keywords / subject | Leaks 'DRAFT' / internal labels | Blanked |
AppVersion | Fingerprints exact IT build | Generic 16.0300 |
Title | May carry firm/period label | Unchanged — clear separately |
| Cell values | Out-of-template notes/figures | Unchanged — review manually |
Coverage by regulator submission type
Illustrative; always follow each regulator's own file requirements.
| Submission | Format | Property scrub fits? |
|---|---|---|
| FCA RegData return | .xlsx template | Yes — wipe before upload |
| SEC EDGAR supplemental schedule | .xlsx | Yes — wipe the supporting workbook |
| EBA ITS reporting template | .xlsx | Yes — wipe after completing the template |
| Ad-hoc data request | .xlsx | Yes — combine with cell-data review |
Tier limits for large reporting files
Big consolidated reporting workbooks may need a higher tier. Single file per run.
| Tier | Max file size | Row cap |
|---|---|---|
| Free | 5 MB | 10,000 |
| Pro (required) | 50 MB | 100,000 |
| Pro-media | 200 MB | 500,000 |
| Developer | 500 MB | unlimited |
Cookbook
Pre-submission scenarios. XML snippets show the exact change; figures stay untouched.
Firm identity removed from app.xml
Company and Manager are blanked so the submission does not disclose your organisation.
Before (docProps/app.xml): <Company>Northgate Asset Management LLP</Company> <Manager>Head of Regulatory Reporting</Manager> After (-clean.xlsx): <Company></Company> <Manager></Manager>
Analyst identity removed from core.xml
The preparing analyst's name/email is cleared from the file the regulator receives.
Before (docProps/core.xml): <dc:creator>r.patel@northgate.example</dc:creator> <cp:lastModifiedBy>compliance@northgate.example</cp:lastModifiedBy> After: <dc:creator></dc:creator> <cp:lastModifiedBy></cp:lastModifiedBy>
'DRAFT' label removed from keywords
Internal draft markers in keywords/subject are cleared so the final submission reads clean.
Before: <cp:keywords>DRAFT;Q2 RegData;not for submission</cp:keywords> <dc:subject>Internal review copy</dc:subject> After: <cp:keywords></cp:keywords> <dc:subject></dc:subject>
Version fingerprint normalised
Your exact Office build is replaced with a generic version, removing IT-environment intelligence.
Before: <AppVersion>16.0.14326.21186</AppVersion> After: <AppVersion>16.0300</AppVersion>
Documented pre-submission control
A repeatable control step you can evidence in your compliance procedures.
Control: 'Pre-submission metadata scrub' 1. Complete regulator template 2. excel-app-metadata-wiper → properties + version 3. clear Title (office-doc-property-wiper) 4. /excel-tools/excel-external-link-auditor → no links to internal data 5. manual review of cell free-text 6. validate against template & submit
Edge cases and what actually happens
Cell-level figures and notes are not redacted
PreservedThis tool only edits document properties. Out-of-scope figures, hidden columns of working, or free-text notes inside cells are preserved exactly. A pre-submission control must include a manual review of cell content — the metadata wipe does not substitute for it.
Title still carries the firm or reporting period
PreservedThe tool does not clear dc:title. A title like 'Northgate – Q2 RegData' survives. Clear it in Excel or with office-doc-property-wiper as part of the control.
Regulator template has protected/locked cells
PreservedSheet protection and locked cells are workbook structure, not properties, and are round-tripped intact. The wipe does not unlock or alter protected ranges, so the template still validates.
Submission portal validates a specific schema/version
CautionSome portals validate the file's internal structure. Because ExcelJS re-serialises the workbook, run the regulator's own template validator on the cleaned file before uploading to confirm it still passes. Do the wipe, then validate, then submit.
Created/modified dates reset to now
ExpectedExcelJS regenerates timestamps on write, so the file looks freshly created. This is not date redaction. If a submission cover note references a specific date, rely on that, not the file property.
Macro-enabled reporting template (.xlsm)
ExpectedOutput is .xlsx and macros are not reliably carried forward. If the regulator's template needs macros to function, do metadata edits in Excel instead; if macros must be removed for submission, use excel-vba-macro-stripper.
Large consolidated workbook over the tier cap
rejectedGroup-level reporting files can exceed Pro's 50 MB. ExcelJS loads the whole file into memory, so over-cap files are rejected. Use Pro-media (200 MB) or Developer (500 MB), or a desktop script.
Encrypted submission file
failsIf the workbook has an open password, ExcelJS cannot read it and the run fails. Remove the password, wipe, then re-apply protection only if the portal accepts (and expects) it.
External links to internal data sources
PreservedLinks to internal workbooks or network shares are formula content, not metadata, and survive. They can disclose infrastructure to the regulator. Audit with excel-external-link-auditor and break links before submission.
AppVersion is generic, not empty
By designThe tool does not blank AppVersion; ExcelJS writes 16.0300. Your real build is removed, satisfying the fingerprint concern, but the field is populated with a neutral value rather than absent.
Frequently asked questions
Do regulators actually inspect Excel file metadata?
Not routinely, but metadata is technically accessible to anyone who receives the file. Submitting clean files is good hygiene and avoids inadvertently disclosing your IT environment, the preparing analyst, or internal draft labels.
Will wiping metadata break the regulator's template?
No. App/core metadata is purely informational; cell formulas, data validation, protection and formatting are round-tripped intact. Still, validate the cleaned file against the regulator's own template checker before uploading, since the workbook is re-serialised.
Does this remove confidential figures from the cells?
No. The tool only edits document properties. You must manually review cell content, hidden columns and free-text notes — the wipe is not a substitute for a data review.
Is the firm's name removed?
Yes — Company and Manager in app.xml are blanked, removing the firm identity and reporting-line fields.
Is the analyst's name removed?
Yes — creator and lastModifiedBy in core.xml are blanked, so the preparer's name/email does not ship with the submission.
What happens to the software version?
Your exact build is replaced with the generic 16.0300 and Application reads Microsoft Excel, removing the IT-environment fingerprint. The field is neutral rather than empty.
Does it clear draft labels?
Yes — keywords, subject, description and category are blanked, so a 'DRAFT – not for submission' tag in those properties is removed. Check the Title and cells separately.
Should I also clear the Title?
Yes, if it names the firm or period — Title is not in scope for this tool. Clear it in Excel or with the office-doc-property-wiper.
Is the file uploaded to a server to process it?
No. ExcelJS runs in your browser; the regulatory file is processed locally and never transmitted, which matters for a controlled submission environment.
Can I process a whole reporting pack at once?
Not in this UI — one file per run. Process each workbook individually, or script ExcelJS for bulk pre-submission processing.
What output do I submit?
A binary .xlsx named <original>-clean.xlsx. Validate it against the regulator's template, then upload through the official portal.
Why is this a Pro-tier tool?
It uses ExcelJS, heavier than the lightweight tools. Pro (50 MB / 100,000 rows) covers the compute and file-size needs of real reporting files; larger consolidated packs may need Pro-media or Developer.
Privacy first
Every JAD Excel tool runs entirely in your browser using SheetJS and ExcelJS. Your spreadsheets, formulas, and data never leave your device — verified by zero outbound network requests during processing.