Your ledger. Your BIR filings. Already done.
Generates the actual BIR outputs from your live ledger — VAT 2550Q, RELIEF DAT files, journals, Form 2307, and EIS e-invoices. No re-keying.
Everything BIR & Statutory Compliance handles
VAT Return 2550Q from posted books
LedgerQ foots your output VAT, input VAT, and net VAT payable per rate directly from GL-posted invoices, then maps them onto the BIR Form 2550Q fields — including prior-period excess input VAT carried forward. (2550M was discontinued in 2023; LedgerQ produces the quarterly 2550Q.)
Summary Lists — RELIEF DAT format
Generate the SLS and SLP that tie out to your 2550Q and Sales Journal — only GL-posted invoices appear, so the summary lists reconcile to the VAT return. Rendered in PHP as BIR RELIEF submission requires.
BIR books of accounts
Produce the Cash Receipts, Cash Disbursements, Sales, and Purchases journals (with VAT breakdown), plus the BIR-format General Journal and General Ledger — in the prescribed columnar layouts under RR No. 9-2009.
Form 2307 withholding certificates
Produce per-vendor, per-quarter Form 2307 data drawn from actual EWT amounts on posted transactions — reading the withholding figure, never the input VAT, so certificates don’t overstate declared income.
Alphalist & eFPS attachments
Generate the Alphalist of Payees for BIR Form 1604-E, plus the withholding attachments eFPS expects — MAP (for 0619-E) and QAP (for 1601-EQ) — all in native BIR .DAT format.
BIR EIS e-invoice submission
LedgerQ maps each invoice to the BIR EIS v2.01 payload, signs it under your tenant’s key, and transmits to the BIR EIS API with acknowledgement polling — with a manual-portal mode for tenants who upload themselves.
From action to ledger, in four steps
- 1Post as usual
Record sales, purchases, payments, and withholding in the O2C/P2P flows. Every transaction lands in the ledger with its VAT and EWT already classified — no separate tax data entry.
- 2Outputs generate from real GL data
When a return or book is due, LedgerQ builds it from the posted ledger — 2550Q, the four special journals, SLS/SLP, Form 2307, and the alphalist attachments — so the numbers are your actual books.
- 3Validate and reconcile
Because only GL-posted invoices flow through, your Summary Lists tie out to your 2550Q and Sales Journal automatically. Review, and let Sebee answer questions about any line before you file.
- 4File and transmit
Download the eFPS attachment files (RELIEF, MAP/QAP DAT) and mapped 2550Q form data for the portal, and submit e-invoices straight to the BIR EIS API from inside LedgerQ.
Real screens, real data
The BIR EIS e-invoicing deadline is 31 December 2026 — be ready now
Under RR 11-2025 and RR 26-2025, covered taxpayers must issue and transmit electronic invoices through the BIR Electronic Invoicing System by 31 December 2026. LedgerQ already maps your invoices to the BIR EIS v2.01 payload, signs them, and transmits to the EIS API — so you can start electronic transmission ahead of the deadline instead of scrambling for it. (LedgerQ is CAS-ready and produces the required BIR outputs; it is not itself BIR-accredited.)
What you get
- No re-keying: every BIR output is generated from the same ledger you already post to.
- Returns that reconcile by design — SLS/SLP tie out to your 2550Q and Sales Journal.
- CAS-ready books: the four special journals, General Journal, and General Ledger in BIR-prescribed formats.
- eFPS-ready attachments in native BIR .DAT format (RELIEF, MAP, QAP), plus mapped 2550Q data.
- Direct BIR EIS e-invoice submission with signing and acknowledgement tracking — or manual-portal mode.
Frequently asked questions
Is LedgerQ BIR-accredited?
LedgerQ is CAS-ready and produces the required BIR outputs; it is not itself BIR-accredited. The BIR capability is live and verifiable in the product; the formal accreditation badge is on our near-term roadmap.
Which VAT return does LedgerQ produce?
The quarterly Form 2550Q. LedgerQ foots your output VAT, input VAT, and net VAT payable per rate directly from GL-posted invoices, then maps them onto the 2550Q fields — including prior-period excess input VAT carried forward. (2550M was discontinued in 2023.)
Do the Summary Lists reconcile to the VAT return?
Yes, by design. Only GL-posted invoices appear on the SLS and SLP, so the Summary Lists tie out to your 2550Q and Sales Journal automatically. They are rendered in PHP, in the BIR RELIEF DAT format submission requires.
Can LedgerQ submit e-invoices to the BIR EIS?
Yes. LedgerQ maps each invoice to the BIR EIS v2.01 payload, signs it under your tenant key, and transmits to the BIR EIS API with acknowledgement polling — with a manual-portal mode for tenants who upload themselves.
What withholding outputs does it generate?
Per-vendor, per-quarter Form 2307 certificates drawn from actual EWT amounts on posted transactions, plus the Alphalist of Payees for Form 1604-E and the eFPS attachments MAP (for 0619-E) and QAP (for 1601-EQ), all in native BIR .DAT format.
Related guides
- BIR CAS Accounting Software in 2026: What "Compliant" Should Actually Mean →
- BIR Form 2550 (VAT Return): How to File It Right in 2026 →
- BIR RELIEF & the DAT File: The Summary List of Sales and Purchases (SLSP), Explained (2026) →
- How to Prepare the BIR Alphalist: A Practical 2026 Guide for PH Businesses →