01 · INVOICINGInvoices with the right BIR-required information
The usual small-business problem: a Word, Excel or generic invoice template looks professional but may omit information that matters for VAT/Non-VAT treatment, buyer details, transaction details, discounts, tax breakdowns or system-registration information.
After EOPT, the invoice is the principal sales document. BIR rules specify information that needs to appear depending on the taxpayer and transaction. eInvoicePH is designed around those invoice-content rules.
Customer-friendly benefit: You do not have to remember the invoice rules every time you bill. Your setup carries the format consistently.
02 · DOCUMENT CONTROLA serial trail you can actually explain later
The usual problem: duplicated invoice numbers, edited PDFs, deleted mistakes, unexplained gaps, or a “final_v7_revised.pdf” folder that becomes impossible to defend months later.
BIR rules for system-generated invoices require approved series information, and computerized-system rules expect auditable records such as void reports and an activity trail. RR 7-2024 also requires “REPRINT” to be shown on reprinted system-generated invoices.
Customer-friendly benefit: Numbers move in a controlled series, voids remain part of the history, and a reprint stays identifiable instead of pretending to be a brand-new original.
03 · BOOKKEEPINGBooks that are built while you work, not reconstructed at year-end
The usual problem: invoices live in one folder, expenses in another, payments in chat messages, and the books get reconstructed weeks or months later.
eInvoicePH’s Business and Firm plans generate six common computerized books from the transactions already encoded: Sales Journal, Cash Receipts, Purchase Journal, Cash Disbursements, General Journal and General Ledger.
Accuracy note: BIR does not say every taxpayer must use exactly those six. RMO 9-2021 says the appropriate books depend on the business requirements. The product’s advantage is that it can maintain a fuller common set without making you encode the same transaction twice.
Customer-friendly benefit: Your records grow with the business day by day, so year-end becomes an export-and-review job instead of an archaeological dig.
04 · SYSTEM REGISTRATIONLess manual work when registering a computerized system
The usual problem: people buy invoicing/accounting software and only later discover that the BIR registration package asks for samples and an audit trail.
Under RMO 9-2021 and the BIR 2026 Citizen’s Charter, CAS/CBA/components can be registered through ORUS. The documentary checklist includes a sworn statement/system description, sample invoices, sample books, an audit trail and the technical-requirements annex.
eInvoicePH says it generates three useful attachments: sample invoices, sample books and the audit trail. The taxpayer still prepares the other required documents and submits the registration.
Customer-friendly benefit: The system gives you the evidence it can generate naturally, instead of making you manufacture sample output by hand.
05 · YEAR-END COMPUTERIZED BOOKSA cleaner path to the annual ORUS step for computerized books
The usual problem: the annual deadline arrives, but the books are incomplete because the business has been recording transactions somewhere else all year.
For computerized books of accounts, BIR guidance requires annual registration through ORUS within 30 days from the close of the taxable year, unless a valid extension applies. eInvoicePH generates the computerized books, while the taxpayer completes the ORUS registration.
Important: this is not the rule for every type of book. Permanently bound loose-leaf books have a different annual deadline, and manual books are not re-registered every year just because a new year starts.
Customer-friendly benefit: When the ORUS deadline comes, you are working from books that were already being built, not trying to recreate a year in a weekend.