RR No. 6-2026 and the BIR Electronic Invoicing System: Where Does the Withholding Tax Line Appear on an E-Invoice?
Revenue Regulations (RR) No. 6-2026 requires the amount of creditable withholding tax (CWT), if applicable, to appear as a separate item on a BIR invoice — and that content requirement applies to an invoice regardless of whether it is printed or generated electronically through the BIR’s Electronic Invoicing System (EIS). What RR No. 6-2026 does not do is describe how an EIS-enrolled taxpayer’s invoicing software should represent that line in its data feed, and neither this site nor the two posts it builds on found a separate BIR issuance updating the EIS data schema for it. This post lays out what’s confirmed and what’s still open for e-invoice issuers specifically.
Reconcile Your E-Invoice Withholding Line to a BIR Form 2307 FREE →This post sits between two others on this site: RR No. 6-2026: Invoices Must Now Show Creditable Withholding Tax as a Separate Item covers the regulation’s text and the printed-invoice stamping transition, and What Is the BIR Electronic Invoicing System (EIS) and Which Taxpayers Must Comply? covers EIS generally. Neither post answers the question an EIS-enrolled taxpayer actually has: does my e-invoice need this line too, and if the stamping rule is written for paper, what applies to me instead?
Does RR No. 6-2026’s new invoice item apply to electronic invoices? #
Yes — the new requirement is a content rule for “the Invoice,” and Section 237 of the Tax Code covers the invoice as a document type without distinguishing paper from electronic format. RR No. 6-2026 amends Section 6(B) of RR No. 7-2024, the section listing the information an invoice “issued under Section 237 of the National Internal Revenue Code of 1997 (Tax Code)” must contain. Section 237 is the statutory invoicing mandate that applies to every covered seller, and the BIR’s own Electronic Invoicing System framework exists specifically to let certain taxpayers issue that same statutory invoice electronically instead of on paper — it does not create a second, lighter-weight invoice with its own content rules. The already-verified text of the amendment itself does not carve out electronic invoices:
“(B) Information Contained in the Invoice – The Invoice shall contain the following information: … 22. The amount of Creditable Withholding Tax, if applicable, shall be shown as a separate item.”
Source: Section 2, Revenue Regulations No. 006-2026, as quoted and sourced in RR No. 6-2026: Invoices Must Now Show Creditable Withholding Tax as a Separate Item. The provision says “the Invoice shall contain” the item — it is a content requirement attached to the invoice as a document, not to a particular medium of issuing it. On that reading, an EIS-generated invoice is still “the Invoice” Section 6(B) describes, so item 22 applies to it the same way it applies to a printed one.
Why can’t the Section 3 stamping rule apply to an e-invoice? #
Section 3 of RR No. 6-2026 is a transitional rule written for physical paper stock, and it has no equivalent action for a system-generated e-invoice — which is exactly why EIS-enrolled taxpayers need a different answer, not the same one. The already-verified transitory text reads:
“All unused or unissued invoices existing as of the effectivity date of these Regulations may continue to be used by taxpayers until fully consumed, provided that the phrase ‘Less: Withholding Tax’ is stamped conspicuously on the face of the invoice. Thereafter, all newly printed invoices shall reflect the same phrase prior to its use.”
Source: Section 3, Revenue Regulations No. 006-2026, quoted the same way in the companion post above.
Read literally, this provision addresses two things: physical inventory of blank invoices (“unused or unissued invoices existing”) and a physical act (“stamped conspicuously on the face”). An EIS-enrolled seller does not hold unused printed invoice booklets for transactions it processes through its Sales Data Transmission System, and there is no “face” of an electronic invoice to stamp in the way a rubber stamp marks paper stock. That makes the stamping transition mechanically inapplicable to e-invoice issuance:
| Printed-invoice concept (RR No. 6-2026 Section 3) | What it assumes | What an EIS-generated invoice has instead |
|---|---|---|
| “Unused or unissued invoices existing” | Physical booklets printed in advance of the effectivity date | No pre-printed stock — each invoice is generated at the moment of the transaction |
| “Stamped conspicuously on the face” | A rubber stamp or pre-printed phrase applied to paper | No physical face to stamp; the content lives in the invoice’s rendered layout and underlying data |
| “Newly printed invoices shall reflect the same phrase” | A new print run from a commercial printer | A template or layout change pushed to the invoicing/POS software, not a print order |
What carries over is the content requirement, not the stamping mechanism: item 22 — the CWT amount shown as a separate item — still has to appear somewhere on the e-invoice a buyer receives and on the structured record EIS stores, even though there is no printed stock to stamp and no transition period tied to existing inventory the way Section 3 describes for paper.
What hasn’t the BIR confirmed about the EIS schema? #
As of this writing, this site found no BIR issuance specifically updating the EIS data schema, the Standard API Guidelines, or the JSON invoice format to add a dedicated field for the RR No. 6-2026 creditable withholding tax item. RR No. 6-2026 itself is silent on EIS and the Sales Data Transmission System; it amends only the printed invoice content rule in RR No. 7-2024. The EIS explainer this post builds on describes EIS as receiving sales data “packaged… into the BIR’s prescribed JSON format” but does not document a field-by-field schema, and neither post has seen a BIR circular reconciling the two.
That gap means an EIS-enrolled taxpayer cannot currently point to a specific schema field name, API version number, or Standard API Guidelines revision and say “this is where item 22 goes.” This post does not invent one. What can be said is narrower and more defensible: the invoice content obligation under Section 6(B) applies to the invoice regardless of medium (see above), so an e-invoice issuer should treat the CWT-as-separate-item requirement as binding on the invoice it generates and presents to the buyer, even while the question of exactly how that line is tagged or transmitted inside the EIS data feed remains unconfirmed by any issuance this site has reviewed.
Until a BIR circular addresses the EIS schema directly, EIS-enrolled sellers should raise this specific question with their invoicing/Sales Data Transmission System vendor and, for the authoritative answer, their BIR Revenue District Office or the BIR’s EIS help desk — not rely on this post, or any other secondary source, to supply a schema field that hasn’t been published.
Worked example: representing the CWT line in an e-invoice line-item schema #
A worked example shows one plausible way a seller already issuing EIS-format e-invoices could represent the new line using an existing line-item type in its software — offered as an illustration of the gap, not as confirmed BIR guidance. Many invoicing/POS systems built for EIS already support a generic “deduction” or “discount” line type within an invoice’s structured line items, used today for things like early-payment discounts or promotional deductions. A seller’s system integrator could, as an interim measure pending BIR clarification, map the CWT amount onto that existing line type rather than waiting for a dedicated field.
Assume the same VAT-registered consultant from the companion post bills a client that is a withholding agent for ₱100,000 of services, but this time through an EIS-enrolled invoicing system rather than a printed booklet:
| E-invoice line item (illustrative schema mapping) | Amount |
|---|---|
line_item: "Services rendered", type: SALE | ₱100,000.00 |
line_item: "VAT (12%)", type: TAX | ₱12,000.00 |
| Invoice total (VAT-inclusive) | ₱112,000.00 |
line_item: "Less: Withholding Tax", type: DEDUCTION (existing line type, repurposed) | (₱2,000.00) |
| Net amount due | ₱110,000.00 |
The consultant’s invoicing software renders the “Less: Withholding Tax” line on the buyer-facing e-invoice exactly as the printed-invoice worked example shows it — satisfying the Section 6(B) content requirement that both posts agree applies regardless of medium — while the underlying DEDUCTION line type is what gets transmitted to EIS in the structured sales data feed. Whether the BIR’s own schema eventually adds a dedicated CWT field, a dedicated tax-type code, or simply accepts the existing deduction line type for this purpose is exactly the open question the previous section describes; this mapping is a reasonable interim approach for a seller that needs to comply today, not a confirmed BIR specification. Sellers should confirm with their EIS-certified vendor whether a DEDUCTION-type line is how their specific certified system already handles non-VAT deductions, since schema details vary by vendor implementation.
What should an EIS-enrolled taxpayer do now? #
- Treat the CWT-as-separate-item content rule as applying to your e-invoices now. The content obligation in Section 6(B), as amended, attaches to the invoice as a Section 237 document, not to a printing method.
- Do not wait for the Section 3 stamping transition to apply to you — it is written for physical stock and has no direct electronic equivalent; your compliance question is about invoice content and data mapping, not stamping.
- Ask your Sales Data Transmission System vendor directly whether and how their EIS-certified system currently supports a withholding-tax line item, since no published BIR schema update was found.
- Escalate to the BIR’s EIS help desk or your Revenue District Office for the authoritative answer on schema-level implementation before assuming any specific field name or line-item type is BIR-approved.
- Reconcile the e-invoice’s withholding line against the BIR Form 2307 you issue or receive, the same way the printed-invoice post recommends — see the BIR Form 2307 hub for the certificate side of this reconciliation.
Summary #
RR No. 6-2026’s requirement that an invoice show creditable withholding tax as a separate item is a content rule that applies to the invoice as a Section 237 document, so it reaches an EIS-generated electronic invoice the same way it reaches a printed one. What doesn’t carry over directly is the regulation’s Section 3 stamping transition, which is written for physical invoice stock and has no literal electronic equivalent. What remains genuinely unconfirmed, and is stated here as open rather than invented, is whether the BIR has updated or will update the EIS data schema or Standard API Guidelines with a dedicated field for this line — no such issuance was found at the time of writing. EIS-enrolled sellers should comply with the content requirement now and confirm schema-level mapping with their vendor and the BIR’s EIS help desk rather than assume a specific field exists.
Sources: Sections 2 and 3, Revenue Regulations No. 006-2026, Bureau of Internal Revenue, as quoted and verified in RR No. 6-2026: Invoices Must Now Show Creditable Withholding Tax as a Separate Item; What Is the BIR Electronic Invoicing System (EIS) and Which Taxpayers Must Comply? for the EIS framework and Section 237-A coverage.