Understand how company records work in Sanka, including customers, suppliers, associations, imports, ownership, and AI checkpoints.
Last updated: May 29, 2026
The Company object stores organizations you work with, such as customers, suppliers, partners, agencies, distributors, and parent or subsidiary companies. Use company records as the shared account master for sales, purchasing, billing, support, and integrations.This reference explains what a company record should contain, how it connects to other records, and what to check before creating or updating company data with AI, CSV, integrations, or manual entry.
What a company record represents
A company record represents one organization. It can be used as a customer, supplier, partner, or another business relationship depending on your workspace setup.Common fields include:
Company name
Email address, phone number, website, and address
Record owner
Customer, supplier, or partner classification
Parent company or subsidiary relationship
External IDs from CSV imports or connected systems
Notes, files, and custom properties used by your process
Company properties can be customized by workspace admins. If a status, category, or classification is not available in your workspace, check the property settings before treating it as a bug.
How companies connect to other records
Companies are often the starting point for downstream work.
Contacts: people who work at or represent the company
Deals: sales opportunities or commercial discussions with the company
Estimates and orders: quotes and accepted orders for the company
Invoices and payments: billing and payment records related to the company
Purchase orders and bills: supplier purchasing and payable records
Contracts and tasks: agreements, follow-ups, and internal work
Parent and child companies: company hierarchy for groups, branches, or subsidiaries
If an associated record is missing from a company view, first check whether the association exists and whether your current view includes that related record section.
Create or update companies
Company records can be created in several ways:
Manually from the Company object
By CSV import
From connected integrations
From an AI-assisted draft
Through actions or workflows configured by your team
When using AI, start with a review step before creating or updating records.
Sample prompt
/sanka Review this customer and supplier list before creating company records in Sanka. Identify duplicate company names, missing owner or classification fields, parent-child relationships, and rows that may need manual review. Do not create or update records yet.
After the review, confirm the records to create or update, the matching key to use, and whether archived records should be considered.
Import and match companies
For CSV imports, include a stable identifier when possible. Company name alone can be risky when spelling, punctuation, or legal suffixes vary.Recommended matching fields include:
Company ID
External ID from the source system
Domain or website
Email address
Phone number
Exact company name when no stronger key exists
For parent-child company relationships, import or update the parent company first, then map the child company to the parent using the configured company reference field.For detailed import steps, see CSV import and Customer and vendor management.
Expected behavior
When a company is created successfully:
It appears in the Company object list unless it is archived or filtered out by the current view
Its owner, source, and key properties are saved on the record
Related contacts, deals, orders, invoices, bills, and other records can be associated with it
Custom fields follow the workspace property configuration
Imports and integrations may store source details so the same company can be updated later
Archiving a company hides it from active views. It does not automatically delete related contacts, orders, invoices, or history.
Troubleshooting
A company does not appear after import
Check whether the import completed, whether the row failed validation, whether the record was archived, and whether your current view filters it out.
A duplicate company was created
Check which matching key was used during import or integration sync. If the source did not provide a stable ID, review company name, email, phone, and domain before merging or archiving duplicates.
A contact is not linked to the company
Confirm that the contact record has an association to the company. If the contact came from CSV, confirm that the company identifier in the contact CSV matched an existing company.
AI cannot decide whether to create or update
Ask the AI to list possible matches first. Do not create records until you confirm which existing company, if any, should be updated.
Checkpoints
Use logs and record history to confirm who created or updated company records and which source was used.
Search Sanka...
Review company changes
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Reviewed duplicate candidates2026/05/10 10:45CompaniesChecked company names, domains, and external IDsClaude integration
2Imported company CSV2026/05/10 11:05CompaniesCreated 12 records and updated 3 recordsCodex integration
1Updated company owner2026/05/10 11:20Green Salon GroupChanged owner to Sales OperationsSanka user
Company changes should be checked together with contacts, associated deals, orders, invoices, and supplier records when they affect downstream workflows.
