The entity does, for its own return. Form 7004 is the automatic extension for business, partnership, trust and corporate returns, so it belongs to whichever entity is asking for more time, and each entity in a group asks for itself. Owners and partners have their own returns and their own extension routes, and one request made by the parent does not sweep up its subsidiaries or the partnerships beneath it. A frequent failure in a group is not a missed form but a missed entity: everything was extended except the one nobody had on the list.
Who files Form 7004?
- 15+Years of the founder's cross-border experience
- 18,000+Clients served across our offices in India, the USA, Canada and the UAE
- 5.0Google rating
- 4Global offices — India, USA, Canada & UAE
Entities that need more time to file, very often because a foreign parent or subsidiary closes its books on a different calendar. The obligation is decided by facts rather than by tax owing, which is why a nil position does not remove it.
The rule on who files
Entities that need more time to file, very often because a foreign parent or subsidiary closes its books on a different calendar.

Where the general answer is wrong
The extension protects the filing, not the information returns that travel with it in every case, and not the payment. In a cross-border group the binding constraint is usually the foreign audit timetable, which is worth mapping before the season starts.
How to get this moving
The full treatment — who it binds, the deadline, the penalty and the fixed fee — is on 7004 — business extension. Ask before the move rather than after it, because most of the useful options expire on the date.
Checked and signed off for the 2025 and 2026 filing seasons by Udit Gupta, International Tax, Cross-Border Tax & Transfer Pricing Expert, Legal Quotient Consultants. This is general information rather than advice about your file — a short call is the way to get the second.
Files that look like this one
Mapping an overseas audit calendar against the US filing dates
A group was extending some entities and not others, on no particular principle, and then scrambling when the overseas audit ran past the US dates. We built a single calendar showing when each set of books actually closed and when each entity's return was due, then identified which entities genuinely needed more time. The engagement produced a list of entities to extend each year, an owner for each request inside the finance team, and a season in which nothing was extended by guesswork.
Read how this one runsExtended return with an information filing left uncovered
An entity had lodged its extension properly and assumed that everything it normally sends at the same time had moved with it. One of the accompanying filings had not, and the exposure on it did not depend on tax being owed. We established which items the extension reached and which it did not, lodged what was outstanding, and documented the position. The engagement produced a complete filing set for the year and a checklist that marks, filing by filing, whether an extension reaches it.
Read how this one runsGroup that extended the parent but forgot a subsidiary
A finance team had extended what it thought of as the group and discovered, when correspondence arrived, that one entity had never been on the list. The extension had never been a single request; it was a set of them, and one member of the set was missing. We dealt with the entity's own filing, then rebuilt the list from the register rather than from the team's working memory. The engagement produced the outstanding filing and a schedule of every entity, its return type and who lodges its request.
Read how this one runsEntity that treated the extension as extra time for the money
A company extended its return and let the liability sit, on the understanding that both dates had moved together. Only the filing had. We separated the two timetables, produced an estimate good enough to meet the liability on its original date while the return remained open, and completed the return once the overseas figures arrived. The engagement produced a filing lodged inside the extended period, a remittance made on the original timetable, and a written note of the two dates for the following year.
Read how this one runsFirst year for a subsidiary of a non-calendar foreign parent
A newly formed entity sat beneath a parent that closed its books on a calendar of its own, and nobody had yet decided which returns the new entity would file or when. We settled the return types first, then the dates, then which of them would need extending in the first year while the reporting line was still bedding in. The engagement produced the lodged requests, a filing calendar for the entity's opening years, and a clear statement of which obligations the extension did not touch.
Read how this one runsExamining which entities in a group actually needed extending
A group extended every entity every year as a matter of habit, which cost little directly but hid the fact that nobody knew which returns were genuinely waiting on anything. We examined the closing timetable entity by entity and found that most could file on their own dates once the sequence of work was set differently. The engagement produced a shorter list of entities that extend, a documented reason for each one, and a filing season with fewer open items running into the summer.
Read how this one runsA US LLC Owned by a Canadian, Taxed Twice by Design
The two countries classify an LLC differently, so the credit relief that ought to apply frequently does not. The engagement looks at whether the structure can be changed, and where it cannot, at how to make the credit work.
Read how this one runsTen Years of Missed Returns Filed as One Engagement
Filing many years at once is a sequencing problem: carry-forwards, instalments and credits from the earliest year feed the latest. Filing them out of order is what turns a recoverable position into an assessed one.
Read how this one runsAll case studies — every published engagement in one place.
Core International & Cross-Border Tax Services
Strategy and compliance for income, assets and families spread across borders.
Industries & Client Types We Serve Worldwide
- Foreign VAT / GST / sales tax registrations
- Marketplace withholding reviews
- Inventory nexus & PE analysis
- Multi-currency books reconciled
Software revenue crosses borders by default — sourcing rules, withholding on licence-like payments and IP location decide the effective rate.
Software revenue is rarely taxed where the team sits. Licence, subscription and service income are characterised differently by each side, and the answer decides withholding at source, treaty relief and whether a foreign customer creates a taxable presence at all — questions that are cheap to settle before the contract and expensive afterwards.
- Cross-border revenue sourcing & withholding
- IP structuring with real substance
- Equity for cross-border teams
- U.S. expansion: entity & PE setup
- Reg 105 / 102 waivers
- Permanent establishment risk
- Partner mobility planning
- Cross-border withholding recovery
- Section 216 rental returns
- FIRPTA withholding recovery
- Section 116 clearance
- Treaty credit optimization
- Transfer pricing documentation (s.247)
- Customs value vs transfer price
- Foreign affiliate reporting (T1134)
- Country-by-country reporting
- Reg 105 & U.S. CWA agreements
- Multi-state & country calendars
- Touring income allocation
- Royalty & image-rights withholding
- Residency analysis before moving
- Employer payroll exposure
- Totalization & social security
- Foreign tax credits
- Treaty access & PPT reviews
- FAPI & surplus computations
- Withholding-efficient routing
- Governance & substance
Also asked about Form 7004
No. The extension protects the filing, not the payment. That distinction does real damage every year, because an entity that believes it has bought itself months discovers that the liability fell due on the original timetable and only the paperwork moved. Treat the extension as separating two dates that used to feel like one: the date the return goes in, which has moved, and the date the liability has to be met, which has not. Where an entity is waiting on overseas figures, we quantify the liability well enough to meet it while the return itself is still open.
Not in every case, and that is the assumption worth testing before you rely on it. The extension protects the filing it was requested for; the information returns that travel alongside a business return do not all follow it automatically. So an entity can be properly extended on its main return and still be late on something that accompanied it, which is a poor outcome because the exposure on those filings does not depend on tax being owed. We list an entity's whole filing set once, mark which items the extension reaches, and keep that list with the calendar.
Routinely, and it is one of the ordinary reasons the extension exists: entities very often need more time because a foreign parent or subsidiary closes its books on a different calendar. What we would not do is treat the extension as the whole answer. In a cross-border group the binding constraint is usually the foreign audit timetable, and that is worth mapping before the season starts rather than discovering each spring. Once the two calendars sit on one page, most groups find that some entities need the extension every year, some occasionally, and some never did.
The extension is automatic in the sense that it does not depend on persuading anyone that your reason is good enough. What it depends on is the request being made properly and in time, for the right entity and the right return. That shifts the risk from the merits to the mechanics, and the things that go wrong are mechanical: the wrong entity identified, a return type that does not match the entity, or a request made once the time it was meant to extend has already run out. We check those before lodging rather than after.
No. Each entity extends its own return, so a group with corporations, partnerships and a trust inside it has a set of requests to make rather than one. Groups are caught here because the group feels like a single taxpayer internally, with one finance team, one set of books and one closing timetable, while the filing population is a list of separate entities. The practical fix is a schedule of every entity, the return it files, and whether it is being extended this year, kept by the person who closes the books rather than remembered each spring.
A taxable presence in another country under the treaty — typically a fixed place of business such as an office, branch, factory or workshop, or a dependent agent habitually concluding contracts on your behalf. Some treaties add a services test measured in days. Purely preparatory or auxiliary activity is excluded, but that carve-out is narrower than it sounds: one senior employee working from home in the other country, with authority, has been enough. See business profits and permanent establishment.
Usually the country you are physically in, because employment income is generally sourced where the work is done, with your residence country taxing it as well if you are resident there and giving credit. Three things follow: your employer may acquire withholding and social security obligations where you sit, a treaty tie-breaker may be needed if both countries call you resident, and a short trip that becomes a long stay can cross a residence threshold nobody was watching. See remote workers and digital nomads.



