Data Importing
StructureGram allows you to import company information directly from ASIC (Australian Securities and Investments Commission) company extracts. This saves time by automatically extracting company details, directors, secretaries, and shareholders.
How It Works
- Upload an ASIC company extract PDF, or order one through the ASIC Direct Feed
- Review the extracted entities and relationships
- Decide how to handle each entity (create, link, or skip)
- Import to add the data to your workspace
For the review step by step, see How to Import from an ASIC Extract PDF.
Joint Shareholdings
ASIC can record a joint shareholding as one combined shareholder name, such as A & B or A && B.
When StructureGram detects this pattern, it separates the owners where it can and shows the result in the Joint shareholdings review step. If you import the joint holding, StructureGram creates:
- Separate owner entities, or links to existing entities if you choose to link them
- One generated joint holding
- A shareholder relationship from the joint holding to the imported company
This keeps the share register accurate: the owners hold one parcel together instead of being imported as one incorrectly named individual.
You can choose Import or Skip for each detected joint holding during review.
See Joint Holdings for more detail.
Duplicate Detection
StructureGram automatically detects potential duplicates to prevent creating redundant records. The system checks for duplicates at two levels:
Entity Duplicate Detection
When you upload an ASIC extract, the system searches your existing workspace for matching entities:
For Companies:
| Match Type | Confidence | Detection Method |
|---|---|---|
| ACN Match | Exact | Same 9-digit ACN (or ARBN) |
| Name Match | High | Identical legal name |
| Nearly the same name | High | A punctuation mark or a letter apart |
| Similar Name | Medium | Close spelling (fuzzy match) |
| Similar name, different ACNs | Low | Close spelling, but each company has its own ACN |
Two companies that each have an ACN, and the ACNs differ, are treated as different companies on the numbers. When their names are identical or nearly so, the review still asks, because a stored ACN may be a typo: the card says, for example, "The names match exactly but the ACNs differ, so check by hand." When the names are merely close, the match is shown as a low one and the row starts as Create.
For Individuals:
Each existing person with the same surname is scored: the name counts most, and the date of birth refines it. A date of birth one typing slip away (a day out by up to 3, a month or a year out by one, or the day and month swapped) counts for the match; a clearly different one counts against it.
| Example | Confidence |
|---|---|
| Same first and last name and date of birth, middle names the same or on one record only | Exact |
| Same full name, no date of birth to compare, or one a slip away | High |
| Same first and last name, middle name on one record only | Medium |
| Same name and date of birth, but different middle names | Medium |
| Same full name, but a clearly different date of birth | Low |
| Different middle names and no date of birth to compare | Low |
| Same surname and a close first name (never more than Low, even with the same date of birth) | Low |
The card says why, for example "Same full name (dates of birth one year apart)".
What happens when a match is found:
- Exact match: Starts on "Link" (you can change this)
- High/Medium match: Starts with no choice. The card is outlined orange, and the import waits until you choose Create or Link (or Skip)
- Low match: Shown on the card for you to check, and starts on "Create"
- No match: Starts on "Create"
Relationship Duplicate Detection
When both the source and target entities are linked to existing records, the system checks whether a relationship already exists between them.
Example: You're importing a director relationship between John Smith and ABC Pty Ltd. If:
- John Smith is linked to an existing individual, AND
- ABC Pty Ltd is linked to an existing company, AND
- A director relationship already exists between them
Then the relationship is automatically marked as Skip to prevent duplicates.
Important: Relationship duplicate detection only runs when BOTH entities are linked to existing records. If either entity is set to "Create", no duplicate check occurs (since a new entity can't have existing relationships).
Entity Actions
When reviewing extracted data, you choose an action for each entity:
Create
Creates a new entity in your workspace with the extracted data.
- Use when the person or company doesn't exist in your system
- A new record is created with all the extracted details
- Any relationships involving this entity will be created
Link
Links to an existing entity instead of creating a duplicate.
- Use when the person or company already exists in your workspace
- No new entity is created
- Relationships will connect to the existing entity
- The system suggests potential matches based on:
- Companies: ACN match or similar legal name
- Individuals: Name and date of birth match
Skip
Excludes the entity from the import entirely.
- Use when you don't want to track this person or company
- No entity is created or linked
- Any relationships involving this entity will NOT be created
Examples
Example 1: New Company Import
You import "ABC Pty Ltd" with directors John Smith and Jane Doe.
| Entity | Action | Result |
|---|---|---|
| ABC Pty Ltd | Create | New company created |
| John Smith | Create | New individual created |
| Jane Doe | Create | New individual created |
Relationships created:
- John Smith → Director of → ABC Pty Ltd ✓
- Jane Doe → Director of → ABC Pty Ltd ✓
Example 2: Existing Director
You import "XYZ Holdings" but John Smith already exists in your workspace (exact match on name + DOB).
| Entity | Action | Result |
|---|---|---|
| XYZ Holdings | Create | New company created |
| John Smith | Link (auto-selected) | Uses existing record |
| Jane Doe | Create | New individual created |
Relationships created:
- John Smith (existing) → Director of → XYZ Holdings ✓
- Jane Doe → Director of → XYZ Holdings ✓
Example 3: Both Company and Director Exist
You import an extract for "ABC Pty Ltd" but both the company and John Smith already exist with an existing director relationship.
| Entity | Action | Result |
|---|---|---|
| ABC Pty Ltd | Link (auto-selected) | Uses existing company |
| John Smith | Link (auto-selected) | Uses existing individual |
Relationships:
- John Smith → Director of → ABC Pty Ltd → Auto-Skipped (already exists)
Example 4: Skipping an Entity
You only want to import the company, not the officers.
| Entity | Action | Result |
|---|---|---|
| ABC Pty Ltd | Create | New company created |
| John Smith | Skip | Not imported |
| Jane Doe | Skip | Not imported |
Relationships created:
- None (both directors were skipped)
Tips
- Review carefully before you import — imports cannot be undone
- Trust exact matches — they're auto-linked because they share unique identifiers (ACN or Name+DOB)
- Answer high/medium matches — the import waits for them; check that it's the right person or company before choosing Link
- Link when possible — this prevents duplicate records and maintains data integrity
- Skip irrelevant data — you don't need to import every officer
- Imported entities are marked with their source for easy identification
Supported Formats
Currently supported:
- ASIC Company Extract PDFs, whether they carry a text layer or are scanned images (a scanned page is read with OCR)
- ASIC Direct Feed extracts ordered inside StructureGram
Note: This page covers importing from ASIC company extracts. To bulk-create entities from a spreadsheet instead, see CSV & Excel Import.
Related Topics
- CSV & Excel Import — bulk-create entities from a spreadsheet instead of an ASIC extract
- How to Import from an ASIC Extract PDF — the upload and its review
- Import History — past imports, downloads and reprocessing
- Joint Holdings — how joint shareholder rows are imported from ASIC
- Connecting to Xero Practice Manager — set up the XPM integration
- Xero Practice Manager Sync — import entities from XPM
- Push to Xero Practice Manager — export entities to XPM
- XPM Reconciliation — compare and resolve SG vs XPM differences
- Understanding Groups — organize imported entities into groups
- Relationship Types Reference — supported relationship types