BIR Compliance

The sentence that matters most is the first one. Kassly is not a BIR-accredited CAS or POS system. It tracks your transactions and stock and produces records in the format the BIR expects, and the receipts you hand customers still come from your own BIR-registered receipts or invoices.

That is not a hedge. It is the state of the software, and everything else on this page follows from it.

This page is general information about what the software does. It is not legal or tax advice. It cannot tell you what your own registration obliges you to do, because that depends on how your business is registered. For that, ask your accountant or your RDO.

Three different things get called "BIR-ready"

Vendors and forum posts lump these together. They are not the same thing, and knowing which is which is most of the confusion gone.

	What it is	Who it attaches to
An accredited CAS or POS	A system the BIR has formally permitted to issue official receipts and invoices, with a Permit to Use for the machine	The software, and then the specific machine
BIR-format reports	Reports laid out the way the BIR expects — Z readings, sales summaries, VAT breakdowns — kept for your records and given to your bookkeeper	Nobody. Any system can produce them
Registered receipts (OR/SI)	The receipts or invoices you issue to customers, registered with the BIR. Usually printed booklets for a small business	You, the taxpayer

Kassly is firmly the middle one. It does not make you the first one, and it does not replace the third.

What Kassly does

	Where	What it costs
Computes and stores VAT on every sale, per line, with the VATable / exempt / zero-rated split	Everywhere. See Tax settings	Free
Senior Citizen and PWD discounts to the statutory formula, with the cardholder's ID number and name recorded	At the counter. See Discounts	Free
An unbroken, gap-free receipt number series per terminal, with gaps detectable after the fact	Receipts	Free
A tamper-evident record of who did what, chained so an altered entry shows	Audit Trail. See Audit logs	Free
Refuses to hard-delete a sale, a payment, a return, a stock movement or a shift	Everywhere	Free
X and Z readings per shift, and a sealed business-day Z per terminal	X and Z readings	Cash Drawer & Expenses, ₱300 per branch each month
General Journal, General Ledger, Trial Balance and Cash Disbursements Journal	Books of accounts	Free
Balance Sheet and Income Statement	Financial statements	Free
Summary List of Sales and Summary List of Purchases, by quarter	Sales → BIR Reports	Business Reports, ₱400 per branch each month

What Kassly does not do

Read this list rather than assuming. Every line on it has produced a support ticket from somebody who assumed the opposite.

Kassly does not	Which means
Issue official receipts or sales invoices	Keep issuing your BIR-registered receipts to customers. Kassly's printout is a transaction record, and says so on its face
Make you accredited, or apply on your behalf	Accreditation and a Permit to Use are separate processes that happen outside Kassly
Register your books	Whether manual, loose-leaf or computerised, registering books is between you and your RDO. Kassly generates documents; it does not register them
Transmit anything to the BIR	Nothing is filed, nothing is submitted, and no invoice is sent to the BIR's electronic invoicing system. Every return is still filed by you or your accountant
Give you an e-journal you can download	There is no e-journal export in the app
Produce every book the BIR may ask for	The four books listed above are what Kassly builds. A Cash Receipts Journal, a Sales Journal, a Purchases Journal and subsidiary ledgers are not produced as separate books
Know your registration	Kassly cannot tell whether you are VAT or percentage-tax registered, whether your branch is separately registered, or what your RDO expects of you. You tell it, in Store settings, and it takes your word
Give tax advice	Including anything on this page

Tracker mode and accredited mode

Every store starts in what the code calls tracker mode, and almost certainly stays there. In tracker mode Kassly deliberately withholds every BIR-regulated field, so nothing it prints can be mistaken for a fiscal document.

	Tracker mode	Accredited mode
Receipt heading	TRANSACTION RECORD	The invoice type — CASH INVOICE, CHARGE INVOICE, SERVICE INVOICE or INVOICE
TIN, MIN, PTU, permit number	Never printed, even when they are filled in	Printed
VAT breakdown on the receipt	Not printed	Printed
Receipt footer	This is not a BIR invoice.	That line goes, replaced by the accredited-supplier block — supplier name, TIN, accreditation number, permit numbers
Z reading title	INTERNAL Z-READING, footed Internal tracking document — not a BIR report.	Z-READING REPORT
Daily Z footer	This is not a BIR Z-reading.	No such line
Accumulated Grand Total	Stays at zero. The lifetime accumulator does not accumulate	Accumulates, and prints on the Z
Books of Accounts in the menu	Hidden. The books are still being built from your transactions	Shown under Sales
Terminal on a sale	Optional	Required — a sale with no terminal is rejected

What does not change is the part that matters for your bookkeeper. VAT is computed and stored either way. Statutory discounts work either way. The readings are sealed and the books are built either way. So if accreditation ever does land, there is nothing to reconstruct — the numbers were right all along.

Accredited mode is not a setting you can switch on, and it is not a cosmetic preference. It is turned on for a store only when the paperwork behind it exists: BIR accreditation on the software side, and a Permit to Use for the machine on yours. Printing a TIN, a machine number and a permit number on a document that no permit covers is considerably worse than printing none of them. If you want to know where the software stands, ask support. If you want to know where you stand, ask your RDO.

Where each BIR identifier lives

If you are filling these in ahead of time, this is the map.

Field	Where you enter it
Registered business name, address, TIN, BIR Permit No.	Settings → Store Settings
MIN, PTU Number, serial number, device brand and model, registration date	Management → Terminals, per terminal
Business Day Start — the cutover that defines a business day for the daily Z	Settings → Store Settings

A branch can in principle carry its own TIN, permit and Certificate of Registration address, for a separately registered branch. There is no screen for those yet; until there is, every branch falls back to the store-level values.

Fill the TIN in before you print anything for anyone. On a book of accounts a blank TIN is left off the letterhead entirely rather than printed empty, which is easy to miss until an examiner points at it.

The records an examiner tends to ask for

Record	Where	Note
Books of accounts	Books of accounts	Derived on demand from your transactions; downloadable as CSV or PDF
Financial statements	Financial statements	Balance Sheet and Income Statement
Audit trail	Audit logs	The CSV export carries the chain fingerprints; pulling it is itself recorded
End-of-day readings	X and Z readings	Per shift, and a sealed business-day Z per terminal
Receipt series, with any gaps identified	Receipts	The series runs unbroken per terminal by design. A gap report exists, but has no screen
Voided sales	Sales → Transactions, and in the Voided Sales line of every reading	A separate void report exists but has no screen
Senior Citizen / PWD sales, listed out	No screen	A statutory-discount sales book exists but has no screen
VAT declaration figures for 2550M or 2550Q	No screen	Same

That last group is worth being blunt about. Kassly builds the VAT declaration aggregates, the receipt-gap report, the void report and the statutory-discount sales books, but the only ones with a page in the app today are the Summary List of Sales and the Summary List of Purchases, on Sales → BIR Reports, chosen by year and quarter. For the rest, ask support to pull them for you.

What stays yours to do

Nothing on this list is something software can do for you.

1. Register your business, and register your receipts or invoices with the BIR.
2. Issue your registered receipts to customers. Kassly's transaction record sits alongside them; it does not replace them.
3. Register your books of accounts in whichever form your RDO requires.
4. Keep your records for the ten years the BIR requires. Kassly protects sales, receipts, payments, stock movements and Z readings from permanent deletion on that basis, but the obligation is yours.
5. File and pay your returns on time, using Kassly's figures as the input, not as the filing.
6. Ask, when in doubt. Your accountant is cheaper than an assessment, and your RDO answers questions.

Limits to be honest about

Limit	What it means
No accreditation	Kassly is not an accredited CAS or POS. Nothing on any screen or printout should be read as claiming otherwise, and if you find something that does, tell support
Accreditation is not self-serve	There is no toggle. It is set per store, and only against real paperwork
Nothing here is per branch	Every book of accounts covers the whole store. A reading covers one shift or one terminal. There is no branch-level view of either
Pre-Kassly history is absent	There are no opening balances and no year-end close. Whatever your business did before you started using Kassly is not in these documents
Some BIR outputs have no screen	The daily Z reading, the void report, the receipt-gap report, the statutory-discount sales books and the VAT declaration figures all exist without a page. Support can pull them
Kassly settles nothing with the BIR	Every question that turns on your own registration — VAT status, branch registration, which books you must keep, whether you may issue machine-generated receipts at all — is a question for your RDO or your accountant, and Kassly's answer to it is whatever you typed into Settings

Take a CSV of your books, a Z reading and a receipt to your accountant before your first filing that leans on any of them, and let them tell you what else they need. That conversation in month one is far cheaper than the same conversation in month twelve.