The Commerce module configuration is used to set up options for how a linked commerce data source should be synchronised with a linked accounting software instance for a company.
The configuration endpoint should be used to set up the following options for data synchronisation. In most instances the endpoint will be used to power an end-user facing UX for merchants to select these options themselves.
The synchronisation can be enabled or disabled at the root level or at the individual data type level: sales, payments and fees (see Overview for description).
The schedule config section specifies when the synchronisation will push new data to the connected accounting software. It is not used to determine the split of commerce data by time period when inserted into the accounting software; for information on this, please see grouping (below).
Payments, transactions, invoices, line items etc. must all be synchronised with the correct linked account from the business' chart of accounts to ensure correctness and consistency of the user's accounting software data. For each account configuration the user can set up, the config data model provides:
Metadata for the account configuration, including if it is
descriptionText. This information is often used to dynamically build front-end UX for the end-user.
A list of valid accounts that already exist in the user's accounting software, the
accountOptions. The chosen account from this list will have the
idset as the
New accounts can be created using the New Account Endpoints.
To ensure data is synchronised with the level of detail required by the user, the grouping configuration must be set.
The grouping config covers the following options:
The split of transaction data synchronised to a user's accounting software is determined by the
selectedGrouping. The greater the number of selected groups, the more granular the data synchronised to accounting software will be.
groupingPeriod defines how transactions should be grouped by time period.
Goods and services sold by companies may have different tax rates, requiring that synchronised sales transaction data is grouped by tax rate. A valid tax rate in the destination accounting package needs to be selected for each of the tax rates which will be used during the synchronisation process.
Updated 4 months ago