Bank Feeds Mapping Enhancements (Coming Soon)

fispan has been working with sage for the past three years to influence some changes to their api infrastructure to improve bank feeds these long awaited changes from sage enable us to enrich the data we map into the erp, providing more detail and accuracy than ever before this will translate directly to a faster, easier, and more intuitive reconciliation process summary of key improvements our team, in consultation with sage experts, has revised our data mapping logic to take full advantage of the new capabilities while many smaller improvements are being made, the most impactful changes that clients will notice are more accurate transaction matching check number we are implementing more robust logic to identify and map the correct check transactions our system will now prioritize the transaction id, followed by the check number, and then the customer reference to ensure the most accurate data is used note while check number is a key identifier, the check number is not always displayed in the native intacct module making it unreliable for matching this is why the transaction id takes precedence over the check number and should be used for matching purposes the check number will still be visible in the description column payee information we will now more reliably capture payee/counterparty information improved data integrity we are implementing stricter data cleaning and formatting rules for example, check numbers will be standardized to a maximum of 12 characters to ensure compatibility with sage intacct this focus on data hygiene prevents errors and improves the success of automatic matching rules important considerations native platform limitations while these enhancements represent a major step forward, we are still bound by certain native limitations within the sage intacct platform that we cannot control we have optimized our service to the fullest extent possible within these constraints we expect these changes to go live early august please note that reconciliation rules may be impacted and will need to be updated to reflect these improvements steps to update (or create) reconciliation rules and rule sets step 1 permissions (admin role) ensure you have the necessary permissions typically, an administrator role will have these, but you can check navigate to company > admin > roles or users select the relevant role or user and go to permissions under cash management , confirm you have "list," "view," "add," "edit," and "delete" permissions for bank transactions bank transaction rules bank transaction rule sets save any changes step 2 create or edit a reconciliation rule navigate to cash management > setup > reconciliation rules > rules to create a new rule click the + add button to edit an existing rule click edit next to the rule you want to modify populate the rule details\ type choose "match rule" (to match bank transactions to existing intacct transactions) or "create rule" (to automatically create new intacct transactions, like for bank fees or interest) id and name enter a unique id and a descriptive name for the rule filter transactions by this is crucial for defining when the rule should apply you'll specify data source (e g , bank transaction) field (e g , description, amount, posting date, document number) operator (e g , equals, contains, begins with, greater than) value the specific text or value to filter by tip for matching rules, "amount" is typically a required field you might also add filters for "document number" or "description" to make the matching more precise click save note you cannot delete rules, but you can set them to "inactive" if you no longer want them to be used