Diagnose rejected CRA information-return files with a controlled change log
Saxum reproduces the technical failure, separates structural defects from unresolved business data and returns a corrected candidate only where the change is deterministic.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Current schema rule
CRA information-return files must be checked against the current filing-year XML specifications and validation rules. Saxum does not reuse an old schema silently; the report records the specification version and validation date used for the case.
Why the standard portal or checklist is not enough
During filing season, one malformed or inconsistent return can block a batch and create a rushed manual search through records and validation messages. Blind repair is dangerous because a syntactically valid file can still contain incorrect tax facts.
Best-fit customer
Canadian accountants, bookkeepers, payroll bureaus and software teams
Problems this product helps control
Rejected CRA XML information returns where schema, transmitter, slip, account or optional-field data needs deterministic diagnosis before resubmission.
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- Rejected XML file
- CRA error message or transmission result
- Return type and tax year
- Customer-approved schema package when required
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Error-by-error diagnosis
- Structural and data-issue separation
- Deterministic corrected candidate
- Masked findings report
- Before/after change log
- Resubmission checklist
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Reproduce
Confirm the failure safely and record hashes of the received material.
Classify
Separate XML structure, schema, identifiers and customer-data questions.
Correct
Change only facts supported by the source or customer instruction.
Verify
Revalidate and provide a transparent residual-risk list.
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
Every engagement starts with scope confirmation. Pilot and research offers are intentionally limited until the workflow is proven on paid cases.
Request a CRA technical diagnosis →CRA SlipFix FAQ
Direct answers on access, responsibility, deliverables and limits.
No. The customer retains filing credentials and submits the final return.
Only from authoritative customer instructions. Saxum does not infer tax facts.
Support is declared case by case and tax year by tax year and schema package; unsupported types fail closed.
No. It is technical diagnostics and controlled correction support.
Yes, with segregated case handling and a seasonal portfolio agreement.
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.