SalesTOSLet’s talk
Reporting & Data · Excel & CSVFile import supported

Start with an approved template and a reviewable import.

Supported file workflows include product CSV preview/import and configured target uploads. Some daily XLSX workflows are restricted to specific enabled deployments. A spreadsheet extension alone does not make a file compatible.

Excel & CSV Scope map · enabled file workflows
Excel & CSVApproved source file
01
Product catalogue CSVFile → SalesTOS
02
Target CSVFile → SalesTOS
03
Daily XLSX dataFile → SalesTOS
SalesTOSProduct creation or updates

Record ownership and direction are defined below. No universal two-way sync is implied.

The operational need

Why connect these systems?

Column names and identifiers must match the selected workflow.

A duplicate product code should not silently create a second product.

Rejected rows need correction before the next upload.

Direction, ownership, prerequisites

What data can be exchanged?

Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.

Excel & CSV data scope
Record or objectDirectionSystem of recordPurposeAvailability / prerequisites
Product catalogue CSVFile → SalesTOSAgreed product masterProduct creation or updatesSupported product template and manage permission
Target CSVFile → SalesTOSApproved target sourceEnabled target workflowSupported in configured target upload
Daily XLSX dataFile → SalesTOSAgreed sourceSpecific daily-data workflowDeployment-restricted; not general Enterprise entitlement
Customer or receivables filesFile → SalesTOSAgreed source systemCandidate migration or balance feedSample and enabled importer assessment required
Connection design

How the connection works

Use the exact template for the enabled workflow. Product imports support preview and row validation, with up to 5,000 rows per submission. Matching product codes can update existing products. Different importers have different duplicate and transaction rules; do not generalise one importer’s behaviour to all spreadsheets.

Illustrative working scenario

From system context to a useful next action.

An authorised manager previews a product CSV, corrects invalid rows and imports the accepted catalogue changes. The result identifies row errors; the manager reviews the result before retrying rejected data.

What happens to writeback?

Importing a file changes the selected SalesTOS records. It does not update the originating ERP or accounting workbook automatically.

Before implementation

Setup requirements

  1. Selected enabled import workflow and current template
  2. Stable record codes and sample rows
  3. Authorised user with required manage access
  4. Backup/review approach and correction owner

Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.

Operating the agreed scope

Reliability & access

Product imports validate rows and match existing product codes within the tenant; a submission may contain partial successes. Restricted daily upload workflows have separate batch and duplicate controls. Inspect the actual result before retrying to avoid unintended updates.

A clearer scope starts here

Questions, answered.

Excel & CSV integration

Can we upload any Excel file?

No. Each workflow expects a specific format and mapping.

Will matching product codes create duplicates?

The supported product importer matches existing tenant product codes for updates; review the preview and result.

Can an import partly succeed?

Yes, product imports may report accepted rows alongside row errors. Retry only after reviewing the outcome.

Are daily XLSX uploads included for everyone?

No. Those workflows are enabled only in specific deployments and require scope confirmation.

What should we prepare for a Excel & CSV discussion?

Selected enabled import workflow and current template; Stable record codes and sample rows; Authorised user with required manage access; Backup/review approach and correction owner. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.

How is Excel & CSV integration scope confirmed?

Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. Importing a file changes the selected SalesTOS records. It does not update the originating ERP or accounting workbook automatically.

Explore the adjacent workflow

Related integrations

View all integrations →

Your systems. A defined scope.

Discuss Excel & CSV with SalesTOS.

Bring your business workflow and current setup. We’ll use them to assess the right data scope.

Discuss This Integration