Your copy. Your pace.

Business-entity relationship intake

Use a business onboarding questionnaire to create a reviewed entity and ownership map for the engagement. The design keeps source references, uncertain matches, and approval decisions visible to the responsible accountant. It coordinates an administrative handoff with version checks and an exception queue. Do not infer tax elections, beneficial ownership obligations, or legal relationships.

Planning workbook. This file helps you document a process. It does not connect to accounts, read records, send messages, or complete external actions. It works offline and sends no entries anywhere. Entries are not saved automatically; export or print a copy before closing. Avoid entering sensitive information.

1. Define the starting point

Start with a business onboarding questionnaire. A successful handoff produces a reviewed entity and ownership map for the engagement. Define the accountable owner before connecting systems. Do not infer tax elections, beneficial ownership obligations, or legal relationships. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.

Process owner and backup rolesWhat will count as complete?

Current handling time and exceptions

2. Walk through the process

1. Collect scoped entity facts

Request legal names, jurisdictions, entity references, and authorized contacts through the approved channel.

We have defined the owner, required information, and completion check for this step.Step 1 working notes

2. Normalize without merging

Keep registered names and trading names distinct. Preserve the original answers.

We have defined the owner, required information, and completion check for this step.Step 2 working notes

3. Build a candidate relationship map

Link supplied parent, subsidiary, and owner references with an explicit unverified status.

We have defined the owner, required information, and completion check for this step.Step 3 working notes

4. Review supporting records

Staff checks the relevant formation and engagement documents and resolves conflicting identities.

We have defined the owner, required information, and completion check for this step.Step 4 working notes

5. Publish the approved map

Use stable entity IDs for downstream document requests and reporting permissions.

We have defined the owner, required information, and completion check for this step.Step 5 working notes

3. Check the information

Use invented references in this worksheet. Keep real documents and personal records in an appropriate private system.

Reference field	Working record	Check
entity_id	entity_id	Resolve the stable source reference in the correct client, entity, and engagement.
registered_name	registered_name	Resolve the stable source reference in the correct client, entity, and engagement.
relationship_type	relationship_type	Resolve the stable source reference in the correct client, entity, and engagement.
verification_ref	verification_ref	Resolve the stable source reference in the correct client, entity, and engagement.

Source of truth and access boundaries

4. Verify the process

Use synthetic examples. Mark a check only after recording what actually happened.

Two similarly named entities remain separate.A disputed ownership relationship enters review.A repeated source event creates only one current review task.A changed source version invalidates an earlier approval.A named person can resolve an unclear or incorrect result.Work stops when the task is complete, withdrawn, or outside the agreed scope.A duplicate or interrupted handoff can be recovered without repeating a consequential action.Expected result, observed result, and recovery notes

5. Decide the next step

Your smallest reversible pilotReview date and decision

Retain qualified professional review for legal, accounting, tax, medical, financial, or other consequential decisions. This workbook does not certify compliance or guarantee results.