How to Avoid Being Flagged as a BIR RAFT Ghost-Receipt Risk: A Compliance Checklist

A legitimate small or medium business avoids being mistakenly flagged as a BIR “ghost receipt” supplier or buyer by verifying every new supplier’s BIR registration before booking a purchase, keeping independent proof (delivery receipts, service reports) that each transaction actually happened, and reconciling RELIEF SLSP figures against its financial statements before filing. These are the same data points the BIR’s Run After Fake Transactions (RAFT) program and the risk-based audit selection under RMO No. 22-2026 rely on — so closing the gaps yourself is the most direct way to stay out of that review queue.

Why a legitimate business can end up in RAFT’s line of sight #

RAFT was built to catch the trade in fictitious receipts, but its screening tools don’t start by asking who’s guilty — they start by asking whose numbers look unusual, and an honest business with sloppy documentation can produce the same red flags as a real ghost-receipt scheme. The BIR has used a 30% threshold test on claimed deductions and input VAT as one such screening tool, per practitioner commentary on Section 248(B) of the National Internal Revenue Code, which treats a substantial overstatement of deductions as prima facie evidence of a false return. As the statute itself provides:

“A substantial underdeclaration of taxable sales, receipts or income, or a substantial overstatement of deductions, as determined by the Commissioner pursuant to the rules and regulations to be promulgated by the Secretary of Finance, shall constitute prima facie evidence of a false or fraudulent return.” — Section 248(B), National Internal Revenue Code

Layered on top of that is RMO No. 22-2026, the BIR’s consolidated Audit Program issued August 24, 2026, which formalizes system-assisted, risk-based selection of “Priority Cases” — taxpayers whose filed-return data shows unusual reporting patterns, including sharp drops in reported sales or VAT payments, spikes in exempt or zero-rated revenue, and by extension the kind of RELIEF SLSP data mismatches covered separately in why RELIEF SLSP mismatches with your financial statements trigger a Letter Notice. None of this proves wrongdoing on its own — but it explains why documentation quality, not just honesty, determines whether a legitimate business gets swept into a review meant for ghost-receipt sellers and knowing buyers.

Verify a new supplier’s BIR registration before you book the purchase #

The single highest-leverage habit against ghost-receipt exposure is checking a supplier’s BIR registration before the invoice is ever recorded, not after an examiner asks about it. Only a purchase from a validly registered supplier, invoiced on a properly authorized receipt, generates a deductible expense or a creditable input VAT claim in the first place.

1. Request the supplier’s BIR Form 2303 (Certificate of Registration) and confirm the registered business name, TIN, registered address, and line of business match the supplier actually invoicing you — a mismatch between the CoR’s registered activity and what’s being sold is itself a warning sign.
2. Confirm the receipt or invoice traces to a valid Authority to Print (ATP) or an accredited CRM/POS system. Under RMC No. 68-2015, all cash register and point-of-sale machines or receipting software must be accredited with the BIR before use; a supplier that cannot show accreditation for the machine or system that generated your receipt is issuing documents the BIR itself may not recognize as valid.
3. Check that the RDO on the CoR matches where the supplier is actually operating. A supplier registered in one RDO but transacting heavily from an unrelated location, with no branch registration to explain it, is a pattern worth a second look before the relationship scales up.
4. Be more careful, not less, with newly registered suppliers offering unusually large or urgent transactions. A brand-new registration paired with an immediate high-peso invoice is exactly the profile ghost-receipt sellers use — legitimate new suppliers exist too, which is why the verification steps above matter more here than for an established counterparty.
5. Keep a dated copy of everything you verified. If a supplier is later found to be a ghost-receipt seller, a documented verification trail at the time of the transaction is the difference between a defensible good-faith purchase and an indefensible one.

Keep proof the transaction actually happened — not just the receipt #

A receipt only proves a document was issued; it does not by itself prove that goods were delivered or services were performed, which is exactly the gap ghost-receipt schemes exploit. Pair every purchase invoice with independent evidence the underlying transaction occurred.

• Delivery receipts or waybills signed by someone at your business who actually received the goods, cross-checked against your inventory or receiving log.
• Service completion reports, timesheets, or signed acceptance documents for purchased services, naming the specific personnel involved and the dates worked.
• Courier, freight, or logistics records for goods shipped from outside your immediate area — a large “delivery” with no corresponding freight cost or shipping record is a red flag.
• Bank transfers or checks, not cash, for material purchases. A pattern of large cash payments to a single supplier, with no bank trail, is harder to defend if that supplier’s legitimacy is later questioned.
• A contract or purchase order predating the invoice, especially for services, showing the transaction was negotiated and agreed before the receipt was issued — not the other way around.
• A watch for receipts dated suspiciously close to a VAT filing deadline with no matching delivery record, since a burst of unsupported purchases right before a 2550Q or 2550M due date is one of the patterns BIR examiners are trained to notice.

Reconcile RELIEF SLSP against your financial statements before you file #

RELIEF SLSP data is one of the inputs the BIR’s system draws on for risk-based case selection under RMO No. 22-2026, and a mismatch between what you report there and what your Audited Financial Statements show is a data point the system can flag without a human examiner ever looking at your file first. Doing this reconciliation before filing, rather than waiting for a Letter Notice, keeps a purely internal timing issue from ever becoming an external flag.

1. Pull your quarter’s RELIEF Summary List of Purchases total and compare it against the purchases figure in your books for the same period.
2. Identify and document any gap — most trace to accrual-timing differences between when you booked a purchase and when a supplier reported the corresponding sale, not to a genuine discrepancy.
3. Confirm every listed supplier’s TIN on your SLSP matches its registered TIN exactly; a transposed digit can make a real, verified purchase look like an unmatched entry in the BIR’s cross-check.
4. Repeat the check before your annual Audited Financial Statements are finalized, since that figure — not just your quarterly VAT return — is one of the reference points third-party data matching draws on, as covered in why RELIEF SLSP mismatches with your financial statements trigger a Letter Notice.
5. If a mismatch traces to a specific supplier rather than a timing difference, treat that as a prompt to re-verify that supplier’s registration status, not just fix the number and move on.

Related-party and circular invoicing need an arm’s-length paper trail #

Invoicing between related entities — sister companies, a business and its officers’ other ventures, or companies sharing common ownership — is legal, but it is also the exact structure ghost-receipt schemes use to circulate fictitious transactions between shell entities that exist mainly to generate deductible expenses for each other. The difference between a legitimate related-party transaction and a red flag is documentation showing the price and terms reflect what unrelated parties would actually agree to.

• Document the business rationale for the related-party transaction — why this counterparty, for this good or service, at this price — in writing, at the time of the transaction, not reconstructed later.
• Benchmark the price against what an unrelated supplier would charge for the same goods or services, and keep that comparison on file.
• Avoid transaction patterns where money and paperwork move in a closed loop among the same handful of related entities with no real third party ever receiving the goods or services.
• Treat any related-party invoice issued shortly before a filing deadline, for a round or unusually convenient amount, as needing extra scrutiny before it’s booked — the same way you would treat one from an unrelated stranger.

Worked example: a ₱850,000 invoice from a newly registered supplier #

A Cavite-based furniture exporter is approached in September by a new supplier offering raw lumber at a notably lower price than its usual vendors, with an invoice for ₱850,000 due before month-end. Before recording the purchase, the exporter’s accountant runs through the following before booking it as a deductible expense and input VAT claim:

The lumber and the paperwork may well have been genuine — a business six weeks into registration is not automatically a ghost supplier. But the missing delivery proof and the mismatch between the registered business line and the goods invoiced were exactly the gaps that would leave the deduction indefensible if this supplier turned out to be a ghost-receipt seller, so the purchase waited until the documentation caught up with the transaction.

If a BIR notice or Letter of Authority names a specific supplier #

Receiving a notice that questions a specific supplier relationship is not the same as being accused of fraud, but it does require an immediate, organized response built around the documentation described above. A Letter Notice, generated by third-party data matching, is different from a Letter of Authority, which authorizes an actual examination — see BIR’s RATE program for how enforcement escalates once a case moves from a data flag toward investigation.

1. Pull every document tied to that supplier: the Certificate of Registration on file at the time of the transaction, the invoices, proof of delivery or service, and proof of payment.
2. Re-verify the supplier’s current registration status, since a supplier valid at the time of the transaction can later be cancelled, suspended, or identified as a ghost-receipt seller — the relevant question for your exposure is usually what you knew and could verify at the time, not what turned out to be true later.
3. Do not contact the supplier to “fix” documentation retroactively. Backdated or reconstructed paperwork produced after a notice arrives tends to make a defensible transaction look indefensible.
4. Route the notice to a tax professional before replying. How the initial response characterizes the transaction affects whether the matter is resolved as a documentation gap or escalates further.
5. Keep a record of everything submitted and when, the same practice recommended for any BIR Letter Notice response, since an unresolved flag can carry forward into a broader audit.

Frequently asked questions #

Can a legitimate business be flagged under the BIR’s RAFT program even if it never knowingly bought a fake receipt? #

Yes, at least in the sense of getting caught up in a review. RAFT’s enforcement focus is on knowing use of fictitious receipts, but a business that unknowingly booked a purchase from a supplier later identified as a ghost-receipt seller can still face scrutiny and disallowance of the related deduction or input VAT claim, because the burden falls on the buyer to substantiate that the transaction actually happened. Verifying suppliers before booking a purchase, and keeping delivery proof afterward, is what separates a defensible good-faith transaction from one the BIR can successfully challenge.

What is the BIR’s 30% threshold test and why does it matter for ghost-receipt risk? #

Under Section 248(B) of the National Internal Revenue Code, a substantial underdeclaration of sales or a substantial overstatement of deductions — defined as exceeding 30% of the amount properly declared — creates a prima facie presumption that a return is false or fraudulent. The BIR has used this same 30% threshold as a screening tool to flag returns where claimed deductions or input VAT look disproportionate, which is one of the patterns that can direct examiner attention toward a taxpayer’s supplier list under RAFT.

Does reconciling my RELIEF SLSP figures actually reduce my audit risk under RMO No. 22-2026? #

It should, because RMO No. 22-2026’s Priority Case selection is system-assisted and draws on data mismatches and unusual reporting patterns from filed returns, which includes RELIEF Summary List of Sales and Purchases data. A RELIEF SLSP that reconciles cleanly against your VAT returns and financial statements removes one of the data-driven signals the BIR’s system uses to select cases for audit, even though it cannot guarantee exclusion from a Mandatory Case category tied to other criteria such as incentive claims or refund requests.

What documents should I keep to prove a purchase from a new supplier was real, not a ghost transaction? #

Keep the supplier’s BIR Certificate of Registration (BIR Form 2303) confirming its registered activity and RDO, proof that its receipt or invoice was issued under a valid Authority to Print or an accredited CRM/POS system, and — separate from the receipt itself — independent proof the transaction happened, such as a signed delivery receipt, a job completion report, courier or logistics records, or correspondence tied to the order. A receipt alone, however official-looking, only proves a document was issued; delivery or service proof is what shows the underlying transaction actually occurred.

What should a business do if it receives a BIR notice or Letter of Authority naming a specific supplier? #

Pull every document tied to that supplier immediately — the Certificate of Registration on file, the invoices or receipts, proof of delivery or service, and proof of payment (bank transfer or check, not cash) — and verify the supplier’s registration status again as of today, since a supplier can be validly registered at the time of the transaction and later cancelled or flagged. Route the notice to a tax professional before responding, since a Letter of Authority carries examination powers that a Letter Notice does not, and how the initial reply frames the transaction matters for how the case proceeds.

Summary #

Avoiding a mistaken RAFT ghost-receipt flag comes down to documentation discipline that most legitimate businesses can build into routine practice: verify a new supplier’s BIR Certificate of Registration and receipt authority before booking a purchase, keep delivery or service proof for every invoice separate from the receipt itself, reconcile RELIEF SLSP figures against your financial statements before filing rather than after a Letter Notice arrives, and document related-party transactions at arm’s length. RMO No. 22-2026’s risk-based, system-assisted case selection means these same data points — reporting mismatches, unusual patterns, unsupported deduction spikes — are exactly what the BIR’s own screening now looks for, so closing the gaps proactively is the most reliable way to stay outside that review queue. For the enforcement mechanics behind these flags, see the BIR’s RAFT program, the BIR’s RATE program, and RMO No. 22-2026’s consolidated audit program.