EazLink guide
Electronic invoicing vs electronic sales reporting in the Philippines
Why issuing a structured electronic invoice and transmitting sales data to the BIR should be tracked as separate obligations.
Updated 2026-09-06 by the EazLink team. Editorial review: EazLink Editorial Team.
Direct answer
Electronic invoicing is the automated creation and exchange of a system-generated invoice in structured data. Electronic sales reporting is the system-to-system storage, transmission or receipt of invoice data by the BIR. RR 11-2025 defines both. RR 26-2025 gives a deadline to named groups for electronic invoice issuance while retaining separate conditions for electronic sales reporting.
What to remember
- Issuing the invoice and reporting its data are related but separate system events.
- Do not attach one date to both without reading the applicable rule.
- The source system must keep a stable invoice identity across both events.
- Architecture should show buyer delivery and BIR transmission as separate paths.
Two connected workflows
Separating them makes legal scope and system status easier to understand.
| Workflow | Recipient | Technical focus |
|---|---|---|
| Electronic invoice issuance | Buyer | System-generated structured invoice and delivery |
| Electronic sales reporting | BIR | Direct structured data transfer and response |
| Internal accounting | Taxpayer | Books, posting, reconciliation and controls |
Draw two arrows
One arrow goes from the invoice system to the buyer. Another goes from the taxpayer's system to the BIR workflow. They may share the same source record but have different timings and responses.
A buyer delivery failure and a BIR transmission failure should not appear as one generic error.
Use one invoice identity
The buyer copy, accounting posting and sales reporting record should refer to the same commercial document. Adjustments should point back to that document through the approved lifecycle.
Without that identity, finance will compare totals but still struggle to explain individual differences.
Keep statuses separate in EazLink
EazLink can track buyer-facing document state where integrated and the configured BIR workflow state as separate fields.
This avoids telling a user that an invoice failed when only one delivery or reporting step is waiting.
Separate the obligations
- Confirm legal scope for each workflow.
- Map the buyer delivery event.
- Map the BIR reporting event.
- Use one source invoice identity.
- Create separate exception queues.
Quick questions
Is issuing an electronic invoice the same as sending data to BIR?
No. RR 11-2025 defines electronic invoicing and electronic sales reporting separately.
Can both use the same JSON record?
They may share source data, but each workflow has its own recipients, required format, status and evidence.
Which deadline applies to sales reporting?
Check the current regulations for the taxpayer group. Do not infer it solely from the electronic invoice issuance deadline.
Continue the preparation
Sources and verification
Check the current BIR rules and portal notices before making a compliance decision.