Deltalyze日本語
← All articles

Claude Cowork and Chat Become One: 3 Things Accounting Managers Should Check

On September 16, 2026, Anthropic announced that it had integrated Claude Cowork's features into Claude itself. The functional merger between Cowork and Chat, previously separate apps, is now underway. For accounting managers, the key points are sorting out internal naming conventions and checking with the contracted support channel used in-house.

A diagram showing Claude Cowork and Chat integrated into one Claude

01What Was Announced

On September 16, 2026, Anthropic announced that it would integrate Claude Cowork's features into Claude itself. Until now, Cowork had been offered separately as a collaborative app for teams, but this integration brings the functionality of Chat and Cowork closer together.

It has also been reported that Cowork itself has been folded into Claude proper. This shows that the change is not merely a rebranding but an integration accompanied by functional changes.

The essence of this change is that users no longer need to spend effort deciding "which app to open."

A diagram showing the flow of Claude Cowork and Chat merging into one Claude app
The structure in which Cowork and Chat merge into a single `Claude` app

02Pricing and Availability

The official announcement Claude Cowork and chat are now one Claude confirms that the integration of Cowork and Chat was announced on September 16, 2026. Within the scope of the materials referenced here, no specific details about pricing plans, contract terms, or rollout timing could be confirmed.

The announcement does mention a notice period of at least 30 days for Enterprise administrators. Since the timing of the switchover and how the notice is delivered may vary depending on contract type, it is worth checking whether a notification email addressed to your internal administrator has been overlooked.

As for the rollout timing for Team and Free plans, the official page does not list specific dates, so this remains unconfirmed.

For availability in Japan as well, the most reliable approach is to check the status page for the plan your company is subscribed to.

2026-09-16Announcement date (Cowork/chat integration)Source: Anthropic「Claude Cowork and chat are now one Claude」(2026-09-16)
30+ days priorAdvance notice period for Enterprise administratorsSource: Anthropic「Claude Cowork and chat are now one Claude」(2026-09-16)

03Applications in Accounting and Business Process Reform

With this integration, it appears that team collaboration work previously done in Cowork and individual queries or text generation previously done in Chat will now be able to move back and forth more seamlessly.

This may reduce the friction of switching apps for tasks such as drafting closing materials, drafting approval requests, or drafting responses to internal policy inquiries. However, within the scope of the materials referenced here, no specific claims backing up concrete effects on these tasks could be confirmed.

The direct impact on more specialized accounting processes, such as reconciling journal entries or matching supporting documents, could not be confirmed from the materials referenced here.

When using AI in on-site operations such as manufacturing, the cost of switching between tools is a similarly relevant issue. When considering a shift to a hands-on operational model, it is necessary to check not only with the accounting department but also with the operational design on the front line.

For an overview of how to incorporate generative AI into accounting operations, see Building Next-Generation Internal Workflows Incorporating Generative AI. The question of why documents created to address knowledge silos stop being used is discussed in Why Do Documents Created to Address Knowledge Silos Stop Being Used?. For operational design around AI adoption on the manufacturing side, Shifting to an AI Hands-On Operational Model in Manufacturing is a useful reference.

  • Drafting closing materials may potentially be completed within a single app (speculative)
  • Drafting approval requests and querying internal policies can be done on the same screen
  • Direct impact on journal entry reconciliation or supporting document matching could not be confirmed from the materials referenced here

04What to Verify Regarding Controls and Data Handling

One point to verify is whether the data storage location and access permission settings after integration remain the same as before. How the permission design from when Cowork and Chat were separate apps carries over after integration needs to be checked individually on your company's administrator screen.

Whether the setting for permitting or restricting use in training data is maintained from before the integration, on a per-plan basis, should also be confirmed before contract renewal if you have an Enterprise contract.

The continuity of audit records is another point to consider. Whether logs from the period when Cowork and Chat were separate apps can be tracked in the same format as logs after integration needs to be confirmed jointly by your IT department and accounting department.

When estimating cost savings or reduced workload, this kind of verification work regarding controls itself needs to be factored in as a cost. Many cases where estimates fail to gain traction on the ground stem from missing this type of premise-checking.

Points regarding controls that should be sorted out before using AI in accounting are summarized in Points on Controls to Sort Out Before Using AI in Accounting. Factors behind why cost-saving estimates get rejected on the ground are discussed in How to Fix Cost-Saving Estimates That Get Shot Down by "So, How Much?".

Official video of the integration announcement by Anthropic

05The Next Step

What you should do this week is check with your company's contracted support channel or status page to confirm whether there have been any changes to pricing plans or contract terms. You should also check weekly whether the tool name shown on invoices matches the name used internally at your company.

Rather than taking comfort in the fact of the integration alone, accounting managers should personally verify pricing plans, contract terms, and permission and data storage settings—that is the next step to take for a change of this scale.

For conditions for successfully driving AI adoption led by frontline staff, see 3 Conditions for Success in Operator-Led AX. For the idea of connecting data and decision-making instantly, The Instant Connection Between Data and Decision-Making That the Deltalyze Platform Aims For is also a useful reference.

  • Confirm your company's contract type (Enterprise/Team/Free)
  • Check with your contract support channel for any changes to pricing plans or contract terms
  • Check permission settings and data storage location on the administrator screen
PROMPT TEMPLATEDraft Prompt for an Internal Notification Email
You are a staff member in the accounting department. Under the following conditions, draft an internal notification email.

Background: On September 16, 2026, Anthropic announced that it would integrate Claude Cowork into Claude itself.

Conditions:
- The recipient is [within the accounting department, or the name of a related department]
- The purpose is to notify staff of the app name change and to standardize tool naming
- Include a line stating: "Check on the monthly invoice whether the labeling remains as [current label] or changes to [new label]"
- Clearly state whether your company has an [Enterprise contract/Team contract/Free plan], and note that you will confirm with the contract support channel whether there are any changes to pricing plans or contract terms
- Use polite/formal tone, within 300 words

Replace the bracketed text with your company's contract type and the name of the department in charge.

SOURCES

Sources and references

  1. Anthropic「Claude Cowork and chat are now one Claude」(2026-09-16)
  2. 9to5Mac「Anthropic merging Claude Cowork with chat」(2026-09-16)
  3. TechRepublic「Anthropic Folds Cowork Into Claude, Adds Document and Slide Tools」(2026-09-17)
  4. Yahoo Tech「Claude looks a little different now that Chat and Cowork are one」(2026-09-21)

KEY TAKEAWAYS

What to carry into implementation

  • Claude Cowork's features have been integrated into Claude itself
  • Check with your internal contract support channel for any changes to pricing plans or contract terms
  • Drafting closing materials or approval requests may potentially be consolidated into one app, but no specific claims backing up the effect could be confirmed
  • Whether permission settings and data storage carry over should be individually confirmed on the administrator screen

FAQ

Frequently asked questions

Will the internal usage fees change due to the Claude Cowork and Chat integration?

Within the scope of the materials referenced here, no specific claims regarding changes to pricing plans or contract terms themselves could be confirmed. Please check with your company's contracted support channel or status page.

For Enterprise contracts, what should be confirmed?

It is recommended to check on the administrator screen whether permission settings and data storage location are maintained after integration, and to confirm whether the setting for use in training data changes, before contract renewal. Note that a notice period of at least 30 days for Enterprise administrators is mentioned in the announcement.

Has a rollout timing been set for availability in Japan?

Within the scope of the materials referenced here, no specific mention of a rollout timing for Japan could be confirmed. Checking the status page for the plan you use is the most reliable approach.