Every transaction matching process starts with transactions. No matter how a company sets up its files, a transaction file can have many columns. For example, it might include columns such as count, type, date, transaction ID, vendor, customer, and amount.
To add data to Matching, you need a tenant with Matching, activate the Matching module, and add a new global variable.
Contact the Anaplan Support team to get your tenant enabled.
Add a transaction ID column
The file needs enough information to create matches with different levels of confidence. At the very least, it should have a date and an amount. You can add more fields if you want, and a transaction ID is optional. A transaction ID is a unique code that helps you find and manage duplicates. If you know your transaction ID is unique, you can use it as a key for identification. If you don't have a unique transaction ID, you can create one by combining other columns, like the account number and date, or the type, vendor, and amount.
Data in the transaction file
Sometimes, you might get a file with only a date, check number, invoice number, amount, or account number. In these cases, you might need more information to match transactions effectively. It's a good idea to hold design meetings to ensure your transaction files contain all the necessary information.
When loading data, duplicates can occur, especially if the data is loaded over multiple days. For example, a company might load data every day for a 3-day period to account for delays in their ERP system. To handle duplicates, you need a unique identifier.
Modify the transaction file
Anaplan doesn't have built-in tools to modify the file, such as combining fields to create a unique identifier. Matching works directly with SQL tables. You may need to use the Anaplan Data Orchestrator, a 3rd party Extract, Transform and Load (ETL) tool, or manually manipulate your data file to create a unique ID. Additionally, Matching doesn't use import definitions or mappings associated with model management.
When you send the file, whether via the Anaplan Data Orchestrator or other upload methods, you need to know what's in each field and the exact field names. If your file has headers, make sure they match exactly. No spaces are allowed in header names, but you can use underscores. Also, know the exact order of the columns in the file to load the data correctly.
Select here to view a video about creating transaction files.
