Filing in EFAST2

The Form 5500 XML format, in plain language

EFAST2 receives a Form 5500, 5500-SF or 5500-EZ as XML data checked against government schema files, with attachments such as the accountant's opinion carried inside as PDF or plain text. You rarely touch the XML: IFILE or certified software builds and sends it. The full rules are in the Software Developer Specification, the Data Element Requirements (DER) and the schema files, which the DOL publishes to registered software developers.

Updated November 20, 2026Sources EFAST2 Software Developer Specification (version 041526); 2026 Data Element Requirements (form year 2026v01.00); PATS procedures; IFILE User Guide; EFAST2 FAQs
At a glance
Data format
XML, validated against DOL schema files
Data elements
1,401 in the 2026 DER
Attachments
PDF or TXT, base64 encoded; some PDF only
Edit tests
593 in the 2026 DER; 586 apply to 2025 filings
Software testing
PATS, before any production filing

What EFAST2 actually receives

Every Form 5500 series return goes to EFAST2 electronically as XML, a text format for structured data. The EFAST2 Software Developer Specification (version 041526) sets the core rule: “Each filing must be formatted as XML data consistent with XML Schema specifications published by the Government for the FormYear and FormVersion specified in the filing header”. The specification says the schemas fix whether each element is required, how often it may occur, and the order and type of every value. They change every year: “Government-defined XML schemas and edit tests for all EFAST2 forms and schedules are subject to annual changes.”

Filers do not write this XML. IFILE or certified third-party software builds it from the form you fill in. The XML matters to a filer in a few places: moving a draft between people or programs, the e-signature option, reading EFAST2 error messages, and understanding the public data. See IFILE or third-party software.

How a filing is put together

The specification defines four kinds of filing, each a FilingHeader followed by one data block:

FilingData blockWhat may go with it
Form 5500FilingDataAny combination of schedules, structured attachments and other attachments
Form 5500-SFShortFormDataSchedule MB or SB, Schedule MEP, and their attachments
Form 5500-EZEZFormDataNo schedules; limited attachments
Form 5558ExtFormDataNothing else: no schedules or attachments

The FilingHeader identifies the plan and year, the schema version and the software, and holds the electronic signatures. A few of its elements, as the 2026 Data Element Requirements (DER, form year 2026v01.00) defines them:

ElementWhat the DER says
FilingIdRequired. A 21-digit ID: “21-char unique ID generated at time of signing a filing. EIN + YYMMDDhhmmss”
TimestampRequired. Date and time with a time zone; it should match the last signature.
EIN and PNThe sponsor's 9-digit EIN (no hyphens) and the plan number. They must match lines 1b and 2b of the form (edit test X-008).
AmendedIndOptional. 1 if the amended box is checked, 0 if not.
RefAckIdOptional. A 30-character ID: the “AckId of original filing submission, used to marry amended to original return.”

The DER is the dictionary for the whole filing. The 2026 DER lists 1,401 data elements, each with its XML element name, element ID, whether it is required, its type and allowed values, and the error text EFAST2 returns when a value is invalid. It also holds the edit tests: 593 business rules for form year 2026 (382 Errors, 196 Warnings and 15 Stops). Seven of them are new for 2026; the other 586 also apply to 2025 filings, and you can search those in the EFAST2 edit test lookup.

The schema itself is a set of XML schema definition (.xsd) files plus one web service definition (EFAST2.wsdl). The 2026 set has a file for the filing structure (Filing.xsd), one for each form (Form5500.xsd, SF.xsd, EZ.xsd and Form5558.xsd), one for each schedule (A, C, D, DCG, G, H, I, MB, MEP, R and SB), files for attachments, DCG attachments and structured attachments, a file of shared data types (efastTypes.xsd), and MessageTypes.xsd for the web service messages. We describe the files rather than reproduce them; your software vendor works from them directly.

An annotated sample

Here is the shape of a Form 5500 filing with a Schedule H, cut down to a few lines of each part. The element names and their order come from the schema files; the values are made-up examples. Each note says which form line the element carries.

Annotated sample: a Form 5500 with Schedule HElement names and order from the 2025 and 2026 schemas; values are examples
<Filing xmlns="http://efast.gov/2025">Root element. The namespace names the form year: the 2026 schemas move it to http://efast.gov/2026.
<FilingHeader>Who is filing what, for which plan year. EFAST2 checks it against the form inside (edit test X-008).
<FilingId>000000123260715103000</FilingId>21 digits: the sponsor EIN plus the date and time of signing (YYMMDDhhmmss). The software creates it.
<Timestamp>2026-07-15T10:30:00-05:00</Timestamp>
<EIN>000000123</EIN>Plan sponsor EIN, nine digits, no hyphen. Example value.
<PN>001</PN>Three-digit plan number.
<PlanYearBeginDate>2025-01-01</PlanYearBeginDate>
<PlanYearEndDate>2025-12-31</PlanYearEndDate>
<FormYear>2025</FormYear>The form year printed at the top of the form, not the year you file.
<FormVersion>2025v01.00</FormVersion>The developer spec gives 2025v01.00 for the 2025 form and 2026v01.00 for 2026.
<FilingSoftwareId>...</FilingSoftwareId>The ID the DOL issues to certified preparation software (PATS).
<AdminSignature>Signer User ID and PIN, plus the signer's name and date. Amended filings add AmendedInd and RefAckId.
<SignerId>...</SignerId><PIN>...</PIN>
<SignedDate>...</SignedDate><SignedName>...</SignedName>
</AdminSignature>
</FilingHeader>
<FilingData>A Form 5500 filing. A 5500-SF uses ShortFormData, a 5500-EZ EZFormData, a Form 5558 ExtFormData.
<Form5500>
<PlanYearBeginDate>2025-01-01</PlanYearBeginDate>Part I, plan year beginning.
<PlanYearEndDate>2025-12-31</PlanYearEndDate>Part I, plan year ending.
<TypePlanEntityCd>2</TypePlanEntityCd>Line A: 1 multiemployer, 2 single-employer, 3 multiple-employer, 4 DFE.
<PlanName>Example Company 401(k) Plan</PlanName>Line 1a.
<SponsDfePlanNum>001</SponsDfePlanNum>Line 1b.
<SponsorDfe>Line 2a to 2d: name, address, phone and EIN.
<Name>Example Company Inc.</Name>
<USMailingAddress><AddressLine1>...</AddressLine1><City>...</City><State>TX</State><ZipCode>...</ZipCode></USMailingAddress>
<EIN>000000123</EIN>Line 2b. Must match the header EIN.
</SponsorDfe>
<Administrator><NameSameAsSponsorInd>1</NameSameAsSponsorInd></Administrator>Line 3a: same as the plan sponsor.
<TotPartcpBoyCnt>145</TotPartcpBoyCnt>Line 5: participants at the beginning of the plan year.
<!-- lines 6 to 11: participant counts, feature codes, funding, attached schedules -->
</Form5500>
<SchH>Schedule H comes after Form5500 in the order the schema fixes.
<NonIntBearCashBoyAmt>12500</NonIntBearCashBoyAmt>Line 1a(a): whole dollars, no commas or decimals.
<!-- the rest of Schedule H -->
</SchH>
<Attachments>...</Attachments>PDF or text attachments such as the accountant's opinion, sent base64-encoded with a type code.
</FilingData>
</Filing>

Every element has a fixed place. The schema sets the order (the Form 5500 first, then the schedules in a set sequence, then attachments), so software that writes elements out of order gets a schema error before any edit test runs.

Look up any element

Search all 1,344 data elements in the DOL's Data Element Requirements by form line (for example Schedule H 1a or 5500-SF 7a), by the label on the form, or by XML name. Each result shows the element's type, whether the schema requires it, its allowed values, and the edit tests that check it, linked to the edit test lookup. The Software Developer Specification says no data elements were added for the 2026 form version, so the list matches the 2025 forms.

1,344 data elements. Type to search.

    How software sends it

    Certified software talks to EFAST2 through a SOAP web service over HTTPS. The specification lists four operations: SendSubmission (send one filing or a batch), GetSubmissionStatus and GetFilingStatus (ask for results), and PreValidateFiling (test a filing without filing it). A batch holds either Form 5500 series filings or Forms 5558, never both, and only one form year.

    The first reply is a receipt with an AckId, a FilingId and a timestamp. The specification says “Each receipt indicates only that the Government has received the filing submission and does not imply acceptance of the filing.” A request that fails the basic checks (credentials, certified software, well-formed XML, schema, virus scan, form year) gets a fault message instead, and its filings are not an "attempt to file." The status that follows comes from the most severe edit test failure:

    Highest severity foundWhat EFAST2 doesFiling status
    UnprocessableRuns no edit tests; filing not acceptedUnprocessable
    StopRuns only Stop edits; filing acceptedProcessing Stopped
    ErrorRuns all edits; filing acceptedFiling Error
    Warning (or nothing)Runs all edits; filing acceptedFiling Received

    Filing Error and Processing Stopped are fixed with an amended filing; see amending a Form 5500 and acknowledgments and edit tests.

    XML in IFILE: import and export

    IFILE imports and exports filings as XML. EFAST2 FAQ 20 says you can export a draft as XML for someone else to import and review; FAQ 30 describes exporting from a preparer's software and importing into IFILE so the plan administrator can sign there. An XML file is not a PDF of the form: the IFILE guide says “Properly formatted XML files must be created by software that has been certified to create specific EFAST2 filing data.” Renaming a PDF to .xml does not work. Exporting or editing a signed return erases the signatures, so the signer signs again. Under the e-signature option, FAQ 33a says “the form that was manually signed, scanned, and attached to the filing must match the information electronically submitted in XML format”. See signer credentials.

    Where the technical documents live

    The specification, the DER, the schema files, the edit test mask lists (rules switched off for a form year) and the Entity Control note on duplicate and amended filings are not on the public EFAST2 pages. A developer registers in EFAST2 through Login.gov with the software developer user type, signs in and opens Software Developer Tools. The public can read the EFAST2 FAQs and the Guide for Filers and Service Providers. Questions go to the EFAST2 Contact Center at 866-463-3278 or support@efast.dol.gov.

    PATS testing and certification

    No software may file in production until it passes testing. The DOL's developer sheet says “The EFAST2 validation and certification process is the Participant Acceptance Testing System (PATS).” The Test and Certification Procedures (April 15, 2026) set the order: transmission software is certified first, and once, unless EFAST2 changes its protocol; filing preparation software is then tested form year by form year. “Filing Preparation software must be certified annually for each Schema/Form Version.” The developer runs the PATS test cases through its software, the DOL reviews them, and certification follows a signed affidavit. A filing sent with an uncertified software ID is not accepted or processed. For a filer, the point is to check that your product is certified for the year and schedules you need (EFAST2 FAQ 7). Form PR can only be filed in IFILE.

    Attachments

    Inside the XML, each attachment is an element with an AttachmentTypeCode and the file itself. The specification says “All Text and PDF attachments must be base64binary encoded for transmission.” The DOL's attachment type list for form version 2026v01.00 maps each code to a form line, for example AccountantOpinion (Schedule H line 3a, Schedule I line 4k), SchAssetsHeld (Schedule H line 4i), FivePrcntTrans (Schedule H line 4j), ESignatureAlternative (the manually signed form), ReasonableCauseLate (reasonable cause for late filing) and OtherAttachment for anything else.

    AttachmentAllowed format (EFAST2 FAQ 27, specification)
    Accountant's opinion (IQPA report)PDF only
    Image of the signed Schedule MB or SBPDF only
    Image of the signed Form 5500, 5500-SF or 5500-EZ (e-signature option)PDF only
    All other attachmentsPDF or TXT
    • No encryption. FAQ 27a: “EFAST2 will not process a filing that includes an encrypted or password-protected PDF.”
    • Right side up, one file per type. FAQs 28 and 29: pages in order, none sideways or upside down.
    • One accountant's opinion per filing, except one per participating plan in a DCG filing.
    • No Social Security numbers, since attachments are public, and never attach Form 8955-SSA or Form 5558.
    • Structured attachments. Schedule MB lines 3(d), 8b(1), 8b(2) and 8b(3) and Schedule SB lines 26a and 26b can be sent as data (from a CSV file in IFILE) instead of a PDF; their schema is StructuredAttachments.xsd.

    Size limits

    LimitFigureSource
    One attachment in IFILE60 MB encoded (about 44.3 MB decoded)IFILE User Guide (version 5.1)
    One submission through the web service300 MBSoftware Developer Specification (version 041526)
    Batch submissionUp to 100 filings and 300 MBGuide for Filers and Service Providers (version 4.0)
    One filing or submissionUp to 100 MB should be acceptedEFAST2 FAQ 44 (Jan. 10, 2025)

    The developer specification puts the web service ceiling at 300 MB: “The maximum size of a submission that can be processed through the EFAST2 exposed web service is 300 megabytes (MB).” The public FAQ uses 100 MB and warns that your network can block smaller files, so plan around 100 MB. FAQ 44 says a filing over 16 MB usually means PDFs scanned at too high a resolution; FAQ 29 suggests 300 by 300 resolution in grayscale and your software's optimize function.

    From filed XML to public data

    The DOL publishes accepted filings two ways. The Form 5500 Search page shows the form images (attachments can take up to 21 days, FAQ 43), except Form 5500-EZ filings and filings with sensitive information. And FAQ 42 says EBSA posts “structured datasets of Form 5500 Series forms and schedules filed each year, including filings prior to 2009”. The Form 5500 datasets come as one zip per form or schedule per form year, each holding a CSV file and a layout file listing every column. In the 2024 layouts, ACK_ID is the first column of every file and joins schedules to their form; other columns include AMENDED_IND, FILING_STATUS, DATE_RECEIVED and DFVC_PROGRAM_IND. These dataset names are the DOL's own and differ from the XML names (the header element is AmendedInd, the dataset column AMENDED_IND). This site's plan lookup and Form 5500 by the numbers use the "Latest" files for Form 5500, 5500-SF and Schedules H and I. Posting is not approval: the EFAST2 guide says it “does not constitute acceptance of the filing by the U.S. Department of Labor, the Pension Benefit Guaranty Corporation, or the Internal Revenue Service”.

    Form 8955-SSA is a different format

    Form 8955-SSA does not go through EFAST2. It is filed with the IRS, and Publication 4810 sets its own electronic record layout: a Transmitter "T" record, a Sponsor "S" record, an Administrator "A" record, Participant "P" records and an End of Transmission "F" record. See filing Form 8955-SSA: FIRE to IRIS.

    Questions filers ask

    Can I get the Form 5500 XML schema?

    The schema files, the Software Developer Specification and the DER are under Software Developer Tools in EFAST2, for users registered with the software developer user type. Filers normally rely on IFILE or certified software instead.

    Can I convert a PDF of last year's return into XML for IFILE?

    No. The IFILE guide says renaming or converting a PDF to XML is not a valid option. Use Create a Filing and enter the data, or get the XML export from the software that prepared the return.

    What is the FilingId?

    A 21-digit number in the filing header: the EIN plus a date and time stamp (YYMMDDhhmmss), generated when the filing is signed. The AckId is different: a 30-character ID EFAST2 assigns when it receives the filing.

    What attachment formats does EFAST2 accept?

    PDF or plain text, base64 encoded inside the XML. The accountant's report, the signed Schedule MB or SB and the e-signature image must be PDF. Encrypted or password-protected PDFs are not processed.

    How big can a Form 5500 filing be?

    The developer specification allows 300 MB per web service submission, but the public EFAST2 FAQ uses 100 MB, and the IFILE guide limits one attachment to 60 MB encoded. Plan around the smaller figures.