BIR compliance software built for Philippine tax law — not retrofitted from a foreign accounting system.

We replace. We build. We optimize.

Every line of code we write is yours at cutover. No license. No annual increase. No lock-in.

What does CAS registration mean and do we need it?

Any business using computerized accounting must register with BIR as a CAS under RMO 9-2021. Without it, your books are not legally recognized.

CAS registration requires submitting the system's source documents, journal formats, and output samples to your BIR Revenue District Office. We generate the complete registration package — technical specifications, sample outputs, and the application form — from your running system. Once accredited, we track renewal triggers so a system upgrade does not catch your compliance team off guard.

Does your system support BIR EIS e-invoicing under RR 11-2025?

Yes. The system transmits structured e-invoice data to the BIR EIS portal within the required window — built in, not a separate integration.

RR 11-2025 mandates electronic submission of invoice data to the BIR Electronic Invoicing System. Large taxpayers face a 31 December 2026 deadline; medium taxpayers follow in 2027. The transmission schema, unique invoice reference number, and real-time posting to the BIR EIS are all built into the billing layer from day one. A top-ranked Philippine private hospital runs this in production today.

How does the system generate BIR Form 2307?

Every withholding transaction posted through AP creates a 2307 certificate for that vendor — no manual assembly, no month-end reconciliation run.

BIR Form 2307 (Certificate of Creditable Tax Withheld at Source) is generated per vendor per month from your posted accounts payable transactions. Vendors receive their certificates on a schedule you set. The annual 1604E alphalist is compiled automatically from the same source. Your bookkeeper stops rebuilding the certificate from printed vouchers.

Can the system file our monthly 2550M VAT return directly?

The system generates a completed, BIR-ready 2550M from your posted transactions. Your accountant reviews and files; we produce the data in the required format.

We generate the monthly 2550M and quarterly 2550Q from your actual AP and AR postings — not from an import. The summary list of sales and purchases (SLSP) is compiled from the same source. Your accountant reviews the computed figures before filing. We do not wire to eBIRForms by default but the export format is compatible.

What BIR forms does the system cover?

The system generates 2307, 2550M, 2550Q, 1604E, 1702, the SLSP, and the daily BIR journal — every statutory output a VAT-registered Philippine entity files.

Coverage is determined during scoping. Standard inclusion: withholding (2307, 1604E), VAT (2550M, 2550Q), annual ITR (1702 RT or MX depending on entity type), SLSP, BIR journal, and the subsidiary ledger in BIR-prescribed CSV format. If your operation involves government contracts, the 1600 withholding on payments to government is added at no extra build cost.

How long does it take to get BIR accreditation after the system goes live?

BIR RDO processing timelines vary; the standard is 15–30 working days after complete submission. We prepare the submission package; you file it.

We generate the system's technical description, sample journal outputs, and supporting documents in the format BIR requires. Processing time depends on your RDO's queue and whether they request clarifications. We support the clarification round at no additional cost. You operate the system immediately on go-live; the formal accreditation follows.

What happens during a BIR audit?

The system produces every document a BIR examiner can legally request — alphalist, subsidiary ledger, sales journal, purchase journal, and invoice copies — in the format BIR specifies.

A BIR Letter of Authority (LOA) requests specific records for a defined period. The system retrieves the alphalist, CWT summary, subsidiary ledger, and sales and purchases journals for any date range in minutes. EIS invoice copies are available as registered electronic originals. Your accountant does not reconstruct records from printed stubs.

Does the system handle VAT-exempt transactions and senior citizen discounts?

Yes. Zero-rated VAT, VAT-exempt, and SC/PWD discount transactions each post to the correct tax classification and appear correctly in the 2550M output.

Philippine VAT rules distinguish zero-rated (e.g., export), VAT-exempt (e.g., medicine under RA 10963), and subject-to-VAT transactions. The system maps each transaction type correctly at posting so the 2550M breaks out input and output VAT accurately. Senior citizen (RA 9994) and PWD (RA 10754) discounts post with the 20% deduction applied before VAT, and the reimbursement summary is generated in BIR format.

Can the system integrate with our existing payroll for withholding on compensation?

Yes. Payroll withholding on compensation feeds the 1601C monthly remittance and the 2316 certificates generated at year-end for each employee.

If you build the payroll module with us, compensation withholding is a single data flow. If you have an existing payroll system, we map its output into the withholding ledger. The monthly 1601C remittance and the year-end 2316 for each employee are generated from the same source.

What if we are a non-VAT registered business?

Non-VAT entities use the percentage tax regime. The system generates BIR Form 2551Q quarterly, and the annual ITR uses the 1701 or 1702 series depending on your entity type.

Under the TRAIN Law, non-VAT registered businesses with gross sales below the ₱3M VAT threshold file BIR Form 2551Q for percentage tax. We configure the tax regime at scoping. Mixed-activity entities — partly VAT, partly percentage — are handled at the transaction level.

How does the system handle the books of accounts requirement?

General journal, general ledger, cash disbursements journal, and cash receipts journal are produced in BIR-prescribed format — all from posted transactions.

BIR requires VAT-registered entities to maintain books of accounts in a specific format. Computerized books must match the registered system's journal definition exactly. We configure the journals to match BIR's requirement during scoping. The subsidiary ledger for every account — AP, AR, fixed assets — is queryable by period.

How much does a BIR compliance build cost?

You own a BIR compliance build outright for one fee — typically 30–50% of a five-year foreign accounting subscription for the same scope, with no per-user licence. Optional ongoing support is ₱50K–250K/month with no lock-in. Your exact scope and price are confirmed on the first call.

The one-time build cost covers the entire compliance output set scoped for your entity type — CAS accreditation package, all statutory forms, EIS integration, and the books of accounts. There is no per-user fee and no annual licence increase. Optional ops support covers BIR calendar monitoring, form updates when BIR revises the schema, and year-end alphalist production.

Is Orkids' system listed as a BIR-accredited CAS?

We build and register each client's system under their own CAS accreditation — not a shared third-party accreditation. The accreditation is yours.

BIR CAS accreditation is entity-specific. When we build your accounting system, we prepare the documentation for your entity's registration — the system is registered in your name, to your RDO. You hold the Certificate of Accreditation. This is distinct from commercial accounting software that holds a single BIR accreditation for all of its users.

How do regulatory updates — new BIR issuances, revised forms — get applied?

Form revisions and new BIR issuances are applied as a configuration update, not a new build. If EIS schema changes, we update the transmission layer.

BIR regularly revises forms and issuances — the 2307 format changed in 2021, the SLSP format changed in 2022, and EIS requirements are still being refined. Under optional ops support, we monitor BIR issuances and apply configuration updates before the effective date. If a regulatory change requires a structural data model change — not just a form layout — we scope it separately.

Does the system cover BIR compliance for businesses with multiple entities or branches?

Yes. Multi-entity and multi-branch setups are handled at the data model level — each entity files independently, branch data consolidates correctly.

Conglomerates and multi-entity groups need separate BIR filings per registered entity. We model each entity's books independently while sharing master data where it makes sense — chart of accounts, vendor list, employee records. Inter-company transactions are flagged and eliminated at consolidation. Each entity's 2550M, 1702, and SLSP are generated separately.

What industries do you build BIR compliance systems for?

We build for manufacturing, distribution, retail, healthcare, food and beverage, construction, and professional services — any Philippine VAT-registered entity.

BIR compliance requirements are substantially the same across industries for VAT-registered entities, but the transaction types differ. A manufacturer has raw material procurement, WIP valuation, and finished goods — the SLSP for input VAT runs large. A hospital mixes VAT-exempt medicine sales with VAT-subject professional fees. We configure the tax mapping per industry during scoping.

Can the system replace Taxumo or a similar form-filing tool?

Yes. Taxumo generates forms from data you enter manually. We generate the same forms from your posted transactions — no re-entry, no reconciliation step.

Taxumo and similar tools are form-layer solutions: you input totals, they produce BIR forms. Our system generates forms from the underlying transaction ledger — AP postings, AR postings, journal entries. The 2307, 2550M, and SLSP tie directly to posted records. If BIR questions a figure, the answer is a ledger drill-down, not a spreadsheet reconstruction.

How does the system handle BIR requirements for importers and businesses with customs transactions?

Import VAT and customs duties are classified at the transaction level, posted to the correct BIR tax account, and flow correctly into the 2550M input VAT schedule.

Import VAT paid at Bureau of Customs is an allowable input tax credit for VAT-registered importers. We configure the purchase journal to record the BOC official receipt number, the import entry number, and the VAT amount paid — exactly what BIR requires to substantiate the input tax claim. The importation schedule in the 2550M is populated from these postings.

Does the system support the quarterly income tax return (1702Q)?

Yes. The quarterly ITR (1702Q) is generated from your running income and expense ledger — no separate computation outside the system.

Under the Philippine Tax Code, corporations file quarterly income tax returns (1702Q) for the first three quarters and an annual return (1702) for the full year. We generate both from the same trial balance. Minimum corporate income tax (MCIT) tracking is included where applicable. The excess input tax carry-over and other tax credits are computed from the ledger.