Why Do I Need To Map Fields When Importing Transactions?

Why Do I Need To Map Fields When Importing Transactions?


We need fields to be mapped in order to:

We try to make the mapping as painless as possible by:
  • Analyzing your data to guess likely mappings
  • Remembering your mappings for future imports
  • Enabling automated imports from connections

To learn more about system vs. imported fields, click here.


    • Related Articles

    • Which Format Do You Support When Importing Transactions?

      We do not have a pre-defined, preferred format. We provide different ways to ingest sales transactions - from CSV files, from CRM and accounting systems (ex: QuickBooks, HubSpot, SalesForce, Stripe, Chargebee, Xero, Dynamics, etc.), from FTP, from ...
    • What Type Of Support Is Available For Stripe?

      By adding a Stripe connection to your workspace, you can automatically import and sync sales transactions to your workspace We support charges, invoices, refunds You will need to map fields the first time you import transactions Newly created Stripe ...
    • How Can I Programmatically Import Sales Transactions?

      For non-programmatic import options, click here. Three options are available: You can use a Web Endpoint. Using this model, you deploy a web page, from which we securely pull transaction data. We will query your web page at least every hour. You can ...
    • What Type Of Support Is Available For QuickBooks Desktop?

      All editions of QuickBooks Desktop are supported: Pro, Enterprise, etc. By adding a QuickBooks connection to your workspace, you can: Automatically import users into your workspace We will detect users who are already present within your workspace ...
    • What Type Of Support Is Available For QuickBooks Online?

      By adding a QuickBooks connection to your workspace, you can: Automatically import users into your workspace We will detect users who are already present within your workspace and only suggest adding missing ones You will be able to review and edit ...