In order to provide you with the flexibility to build your own custom reports with details of customer transactions, we've built the Transactions Object!

Our object gives you the flexibility to ingest transaction information from some of the largest accounting providers and transform it into whatever your users need, and your use case. Leveraging this object will allow you to reference Accounts, Contacts, and Items to build up complex views and histories for your users.

The Current Support of Transaction Types:

Netsuite:

Our Netsuite integration captures a majority transaction offered by the third party provider, which you can find here. The ones that will not be covered as a transaction_type are those that are supported by other Common Model Objects such as Invoices, Memos, and Vendor Credits .

Quickbooks:

There are two types of Transactions currently supported for Quickbooks: Estimates and Deposits.

Estimate:

The "Estimate" transaction_type will involve transactions from the business to a customer for good/services that are proposed to be sold. This will also include proposed pricing.

Deposit:

The "Deposit" transaction_type will involve transactions where there is a customer payment that's originally held in the "Undeposited Funds Account" within Quickbooks, is moved into a specific "Asset Account". It can also reference a direct deposit listed within Quickbooks.

Xero:

We support a single transaction_type for our Xero Integration: "Bank Transactions". This will involve the transaction where there are spending and receiving of money, overpayments, and prepayments. You can find more information on the transaction type here.

Note: This does not access any bank statements or direct bank feed!

Did this answer your question?