# How does Filed AI extract and process K-1 data?

Filed's AI model extracts and structures data from Schedule K-1 forms across three primary pass-through U.S. income tax sources: Form 1041 (Estates and Trusts), Form 1120-S (S Corporation), and Form 1065 (Partnership Income). The extraction logic aligns with major tax software platforms including CCH Axcess Tax, Drake Software, ProConnect, Ultratax CS and Lacerte's architecture to enable seamless data transfer.

## Key Capabilities by Form Type

### Form 1041 Support

The system processes beneficiary income allocation data, handling:

* General screens
* Activity information (Lines 1–14)
* Carryovers
* QBI activities (up to 15)
* Foreign tax data
* Multi-state fields

### Form 1120-S Support

Comprehensive shareholder income extraction including:

* General and activity information (Lines 1–17)
* Schedule 1 deductions
* Various carryover types
* QBI activities
* Foreign transactions via Schedule K-3
* Basis limitation information
* Multi-state data

### Form 1065 Support

The model captures partner share details across:

* General screens
* Activity information (Lines 1–21)
* Schedule 1 deductions
* Carryovers
* QBI activities
* Schedule K-3 foreign transactions
* Basis information
* Multi-state fields

All three forms support business use of home data (Form 8829) integration and basis carryover tracking.

***

Legacy URL: <https://support.filed.com/articles/3946483774-how-does-filed-ai-extract-and-process-k-1-data>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.filed.com/filed-help-center/ai-tax-prep/how-does-filed-ai-extract-and-process-k-1-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
