How to Correct and Resubmit a RELIEF, SAWT, or QAP DAT File After eSubmission
There’s no dedicated “amended DAT file” form — correcting a RELIEF, SAWT, or QAP DAT file after it’s already been submitted to the BIR means regenerating the file from corrected source data, re-validating it, and resubmitting it through the same esubmission@bir.gov.ph channel used for the original. The distinction that matters is timing: an error caught by the Validation Module before submission is a routine fix; an error discovered after the BIR has already acknowledged the file is a resubmission of record, and it usually needs to travel together with an amendment to the return the DAT file supports.
This guide covers what to do once a DAT file error surfaces after submission. For catching errors before that point, see How to Validate a BIR DAT File Before eSubmission and the form-specific error guides for RELIEF SLSP, SAWT, and QAP.
Regenerate a Clean DAT File FREE →Why does timing change how a DAT file error gets handled? #
A DAT file error caught by the BIR’s Alphalist Data Entry and Validation Module before eSubmission never becomes part of the BIR’s record — it’s fixed and re-validated before it’s ever sent. An error discovered after the BIR has already replied with an eSubmission acknowledgment is a different situation: the flawed file is now the taxpayer’s filing of record for that period until a corrected version is submitted and acknowledged in its place.
This is exactly the same logic that governs amending any other BIR filing — the earlier a correction happens, the more it looks like routine data hygiene; the later it happens, the more it looks like a filing the BIR needs to formally supersede.
How do you correct and resubmit a DAT file after eSubmission? #
Correcting a submitted DAT file means regenerating it from corrected source data — never hand-editing the DAT file itself — and resubmitting it through the same channel as the original.
- Identify the specific error — a wrong TIN, a misclassified sale or purchase, a wrong ATC on a QAP entry, or a missing payee or counterparty row.
- Correct the source data in the spreadsheet or system that generated the original file, not the DAT file directly.
- Regenerate the DAT file for the same filing type and period.
- Re-run it through the BIR’s Alphalist Data Entry and Validation Module and confirm zero errors, the same as any first-time submission.
- Email the corrected file to esubmission@bir.gov.ph, using the same subject-line convention (form type, TIN, RDO code, registered name, period) as the original, so the submission is identifiable as covering the same period.
- Retain the BIR’s eSubmission acknowledgment for the corrected file alongside the one for the original — both are proof of what was filed and when.
- Check whether the return the DAT file supports also needs amending — see below.
Does the underlying return also need to be amended? #
Usually, yes, if the DAT file correction changes any total the return reported. A RELIEF SLSP, SAWT, or QAP file is a supporting attachment to a return — the VAT return for RELIEF SLSP, the income tax return for SAWT, the withholding tax return for QAP — not an independent filing on its own. A correction that changes the sales, purchases, or withheld-amount totals behind that return should be matched by an amended return under NIRC Section 6(A), following the same three-year, no-audit-notice window described in How to Amend a Filed BIR Tax Return.
| DAT file | Return it typically supports | If the correction changes totals |
|---|---|---|
| RELIEF SLSP | BIR Form 2550Q (VAT) | Amend the 2550Q — see Amending BIR Form 2550Q |
| SAWT | Income tax return claiming the CWT credit | Reconcile the corrected SAWT against the return before the credit is claimed |
| QAP | BIR Form 1601-EQ (withholding) | Amend the 1601-EQ — see Correcting a Wrong ATC on a Withholding Tax Return |
A correction that only fixes a formatting or consolidation issue without changing any reported total — a counterparty name spelling, for example — doesn’t require amending the return itself, only the resubmitted DAT file.
A real example: mandatory resubmission after a Validation Module version update #
Timing-driven resubmission isn’t hypothetical. Revenue Memorandum Circular No. 15-2025 announced Version 7.4 of the Alphalist Data Entry and Validation Module, adding new alphanumeric tax codes and updated withholding tax rates, as covered in How to Validate a BIR DAT File Before eSubmission. Taxpayers who had already submitted DAT files validated against the older Version 7.3 needed to re-validate and resubmit against the new version — a file that was clean under the old rules could fail once the BIR reprocessed it against the updated schedule. This is the same mechanic as any other post-submission correction: regenerate, re-validate against the current standard, and resubmit through esubmission@bir.gov.ph.
Frequently asked questions #
Can I resubmit a RELIEF, SAWT, or QAP DAT file after the BIR already acknowledged the original? #
Yes. There is no separate “amended DAT file” form — a correction is a new DAT file, re-validated through the BIR’s Alphalist Data Entry and Validation Module and resubmitted through the same esubmission@bir.gov.ph channel used for the original, referencing the same filing type, TIN, RDO code, and period so the BIR can identify it as a correction to that submission.
Does resubmitting a corrected DAT file mean I also need to amend the return it supports? #
Usually, yes, if the correction changes any total the return reported — output VAT, input VAT, or a payee’s withheld amount. The DAT file is a supporting attachment, not an independent filing, so a correction that changes its totals should be accompanied by an amended version of the return under NIRC Section 6(A).
What happens if the BIR updates the Validation Module version after I already submitted? #
A file that passed validation on an older version can fail once the BIR reprocesses it against a newer one. Revenue Memorandum Circular No. 15-2025, which introduced Version 7.4 of the Alphalist Data Entry and Validation Module with new ATCs and rates, is a real example — taxpayers who had already submitted using the older Version 7.3 needed to re-validate and resubmit against the new version.
Should I keep proof of both the original and the corrected DAT file submission? #
Yes. Keep the BIR’s eSubmission validation report or acknowledgment for both the original and the corrected file. Having both on record shows the correction was made and when, which matters if the BIR’s own records still show the earlier, uncorrected version during a later reconciliation or audit.
Can I just re-edit the DAT file directly instead of regenerating it from the source data? #
No. A DAT file is a fixed-format, delimiter-separated file, and hand-editing it risks silently breaking the layout the Validation Module expects. Always correct the error in the source spreadsheet or system, regenerate the DAT file from that corrected source, and re-validate before resubmitting.
Summary #
A DAT file error found after eSubmission is fixed the same way as one caught before it — correct the source data, regenerate, re-validate — with two things added: resubmitting through the same esubmission@bir.gov.ph channel so the BIR treats it as a correction to that period, and checking whether the return the file supports needs an amended filing to match. A BIR Excel Uploader or any other Excel-to-DAT converter can regenerate the corrected file, but none of them replace the BIR’s own Validation Module or the resubmission step itself — those stay the taxpayer’s responsibility either way.