BIR XML Filing Guide for Philippine Workflows

When BIR compliance goes electronic, your returns stop being paper you sign and become data you transmit. For most e-filed returns, that data travels as XML — a structured, machine-readable file the BIR's systems parse automatically. It's a different pipeline from the .DAT files that carry your summaries and alphalists, and confusing the two is a common source of last-minute filing trouble. This guide explains what XML e-filing is in the BIR context, which forms file as XML versus DAT, how XML is generated from your books and validated, and why one clean set of records should feed every output you submit.

The short answer

XML e-filing is how the BIR receives your returns as structured data instead of typed forms. You prepare the return — from your books or in an e-filing tool — generate or load the XML, and transmit it through the BIR's electronic channel you're enrolled in (eFPS for large/enrolled taxpayers, eBIRForms for the broader population). The summaries that support those returns — your SLSP, SAWT, QAP, and alphalist — generally go in separately as .DAT files. Get your books right and both the XML and the DAT fall out as exports of the same posted entries; get them inconsistent and the two pipelines disagree.

Who this guide is for

• Business owners moving from manual or over-the-counter filing to e-filing for the first time.
• Freelancers and professionals enrolled in eBIRForms who want to understand what the tool is actually transmitting.
• Bookkeepers and accountants who file returns and summaries for clients and want one pipeline instead of re-keying each output.

What XML e-filing actually is

Think of an XML file as a tightly-structured text document that encodes a return's fields — the taxpayer, the period, the line items, the totals — in a layout the BIR's systems can read automatically. It isn't meant to be eyeballed or hand-edited; open one and you'll see nested tags and values, not a friendly form. The BIR defines the structure for each return, and the e-filing tool (or compatible software) writes that structure so you don't have to. The point is machine ingestion: rather than a person retyping your figures into a portal screen, the BIR loads your file directly and runs its own checks.

Because the format is rigid, an XML submission is accepted or rejected — there's little middle ground. That's a feature, not a frustration: it forces each return to be complete and internally consistent before the BIR will take it.

XML vs DAT: which forms use which

The cleanest way to keep the two straight is by what they carry. Returns — the forms you file to declare and pay a tax — generally go in as XML through your e-filing channel. The summaries and alphalists that support those returns — the line-by-line lists the BIR ingests as bulk data — generally go in as .DAT files, a pipeline covered in our BIR DAT file guide.

A quarterly VAT return is a good example of the return side — see the BIR Form 2550Q guide for what that form declares, and the broader VAT filing guide for how the return and its SLSP support file fit together. For a deeper look at the file-format idea underneath both, see BIR DAT files explained.

eFPS vs eBIRForms

The BIR runs two main e-filing facilities, and which one you use depends on your enrollment, not your preference. eFPS (Electronic Filing and Payment System) is the online facility used by enrolled and larger taxpayers, with integrated electronic payment. eBIRForms is the offline package plus online submission used by the broader taxpayer base. Both ultimately transmit a structured return to the BIR; the difference is enrollment, the interface, and how payment is handled.

How an XML return gets produced, validated, and filed

Whatever the return, the lifecycle is the same: assemble the figures, encode them into the return's structure, prove the file is sound, transmit it, and keep the proof.

1. 1

   Assemble the figures from your books

   Pull the period's totals — sales, purchases, tax bases, withholding — from your ledger so the return is built on posted, balanced data rather than re-keyed estimates.

2. 2

   Encode into the return's structure

   Prepare the return in your e-filing tool, or generate the XML directly from software that writes the BIR's layout, so the same figures flow through without retyping.

3. 3

   Validate before transmitting

   Let the tool check the file's structure and required fields. Like a DAT file, an XML return is accepted or rejected — fix anything flagged at the source and re-check until it passes.

4. 4

   File through your channel

   Transmit through the facility you're enrolled in — eFPS or eBIRForms — following the current BIR steps for that form, and handle payment through the prescribed method.

5. 5

   Submit the supporting DAT files

   Where the return requires a summary (for example, the SLSP behind a VAT return), generate and validate that .DAT file from the same books and submit it through its own channel.

6. 6

   Archive the file and the confirmation

   Keep the transmitted return, any DAT files, and the BIR acknowledgements with your records, so you can reproduce exactly what you filed.

How this connects to your books

Here's the quiet truth about XML filing: the file is the easy part. The hard part is that the figures inside it have to match your books, your certificates, your summaries, and last period's filings. When your transactions live in a real double-entry ledger — each sale split into net and output VAT, each withheld payment carrying its payee and ATC — the XML return and the DAT summary are simply two views of the same posted entries. Build them from one source and they can't disagree; rebuild each in a spreadsheet and you've signed up for a reconciliation problem every period, which the BIR's own cross-checks will eventually surface.

Common mistakes

• Treating XML and DAT as one step. They're separate pipelines — filing the return doesn't submit the summary, and vice versa. Track both for each period.
• Hand-editing the XML. The structure is exact; opening a file to 'just fix a number' usually corrupts it. Fix the source figures and regenerate.
• Using an outdated form package. The BIR updates eBIRForms and eFPS form versions; an old version can produce a return the channel rejects.
• Filing figures that don't tie to the books. If the return doesn't foot to your ledger, it won't reconcile with your summaries — or with next period's filings.
• Not keeping the confirmation. If you can't reproduce exactly what you transmitted, you can't defend it later.