Do You Need a Registered Cash Register Sales Book for Every Machine? BIR Bookkeeping Rules Under RR No. 11-2004

Revenue Regulations No. 11-2004, Section 10.1.1, requires a duly registered cash register sales book for every cash register machine (CRM) a business uses — one registered book per machine, showing the columns Section 2.3 of RR No. 10-99 requires — not a single book shared across multiple registers. RMO No. 7-2015’s compromise-penalty schedule lists this as its own line item under Annex C, but the schedule’s compromise-amount column for this specific entry is left blank rather than printing a fixed peso figure.

This is one of several CRM/POS bookkeeping requirements from RR No. 11-2004 that Annex C lists without a stated compromise amount — see BIR Compromise Penalties for CRM and POS Compliance Failures for the related items, and BIR Books of Accounts for how the sales-book requirement fits into the broader bookkeeping picture.

What does RR No. 11-2004 actually require? #

Section 10.1.1 of Revenue Regulations No. 11-2004 states the rule directly: “A duly registered cash register sales book shall be maintained for each machine used, showing the columns required under Section 2.3 of RR No 10-99.” The requirement is per-machine, not per-establishment — a store running three registers at checkout needs three separately registered sales books, each tracking that specific machine’s transactions in the format Section 2.3 of RR No. 10-99 prescribes.

Why this matters during a tax mapping visit: a revenue officer checking a business with multiple registers can find one machine’s sales book properly registered and another’s missing entirely — each unregistered machine is a separate instance of the same violation, not one combined finding.

Why doesn’t the compromise schedule show a peso amount for this? #

RMO No. 7-2015’s Annex C lists “Failure to register Books of Accounts” under Section 10.1.1 of RR No. 11-2004 as its own row, distinct from the general Section 232/235 record-keeping violation, but the compromise-amount column for this row is not populated in the published schedule — unlike most of the other bookkeeping and registration entries around it, which carry specific figures. The exact text as published:

Sec 10.1.1 of RR 11-2004 — Failure to register Books of Accounts. (Revenue Regulations No. 11-2004. Section 10.1.1 — A duly registered cash register sales book shall be maintained for each machine used, showing the columns required under Section 2.3 of RR No 10-99.)

Because no distinct figure is printed, two general provisions are the most likely reference points a revenue officer would apply in practice, though neither is stated as governing this specific line item by name:

How does this relate to CRM/POS machine registration itself? #

Registering the sales book is separate from registering the cash register machine, POS terminal, or Computerized Accounting System (CAS) it belongs to. A business must register the machine or system under the BIR’s current CRM/POS/CAS framework — see BIR Books of Accounts for the manual, loose-leaf, and CAS formats — and separately maintain the per-machine sales book Section 10.1.1 requires. Missing the CRM/POS/CAS sticker or decal on the machine itself carries its own, clearly stated ₱1,000-per-unit compromise under BIR Compromise Penalty Table for Registration, Receipts, and Invoicing Violations — a distinct finding from the sales-book requirement covered here.

Frequently asked questions #

Do I need a separate cash register sales book for each machine? #

Yes. Revenue Regulations No. 11-2004, Section 10.1.1, requires a duly registered cash register sales book to be maintained for each cash register machine used, showing the columns required under Section 2.3 of RR No. 10-99 — one machine, one registered book, not a single combined book covering multiple machines.

How much is the compromise penalty for not registering a cash register sales book per machine? #

RMO No. 7-2015’s Annex C lists this as a distinct violation under Section 10.1.1 of RR No. 11-2004 but does not print a specific peso compromise figure in that line item — unlike most other registration and bookkeeping entries in the same schedule. Confirm the applicable amount with the examining office; the general bookkeeping and catch-all provisions covered above are the most likely reference points.

Does the general books-of-accounts compromise table apply here instead? #

It’s the closest analog. Failure to keep or preserve required records under NIRC Section 232/235 is priced from ₱1,000 to ₱50,000 by gross annual sales — a missing per-machine registered sales book could reasonably be treated as part of that same failure, though the schedule doesn’t say so explicitly for this specific RR No. 11-2004 line item.

Is there a fallback penalty if no specific amount applies? #

NIRC Section 275 sets a general catch-all: any Tax Code or Department of Finance regulation violation with no specific penalty provided carries a compromise of ₱1,000 per violation. This is the floor amount that applies when a more specific line item doesn’t state its own figure.

How is this different from registering the machine itself as a CRM/POS/CAS? #

Registering a cash register machine (CRM), point-of-sale (POS) terminal, or Computerized Accounting System (CAS) with the BIR is a separate step from registering the sales book that records what each machine rings up — see BIR Books of Accounts for the CRM/POS/CAS registration process, and BIR Compromise Penalty Table for the ₱1,000-per-unit penalty for failing to attach the required CRM/POS/CAS sticker or decal.

Summary #

RR No. 11-2004 requires a separately registered cash register sales book for every machine a business runs, but RMO No. 7-2015’s own compromise schedule leaves this specific line item’s peso amount unstated — a gap worth flagging rather than guessing at. The general Section 232/235 bookkeeping table and the Section 275 catch-all are the most plausible fallbacks, but a business found with an unregistered per-machine sales book should confirm the actual figure with the examining revenue office rather than assume either one applies automatically.