Update to SWIVEL Migrations

Please see below update regarding the SWIVEL migration:

• All former Magic-Wrighter credit unions have been contacted, but not all have actually completed signing contracts with SWIVEL
• The deadline for shutting down the existing Magic-Wrighter connection to the Fed was originally July 1, but was extended to July 9
• Before July 9, any CU who chooses to stay with SWIVEL for the following products MUST be migrated to a temporary solution that uses the existing M-W process but connects to the SWIVEL system in Texas
  • A2A in CBX and online banking
  • A2AFT (recurring A2As)
  • LoanPay Xpress
  • Accounts Payable payments via ACH in CBX
  • MOP new account funding
• Migrations began last week but are not done yet
  • Migration includes ALL products at the same time
  • A CU's decision to move to SWIVEL doesn't always mean the migration has already taken place
• Last week SWIVEL sent notices to CUs who hadn’t yet been moved or who hadn’t finished their contract, notifying them that they were still being run on the old M-W lines until the 9^th, at which time if they hadn’t been migrated, they would be discontinued 
  • This message was meant to communicate that services would not be discontinued until July 9, providing additional time beyond the originally planned July 1 date
• SWIVEL does things differently from Magic-Wrighter, especially when it comes to ACH
  • This “façade” takes what we have sent all along to M-W (plus some additional data they recently required us to add to the file) the same way we’ve always done
  • Then SWIVEL takes and processes the transactions according to their rules for ACH
  • With M-W, the CU was the ODFI (originator), but with SWIVEL, SWIVEL is – so their rules are different
  • That means the resulting ACH that goes out is different, and might look different when it arrives in the CU’s ACH file (or the other FI’s ACH file)
  • We can check to make sure we’re writing the data the same on the file we send to them, but after that, it’s up to SWIVEL what happens to it
• The migration process is all on SWIVEL’s side, and requires a lot of configuration work
  • SWIVEL and CU*SOUTH are monitoring carefully and if we see a high level of rejections SWIVEL is immediately reviewing and adjusting configs that may have been done wrong or missing
• As with M-W, daily limits are in place both in our software (stops the member from ever submitting the item in the first place) AND on the SWIVEL side (stops it after it’s been submitted)
  • Some CU's are adjusting their limits with SWIVEL, but not realizing that this might be lower than the limits in CBX
  • This will cause more items to be rejected which previously might have worked, which will confuse staff and members – please check your limits in Tool #569 and also check with SWIVEL if those limits to be adjusted
• After all of this is behind us, we still have our next task: rewriting the entire integration with SWIVEL for every product, using their APIs instead of the file / façade we’re migrating to now
  • Deadline for that is August 1, stay tuned for news as we get through July!

Please reach out to the support team at [e-mail] with any questions.