Return workflow / Business entities
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
Partnership workflow under design-partner validation.
S-corporation workflow under design-partner validation.
C-corporation workflow planned.
Trust and estate workflow planned.
Under validation.
Entity-to-owner K-1 generation under validation.
02/Entity to owner
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
04/The stages
·/Limitations
Business-entity validation is exactly where design partners change what gets built first.