June has a way of sneaking up on Finance Managers. Q1 filings are done, the annual ITR is signed and sealed, and it finally feels like there's room to breathe. Then someone on the team asks: "When did we last review our CAS compliance?"

For businesses operating a Computerized Accounting System in the Philippines, mid-year is exactly the wrong time to be caught off guard. The BIR doesn't pause between audit cycles, and with the EIS e-invoicing deadline coming at the end of December 2026, the second half of the year will move fast. A quiet June is the best time to run a deliberate, structured review of your CAS setup, before the pressure builds.

This checklist is designed specifically for Philippine SMEs running a BIR-registered CAS. Whether you're on SAP Business One, a legacy system, or something in between, use this guide to identify compliance gaps now, while you still have time to fix them.

What BIR CAS Requirements Philippine Businesses Must Maintain Year-Round

Most Finance teams treat CAS compliance as a one-time registration event: submit BIR Form 1900, secure the Permit to Use, and consider the matter closed. That's not entirely wrong. The Permit to Use a CAS is valid indefinitely, provided your system doesn't undergo significant changes or upgrades without BIR approval.

The problem is that businesses change constantly. New branches open. Product lines are added. ERP modules are upgraded. Workflows are reconfigured. Each of these changes can trigger a material modification to your CAS that legally requires you to file for a system enhancement with the BIR, and many companies miss this entirely.

Here's what BIR CAS requirements in the Philippines actually cover on an ongoing basis:

• Integrity of financial records — all transactions must be recorded accurately, completely, and in chronological order within the system
• Audit trail maintenance — your CAS must generate unalterable logs of every transaction entry, modification, and deletion
• Data retention — electronic records must be retained for a minimum of ten years from the date of filing, per BIR regulations (revised from the previous six-year standard under updated EIS rules)
• Reportability — the system must be able to produce BIR-required reports: Sales Journal, Purchase Journal, General Ledger, Subsidiary Ledger, and the Summary List of Sales and Purchases (SLSP) on demand
• System change notification — any modification or enhancement to a previously approved CAS must be reported to the BIR with supporting documentation, including a letter detailing the changes and a photocopy of the previously issued Permit to Use

If your team has made system changes in the past 12 months, even routine software version updates, this is the first thing to verify.

Your Mid-Year BIR CAS Compliance Checklist

Walk through each item below with your Finance Manager, IT head, or ERP administrator. Flag any gap for immediate remediation.

1. Permit to Use: Is It Still Accurate?

Pull out your original BIR Permit to Use CAS. Confirm that the system described in the permit still matches your current setup: the software name, version, modules in use, and the Revenue District Office (RDO) on record. If you've migrated to a newer version of your ERP, for example, upgrading SAP Business One from an older patch level to the current release, this constitutes a system modification and may require a fresh BIR application.

Action: Compare your current ERP version against what is listed on your Permit to Use. If they don't match, prepare a modification application with your BIR-accredited ERP partner.

2. Registered Modules and Components

Your Permit to Use covers specific CAS components, typically the core accounting modules, invoicing, and reporting functions. If your business has added new modules since registration (say, a Warehouse Management System, a Point-of-Sale integration, or a new payroll component), those additions may not be covered under your original permit.

Action: List all active ERP modules your business currently uses. Cross-check against your original CAS registration. Identify any additions that have not been disclosed to the BIR.

3. SLSP Generation and Accuracy

The Summary List of Sales and Purchases (SLSP) is one of the BIR's primary tools for cross-referencing taxpayer data. Your CAS must generate an accurate SLSP, broken down by TIN, name of customer or supplier, gross amount, VAT amount, and net amount, every quarter.

Common errors that surface at mid-year:

• Suppliers or customers recorded without a valid TIN
• VAT-exempt transactions miscategorized as VATable
• Import purchases not captured in the Purchase Journal
• Duplicate entries from manual adjustments made outside the system

Action: Run your Q1 and Q2 SLSP reports now. Reconcile against your BIR Form 2550Q (Quarterly VAT Return) filings. Correct discrepancies in the system before year-end, when these errors become exponentially harder to unwind.

4. Expanded Withholding Tax (EWT) Records ; Form 2307 Reconciliation

If your business withholds EWT from suppliers (at rates of 1%, 2%, 5%, or 10% depending on the nature of the transaction), your CAS must maintain a complete record of all BIR Form 2307 certificates issued. These must tie back to your BIR Form 1601-EQ quarterly filings and ultimately to your Annual Information Return (BIR Form 1604-E).

Mid-year is the ideal time to run a reconciliation: pull every 2307 issued in Q1 and Q2 from your ERP, sum the EWT amounts by income payment category, and match against what was filed and remitted. Discrepancies here are a common audit trigger.

Action: Generate an EWT summary report from your CAS for Q1 and Q2 2026. Compare totals against 1601-EQ filings. Flag any unissued 2307s for certificates due to suppliers.

5. Audit Trail Integrity

Your BIR-registered CAS must maintain a complete, tamper-proof audit trail. This means tracking who posted a transaction, when it was posted, whether it was modified, and by whom. If your system allows users to delete posted journal entries or overwrite invoices without creating a system log, your CAS may not meet BIR standards.

Action: Ask your ERP administrator to generate an audit trail report for a sample of transactions from Q1. Verify that the trail is complete, timestamps are accurate, and no transactions have been manually edited outside the system without a corresponding log entry.

6. Data Backup and Disaster Recovery

BIR regulations require that electronic records be accessible for audit at any time. If your data is stored only on a local server with no offsite backup, a hardware failure could leave you non-compliant and exposed to penalties, independent of any audit finding.

Action: Confirm that your CAS data is backed up at minimum weekly to an offsite or cloud location. Verify that your IT team can restore a backup within a defined recovery time objective. Document this process for the BIR's reference during an audit.

The EIS Factor: Why June 2026 Is Not Too Early to Prepare

Here is the piece of news that every Philippine Finance Manager should have on their calendar: under Revenue Regulation No. 26-2025, businesses using a CAS, including those on SAP Business One, are included in the first phase of the BIR's Electronic Invoicing System (EIS) mandate, with a compliance deadline of December 31, 2026.

This is not a drill. The mandate requires eligible businesses to issue structured electronic invoices in a BIR-prescribed JSON format and transmit them to the EIS platform within three calendar days of each transaction. PDF invoices will no longer qualify as e-invoices under this framework.

For SMEs currently running a CAS, the EIS rollout means:

• Your current invoice-generation workflow needs to connect to the BIR's EIS portal
• Your ERP or CAS must be capable of generating invoices in the required JSON format
• You'll need a BIR-certified software solution or integration partner to manage the transmission
• Your team will need training on the new submission and error-correction process

If you're running SAP Business One with a BIR-accredited partner, the integration path already exists, but it requires configuration, testing, and BIR portal registration that takes time to complete properly. Six months sounds like a lot. In ERP implementation terms, it isn't.

Action: Contact your SAP B1 partner now to assess your EIS readiness. Confirm whether your current CAS setup is already registered on the EIS Certification Portal (eis-cert.bir.gov.ph) and what steps remain before the December deadline.

Common CAS Compliance Gaps Found in Philippine SME Audits

Based on typical BIR audit findings for SMEs using computerized accounting systems, these are the gaps that most frequently result in deficiency assessments:

• Unregistered system enhancements — using a newer ERP version than what's listed on the Permit to Use
• Missing or incomplete SLSP — especially for businesses with high transaction volumes in retail or distribution
• Manual adjustments made outside the CAS — journal entries posted directly to the books without going through the system, breaking the audit trail
• TIN mismatches — suppliers listed in the CAS without a valid or accurate TIN, creating SLSP errors that can trigger a letter-notice
• Delayed or incomplete EWT remittance — 2307s issued but corresponding tax amounts not remitted through the 1601-EQ on time

None of these are catastrophic on their own. All of them are far easier to fix in June than in November, when your team is simultaneously closing out Q3, preparing for year-end, and managing EIS go-live pressure.

How SAP Business One Keeps Your CAS Compliant Automatically

One of the structural advantages of running SAP Business One as your CAS is that compliance controls are built into the workflow, not bolted on as an afterthought.

SAP B1 generates a complete, unalterable audit trail for every transaction. It produces SLSP-ready reports in the BIR's required format. Its A/R Invoice and A/P Invoice modules enforce TIN capture at the point of entry. And with Superspeed's BIR-accredited CAS implementation, your system is registered, documented, and configured to meet Philippine regulatory requirements from day one.

For the EIS mandate specifically, SAP Business One's architecture supports the integration required to connect your invoicing workflow to the BIR's EIS platform, making it one of the most practical starting points for businesses that need to be compliant by December 2026.

Why Superspeed?

Superspeed Solutions & Services, Inc. is a BIR-accredited SAP Gold Partner based in Antipolo City, with a track record of CAS implementations across distribution, manufacturing, retail, and professional services companies throughout the Philippines. We don't just implement the software. We guide your team through BIR registration, SLSP configuration, audit trail setup, and now EIS integration, so you're covered at every compliance checkpoint.

If your mid-year checklist has turned up gaps, or if you simply want the confidence of knowing your CAS is fully airtight before Q3, the best next step is a conversation with our ERP specialists.