How to Prepare a BIR DAT File From Google Sheets (No Excel License Needed)

A BIR DAT file can be prepared entirely from Google Sheets — the BIR’s fixed delimiter, header/detail/trailer structure, and field-order requirements don’t care which spreadsheet application produced the source data. The practical risk isn’t the DAT format itself; it’s Google Sheets’ own auto-formatting defaults, which can silently strip leading zeros from TINs, insert thousands separators into amount fields, or auto-correct quote characters before the file ever reaches a DAT converter.

Does a BIR DAT file require Microsoft Excel? #

No — a BIR DAT file is a plain-text file with fields separated by a fixed delimiter, in the header/detail/trailer record structure the BIR’s Alphalist layout requires for that filing type, and that structure has nothing to do with which spreadsheet application prepared the underlying data. As covered in What Is a BIR DAT File?, the file itself is delimiter-separated text — not a spreadsheet workbook — so Excel is a common tool for organizing source data before conversion, not a format requirement.

This post is not about operating systems (that’s covered separately in How to Prepare and Validate a BIR DAT File on a Mac or Chromebook) and not about accounting-software exports (covered in How to Convert QuickBooks or Xero Data Into a BIR DAT File). It’s specifically for filers who do their spreadsheet work in Google Sheets — often because they have no Microsoft 365 license at all — and need to know what breaks differently there before running a conversion.

Exporting a Google Sheet correctly before conversion #

Getting a Google Sheet ready for DAT conversion means downloading it in a format the converter accepts and confirming the download didn’t quietly re-format the columns that matter most — TIN, ATC, and amount fields — in the process. Google Sheets offers several download formats from File > Download, and the choice affects how faithfully the data survives the trip.

The safest workflow is to format the sensitive columns as Plain Text inside Google Sheets before entering or pasting data, then export once and upload that file directly — without reopening the exported file in Sheets, Excel, or Notepad first, since each reopening is another chance for a default number or date format to reassert itself.

The Google Sheets-specific traps that cause DAT validation errors #

Three Google Sheets defaults account for most DAT validation failures that are specific to this workflow rather than to Excel: automatic type conversion on TIN and ATC columns, auto-formatting of dates, and smart-quote autocorrect on text fields — and each one is invisible on screen until the converter or the BIR’s Validation Module flags it. None of these are bugs; they’re Sheets doing exactly what a general-purpose spreadsheet is designed to do, which is not what a fixed-format government file needs.

• Leading zeros dropped from TIN, ATC, or branch code columns. Google Sheets treats a column of digits as a number by default. A TIN or ATC beginning with 0, typed or pasted into a number-formatted cell, has that leading zero silently removed with no on-screen warning — a value like 012345678 becomes 12345678, one digit short of what the BIR layout expects. Fix: select the column, apply Format > Number > Plain Text, before entering or pasting the values — reformatting after the fact does not restore zeros already lost.
• Dates auto-converted to Sheets’ own format or locale. A return period or transaction date typed as 01/2026 can be auto-interpreted as a date and reformatted to Google Sheets’ default date display, which may not match the exact MM/YYYY or MM/DD/YYYY string the BIR layout expects for that field. Fix: format the date/period column as Plain Text, or use a formula that outputs the exact required string, rather than relying on a date-formatted cell’s default display.
• Smart quotes and autocorrect on registered-name or address fields. Google Sheets’ text autocorrect can convert a straight apostrophe in a name like O'Brien Trading into a curly typographic apostrophe, and can autocorrect certain letter sequences in company names. A curly quote is a different character to a validator expecting plain ASCII text, and can cause a silent mismatch or rejection on that field. Fix: disable Sheets’ automatic substitution under Tools > Preferences before entering registered names, or paste values using Paste special > Values only from a source that doesn’t already contain smart quotes.

A fourth, lower-frequency issue is worth a mention: copy-pasting figures from a Google Doc, PDF, or web page into Sheets can carry invisible non-breaking spaces or other formatting characters along with the visible text, which look identical on screen but can break a TIN or amount field’s expected character pattern. Pasting with Paste special > Values only strips this along with removing formatting, so it solves both problems at once.

Worked example: a freelance bookkeeper preparing a RELIEF SLSP file in Google Sheets #

A freelance bookkeeper who manages several small-business clients entirely in Google Sheets — no Microsoft Office license, everything shared and edited from a browser — needs to prepare a quarterly RELIEF Summary List of Sales for one client that just crossed the sales threshold under Revenue Regulations No. 8-2002. The figures below are fictional, for illustration only.

The bookkeeper’s Sheet has one row per customer for the quarter: TIN, Registered Name, Address, Taxable Sales, and Output Tax — the same column shape covered in How to Convert Excel to BIR DAT File for RELIEF SLSP. Before exporting, she runs through the Sheets-specific checks:

1. Checks the TIN column format. Two customer TINs — 009876543000 and 012345678000 — both start with a zero. She confirms the TIN column is already set to Plain Text (she formats new columns this way as a habit before entering data), and spot-checks both cells to confirm the leading zeros display correctly rather than trusting the column format alone.
2. Checks the Registered Name column for smart quotes. One customer is D'Angelo Retail Corp. — she turns off automatic substitution under Tools > Preferences beforehand, then confirms in the cell that the apostrophe is a straight ' and not a curly '.
3. Confirms the Taxable Sales and Output Tax columns are numeric, not formatted as Currency. She had briefly applied a Philippine Peso currency format to preview the totals, then reverts both columns to plain Number formatting before export, since a currency symbol carried into the export as a literal character would break the amount field.
4. Exports as Microsoft Excel (.xlsx) rather than CSV, since the converter she uses accepts XLSX directly and this avoids a second round-trip through a spreadsheet application that could re-trigger auto-formatting.
5. Uploads the exported file directly to the RELIEF module in BIR Online Tools without reopening it first, and reviews the validation preview for any remaining TIN or amount flags before generating the DAT file.

Because she caught the leading-zero and smart-quote risks before export rather than after a validation failure, the file converts cleanly on the first attempt — the same outcome an Excel user would get, reached through a different set of checks specific to Sheets’ defaults.

FAQs #

Can I prepare a BIR DAT file without owning Microsoft Excel? #

Yes. A BIR DAT file is a plain delimiter-separated text file in a fixed column layout, and any spreadsheet application — including the free, browser-based Google Sheets — can produce the source data that a DAT converter needs. Excel is a common tool for this work, not a requirement of the BIR’s DAT file format itself.

Should I export a Google Sheet as CSV or XLSX before converting it to a DAT file? #

Either can work, but XLSX preserves column formatting (such as text-formatted TIN columns) more reliably than CSV, which strips formatting and can re-trigger auto-conversion of leading zeros or number formatting if the CSV is reopened before upload. Export as XLSX when the converter accepts it, and if using CSV, upload it directly without reopening it in another spreadsheet application first.

Why did my TIN or ATC column lose its leading zeros in Google Sheets? #

Google Sheets treats a column of digits as a number by default unless the column or cell is explicitly formatted as plain text. A TIN or ATC value with a leading zero, entered into a number-formatted cell, has that leading zero silently dropped, and no visible warning is shown. Format the column as Plain Text before entering or pasting TIN, ATC, or branch code values to prevent this.

Does Google Sheets add thousands separators or currency symbols that break DAT file amounts? #

Yes, if a column is formatted as Number, Currency, or Accounting. Google Sheets displays 100,000.00 or ₱100,000.00 in the cell, but a DAT conversion tool reading the underlying value should still receive the correct number — the actual risk is copy-pasting that formatted, displayed value as text into another field or tool, which carries the comma and currency symbol along as literal characters instead of a clean number.

Summary #

A BIR DAT file’s delimiter, field order, and header/detail/trailer structure are the same regardless of whether the source data was built in Microsoft Excel or Google Sheets — there is no Excel license requirement anywhere in the BIR’s DAT format itself. What differs is the auto-formatting a filer has to watch for: Google Sheets can silently drop leading zeros from TIN and ATC columns, auto-convert dates to its own display format, and autocorrect straight quotes into smart quotes inside registered names, each of which reaches the BIR’s Validation Module as a formatting error even though the data looked correct on screen. Formatting sensitive columns as Plain Text before data entry, disabling autocorrect for name fields, and exporting once without reopening the file are enough to avoid all three traps.

Sources #

Primary sources

• Bureau of Internal Revenue — Alphalist Data Entry and Validation Module, bir.gov.ph/Downloadables (the DAT file layout and validation requirements this post’s structural facts are grounded in, as already documented on this site).
• Revenue Regulations No. 1-2014, as clarified by Revenue Memorandum Circular No. 5-2014 — the electronic alphalist framework requiring DAT files in the BIR’s fixed layout, cited and corroborated in this site’s What Is a BIR DAT File?.

Secondary sources

• This site’s own prior, independently researched posts on DAT file structure and platform-specific pitfalls: What Is a BIR DAT File?, How to Prepare and Validate a BIR DAT File on a Mac or Chromebook, and How to Convert Excel to BIR DAT File for RELIEF SLSP — reused here for the DAT format baseline rather than re-derived.
• The Google Sheets auto-formatting behaviors described (number/text type conversion, date auto-formatting, autocorrect substitution) reflect Google Sheets’ documented, publicly observable default behavior rather than a claim requiring a regulatory citation.