Tax1099 or Track1099 for a Civil Engineering Firm's Subs?

If your firm holds back 10% of a subconsultant's fee until project closeout, that retained amount isn't paid, and therefore isn't reportable, until it's actually released, which might happen in a different tax year than the bulk of the work. Neither Tax1099 nor Track1099 tracks retainage schedules; that has to come from your project accounting or job-cost system, reconciled against actual disbursements before you build your 1099 batch. Filing based on total contract value rather than amounts actually paid is a common and avoidable mistake here. Note the release date the moment it happens, so nobody has to reconstruct it from an old project ledger months later.

An independent professional engineer brought in once to stamp drawings outside your firm's licensed scope is exactly the profile most likely to be missed: a single payment, no ongoing relationship, easy to file as a one-off expense rather than route through your normal vendor intake. What catches this kind of infrequent, high-value vendor is a check that runs the moment you enter a new payee, before the payment clears, rather than relying on a January sweep; confirm that's how your chosen platform actually behaves. Route it through the same intake process as any recurring subconsultant, not around it.

A geotechnical or surveying firm that works with you on several projects concurrently should be filed as one payee for the year, not split across each project's job-cost code. Track1099's CSV import requires mapping to a payee at upload, which forces this consolidation. Tax1099's direct sync from your accounting system handles it automatically if your chart of accounts rolls subconsultant payments up by vendor rather than leaving them siloed under individual project budgets.

Payroll and contractor costs in professional, scientific and technical services firms typically run well above a third of revenue¹, and for a firm running subconsultants across a dozen active projects at once, untangling that from twelve months of project accounting in January is exactly the kind of task that eats a senior project accountant's time during the firm's busiest season, right alongside actual project delivery deadlines. Fixing the source data once is cheaper than repeating the reconciliation every year.

A firm whose project accounting already totals subconsultant costs by vendor, not just by job, will find Tax1099's ledger sync does most of the consolidation work automatically. A firm whose job-cost system is the source of truth, with vendor totals split across many project codes, will likely find Track1099's CSV-first workflow easier, since building that payee-level export is unavoidable either way and Track1099's import is built specifically for it.

It happens more than you'd expect in this industry: a surveying firm bills one project under an LLC and another under a DBA that's actually the same taxpayer. If you don't catch this, you'll file two 1099s for what should be one, or worse, file under the wrong name entirely. Confirm the taxpayer identification number, not just the entity name, matches across every project before consolidating, since the TIN is what actually determines whether it's one payee or two. A quick TIN check at intake catches this before it becomes a filing-season puzzle.

Add a two-line step to your project kickoff checklist: confirm which subconsultants are on your firm's contract versus the client's, and collect a W-9 from any new subconsultant before their first invoice is approved for payment. That single habit, repeated at every kickoff, is worth more to a clean January than any feature comparison between filing platforms. It also gives your firm a documented answer if a client or auditor ever asks how subconsultant payments and retainage releases are tracked across active projects, which is a reasonable question on any project of meaningful size.

Add these steps to your project kickoff checklist:

1. Confirm which subconsultants sit on your firm's contract and which sit on the client's, so you know who the payer is.
2. Collect a W-9 from every new subconsultant before their first invoice is approved for payment.
3. Track retainage separately and report it in the year it is actually released, not the year the work was done.
4. Key each subconsultant record to a taxpayer identification number so payments across projects roll into one payee.
5. Check whether a subconsultant bills under an LLC on one project and a DBA on another, since it may be one taxpayer.