Clubtreasurer’s Transaction Import feature allows you to upload transactions from your bank statements or online payment systems to quickly create multiple Receipts & Payment transactions.
- Transaction Import – Overview Tutorial
- Mapping Import Columns
- Automatching Options
- Importing Data from Online Payment Systems
- Other stuff
Transaction Import – Overview Tutorial
This tutorial shows you the basic steps required to run a Transaction Import from a Bank Statement and is mandatory viewing for anyone wanting to use this feature. Please also see the Importing Data from On-line Payment Systems video below if you need to import transactions from on-line payment systems such as Paypal, SumUp, GoCardless, etc..
Click the the 3-dots icon to expand (Enter full screen). Use Space bar or Enter to move slides.
Import Mapping Columns
When you import your data you need to map the source columns to Clubtreasurer’s “Target” columns. The import process will automatically map the columns where it finds a name match but in many cases, you will need to manually map them by selecting the appropriate value from the Target column.
The minimum mandatory Target columns required to import your data are
DATE, DETAILS and AMOUNT
| DATE | DETAILS | AMOUNT |
|---|---|---|
| 10-JAN-2024 | John Smith Membership Income | 25.00 |
| 11-JAN-2024 | Building Maintenance Costs | -1050.00 |
| DATE | DETAILS | PAID OUT | PAID IN |
|---|---|---|---|
| 10-JAN-2024 | John Smith Membership Income | 25.00 | |
| 11-JAN-2024 | Building Maintenance Costs | 1050.00 |
Full list of columns that can be imported
| Target Column | Required? | Comments |
|---|---|---|
| DATE | Required | Map this column to your bank statement’s Date column |
| DETAILS | Required | You can also use the alternative DESCRIPTION or MEMO mapping columns but you must only use one of these in your import. |
| AMOUNT or PAID-IN (CR) AMOUNT + PAID-OUT (DR)AMOUNT | Required | *Used where the statement has a single Amount column *Used where the statement has separate Dr/Cr Amount columns. (You must map both columns if using this option). |
| Paid/Pmt Ref | Optional | Paid-in/Payment Reference Details |
| Vouch/Inv. No. | Optional | Voucher or Invoice Number |
| Comments | Optional | Comments |
| Cost Code | Optional | You can import Receipt & Payment Cost Codes in your source data if required. Importantly. the imported Cost Codes MUST start with their 4-digit codes (e.g. “4002 Membership Income“) which the import process will use to match to the correct Cost Code. If no match is found it will return the Default Cost Codes in the Import Transactions page (or be over-written by the Cost Code Auto-matching, if selected). |
| Events | Optional | You can import Events during the import process. Imported Event names must exactly match the existing Events already setup in Clubtreasurer, otherwise the import will fail for that line. You can leave the Event field blank for row(s) that you do not want to define an Event. In this case, the system will use the Default Event during the Import Transactions process. |
Auto-Matching Options
As well as the Default Import values in the final Transaction Import page, you also have options that use algorithms to automatically match Cost Codes and Members that can dramatically speed up the import process.
Cost Code Auto-Matching
When the “Use Cost Code Auto-Matching?” option is selected and you click the “Create/Refresh Draft Import Rows…..” button, the import process will attempt to automatically assign Cost Codes to the imported rows based on matching row descriptions to existing historic transactions. Rows that fail auto-matching will use the default Cost Codes and will be highlighted in red.
You can change all Cost Costs as before by editing rows in the Draft Import Rows table.
CAVEAT: The matching algorithm is an approximation and may not always provide an accurate match in all cases. You should therefore review your imported rows and manually change incorrectly matched Cost Codes in the Draft Import Rows table below.
Members & Membership Auto-Matching
Organisations using the Membership Management application will see “Member” and “M’ship Billing Line” columns in the Draft Import Rows table.
When the Match Members & Membership option is selected, the Import process will try to match Members to your imported rows based on the source data Details column.
The matching algorithm attempts to match Members and Membership Billing Lines in the following order:
Matching Process #1: Billing Line ID (= Invoice No.)
Returns Member and Billing Line/Invoice when the import process matches an existing, unpaid Billing Line in the imported Details column. This is the most accurate method and we recommend asking your members to add the Billing Line/Invoice No. to their payment references. (Your members can see the Invoice No. on their invoices and/or statements)
This is the only matching process that returns the Member AND Billing Line/Invoice and is therefore the recommend process.
eg. Source Details: “Burt Bison ref123456” would match to Billing line/Invoice 123456 and return both the Member and Billing Line.
Matching Process #2: Transaction Import Reference
If no match is found in Step 1. then the import process will try to return the correct Member record by finding an exact match within the imported Details column and the Transaction Import Reference value stored against the member record.
The Transaction Import Reference is a unique ID that can be used to identify a specific member when included in the source data Details columns.
Examples include:
– Direct Debit/Faster Payments Mandate
– External Payment system reference
– Alternative member names
You can store up to 3 x Transaction Import References per member.
eg. Source Details: “Bison DD009998877” would match to member Burt Bison if he has “DD009998877” Transaction Import Reference stored in his member record.
Matching Process #3: Member Name Matching
The final matching process is used if #1 and #2 are not successful. It uses a ‘fuzzy logic’ process to find the nearest matching member name based on the Details column.
eg. Source Details: “B.Bison” would match to member Burt Bison*
*CAVEAT: The matching algorithm is an approximation and may not provide an accurate match in all cases. It is very sensitive to the quality and/or completeness of the source data – eg. the example above might also return “Bessie Bison” or “Bill Bison” as other close matches. You should always review your imported rows and manually change or remove incorrectly matched Members and Billing Lines in the Draft Import Rows table.
Matching Billing Lines / Invoices
When Members are matched by Processes #2 and #3, the process will also try to select the oldest unpaid Billing Line/Invoice that matches the imported line amount, otherwise it will return “Unallocated Membership Transaction” or “Non-Membership Transaction” (based on an import process option). You can then manually update this in the Draft Import Rows table and select the correct Billing Line / Invoice.
For more details on importing Membership payments and Transaction Import Reference please see Managing Billing & Payments – Importing Membership Payments #4 tutorial for more details.
Importing Data from Online Payment Systems
This is a demo of how to import transactions from online payment systems such as PayPal, GoCardless, SumUp.
Unlike bank statements, online payment system downloads will often have multiple amount columns for each transaction line, eg. a gross amount; a transaction or processing fee; and a net amount. When you import these into Clubtreasurer you will usually want to import these as separate transaction lines.
The following tutorial video shows you how to easily do this by running the import process two (or more) times.
Import Update: When mapping source columns we now recommend also mapping your TRANSACTION_ID (or equivalent) to Vouch/Inv No. column in Clubtreasurer. The TRANSACTION_ID is a unique reference number for each imported line and will ensure the imported transactions are accurately matched together. Note this is highlighted in the video tutorial but is not demonstrated.
Other Stuff
How to split & copy lines during Import Transaction
This quick video shows you how to split/copy and edit lines during the Import Transaction process (1:19)