Audit Trail + CRA Period Copy Bundle

Why the period copy runs first in the sequence

Audit Trail Removal is irreversible — once the meta-history table is dropped, the per-edit history is gone for good. Producing the CRA Period Copy first, against the still-intact source file, captures the historical audit-trail state cleanly inside the period boundary so the period copy carries that evidence forward. Running the order in the opposite sequence would mean the period copy reflects the post-removal state, which is materially less useful for an actual CRA audit response. The bundle locks the sequence in so order-time mistakes that would otherwise be irrecoverable become impossible to make.

What the cross-verification step adds

Each standalone service has its own verification PDF documenting the trial-balance match against the source. The bundle adds a cross-verification step that confirms the period copy's end-of-period trial balance matches the post-removal file's opening trial balance at the same date, dollar-for-dollar, on every account. That match is the structural integrity gate of the bundle: if it ever failed, neither file would leave our environment, because a mismatch would mean one of the two services produced a deviation. The cross-verification PDF documents the match line by line for direct reviewer handoff.

Pricing math against the standalone services

Standalone Audit Trail Removal is $50.00 CAD at the launch rate ($99.00 CAD regular). Standalone CRA Period Copy is $50.00 CAD at the launch rate ($99.00 CAD regular). Bundle launch is $75.00 CAD against a regular price of $149.00 CAD, which is a meaningful discount over either combination of standalones. The discount reflects shared diagnostic and verification overhead, not a quality compromise — the deliverables are identical to the two standalones with the additional cross-verification step on top, ordered in the correct sequence to preserve the historical audit-trail evidence inside the period boundary.

Can I buy this bundle without an open CRA audit?

Yes — most practices order the bundle proactively rather than reactively, often during a year-end close or a fiscal-year transition when both deliverables make sense at the same moment. The period copy serves as a frozen historical reference even outside an active audit, and the post-removal main file becomes the smaller, faster operating file your practice continues using day-to-day. Pre-purchase chat in the Portal will scope the right period boundary dates if your engagement is proactive rather than triggered by a specific CRA letter.

Does the bundle support custom period boundaries beyond fiscal years?

Yes. The period boundary is defined by a start date and an end date plus an optional posting-cutoff timestamp, and there is no constraint that the boundary align to a fiscal year. Common non-fiscal boundaries include a partner-buy-in event date, a sale-of-business closing date, a multi-month CRA audit window that spans two fiscal years, and a retroactive period requested by an external accountant. The verification PDF echoes the boundary back in ISO format unambiguously so the deliverable matches the request exactly.

Is the cross-verification PDF separate from the per-service verifications?

The bundle delivers three documents: the period-copy verification PDF, the audit-trail-removal verification PDF, and the bundle cross-verification PDF that confirms the two outputs reconcile against each other. All three travel together in your Portal download alongside the two .qbm files. Reviewers we have worked with consistently treat the cross-verification PDF as the high-confidence document of the engagement because it answers the integrity question that the two standalone PDFs cannot answer on their own — that the two deliverables are consistent.

Can I attach Rush Delivery to the bundle?

Yes. The Rush Delivery add-on attaches to the bundle the same way it does to any other order in this Portal, moving the bundle to the head of the standard processing queue ahead of every non-rush ticket. The cross-verification step is still run in full — Rush only changes scheduling, not the verification work or the deliverable shape — so the rush bundle ships with all three verification documents on the faster clock. If your timing is tighter than rush would deliver, pre-purchase chat can scope a custom escalation directly.