iBill.ca
Get Started
CRA Compliance

9 CRA Audit Defense Reports — Generated Automatically

Run a compliance check and get 9 CRA audit defense reports instantly. Voided register, credit note register, AR reconciliation, tax reconciliation, and more. For Canadian businesses.

iBill generates 9 CRA compliance reports:

  1. Voided Invoice Register
  2. Credit Note Register
  3. Invoice Sequence Analysis
  4. AR Reconciliation
  5. Tax Liability Reconciliation
  6. GST Amendment Tracker
  7. Correction Chain Report
  8. User Action Summary
  9. Full Audit Trail Export (CSV, JSON, XML)

What Are CRA Compliance Reports?

CRA compliance reports prove your books meet ITA s.230 and ETA s.232 requirements. They are the documents a CRA auditor asks for first.

ITA s.230 Record Keeping

The Income Tax Act s.230 requires every person carrying on a business to keep records and books of account in Canada. This includes every invoice issued, every void or cancellation with a reason, every correction chain, and a complete audit trail — all of which iBill generates automatically.

ETA s.232 Tax Adjustments

The Excise Tax Act s.232 governs credit notes and tax adjustment notes for GST/HST. When you void an invoice or issue a credit memo, iBill creates the required tax reversal documentation with per-component breakdowns (GST, HST, PST, QST) that match your general ledger.

Audit Defense

CRA auditors look for gaps in invoice numbering, unexplained voids, mismatched tax liabilities, and missing documentation. iBill's 9 reports address every one of these audit triggers. Your books stay clean, and if the CRA comes calling, every answer is one click away.

The 9 CRA Audit Defense Reports

Each report is generated from your double-entry accounting data and exportable to CSV

Report 1

Voided Invoice Register

Lists every voided invoice with the original invoice number, date, amount, the user who voided it, the date of the void, and the mandatory reason code. Shows the GL reversal journal entry that backed out the original transaction. This is the first report a CRA auditor requests to check for suppressed income.

CRA relevance: ITA s.230 requires documentation of every void. Unexplained voids are a top audit trigger.
Report 2

Credit Note Register

Lists every credit memo with per-component tax breakdowns: GST/HST, PST, QST, and the subtotal adjustment. Shows which invoice the credit applies to, the GL journal entry (DR Revenue + Tax / CR Credits Payable), and the impact on your next GST/HST return filing.

CRA relevance: ETA s.232 requires tax adjustment notes when GST/HST is reduced via credit. This register proves compliance.
Report 3

Invoice Sequence Analysis

Parses your invoice numbering sequence (INV-YYYYMM-NNN format), detects gaps, and cross-references the invoice_number_gaps table to distinguish documented gaps (e.g., voided invoice) from undocumented ones. Undocumented gaps are flagged for investigation.

CRA relevance: Sequential invoice numbering is a CRA best practice. Unexplained gaps suggest missing revenue.
Report 4

AR Reconciliation

Compares your accounts receivable sub-ledger against GL account 1100. For cash-basis businesses, this check verifies GL 1100 is zero (since revenue is recognized at payment, not invoicing). Any non-zero balance flags a posting error.

CRA relevance: Sub-ledger to GL reconciliation proves the integrity of your accounting system.
Report 5

Tax Liability Reconciliation

Cross-checks each tax component independently: GST/HST collected (GL 2100) minus void reversals minus credit reversals = net liability, compared against the GL balance. Runs the same check for PST (GL 2200) and QST (GL 2300). Any variance flags a tax posting error.

CRA relevance: Tax remittance must match collected amounts. This report proves every dollar of tax is accounted for.
Report 6

GST Amendment Tracker

Tracks the full lifecycle of GST/HST return amendments: original filing, amendment reason, adjusted amounts, submission date, and CRA confirmation. Shows which invoices or credit memos triggered each amendment.

CRA relevance: Amendments must be traceable to source documents. This report provides the complete chain from event to filing.
Report 7

Correction Chain Report

Traces every invoice correction from the original to the final version. Uses a recursive chain through corrects_invoice_id / corrected_by_invoice_id relationships, tracked back to the correction_chain_root_id. Shows whether the original was unpaid (void + reissue) or paid (credit + reissue).

CRA relevance: Corrections must preserve the complete document trail. This report proves no invoice was simply deleted and replaced.
Report 8

User Action Summary

Aggregates user actions from the append-only financial audit log: who created, voided, corrected, or approved each financial document, and when. Groups by user and action type for a quick overview of who did what during the period.

CRA relevance: Segregation of duties and user accountability are key audit criteria. This report proves controls are in place.
Report 9

Full Audit Trail Export

Exports the complete financial audit log with SHA-256 document hashes, timestamps, user IDs, action types, and before/after snapshots. Available in CSV, JSON, or XML format. Every entry is append-only and tamper-evident — entries cannot be edited or deleted.

CRA relevance: ITA s.230 requires a 7-year retention period. This export is your complete, immutable record.

Be CRA Audit-Ready — Automatically

All 9 compliance reports generate from your existing invoicing and accounting data. No extra work required.

Get Started Now
Trusted by Canadian Businesses — 1,200+ signups

8 Automated Period-End Checks

When closing a fiscal period, iBill runs 8 automated reconciliation checks to flag issues before they become audit findings

Trial Balance

Verifies total debits equal total credits across all GL accounts. A mismatch means a journal entry posted incorrectly — this check catches it before the period closes.

Balance Sheet Equation

Confirms Assets = Liabilities + Equity. If this equation does not hold, the balance sheet is out of balance — the check identifies which account group is off.

AR Reconciliation

Because iBill posts revenue to the GL at payment date, GL 1100 (Accounts Receivable) should be zero. Any balance means a payment posting was missed or an invoice was booked incorrectly.

Tax Reconciliation

Cross-checks GST/HST (GL 2100), PST (GL 2200), and QST (GL 2300) between the invoice sub-ledger and general ledger. Flags per-component variances.

Revenue Reconciliation

Compares paid invoice subtotals against GL 4000 Revenue for the period. Ensures every payment was posted to the GL and no revenue was missed or double-counted.

Orphaned JE Check

Finds journal entries without a reference_type or reference_id. Orphaned entries mean a posting happened without a source document — a red flag for auditors.

Invoice Sequence Gaps

Detects undocumented gaps in your invoice numbering sequence. Documented gaps (voided invoices) are expected. Undocumented gaps need investigation before closing the period.

Pending Approvals

Checks for unresolved approval requests. Pending approvals for voids, credits, or corrections should be resolved before closing the fiscal period to avoid carryover issues.

CRA Compliance Reports FAQs

What are CRA compliance reports?
CRA compliance reports are financial documents that demonstrate your business meets Canada Revenue Agency record-keeping requirements under ITA s.230 and ETA s.232. They include voided invoice registers, credit note registers, AR reconciliation, tax reconciliation, invoice sequence audits, and full audit trails — everything a CRA auditor needs to verify your books.
Which 9 compliance reports does iBill generate?
iBill generates 9 CRA audit defense reports: (1) Voided Invoice Register, (2) Credit Note Register, (3) Invoice Sequence Analysis, (4) AR Reconciliation, (5) Tax Liability Reconciliation, (6) GST Amendment Tracker, (7) Correction Chain Report, (8) User Action Summary, and (9) Full Audit Trail Export. Each report can be exported to CSV, JSON, or PDF.
What is AR reconciliation in CRA compliance?
AR (Accounts Receivable) reconciliation compares your accounts receivable sub-ledger against the general ledger GL 1100 balance. For cash-basis businesses, this check verifies that GL 1100 is zero (since revenue is only recognized at payment, not at invoicing). Any discrepancy flags a potential posting error that needs investigation before a CRA audit.
What is tax liability reconciliation?
Tax liability reconciliation cross-checks each tax component — GST/HST (GL 2100), PST (GL 2200), and QST (GL 2300) — between your invoice sub-ledger and general ledger. It calculates taxes collected minus void reversals minus credit note reversals to arrive at a net liability, then compares that against the GL balance. Any variance indicates a tax posting error.
How does period-end reconciliation work?
Period-end reconciliation runs 8 automated checks when closing a fiscal period: (1) Trial balance (debits = credits), (2) Balance sheet equation (assets = liabilities + equity), (3) AR reconciliation, (4) Tax reconciliation, (5) Revenue reconciliation (paid invoices vs GL 4000), (6) Orphaned journal entry check, (7) Invoice sequence gap detection, and (8) Pending approval check. These are advisory — they flag issues without blocking the close.

Ready to be CRA audit-ready?

Create Account

Be CRA Audit-Ready — Automatically

9 compliance reports generated from your existing data. No extra work.

Create Account

• CRA ITA s.230 Ready