A quarter-end audit runs on one workbook. The auditor has it. The CFO wants to see it. The analyst is mid-revision. Historically, this means three copies of the same file, two angry emails, and a twenty-minute call to figure out which version the board saw.
The fix isn't a better email convention. It's opening the spreadsheet in the app, together.
Excel in the route, not in an export
Files opens Word, Excel, and PowerPoint in place — inside the route you already have. Versioning, locking, and live presence are built in. Two people editing the same workbook see each other's changes; nobody overwrites the tab somebody else is working on.
<wy-files uid="audit-<%= audit.id %>"></wy-files>One app per audit, one component on the review route. The auditor opens it, edits, saves. The CFO opens the same uid on their side, sees the latest version with full history, leaves a comment on the row that's off. No emailed attachments, no "which version."
Version history is a first-class tab
Every save is a version. Roll back to last week's draft, compare cell-by-cell, attribute the change to the user who made it. Audit season ends and the paper trail is already there.
Cloud sources when the source isn't yours
External auditors work in their own Google Drive or OneDrive. Files mounts the cloud providers — Google Drive, OneDrive, Dropbox, S3 — so the workbook shows up inline without a download-and-reupload ritual. Permissions carry through; nothing gets duplicated into your storage without you wanting it to.
What you don't have to build
- In-app Office editing with presence, locking, and version history.
- A file-synchronization layer to the cloud storage providers your customers actually use.
- The "who changed what, when" audit trail your compliance team needs on day one.
The financial portal stops being a dashboard that links out to documents and starts being where the documents actually live.