One person often runs several entities: a company, a trust, a self-managed super fund. You can send a separate request for each, though most people don't need to.
Give each entity its own page
This is the setup we recommend.
- Open Requests.
- Create or open the request.
- Add one page per entity, and name each page after the entity it covers.
Your client answers for every entity in one place, and you follow one request instead of a stack of them.
If every entity needs the same questions, use a repeatable section instead and your client fills it in once for each entity. A section can be filled in up to 20 times. For a client with more entities than that, use separate pages or split the work across two requests. Let clients repeat a section covers how to set one up.
Nothing stops you putting questions for several entities on one page instead, if that suits the work better.
You can also send a separate request for each entity. The downside is that your client gets several sets of email reminders. If they sign in to the client portal, they see all of those requests and their progress in one place.
When one person acts for several entities, this article covers how to set them up as one client with a company for each entity.
Which client your integrations use
A request can have more than one client on it, but your integrations only ever use the first one. That's the primary client, and its details are what the later steps work from.
- Files in cloud storage. Every file integration files documents under the primary client, so FYI, SharePoint, Google Drive, OneDrive and Dropbox all put a request's files in one place, whichever entity's page they came from. Content Snare can't send each entity's files to its own place in your storage. In FYI, if that client is linked to more than one entity, the same file goes to each of them. To change that, open the client and unlink any entity you don't want files going to. Connect FYI covers the connection.
- Exports. Exports do separate by page. Turn on Attachments and the export comes down as a zip with a folder for each page, named after that page, so one page per entity gives you one folder per entity.
Xero Practice Manager is the one exception. It can create a separate client for each entity through integration actions, which is what the rest of this article covers.
Create a Xero Practice Manager client for each entity
Adding another entity page does not create another client in Xero Practice Manager (XPM) on its own. The Create new client action attaches to one page or section, so every entity page needs its own action.
On each entity's page:
- Turn on Enable integration actions.
- Add a Create new client action.
- Map that entity's own client name and email into it.
Check the result in XPM the first time you do this, before you rely on it for a run of clients.
An action can only access the questions on its own page, so keep each entity's name and email questions on that entity's page. If you don't map them, the new client arrives in XPM under the first client's details instead of the entity's own.
A repeatable section works differently from a page. It creates one XPM client each time your client fills the section in, and takes the name from the first and last name questions you map. Map an email question too, or those clients arrive in XPM with no email address. Connect Xero Practice Manager covers setting the integration up.
Actions run for the whole request at once
Run integration actions runs every entity's action together. If one entity's XPM client didn't come through, you re-run the whole set, because there's no way to run one entity's page on its own.
Map an email for every entity before you do this. The email is how Content Snare recognizes an entity that already exists in XPM, so it stops and warns you instead of creating a second one. With no email it has nothing to match on, and a re-run makes duplicates.