Two professional languages. One clear handover.

Separate the tax timetable from the reporting timetable.

A US return and a monthly reporting package may concern the same client but have different deadlines, preparation inputs and reviewers. Define the next action for each engagement, then discuss the client with both situations in view. This helps the team explain why a return is waiting while the monthly review can still move forward.

Keep the client facts and responsibilities clear across locations. A French colleague may gather group information while a US colleague manages the return. The useful handover includes the requested information, the relevant period and the professional decision it will support.

Let each professional work in the right language.

The application is available in English and French, chosen by each user. Tax Workflow status labels such as Not in yet, Extension, Filed, Complete and the signature stages stay in English, matching the working vocabulary of the application.

Explain those labels when coordinating the work. A shared label should refer to the same completed event in both languages. In review discussions, identify the accounting concept and its supporting document rather than relying on a translated account name alone.

Scroll the table if needed.

A fictional subsidiary shows the two workflows together.

Sample subsidiary Meridian US has a 1120 engagement and a monthly QuickBooks review. The tax manager checks the return checklist and records the missing information. The reviewer works on the close period, reconciles the bank balance and requests an intercompany confirmation from the parent.

The team agrees who obtains each document and who approves the resulting work. The tax return is prepared and filed in the firm's tax software. The review ends with a supported Excel workpaper that can be discussed with group finance.

Fictional example · sample data

Read each jurisdiction before discussing the payment plan.

Estimated payments may concern federal and state positions for the same client. The baseline workflow brings the inputs and manager approval together, then creates the Q1–Q4 installments. As completed payments are recorded, the amounts remaining are recalculated.

For the bilingual handover, name the taxpayer, jurisdiction, year and amount. This is more useful than a general message saying that the quarterly payment is done. The professional responsible checks the applicable taxpayer rules before approval.

Agree the deliverable the parent expects.

A useful monthly handover explains the reviewed balances, unresolved questions and proposed adjustments. Close Review exports the summary, financial statements, adjusting entries and cycle schedules in Excel. Discuss the group's expected period and reporting format before the work begins.

The underlying accounting conclusion belongs to the professionals. The workpaper supports the discussion by connecting balances and evidence, while the group defines its reporting requirements. Use the subsidiary reporting page when the question is what finance should receive.

Begin with one cross-team handover.

Choose a sample subsidiary with one return and one close period. Explain which colleagues prepare, review and exchange the supporting information. A demo can follow that case in both workspaces and make the bilingual coordination concrete.

The product was shaped on day-to-day US tax and review work, including US subsidiaries of foreign groups. Pilot onboarding gives the firm a direct way to examine the relevant workflow with the product team.

Common questions