You should contact the MCA Suite support team to gain access to the MCA Suite test environment to test the format of your comma separated values (csv) file before importing your transactions to your MCA Suite instance.
You can perform a bulk import of your transactions into MCA Suite instead of entering each manually. To import your transactions, you must create and format a comma separated value (csv) file with the following columns:
| Column | Label | Required? | Description |
| A | Collector Name | Yes | The name of the collection company. This company must exist in your system and be an exact match |
| B | Date | Yes | Date of the transaction |
| C | Merchant Number | Yes | The unique merchant number associated with the deal collection method under 'Deal Tracking' |
| D | Merchant Name | A merchant name for this transaction | |
| E | Amount | Yes | The amount of the transaction |
F | Description | A description for the transaction | |
| G | Type | Either "Upload, Fee, or Discount". Or leave blank for 'Upload' default. |
Read more about collector and merchant number here.
Once you have your file ready, go to Admin > Import > Transactions page to select the file to be imported. For Advance users creating a custom import format, please review this article.
Click the "Upload" button to upload your file to MCA Suite. If your csv file format does not meet our validation rules, you will see a rejection message. After your csv file has been accepted by MCA Suite, you will see an "Upload Success!" message and the uploaded file listed.
A format dropdown will appear, choose "Default" and then click the "Process" button to complete the upload process. If there are any errors while processing, you will receive error messages detailing the problems that need to be resolved in order to continue. It will also display any deals that were paid off.
Attached to this article, you will see a template containing an example of what can be imported into MCA Suite. Note the header file (first row) is required and will be ignored during the import process.
Before you run a large transaction import file, it is HIGHLY suggested that you test a FEW lines of transactions first. In case there is an issue, it is easier to identify the problem if there are less new transactions to sift through, as well as delete any faulty transactions that may have been added.