Workday enforces a fixed 30 MB (30,720 KB) maximum file size on transactional attachments (10,240 KB for standard tenant images), permanently blocks 16 executable and script extensions (exe, bat, js, vbs, lnk, and related types) alongside any tenant-specific allowlist configured in Edit Tenant Setup - System, and does not run Workday’s built-in virus scanner on files uploaded via REST or SOAP web services. Any external form, mobile app, or chat workflow that uploads expense receipts or medical leave certificates into Workday must therefore run malware scanning and MIME/size checks before forwarding the file, and bind sensitive attachments to segmented Document Categories so front-line supervisors cannot open clinical records.
Uploading files into Workday fails silently or leaks sensitive documents when developers treat an attachment endpoint like a generic S3 bucket. Below are the exact payload contracts, tenant setup gates, virus-scanning rules, and security domains governing attachments across Leave of Absence, Expense, and Worker Documents.
Workday Attachment Limits, File Types, and Scanning Rules at a Glance
Check these tenant-wide boundaries before writing upload code or sizing reverse-proxy body limits:
| Boundary | Workday Rule / Limit | Controlling Task or Documentation |
|---|---|---|
| BoundaryMax Attachment Size | Workday Rule / Limit30 MB (30,720 KB) per file across UI, REST, and SOAP (non-configurable) |
Controlling Task or DocumentationEdit Tenant Setup - System (Maximum Attachment Size (KB)) |
| BoundaryMax Image Size | Workday Rule / Limit10 MB (10,240 KB) in tenant setup (30 MB max on WWS image operations) |
Controlling Task or DocumentationEdit Tenant Setup - System (Maximum Image Size (KB)) |
| BoundaryTotal Tenant Document Storage | Workday Rule / Limit10 TiB (10,240 GB) across resumes, receipts, worker docs, and reports |
Controlling Task or DocumentationPlatform Consumption Console (Consumption Usage tab) |
| BoundaryPermanently Blocked Extensions | Workday Rule / Limitbas, bat, com, exe, js, lnk, ocx, reg, sct, sys, vb, vbe, vbs, wsc, wsf, wsh |
Controlling Task or DocumentationEdit Tenant Setup - System (File Type Setup Instructions) |
| BoundaryTenant Allowlist Mode | Workday Rule / LimitAllow All File Types (default) vs. Allow ONLY Specific File Types (e.g., pdf, jpg, png, docx) |
Controlling Task or DocumentationEdit Tenant Setup - System (File Type Setup Instructions) |
| BoundaryPassword-Protected / Corrupted PDFs | Workday Rule / LimitRejected when rendering/printing Business Forms; avoid encrypted PDFs | Controlling Task or DocumentationDocument & Printing Limits |
| BoundaryBuilt-In Virus Scanning | Workday Rule / LimitScans UI uploads (Add Worker Document, Create Expense Report, career sites); skips web services & integrations |
Controlling Task or DocumentationWorkday Virus Scanning Limitations |
BoundarySOAP File_Name & Content_Type Length |
Workday Rule / LimitFile_Name max 255 chars (single line); Content_Type max 80 chars |
Controlling Task or DocumentationBusiness_Process_Attachment_DataType XSD |
Two REST Multipart Patterns vs. SOAP Base64 Attachments
Workday exposes three distinct wire formats depending on whether you attach a file to an existing REST resource, create a new REST object with inline attachments, or submit a Business Process via SOAP.
Pattern 1: REST Sub-Resource Upload (attachmentContent on Existing Objects)
Services such as Expense (POST /expense/v1/{tenant}/entries/{ID}/attachments), Procurement (POST /procurement/v3/{tenant}/requisitions/{ID}/attachments), Accounts Payable (POST /supplierInvoiceRequests/{ID}/attachments), and Recruiting (POST /prospects/{ID}/resumeAttachments) accept multipart/form-data with a single form field named attachmentContent:
POST /api/expense/v1/tenant_dpt1/entries/4d718d459cce01000c6fb285efa20000/attachments HTTP/1.1
Host: wd5-services1.workday.com
Authorization: Bearer <employee_oauth_access_grant>
Content-Type: multipart/form-data; boundary=----WorkdayUploadBoundary
------WorkdayUploadBoundary
Content-Disposition: form-data; name="attachmentContent"; filename="parking-receipt-nov14.pdf"
Content-Type: application/pdf
<raw_pdf_bytes>
------WorkdayUploadBoundary--Workday responds with the created attachment WID, resolved MIME contentType descriptor (for example, application/pdf), byte fileLength, and fileName.
Pattern 2: REST Composite Create (jsonData + cid: File Parts)
When creating a parent object and its attachments in one atomic call—such as POST /request/v1/{tenant}/requests or POST /staffing/v6/{tenant}/workers/{ID}/checkInTopics—send multipart/form-data combining a jsonData part and one or more binary file parts referenced via Content-ID (cid:file1, cid:file2):
POST /api/request/v1/tenant_dpt1/requests HTTP/1.1
Host: wd5-services1.workday.com
Authorization: Bearer <employee_oauth_access_grant>
Content-Type: multipart/form-data; boundary=----WorkdayCompositeBoundary
------WorkdayCompositeBoundary
Content-Disposition: form-data; name="file1"; filename="medical-clearance.pdf"
Content-Type: application/pdf
<raw_pdf_bytes>
------WorkdayCompositeBoundary
Content-Disposition: form-data; name="jsonData"
Content-Type: application/json
{
"description": "Ergonomic accommodation request",
"requestType": { "id": "8aae3f174909012f50f2ff5e505f5a09" },
"questionnaireResponses": {
"questionnaireAnswers": [
{
"questionItem": { "id": "8aae3f174909011301757039505f4d09" },
"questionnaireAttachments": [
{ "file": "cid:file1" }
]
}
]
}
}
------WorkdayCompositeBoundary--Pattern 3: SOAP Business Process Attachments (Request_Leave_of_Absence & Maintain_Worker_Documents)
For Business Processes whose initiation payload lives in Workday SOAP Web Services—such as attaching a physician’s certification to Request_Leave_of_Absence in Absence_Management (v45.1) or uploading a standalone worker file via Put_Worker_Document in Human_Resources—embed Base64-encoded bytes inside Business_Process_Attachment_Data (or Worker_Document_Data):
<wd:Business_Process_Parameters>
<wd:Auto_Complete>false</wd:Auto_Complete>
<wd:Run_Now>true</wd:Run_Now>
<wd:Business_Process_Attachment_Data>
<wd:File_Name>physician-certification-2026-11.pdf</wd:File_Name>
<wd:Event_Attachment_Description>FMLA medical certification</wd:Event_Attachment_Description>
<wd:Event_Attachment_Category_Reference>
<wd:ID wd:type="Document_Category_ID">LEAVE_MEDICAL_DOC</wd:ID>
</wd:Event_Attachment_Category_Reference>
<wd:File>JVBERi0xLjUKJeLjz9MK...</wd:File>
<wd:Content_Type>application/pdf</wd:Content_Type>
</wd:Business_Process_Attachment_Data>
</wd:Business_Process_Parameters>Watch Base64 Overhead and Category Validation
Base64 encoding inflates payload size by roughly 33%, though Workday measures the 30 MB attachment cap against the decoded file (500 MB incoming gateway limit applies to the overall non-Import SOAP envelope). Only include <wd:Event_Attachment_Category_Reference> if the Business Process type supports attachment categories—otherwise Workday returns a Validation_Fault (“This Business Process Type has been configured to not accept Attachment Categories”).
Critical Security Gap: Web Service Uploads Bypass Workday Virus Scanning
Workday’s Concept: Virus Scanning documentation states a crucial operational boundary that catches many InfoSec teams off guard: Workday automatically scans browser uploads on tasks like Add Worker Document, Create Expense Report, Create Supplier Invoice, and external career sites, but Workday’s virus scanning service does NOT scan files imported using web services and integrations (nor files larger than 30 MB or certain media streams).
Whenever an external portal, mobile app, or chat integration accepts a PDF or photo from an employee’s phone and forwards it over Workday REST or SOAP:
- Scan in memory before calling Workday: Stream the uploaded file through an antivirus engine (such as ClamAV or cloud malware inspection) in RAM before opening the outbound request to Workday, and drop infected payloads immediately without writing them to disk.
- Verify magic bytes, not just file extensions: Confirm that a file named
doctor-note.pdfactually begins with%PDF-(25 50 44 46 2D) or valid JPEG/PNG/HEIC headers, and convert mobileHEICcamera photos toJPGorPDFif Edit Tenant Setup - System uses Allow ONLY Specific File Types withoutheicenabled (and if downstream Expense Business Form PDF printing requiresJPG,PNG,GIF,TIFF,BMP, orPDF). - Avoid stalled chunked uploads: Workday enforces a request upload idle timeout across consecutive data chunks and terminates stalled upload connections to protect gateway resources. Validate and buffer/stream cleanly over fast TLS connections.
Securing Doctor’s Notes and Medical Attachments on Leave Events
When a worker attaches a doctor’s note to Request Leave of Absence (a worker-related business process, which also adds the attachment to the worker’s document file), default inheritance can expose that note to the worker’s direct manager if attachment security is left unconfigured!
By default, if you leave Attachment Settings in BP Toolbar blank on a Business Process Security Policy, Workday automatically inherits attachment view/edit permissions from the security groups assigned to each Business Process step—meaning a Manager assigned an Approval step on Request Leave of Absence could view the attached medical note unless segmented.
Lock down clinical and accommodation attachments with four tenant steps:
- Check the “Most Recent Change Wins” Tenant Trap: Attachments can be toggled globally on Edit Tenant Setup - Business Processes (Enable Attachments) or per workflow on the Business Process Security Policy. When the two conflict, Workday honors whichever task was saved most recently—even if someone edited an unrelated field on Edit Tenant Setup - Business Processes! Always check both audit trails if an upload suddenly fails.
- Create a Dedicated Medical Document Category: Run Maintain Document Categories (secured by Set Up: Tenant Setup - Document Categories) and create
Leave / Medical Documentation(LEAVE_MEDICAL_DOC). - Segment Access Away from Line Managers: Run Create Document Category Security Segment to isolate
LEAVE_MEDICAL_DOC, bind it to a Segment-Based Security Group containing onlyAbsence Partner/HR Administratorroles (plusEmployee As Selfif workers should upload/view their own), and exclude supervisoryManagergroups. - Configure the Business Process Policy & Activate: Open the Request Leave of Absence Business Process Security Policy → Edit → Attachment Settings in BP Toolbar, assign your segmented security groups to View Permissions, Edit Permissions, and Manage Attachment Permissions, verify self-service worker document domains (Self-Service: Add Worker Documents in the Personal Data functional area where applicable), and run Activate Pending Security Policy Changes.
When employees upload a receipt or leave document through a custom screen built with Kiweely Leaf (coming next), Leaf streams the file statelessly without storing HR documents at rest on Kiweely servers and executes the Workday upload under that signed-in employee’s own OAuth permissions—honoring every Document Category Security Segment and Business Process policy in your tenant.
Frequently asked questions
Does Workday automatically scan files uploaded via REST or SOAP APIs for viruses?
No. While Workday runs automatic virus scanning on browser uploads in tasks such as Add Worker Document, Create Expense Report, and Apply to Job, Workday's virus scanning service explicitly does not scan files imported through web services and integrations or files over 30 MB.
What is the maximum file size for a Workday attachment uploaded via REST or SOAP?
The hard tenant ceiling is 30 MB (30,720 KB) per attachment across both the Workday UI and SOAP/REST web services, and 10 MB (10,240 KB) for tenant image uploads (up to 30 MB on specific web service image endpoints). Administrators cannot raise these limits in Edit Tenant Setup - System.
Where do Workday administrators restrict allowed file extensions for uploads?
In Edit Tenant Setup - System under System Setup (File Type Setup Instructions), administrators choose between Allow All File Types (minus Workday's permanently blocked executable extensions like exe, bat, js, lnk, and vbs) or Allow ONLY Specific File Types.
How do I keep managers from viewing sensitive medical or doctor's note attachments on a Leave of Absence event?
Create a dedicated Document Category (via Maintain Document Categories), restrict it with Create Document Category Security Segment to a segment-based security group (such as Leave Partners), and configure Attachment Settings in BP Toolbar on the Request Leave of Absence Business Process Security Policy.