Solomon Cloud Solutions

  • Services
  • Software Solutions
    • Beyond Software
    • Dynamics SL >
      • Account Central
      • All-In-One Project Invoice
      • Audit Utility
      • Mobile Time and Expense
      • Notifications
      • Project Invoice Posting Selection
      • Salesforce Integration
      • Transaction Import Automation
      • Two Factor Authentication
      • Web Apps Reports
      • Web Apps ROI Scheduler
    • Strategic Partners
  • Partner Portal
  • News & Events
  • About Us
    • Board of Directors
    • Careers
    • Community
    • Our History
    • Mission & Values
    • Testimonials
  • Contact Us
  • Services
  • Software Solutions
    • Beyond Software
    • Dynamics SL >
      • Account Central
      • All-In-One Project Invoice
      • Audit Utility
      • Mobile Time and Expense
      • Notifications
      • Project Invoice Posting Selection
      • Salesforce Integration
      • Transaction Import Automation
      • Two Factor Authentication
      • Web Apps Reports
      • Web Apps ROI Scheduler
    • Strategic Partners
  • Partner Portal
  • News & Events
  • About Us
    • Board of Directors
    • Careers
    • Community
    • Our History
    • Mission & Values
    • Testimonials
  • Contact Us

Solomon News & Events

REMINDER: Update February Month End Date in Dynamics SL Back to 28 Days!

2/5/2021

0 Comments

 

Calendar Year 2020 Was a Leap Year - Remember to Update the February 2021 Period in GL Setup Back to 28 Days

Because the calendar year 2020 was a leap year, you'll need to verify the February 2021 period is updated to reflect 2/28 (not 2/29) as the last day of the month.

How to update the February period in GL Setup:
If you have a Fiscal Year-End (June 30th, September 30th, etc.), you are likely already in F/Y 2021. If you have a Calendar Year-End December 31st, you will soon be closing F/Y 2020 (if you haven't already) and rolling into F/Y 2021.

For Calendar-Year databases, please do this AFTER you close F/Y 2020.
  1. Navigate to the Fiscal Info tab in the GL Setup screen in each of your Dynamics SL/Solomon databases
  2. Confirm or update the month-end date for February to reflect 2/28

Picture

For any questions about this post or anything Dynamics SL & Solomon Software related, get in touch with us!
Contact Us
0 Comments

How to Handle the 2020 Leap Year in Dynamics SL

1/8/2020

0 Comments

 
Picture

Calendar Year 2020 is a Leap Year - Remember to update the February Period in GL Setup

Because the calendar year 2020 is a leap year, you'll need to verify the February period is updated to reflect 2/29 as the last day of the month.

How to update the February period in GL Setup:
If you have a Fiscal Year-End (June 30th, September 30th, etc.), you are likely already in F/Y 2020. If you have a Calendar Year-End December 31st, you will soon be closing F/Y 2019 (if you haven't already) and rolling into F/Y 2020.

For Calendar-Year databases, please do this AFTER you close F/Y 2019.

  1. Navigate to the Fiscal Info tab in the GL Setup screen in each of your Dynamics SL/Solomon databases
  2. Confirm or update the month-end date for February to reflect 2/29
Picture
For any questions about this post or anything Dynamics SL & Solomon Software related, get in touch with us! 
Contact Us
0 Comments

Are Database Backups Important in the Cloud Era? (YES)

2/4/2019

0 Comments

 
Picture
In an era where Digital Transformation and Cloud Technology drive how businesses make decisions, are database backups still necessary?

Choosing to use software that sits ‘in the cloud’ or apps that download and connect you to your data with minimal learning time, might leave you thinking it removes any responsibility you have for making sure your data is being backed up.

​But is it this easy? Is it safe to assume that wherever that ‘cloud’ is, your data is being managed with the same precision as you would do yourself if it was on hardware in your building?

How we got to this point:

Thirty years ago the stand-alone computer that contained all of a company’s data was locked in a closet nightly. Literally a closet…usually located along the least used hallway in the building.

That closet was treated much like a bank vault. Only certain individuals were granted access through that door. Employees caught walking down that hallway were met with 20 questions before they could proceed on, in order to make sure they were allowed to be there. Backups were made nightly/weekly/monthly and stored off site. The IT department was responsible for all of these activities.
Picture
Then, organizations changed to placing their corporate data on a server accessible by everyone in the company. Security policies were put in place assigning each employee to a role. The role defined what access, or permissions, the individual was granted to in the database. IT departments managed the security policies and were responsible for maintaining employee access rights. Servers were set up with mirroring capabilities and virtual images were created to store backups. If a server went down, the backup servers could be configured for direct access. The IT department was responsible for managing these practices. 

Now, companies trust a third-party Cloud Solutions Provider (CSP) to maintain the hardware, software, operating system, databases and access to each. Companies have downsized, and in some cases eliminated altogether, their IT department. They depend on the CSP to provide all IT related services. The CSP is now responsible for maintaining security policies. The company’s ability to manage disasters rests in the agreements they have with the CSP.

Do you know if, and how often, your database is being backed up?

Cloud providers usually include this information in their Disaster Recovery Plan, which is part of the service you’re paying for (it's important to read all the provisions of a Cloud Solutions Provider).

​Make sure to ask your CSP to demonstrate proof that the Disaster Recovery Plan is more than just backing up the database regularly. Whatever backup method is being used, the provider should be able to prove they can recover/restore the backups in a reasonable timeframe.
Having backups that cannot be restored or recovered is of no value. Downtime is one thing. Losing years of history and your current activity is something completely different.
​Imagine the following scenario:
  • You get a call from one of your top customers asking what their outstanding balance is so they can make payment.
  • When attempting to access the data, you are unable to connect to the database.
  • You tell the customer you will gather the details and get right back with them. After waiting five minutes, you still get the same result; unable to connect.
  • Then you receive an email notification that your service is down temporarily. Hours later you are still waiting for news that the data is accessible again.
  • By the end of the day, you call your provider, only to be told there was a hardware failure and they are working to restore your database. "Expect a 24-48 hour turnaround."
  • Days go by and you hear nothing; you have nothing to tell your customer, so no payment is made.

Similarly, when customers can't pay, it strains cash flow and makes it harder for you to pay your bills. This is not a situation you want to find yourself in.

So the answer is YES. Database backups are still relevant and important!

​Regardless of who you have tasked with maintaining your data, at the end of the day it is 
YOUR data.  Making sure you make one extra inexpensive backup every once in a while can prove to be worth its weight in gold.
0 Comments

Dynamics SL 2018 Year-End Reporting Tips & Hints

1/9/2019

0 Comments

 
Picture
Are you experiencing year-end reporting issues? Our Dynamics SL support team has put together a summary of a few common issues & questions that tend to resurface this time of year pertaining to tax year 2018 government tax filing and 2018 payroll tax withholding.

Access December Tax Table Updates

The tax table updates can be accessed here:
https://mbs.microsoft.com/customersource/northamerica/SL/downloads/tax-regulatory-updates/MDSLDec2018PayrollTaxUpdates

The updates contain the following revisions:
  • Federal – Effective January 1, 2019
  • California - Effective January 1, 2019
  • Georgia – Effective January 1, 2019
  • Iowa – Effective January 1, 2019
  • Kentucky – Effective January 1, 2019
  • Maine – Effective January 1, 2019
  • Missouri – Effective January 1, 2019
  • New York – Effective January 1, 2019
  • North Carolina – Effective January 1, 2019
  • Ohio – Effective January 1, 2019
  • Oregon – Effective January 1, 2019
  • South Carolina – Effective January 1, 2019​

When will the January tax table updates be released?

​Microsoft is expected to release them in mid-to-late January and this update should contain all the recent federal withholding changes.

Accounts Payable

​If you are using the Accounts Payable module, the main takeaway is:
  • If you need to run the 1099 history rebuild, it won’t work in 2015 unless you install the year-end updates. The 1099 history rebuild was broken in SL 2015.

​The year-end updates should fix this for 2015 CU1, even though it doesn’t appear to be documented anywhere.

Access Year-End Updates

The Dynamics SL 2018 year-end updates can be accessed here:
https://mbs.microsoft.com/customersource/northamerica/SL/downloads/tax-regulatory-updates/msdl2018yearendupdates

How can we help?

For more information or to request assistance on these issues, contact Ruth Ann Ellerbrock at rellerbr@solomoncloudsolutions.com or (419) 581-2833. 
0 Comments

Dynamics SL Tip: Purge last year's 1099 Year (2017) before trying to print checks in 2019

1/2/2019

1 Comment

 
Picture
Are you a Dynamics SL customer? If you are, chances are that you’ll need to print checks in SL in 2019.
​
Before attempting to print checks in 2019, remember to purge the 2017 year so that 2018 will become “current” and 2019 will be the “next” 1099 Year.

How to purge oldest year in Dynamics SL

From within the Accounts Payable (AP) module in SL, open the 1099 Calendar Year Control screen. If the “current” year value is 2017, then it needs to be purged.

As the screen notes, ‘the purge option should only be used after final printing of the 1099 forms for the oldest year displayed on this screen has been completed…it is recommended that backup copies of your database be made immediately prior to this process.’
Picture
​Once you are ready to purge, click ‘Begin Processing’.

Have questions?

Get in touch with Solomon Cloud Solutions today for all your Dynamics SL needs.
1 Comment

How Often Should I Bill My Customer?

4/23/2018

0 Comments

 
Picture

Read More
0 Comments

Visit Us at SL User Group 2018!

4/17/2018

0 Comments

 
Picture

Read More
0 Comments

Winter Cleaning for Your ERP System

1/19/2018

3 Comments

 
Picture

Read More
3 Comments

Dynamics SL 2017 Year-End Reporting Tips & Hints

1/10/2018

0 Comments

 
Updated 2/2/18 to include January 2018 Payroll Tax Table updates*

Year-end reporting issues in Dynamics SL tend to resurface every January. We've put together a summary of a few common issues/questions our support team receives, pertaining to tax year 2017 government tax filing and 2018 payroll tax withholding.

Read More
0 Comments

Congratulations to Our Own Suzanne Farquharson

1/12/2017

2 Comments

 

Please join us in congratulating Suzanne on her upcoming retirement.

Picture

Read More
2 Comments
<<Previous

    Categories

    All
    Dynamics SL
    Management Reporter
    SLUG
    SQL
    Technical
    Visual Studio
    Web Apps
    Year End

    RSS Feed

      Subscribe for more updates

    Subscribe
HOME     |      ABOUT     |    TESTIMONIALS     |      SERVICES     |     SOFTWARE     |     PARTNER PORTAL     |     NEWS & EVENTS      |      CONTACT US
©​ 2023 Solomon Cloud Solutions 

SOLOMON CLOUD SOLUTIONS and SOLOMON SOFTWARE  are trademarks or registered trademarks of Plumbline Solutions, Inc. in the U.S. and other countries.