FOR TAX PROFESSIONALS|FIND A TAX PROFESSIONAL

Return workflow / Business entities

Business returns, with each entity type stated at its real maturity.

Entity work is where a workflow tool usually stops being honest: the architecture is shared, so every entity type gets described as supported, and the firm discovers the difference during filing season.

Each entity return below carries its own status. 1065 and 1120-S are in design-partner validation. 1120 and 1041 are planned. Nothing here is described as available until it is.

01/Per-entity status

Where each return type actually stands.

1065Design-partner validation

Partnership workflow under design-partner validation.

1120-SDesign-partner validation

S-corporation workflow under design-partner validation.

1120Planned

C-corporation workflow planned.

1041Planned

Trust and estate workflow planned.

Trial balance importDesign-partner validation

Under validation.

K-1 outputDesign-partner validation

Entity-to-owner K-1 generation under validation.

02/Entity to owner

The connection that has to survive.

An entity return produces K-1s, and those K-1s become inputs on somebody's 1040. When the entity workspace and the owner workspace live in different systems, that link is a spreadsheet and a memory.

An owner's separate 1040 is a separate return credit from the entity return, and K-1 output from an entity workspace is included in that entity's credit. At volume that distinction decides the bill, which is why it is written the same way in pricing, Terms, invoices and here.

How return credits are counted →

03/Typical sources

What a business return is built from.

  • Trial balance from the firm's accounting system
  • Prior-year entity return, used for comparison
  • Fixed asset and depreciation schedules
  • Partner or shareholder basis records
  • Loan and capital account documentation
  • Owner information needed for K-1 output

·/Limitations

What this does not do today.

  • TaxScout e-files supported federal and state returns through IRS MeF under your firm's EFIN — or hands approved data to the professional tax software your firm already uses. E-file coverage is published per return type, and nothing is transmitted before the reviewer approves and the 8879 is signed.
  • 1120 and 1041 workflows are planned. They are not usable today, and no date is published for them.
  • 1065 and 1120-S are in design-partner validation, which means real firms are testing them and the scope is still being established.
  • Trial balance import is under validation and its accepted formats are not yet fixed.
  • A shared architecture across entity types does not mean equal maturity across entity types.
  • TaxScout assists preparation and review; it does not replace professional judgment.
Validate a business workflow with us

Business-entity validation is exactly where design partners change what gets built first.