If you work in accounting or administration in Panama, you most likely use Sage 50 (formerly Peachtree). It is by far the most widely used accounting system in the country’s small and medium businesses. It is also the software that brings us the most configuration problems at Solutech: crooked installations, multi-user setups that fail, emailing reports that does not work, backups that were never taken and then the file is lost.

This guide covers what we learn every week working with Panamanian accountants and administrators.

What Sage 50 is and why doing it right matters

Sage 50 (Peachtree) is an accounting system from Sage covering general ledger, accounts receivable, accounts payable, inventory, payroll and financial reports. It is relatively affordable, robust, and sufficient for small and medium businesses.

But Sage does not forgive improvised installations. A bad initial setup will give you headaches for years: corrupted files, reports that will not print, users who cannot connect, data that gets lost.

Before installing: the real requirements

What the official documentation says is the bare minimum. What we recommend in production:

  • Windows 10 Pro or Windows 11 Pro (the Home editions have problems with network permissions in multi-user setups).
  • At least 8 GB of RAM, ideally 16 GB if you will have several users or many years of data.
  • An SSD is mandatory. Sage on an HDD becomes unbearably slow with 3+ years of data. This is one of the most common complaints and it is solved with an SSD upgrade.
  • A properly configured antivirus. We explain why below.
  • A Windows account with administrator rights during installation.
  • For multi-user setups: a wired local network, or stable 5 GHz Wi-Fi. Slow 2.4 GHz Wi-Fi causes Sage to drop users.

Common installation mistakes

Mistake 1: installing on OneDrive or a synced Desktop

This is the most serious and most common mistake. Sage stores its database as files. If those files are in a folder synced with OneDrive, Dropbox or Google Drive, the sync corrupts the database. The result: broken files, “index out of range” errors, and sometimes total loss.

The fix: install Sage and keep the companies in a folder that is NOT synced. A good practice is to create C:\Sage\Empresas\ and keep everything there.

Mistake 2: installing in a folder with restricted permissions

If you install Sage in C:\Program Files\ and keep the companies in C:\Users\YourUser\Documents\, you will run into permission problems when another user tries to open it. The correct approach:

  • Program: C:\Program Files\Sage\ (default, leave it alone).
  • Companies: a folder with “All users → full control” permissions. C:\Sage\Empresas\ works well.

Mistake 3: not excluding Sage from the antivirus

Your antivirus can block or slow down Sage’s operations. This shows up especially during month-end closes or when generating large reports. The fix is to add exclusions in the antivirus:

  • The program folder: C:\Program Files\Sage\
  • The companies folder: C:\Sage\Empresas\
  • The processes: Sage50.exe, peachw.exe, peachtree.exe (depending on the version)

If you use Kaspersky or McAfee, we configure this during the installation session. If you do it yourself, look for “Exceptions” or “Exclusions” in your antivirus settings.

Multi-user installation: what almost nobody gets right

Sage’s multi-user mode works with a server (the computer holding the files) and clients (the ones connecting to the server). Here is what matters:

On the server

  1. Install Sage 50.
  2. Create the companies folder in an accessible path: C:\Sage\Empresas\.
  3. Share that folder on the network with read/write permissions for the users who will connect.
  4. Assign a static IP address to this computer (important so the clients do not lose it).

On each client

  1. Install Sage 50 (with exactly the same version as the server — different versions break the connection).
  2. When opening Sage for the first time, indicate that the company is on the network and browse to the shared folder.
  3. Check that you can open the company correctly.

Network configuration

  • Wired whenever possible. Multi-user problems in Sage are almost always network problems, not software problems.
  • 5 GHz Wi-Fi if wireless is necessary. Avoid 2.4 GHz for this.
  • No VPN between users and server, unless you know exactly what you are doing. Sage needs low latency.

Setting up emailed reports

This is the question we are asked most often about Sage in Panama: “how do I configure Sage to email a statement of account directly to the client?”

Sage has this feature, but the configuration is very specific and usually needs adjusting depending on the mail provider. Here is how it goes for the most common ones.

For Microsoft 365 / Outlook

  1. Sage → Maintain → Company → Current user information.
  2. Under “Email”, configure:
    • SMTP server: smtp.office365.com
    • Port: 587
    • Use SSL/TLS: yes (STARTTLS)
    • User: your full email address (you@company.com)
    • Password: this is the trap — it is not your normal password.

The password problem with Microsoft 365

Microsoft no longer allows applications like Sage to use your normal password directly. You need an app password. The steps:

  1. Enable two-step verification on your Microsoft account (non-negotiable).
  2. Go to https://account.microsoft.com/security → Advanced security options.
  3. Create an app password.
  4. Paste that password (16 random characters) into Sage instead of your normal one.

For Gmail / Google Workspace

Same principle:

  • SMTP server: smtp.gmail.com
  • Port: 587
  • SSL/TLS: yes
  • User: your Gmail address
  • Password: an app password generated at https://myaccount.google.com/apppasswords (requires 2FA to be active).

For email on your own domain (cPanel and similar)

Ask your provider for:

  • The outgoing SMTP server
  • The port (usually 587 with TLS or 465 with SSL)
  • Whether SMTP authentication is required

Then configure it in Sage.

Backups: the difference between sleeping soundly and losing years of work

Sage has a built-in backup feature (File → Back up company) but it does not run by itself. Every month we see someone who lost their accounts because “they thought automatic backup was running”.

Real recommendations:

  1. A manual backup at the end of each day. It takes 2 minutes.
  2. Keep the backup on an external drive or in the cloud, not on the same computer where Sage runs. If the PC dies, you lost everything anyway.
  3. Test restoring the backup from time to time. A backup you cannot restore is not a backup, it is a decorative file.
  4. For serious businesses, use automatic backup with dedicated software (Veeam, Acronis, or a OneDrive/Dropbox setup that excludes only the live folder).

If you need automatic backups set up for your Sage, we configure it in one session and it keeps working from then on.

When to call a technician

The initial Sage installation is worth doing with a technician. Not because it is complex — someone patient can do it alone by following manuals. But because early mistakes cost dearly for years.

If your Sage:

  • Works but is very slow → it probably needs an SSD or a clean-up of old data.
  • Throws random errors when closing a company → usually an antivirus or sync problem.
  • Will not connect between users → a network or permissions problem.
  • Will not send email → SMTP configuration or the app password.

Any of these we resolve through remote support in under an hour. If you manage Sage 50 at a Panamanian company and want it all running smoothly without being the one fighting the configuration, message us on WhatsApp.

Next steps

  • If you are about to install Sage for the first time, read this before you start.
  • If you already have Sage running but it gives you trouble, book a diagnosis.
  • If the machine running Sage has an HDD, consider moving to an SSD. The performance change is dramatic.