ⓘ This article is for all users of Sumday
Sumday uses financial transaction data as a base for the calculation of an organisation's emission assessment, before overlaying activity data to enhance relevance and accuracy of the carbon assessment. This process involves associating emissions with purchases to create an emissions profile.
The data Sumday needs is often held in a business's finance or ERP system. Users may need to engage their finance team or accountant to assist in exporting financial data from the finance system to import into Sumday if they do not have access to it themselves.
There are three ways to import financial data into Sumday:
- CSV file import - export a CSV file of data from the finance system to import into Sumday.
- API Connection - custom connection to your finance or ERP system with the support of an IT expert
- Xero Integration - import transactions from your Xero account directly to Sumday
💡 Tip: We recommend that you finalise your end of financial period procedures and adjustments prior to importing transaction into Sumday, this will help to ensure that the amounts in Sumday reconcile back to your finance system. And there is nothing more satisfying when the books balance - so try and keep it that way!
Data required from the Finance System
| Field Name | Details |
Required/ Optional |
|---|---|---|
| Transaction Date | The date the transaction occurred | *Required |
| General Ledger Account | This is the Name of the Account in the General Ledger. This will be linked to the Account Code above | *Required |
| Amount | This is the monetary value associated with the transaction | *Required |
| Contact | The Supplier/ Customer associated with the transaction | Optional |
| Contact Business ID Number | The Business ID number associated with the supplier/customer (e.g NZBN, ABN) | Optional |
| Reference | Include the invoice or journal reference number to allow this transaction to be tied back to the source data. | Optional |
| Description* | The description of the transaction as outlined from the general ledger transaction details | Optional |
| Tracking Category | If your organisation uses divisional reporting, this will be the relevant reporting category within your account structure. | Optional |
| Account Code | Code, usually numeric, associated with a General Ledger Account | Optional |
| Transaction Reference | Any other references related to the transaction that may be useful to include. | Optional |
*We recommend including transaction reference details in the ‘Description’ column, to provide more context for the Carbon Bookkeeping process.