MYOB e-Invoicing in the Philippines: Frequently Asked Questions
1. What is e-invoicing in the Philippines?
It is the mandated process of generating a structured, digitally signed invoice and transmitting that data to the BIR’s Electronic Invoicing System (EIS). A PDF or scan does not count as an e-invoice.
2. Why does an MYOB user need an e-invoicing solution?
MYOB records and issues your sales documents, but BIR reporting requires a specific JSON format, a digital signature and a live connection to EIS. An integration layer bridges that gap.
3. Does MYOB natively submit invoices to BIR EIS?
You should not assume so. The Philippine EIS schema is its own build, so most MYOB setups need a certified connector or middleware. Check your MYOB version and edition with the vendor.
4. How does Advintek work with MYOB?
Advintek receives invoice data from MYOB, maps it to the BIR schema, signs it, transmits it to EIS and returns the result so your finance team can see what was accepted or rejected.
5. What is the difference between EIS and ESRS?
EIS is the BIR platform. ESRS, the Electronic Sales Reporting System, is the obligation to transmit sales data to that platform in structured form. Both apply to covered taxpayers.
6. What regulations govern this?
Revenue Regulations 11-2025 and 26-2025, built on the TRAIN Law, the EoPT Act and the CREATE MORE Act.
7. Is my MYOB business in scope for Phase 1?
Phase 1 covers e-commerce and internet businesses, taxpayers under the Large Taxpayers Service, large taxpayers under the EoPT Act, and users of CAS, CBA or invoicing software. Using MYOB for invoicing may place you in the last group.
8. What is the Phase 1 deadline?
31 December 2026. Plan certification and testing well before that date.
9. Are micro and small businesses exempt?
Micro-taxpayers are exempt for now unless they already use an electronic invoicing system. Small is not the same as micro, so confirm your BIR classification.
10. Are exporters covered by the December 2026 deadline?
No. Exporters fall under a later phase that will be set by a separate Revenue Regulation, but they will eventually need e-invoices too.
11. Do all branches need to comply?
Yes. Every branch, identified by its four-digit branch code in the TIN, must issue e-invoices and be configured separately.
12. Does the buyer type change my obligation?
No. B2B, B2C, B2G and export transactions all require an e-invoice from a covered seller. Only the content of the data changes.
13. How does data move from MYOB to the BIR?
MYOB generates the sale, the integration converts it to BIR JSON and signs it, and the signed invoice is sent to EIS. The BIR validates it and returns a unique ID.
14. Which MYOB versions can be integrated?
Integration options depend on the MYOB product and how it exposes data, such as API access or export files. Advintek can assess your specific version during scoping.
15. Do I need to change my chart of accounts or item setup?
Usually only minimally, but items, tax codes and customer records should be consistent so they map cleanly to BIR fields.
16. How are MYOB tax codes mapped?
VAT, zero-rated and exempt codes are matched to the BIR tax categories so each line carries the right treatment and the invoice totals reconcile.
17. Where do I record the buyer's TIN?
Store it in the customer card or a custom field. For B2B invoices the buyer TIN is mandatory.
18. How are discounts handled?
The BIR schema separates Senior Citizen, PWD, Regular and Special discounts. If MYOB holds a single discount value, it may need to be classified during mapping.
19. What about withholding tax?
There are four withholding buckets in the schema: Income Tax Withheld, CWT, Business Tax and BPT. Your setup should capture these as separate values.
20. Can I use foreign currency invoices?
Yes, but each invoice must show the transaction currency and the PHP equivalent.
21. How long does implementation take?
Budget about six to ten weeks end to end, covering mapping, the Acknowledgement Certificate, certification and the Permit to Transmit.
22. What format and signature are required?
Structured JSON signed with JWS using RS256.
23. What is the Permit to Transmit?
The BIR’s approval to send live invoice data to EIS, granted after certification and sandbox testing.
24. What is the Acknowledgement Certificate?
The BIR’s acknowledgement of your invoicing software, filed at branch level. Preparing it, including the compliance matrix, typically takes several weeks.
25. What is the three-day rule?
Invoice data must reach the BIR within three calendar days of the transaction date.
26. What are the volume limits?
Up to 1,000 line items per invoice and up to 100 invoices per API call.
27. What about key management?
Your private signing key stays in your control. The BIR also rotates its public key, so rotation must be handled as a routine operational event.
28. What happens if the BIR rejects an invoice?
The rejected payload goes into an error queue. Fix the data and retransmit under the same invoice ID. The customer’s copy is unaffected unless the content itself was wrong.
29. Can I edit an invoice after it is transmitted?
No. Corrections are made through credit notes, debit notes, or cancel and reissue.
30. What are the penalties?
Failure to issue and late or failed transmission both carry fines, and serious or repeated violations can lead to imprisonment or closure. Responsible officers can be personally liable.
31. How long do I keep e-invoices?
For 10 years, as the full signed record rather than only the BIR unique ID.
32. Can I continue manual invoicing in MYOB?
Only until you go live on EIS. After that, covered transactions must use the e-invoicing process.
33. Is there an incentive for setting this up?
CREATE MORE allows an additional deduction for reporting system costs, subject to eligibility. Check with your tax adviser.
34. How do I start?
Contact Advintek to review your MYOB environment, confirm scope and build a timeline to the 31 December 2026 deadline.
