Mapping Transactions for Automated Reconciliation

BlueBean allows you to automatically map G/L accounts and Cost Objects to transactions. To do so click on the “Map” tab in the account automation menu of the Accounting area of the application.

Start by choosing whether you wish to work with G/L accounts or cost objects. 

G/L accounts can be mapped using two methods:

• Merchants to G/L accounts

• MCC to G/L accounts

The merchants to G/L accounts mapping supersedes the MCC to G/L accounts mapping.

Note that to map Merchants to G/L accounts mapping you already need to have transactions in the systems as we use the actual merchant account identifiers to map the account. This method is therefore used over time as you collect transactions.

The MCC to G/L accounts mapping uses the MCC codes of your card issuer’s network and can be performed prior to any transaction in the system.

To start MCC to G/L accounts mapping click on the method and choose to add a mapping either manually or automatically.

The automatic mapping in BlueBean is AI assisted. By clicking on Automate Mapping the system will pull your visible G/L accounts and will map them with the MCC code.

Once the job is done you are to review the mapping, accept it, update it or reject it completely. You can always manually add or update your mapping. 

Note that when reviewing users’ transactions and manually adding or updating G/L accounts for which no automation rule exists, BlueBean will propose you to automate it either by mapping the Merchant to the G/L account, the MCC to the G/L account or both. Doing so will update the mapping table and will automatically reconcile the transaction for the future.

Cost object mapping is done by mapping an employee to a cost object. This will automatically pre-fill the cost object from that table as default allocation.