TaxDome vs Ignition: Can 3 Checks Automate 2026?

The accounting category decision is which system is allowed to say the client is engaged for the next period, not which portal has more file-request templates. An engagement-letter renewal is the signed, dated agreement that restates scope, fee, and period before work starts again. TaxDome can store the client, the job, and a letter template. Ignition can issue the proposal, collect the signature, and request the payment method. Neither product is your tax engine. Neither is a substitute for a partner who decides that scope actually changed.

Automating collection of engagement-letter renewals means listing clients whose current letter expires, sending the next letter or proposal, recording a signature, and blocking the job until that signature exists. It is not a mail merge. It is not the same workflow as tax document collection. Document chase and letter chase share a client id; they do not share a legal meaning. US Tech Automations holds only when the letter system, the practice system, and the billing system disagree on whether work may start. no accounting vendor paid for inclusion.

TL;DR: Choose Ignition when the letter is a commercial proposal you want signed and paid from one object. Choose TaxDome when the letter is one artifact inside a practice portal you already run for jobs, messages, and files. Stay on one accounting system of record for “engaged / not engaged.” Add a second tool only when you can join client id, period, and envelope id.

What engagement-letter renewal actually means

An engagement-letter renewal is the next period’s written agreement: who the client is, what the firm will do, what it will not do, what it will charge, and when the period starts. Collection is the operations problem of getting that agreement signed before timesheets start. If the firm starts work on a handshake and files the PDF later, you do not have a renewal process. You have a documentation lag, and automation will only timestamp it.

This is a different object from a source-document request. W-2s, 1099s, and organizers belong in client document collection and the TaxDome / Liscio / ProConnect comparison at tax document collection across portals. A tax document collection workflow can run in parallel once the letter exists. Do not merge the two queues. A client can upload every PDF and still be unengaged.

Cloud workflow adoption: 62% of firms according to AICPA (2025), 62% in the 2025 PCPS CPA Firm Top Issues Survey for firms adopting cloud-based workflow tools as an aggregate, not as a named vendor category. Use 62% as proof that most firms already bought a accounting system of record. The renewal gap is usually that the letter still lives in a shared drive while the job lives in the portal.

AICPA membership: more than 400,000 according to AICPA (2024), more than 400,000 members. That is association scale, not a claim that 400,000 firms need a new letter product. It is why a generic “send the PDF” process does not survive busy season: too many entities, too many periods, too many partners.

Accountants and auditors: 1.5 million jobs according to BLS (2024), about 1.5 million accountant and auditor jobs. Capacity is people. A letter that arrives after fieldwork has started wastes that capacity on work the firm may not be able to bill cleanly if the scope was never restated.

The three checks in the title are the only ones that matter at collection time. Check 1: is there a current letter whose end date is before the next period start? Check 2: is there a signed artifact (portal signature or envelope) for that next period? Check 3: is the job or invoice blocked until check 2 is true? Firms often pass check 1 in a spreadsheet, pass check 2 in email, and fail check 3 because the tax app will still open the return. Automation that sends mail without enforcing check 3 is a reminder tool.

Identity has to be boring and strict. Client number plus period (tax year or month) plus entity (1040 versus 1120 versus bookkeeping) is the minimum key. Email alone fails when one household has three entities. A partner name is not a key. If Ignition’s proposal id and TaxDome’s client id cannot be joined, you will send two letters or start work on the unsigned one.

Scope change is a human event. A 1040 that adds a new K-1, a bookkeeping client that adds payroll, or a notice-response engagement is not a renewal. It is a new letter. Any job you design should stop when fee, entity count, or service line differs from last period by a rule you write down. Do not ask a template to invent legal scope.

Busy-season sequencing is the other half of collection. Letters that go out after organizers, after first interviews, and after the return is already in review will be signed as theatre. Sequence is: expire list, send letter, wait for signature, then open the organizer and the document queue. If the firm’s culture is “we always start in January,” then the letter campaign belongs in December, not in the week of the first extension. A calendar that only has tax due dates is not an engagement calendar.

Unpaid prior-year fees are a stop, not a footnote. A renewal that collects a signature while last year’s invoice is 90 days past due teaches the client that letters are paperwork. Put AR status on the same client-period key. If the proposal tool can request a payment method, use it for the new period only after you have a written rule for old balances: hold, payment plan, or partner waiver. Do not hide that rule in a partner’s head.

Language and entity type have to be templates, not one Word file with yellow highlights. A 1040 with a Schedule C is not an 1120S. A monthly bookkeeping letter is not a single-year tax letter. A nonprofit Yellow Book engagement is not a compilation. If Ignition or TaxDome has three templates and the firm has nine service lines, the missing six will go back to email. Count templates against service lines before you buy a send button.

Peer review and quality control do not require a new product, but they do require a retrievable letter. If a reviewer asks for the engagement documentation on a file and the staff cannot open it from the job, the collection process failed even if the client “signed something.” Store the artifact on the client-period record. Name the folder convention once. Ban a second copy on a desktop.

Extension season is a second renewal test. A 1040 that was engaged for the original due date is not automatically engaged for an extended return if scope changed, if a new state appeared, or if the fee letter was “through April.” Write whether an extension is in-scope. If it is not, the job that prints Form 4868 should still see the same engaged/not-engaged field as the original return.

Key Takeaways

• Engagement-letter renewal is a signed next-period agreement, not a document request and not an invoice.

• Ignition is the tighter commercial proposal-and-pay object; TaxDome is the tighter practice portal if it is already the job system.

• The three checks are expiry, signature, and a block on work until the signature exists.

• Native Ignition or TaxDome flows can be enough when one system already holds those three checks.

• Orchestrate across portal, e-sign, and billing only after unique client-period ids and a partner exception exist.

Evaluation criteria for the renewal stack

Weights assume a CPA or EA practice that already issues written letters and already has a portal or proposal tool. A sole practitioner who meets every client in one room and files 80 returns may only need a template and a calendar.

Identity is first because duplicate letters destroy trust. Signature artifact is second because a portal checkbox that does not produce a retrievable object will fail a peer review conversation. Work-start block is third because collection that cannot stop the job is theatre.

Normalized feature matrix

Scores from public product accounting pages checked 2026-09-04: 2 = first-party accounting description for engagement or proposal letters; 1 = adjacent practice feature, confirm in the accounting contract; 0 = not found for this use. The US Tech Automations row is a first-party publishing-velocity figure, not a practice-management benchmark.

3,200 is this accounting publisher artifact-backed June velocity ceiling (~3,200 accounting pages in two weeks for automate collect engagement-letter renewals). It does not mean TaxDome indexes letters faster than Ignition. It is here so this comparison is not a swap-in feature grid.

Pricing and TCO, dated

TaxDome packages practice management, portal, and related modules as firm subscriptions; public marketing pages on TaxDome (checked 2026-09-04) do not publish a universal per-letter price for renewals. Write contact vendor, then add user seats, client volume tiers, and any e-sign or payments add-on named in the quote.

Ignition packages proposals, engagement, and payment collection as a firm subscription; public pages on Ignition (checked 2026-09-04) do not publish a single national sticker that maps to “renewal collection only.” Write contact vendor, then add proposal volume, payment processing, and implementation.

A 12-month sheet that ignores partner time is incomplete. Someone still reads scope changes. Someone still calls the client who will not sign. If that person does not exist, do not buy a more flexible stack.

E-file share: more than 90% according to IRS (2024), more than 90% of individual income tax returns are e-filed. E-file is not engagement. It is a reminder that the production system will happily transmit work the letter never covered if you do not block the job.

PCAOB-registered firms: more than 1,500 according to PCAOB (2024), more than 1,500 registered public accounting firms. Most practices reading this page are not PCAOB issuers. The number is here as a ceiling on “the profession,” not as a buying threshold. Non-issuer firms still need a letter; they do not need an audit-committee portal to collect one.

Vendor profiles

TaxDome: practice portal with jobs and letters

TaxDome is the accounting shortlist pick when the firm already runs jobs, messages, e-sign, and files in that portal and the engagement letter is one more template on the client. Primary evidence is TaxDome. Best fit is a firm whose staff already live in TaxDome for the return, the organizer, and the invoice. Limitations: TaxDome is not a dedicated commercial-proposal product in the Ignition sense, and a letter template that is never tied to a job start date will not block work. Choose TaxDome when one portal should own the client. Disqualify it when Ignition already is the paid proposal of record and nobody will join ids.

Implementation is a client-period field, a letter template per service line, a signature artifact stored on the client, and a rule that a job cannot move to in-progress without it. If you cannot point at the signed object from the job, you implemented file storage, not engagement.

Ignition: proposal, signature, and payment as one object

Ignition is the accounting shortlist pick when the renewal is a commercial proposal: scope, fee, signature, and payment method in one client-facing object. Primary evidence is Ignition. Best fit is a firm that wants the letter to be the thing the client pays, not a PDF that sits next to a separately emailed invoice. Limitations: Ignition is not your full tax preparation system and not your full document-request portal. Choose Ignition when “accepted proposal” is the definition of engaged. Disqualify it when the partners will not stop opening returns from a different app that ignores proposal status.

Implementation is proposal templates per service line, a renewal campaign by end date, payment collection if you use it, and an export of accepted proposal ids into the job system. If accepted proposals do not change job status, you bought a nicer PDF.

Where a third system still appears

DocuSign, Adobe Acrobat Sign, or a portal-native signature may be the artifact even when TaxDome or Ignition is the accounting system of record. QuickBooks may be the invoice. The practice app may be CCH, Thomson Reuters, or Drake. That is normal. It is also how renewals fail: the signature is “done” in e-sign and “not done” in the job. US Tech Automations can be configured, as a proposed capability, to read a signed envelope.status of completed, match client-period, and still hold the job if fee or entity count changed—only after API credentials, a uniqueness key, and a partner reviewer exist. That is not a live deployment claim.

Worked example (illustrative, not a measured result): a 12-partner firm with 340 tax-season clients, 280 letters with end dates inside 21 days, and a typical 1040 engagement fee (contact vendor for the firm’s actual rate) can send Ignition or TaxDome renewals in one batch, then treat DocuSign envelope.status equal to completed as check 2, while 18 scope-change households (new K-1, new state, new payroll) route to a partner instead of auto-accepting last year’s PDF. The figures 12, 340, 280, 21, and 18 are a mapping scenario, not a benchmark.

IFAC network: more than 3 million according to IFAC (2024), more than 3 million professional accountants in the IFAC network worldwide. Global headcount does not pick TaxDome or Ignition. It explains why letter language, entity types, and e-sign rules are not one template: the work is professional services, not a SaaS onboarding checkbox.

Decision checklist before you switch

Write the accounting system of record in one sentence: “Ignition is engaged/not engaged” or “TaxDome is engaged/not engaged.” If you cannot write that sentence, pause. List the three checks against ten real clients. Confirm you can export last year’s letters. Confirm a job can be blocked. Confirm a scope change has a partner. Confirm you will not also keep a Word folder “just in case” without a join key. Confirm document collection stays a separate queue so organizers do not masquerade as letters.

Walk ten files before you send a campaign. For each file write: client number, period, entity type, last letter end date, last fee, whether scope looks unchanged, whether AR is clean, and whether a job can be opened today without a signature. If more than a few of those ten cannot answer those fields, the problem is master data, not send volume. Fix the key, then send.

Common failure: the firm buys Ignition, keeps Word letters for “special” clients, and keeps TaxDome jobs opening anyway. You then have three truths. Pick one truth or do not automate. A second common failure is treating a portal “acknowledged” click as a signed letter when the click does not store scope and fee. If you cannot print what the client agreed to, you do not have check 2.

Staff who prepare returns need a visible engaged/not-engaged flag on the job list they already use. A dashboard only partners open will not stop work. If the tax application cannot show the flag, export a daily accounting exception list of jobs in progress with no letter, and make that list someone’s morning job. Collection that cannot be seen on the production screen is optional, and optional collection fails in March.

Who this accounting page is for

This comparison is for a partner, firm administrator, or operations manager who already issues written engagement letters and already feels the lag between busy-season start and signed PDFs. It assumes a portal or proposal tool exists or is on the shortlist.

Red flags: skip a new layer when TaxDome or Ignition already blocks the job until the letter is signed, when you have no client-period key, or when partners will open returns regardless of letter status. Do not buy Ignition to replace a tax application. Do not buy TaxDome only to store PDFs you still email from Outlook.

Engagement-letter renewal FAQ

Should a CPA firm pick TaxDome or Ignition for renewals?

Pick Ignition when the proposal-and-pay object is the definition of engaged; pick TaxDome when the practice portal already is the job system and the letter is one artifact on the client.

Is an organizer the same as an engagement letter?

No. Organizers collect facts. Letters collect permission, scope, and fee. Run both, on separate queues.

Do we need a second e-sign product?

Only if the accounting system of record cannot produce a retrievable signature artifact. Two e-sign tools without a join key create two truths.

What blocks work until the letter is signed?

A job-status rule, a calendar rule, or an export that the tax app actually honors. Email reminders do not block work.

How should we pilot letter collection?

run 30 accounting days across 12 entities, 10 clean renewals, 6 scope-change holds, and 2 duplicate EINs. Expand on unique ids and blocked jobs, not on send volume.

Can we keep Word letters for exceptions?

Yes, if exceptions still write the same engaged/not-engaged field. A parallel Word folder with no id is how check 3 fails.

Pick the letter system, then the chase

Choose Ignition for a commercial proposal object, TaxDome for a practice-portal object, and one sentence that names which of those two is engaged/not engaged. Then prove client-period ids from expiry to signature to job block. Collect source documents on a different workflow after the letter exists.

The team at US Tech Automations can map a configurable expiry-to-block trail when the letter, the job, and the invoice are already named. Review finance and accounting workflows after you have named the automate collect engagement-letter accounting system of record, the signature artifact, and the partner who owns scope changes.