SAP CAS Accreditation & BIR EIS Readiness for S/4HANA in the Philippines

Any SAP S/4HANA, RISE, or GROW system that generates invoices, official receipts, or computerized books of accounts needs BIR accreditation as a Computerized Accounting System (CAS) — a separate step from, and a prerequisite to, EIS e-invoicing readiness. Since RMO No. 9-2021, that no longer means a Permit to Use; it's a registration that ends in an Acknowledgement Certificate, issued within three working days of a complete application. Skip it, and your S/4HANA go-live runs on an unregistered system — an exposure separate from the December 2026 e-invoicing deadline.

Most SAP compliance conversations here jump straight to EIS transmission because it has the harder deadline. CAS accreditation gets less attention precisely because it's older and, on paper, simpler — but it's the registration EIS is built on top of, and SAP project timelines routinely treat it as an afterthought rather than a workstream with its own documentation and re-registration triggers.

What is BIR CAS accreditation, and why does it still matter alongside e-invoicing?

A Computerized Accounting System, under BIR rules, is any system — SAP included — that generates a taxpayer's books of accounts, subsidiary ledgers, and commercial invoices or official receipts electronically rather than through manually printed, pre-approved forms. All Large Taxpayers must run one, and any non-Large Taxpayer using a system that produces General Journals, subsidiary books, or invoicing output through a CRM, POS, or full ERP falls under the same rule.

Historically this meant applying for a Permit to Use (PTU) — BIR Form 1900 — with a live system demonstration before a BIR evaluation team. RMC No. 5-2021 suspended that requirement, and RMO No. 9-2021 formalized the replacement: taxpayers now register their CAS, CBA, or components (including electronic storage systems and middleware) with their Revenue District Office, which issues an Acknowledgement Certificate (AC) within three working days of a complete submission. There's no more pre-approval gate, but the trade-off is post-evaluation: the BIR can examine the system during an audit, and penalties apply if what's running doesn't match what was registered.

That distinction matters for SAP customers specifically. EIS e-invoicing under RR No. 11-2025 names "taxpayers using CAS or CBA with invoicing modules" as one of the categories required to transmit to the BIR's Electronic Invoicing/Sales Reporting System. An S/4HANA system that isn't properly CAS-registered doesn't have a clean starting point for the EIS build — it has two compliance gaps stacked on top of each other.

Does every SAP S/4HANA, RISE, or GROW deployment need a CAS Acknowledgement Certificate?

In practice, yes. Whether you're on RISE with SAP (private cloud S/4HANA), GROW with SAP (public cloud S/4HANA), or SAP Business One as a smaller enterprise, the system generates invoices, official receipts, and computerized books the moment it goes live on real transactions — which is exactly what triggers registration. GROW's less-customized, best-practice delivery model doesn't change the CAS obligation; it only changes how much of the documentation is templated versus bespoke.

SAP Business One ships with a Philippine Tax module built for SME compliance, making its CAS documentation more straightforward. S/4HANA has no equivalent packaged Philippine localization — the same gap that makes EIS integration a build rather than a configuration switch also means the sample invoices, receipts, and audit trail output the BIR checklist asks for have to come from your actual configured system, not a standard country package.

What documents does an SAP implementation need to produce for CAS registration?

The BIR's Checklist of Documentary Requirements, under RMO No. 9-2021's Annex A, asks for:

• A Sworn Statement (or joint sworn statement, if a parent or affiliate owns the licensed software) summarizing the system description.
• Sample computer-generated output — invoices, official receipts, and books of accounts or subsidiary records the system produces.
• Forms, records, and reports specifications, describing how each document type is generated and numbered.
• A completed Standard Functional and Technical Requirements form (Annex B), covering audit trail capability, backup procedures, and system integrity controls.
• Supporting documents: BIR Certificate of Registration, current Annual Registration Fee proof, and — for multi-branch rollouts — the list of branches adopting the system.

For an SAP project, most of this maps onto artifacts a well-run implementation already produces during realization and testing — configured invoice and OR layouts, numbering ranges, audit trail configuration. The gap is usually that nobody packages them for BIR until someone remembers the registration is overdue.

Does a new go-live or an ECC-to-S/4HANA migration require a new Acknowledgement Certificate?

Usually, yes — and it's the detail SAP project teams most often miss. RMO No. 9-2021 distinguishes major from minor system changes. Minor changes — interface tweaks, bug fixes — only need a written notice to the RDO. Major changes — a functionality change, a module addition or removal affecting financial output, or a version/release change with financial impact — require a brand-new registration, with the old AC or legacy PTU surrendered.

Migrating off SAP ECC onto S/4HANA, whether through RISE or GROW, is squarely a major change under that test: it's a different system generating your invoices, receipts, and books, not an upgrade to the one the BIR acknowledged before. The same logic applied to the OR-versus-Invoice reconfiguration many companies made under the Ease of Paying Taxes Act. Treat CAS re-registration as a fixed cutover line item — the AC needs to be in hand before the new system produces official documents, and post-evaluation audits don't care that the project was busy migrating.

How does CAS accreditation connect to BIR EIS readiness?

CAS registration and EIS certification are separate BIR processes, run through separate channels — CAS through your RDO, EIS through the dedicated EIS Certification Portal. But they're sequential in practice: EIS's near-real-time transmission builds on the assumption that invoices come from a properly registered system. Since RR No. 11-2025 names CAS/CBA users with invoicing modules as a covered group, an SAP customer's path typically runs CAS registration (or re-registration, post-migration) first, then the SAP BTP-based integration that extracts, maps, and transmits invoice data to EIS, then EIS's own sandbox testing, e-certification, and Permit to Transmit.

Run these as one coordinated compliance track, not CAS as an IT afterthought and EIS as the "real" tax project — that avoids resubmitting documentation twice when schema mapping turns up a gap the original CAS registration didn't anticipate.

What's the practical sequence for an SAP project team in 2026?

• Confirm your current CAS status first — is there a live PTU or AC on file, and does it match what's actually configured today?
• Treat CAS registration as a cutover deliverable on any RISE or GROW project, ECC migration, or major enhancement, owned by someone on the project, not deferred to finance after go-live.
• Sequence CAS before EIS build work where possible, so the sample output and system description on the Acknowledgement Certificate line up with what gets mapped into the EIS integration.
• Use process mapping to catch what documentation alone won't. SAP Signavio can validate the actual invoice and OR issuance process — multi-branch variations, manual overrides, intercompany billing — before you certify a system description that doesn't match reality.
• If you're still on ECC, mainstream maintenance ends December 31, 2027. A migration driven by that deadline is also the moment to re-register CAS correctly, rather than leaving it unfinished.

Frequently asked questions

Do we still need a Permit to Use for our SAP system? No. Since RMC No. 5-2021 and RMO No. 9-2021, the BIR replaced the Permit to Use with a registration process ending in an Acknowledgement Certificate, issued within three working days of a complete submission. Systems remain subject to post-evaluation during audits, so the documentation still has to genuinely match what's running.

Is CAS accreditation the same as BIR e-invoicing (EIS) compliance? No — related, but separate. CAS/CBA registration authorizes your system to generate invoices, official receipts, and books of accounts electronically. EIS compliance under RR No. 11-2025 is the additional requirement to transmit that invoice data to the BIR's Electronic Invoicing/Sales Reporting System. CAS-registered systems with invoicing modules are explicitly named as one of the groups covered by the e-invoicing mandate.

Does moving from SAP ECC to S/4HANA require a new Acknowledgement Certificate? Generally, yes. Under RMO No. 9-2021's major-versus-minor distinction, a new system generating your financial output — which an ECC-to-S/4HANA migration is — counts as a major change requiring fresh registration, with the prior PTU or AC surrendered.

Who has to register a CAS in the first place? All Large Taxpayers must use a registered CAS, and any non-Large Taxpayer running a system that produces general journals, subsidiary books, or invoices through a CRM, POS, or ERP — SAP included — must register too. There's no exemption for standardized, template-based deployments like GROW with SAP.

What happens if our SAP system isn't properly registered? Since registration is no longer pre-approved, the BIR finds gaps during post-evaluation — typically an audit. Penalties apply under existing revenue issuances, and an unregistered or misregistered system undercuts the EIS transmission built on top of it, since the invoicing module was never formally acknowledged.

CAS accreditation is the paperwork foundation underneath every SAP invoice, official receipt, and book of account your business produces — and it needs to be right before EIS transmission becomes the priority. Appcentric works with RISE, GROW, and SAP Business One customers on both tracks together. Talk to our team about sequencing your SAP system's CAS registration and EIS readiness correctly.