Choosing 1099 Software When You Pay Structural Subconsultants

On some projects, the architecture firm holds the prime contract and pays every subconsultant directly, deducting their fee from what the client pays your firm. On others, particularly larger commercial projects, the client contracts directly with the structural or MEP engineer, and your firm merely coordinates the work. Only in the first structure does your firm owe those subconsultants a 1099. Confirm this project by project, since a firm running both contract structures at once can easily assume the wrong one applies to a given subconsultant. A short annual review of active contracts catches any that changed structure mid-project.

Visualization freelancers hired for a single client presentation are often paid a flat fee outside the firm's usual subconsultant workflow, sometimes through a personal payment app rather than a formal invoice process. That informality is exactly why they're easy to miss at filing time. Track1099's simple CSV import is a reasonable fit for this shorter, more occasional vendor list, since you're likely building a manual export regardless of which platform you choose for a handful of one-off renderer payments each year. Keep a running list rather than reconstructing it from old email threads each January.

A structural engineering firm you work with regularly, across several concurrent commercial and residential projects, should be filed as one payee for the year's total, not split by project. A direct sync from your accounting system, where the vendor supports it, can handle this automatically if your chart of accounts already totals by vendor; confirm current system coverage before counting on it. If your firm still tracks costs primarily by project number, you'll need to consolidate manually before uploading to either platform, so check that step regardless of which tool you pick.

When your firm's prime fee already includes a structural or MEP subconsultant's portion, and you pass that portion through to them, only the amount you actually paid the subconsultant is reportable, not your firm's gross fee. This distinction matters most on design-build or fast-track projects where fee splits shift mid-project. Keep a clear record of what portion of each payment was actually disbursed to the subconsultant versus retained by your firm, since that record is what you'll need at filing time. A simple ledger note at the time of each disbursement is enough to avoid a reconstruction project later.

A structural or MEP subconsultant sometimes starts a project billed through your firm and ends it billed directly by the client, often because a value-engineering pass partway through construction documents shifts who's holding the contract. When that happens, your firm only owes a 1099 for what it actually paid before the switch, not for the subconsultant's full-year total. The client becomes the filer for everything paid after that point. This is easy to get wrong because the subconsultant's name keeps showing up in your project files all year, even after your firm has stopped cutting them checks, so a report that pulls every payee billed to that project number will overstate what your firm needs to report. When a contract like this changes hands, note the exact invoice or date in your accounting system at the time it happens, and confirm with the client's accounting team who's filing for the period after the switch, rather than assuming either side has it covered.

US small businesses wait an average of 28.8 days to get paid after invoicing¹, and architecture firms that pay subconsultants on their own schedule, ahead of collecting the client's payment, absorb that gap directly. This isn't a filing-platform issue, but it affects which payments actually clear in a given tax year versus the next, which in turn affects which year a subconsultant's payment gets reported in.

A firm that consistently holds the prime contract and pays every subconsultant directly benefits from Tax1099's ongoing TIN validation and ledger sync, since subconsultant relationships are active and recurring throughout the year. A firm that more often coordinates subconsultants contracted directly with the client has a shorter list of its own actual payees, mostly freelance renderers and occasional specification writers, which fits comfortably within Track1099's simpler, lower-volume workflow.

The firms that avoid January confusion settle the payer-of-record question in the prime contract itself, spelling out plainly whether the architecture firm pays subconsultants directly or the client does, project by project. That single decision, documented once per project rather than reconstructed from memory in January, removes most of the ambiguity that causes filing mistakes in this business. It's a five-minute addition to a contract template that saves hours of reconciliation later, and it gives the firm a clean, consistent answer if a client's accounting team ever asks how a project's fees were actually disbursed.

Settle these points in each prime contract:

• State plainly whether your firm pays each subconsultant directly or the client contracts with them, project by project.
• Report only the amount actually passed through to a subconsultant, not your firm's gross fee.
• Route freelance renderers and other one-off payees through a formal invoice process, even when they prefer a personal payment app.
• Note in writing any mid-project change in who pays a subconsultant, such as a shift to the client after a value-engineering pass.
• File one 1099 per payee for the year, not one per project.