Tax software and documents
What connects directly, and how everything else arrives.
Updated August 2026
Tax material joins a piece of work two ways, and both are read inside the firm.
| How it joins | What arrives |
|---|---|
| Connects directly | Client, engagement and return identity, period and jurisdiction, form and filing state, diagnostics and review status, workpaper and source-document references, mapped fields |
| Arrives as documents | Everything else: exports, workpapers, PDFs, spreadsheets, scans, statements |
What connects directly
Selected tax systems connect where an exact supported capability exists, proven against the provider's actual contract; a generic create-or-update tool pointed at a tax engine is refused. Where no safe write exists, the result is a review artifact the preparer acts on, never a fabricated change.
Firms run UltraTax CS, CCH Axcess, Lacerte, Drake and others. What each exposes differs, so what connects is settled for your engine at setup.
How everything else arrives
A firm can designate the folders where tax-system exports land, and print a return draft straight to Proxara. Both feed the same pipeline as any other document. What could not be read is stated rather than assumed away, and never leaves the firm (how Proxara works).
What the pipeline keeps, and what it records as unread
Every extracted unit keeps its provenance: page, sheet, cell, attachment, layout, reading order, parser, confidence, and source version. Unsupported pages, hidden sheets, password-protected sections, corrupt objects, unprocessed images and truncated provider content are recorded as gaps rather than passed through. An opaque region is treated as unsafe to release, not as empty.
Where the firm already lawfully controls a local database, file store or documented export, that material can be read directly too. That is not a claim that any proprietary format can be bypassed; it uses access the firm is authorized to use.
What this means for your engine
If it exposes a supported capability, it connects and reads back. If not, its output still arrives as documents and the work completes.
If something doesn't work
- A value missing from a review? Anything unreadable is recorded as unread, never guessed.
- Nothing written back? Where no safe write exists, the change arrives for the preparer to make.
Next: Connect Karbon, the work items those returns hang off.