Sage 100 Training: How to Train Your Team on Sage 100 ERP

If you've ever had to handle Sage 100 training for a new hire, you know how painful it gets.

This isn't modern cloud software with a clean interface and helpful tooltips. Sage 100 ERP is a legacy system with decades of history buried in its menus, modules, and workflows. It's powerful -- mid-market companies run their entire operations on it -- but figuring out how to train your team on Sage 100 is a challenge that goes well beyond "here's your login."

I'm Yuval, founder of Glitter AI. Through building a tool that helps teams create training guides from screen recordings, I've talked to dozens of Sage 100 teams who all describe the same problem. The tribal knowledge is massive. And the traditional approaches? They just don't cut it.

Sage 100 Training Has a Tribal Knowledge Problem (And It's Worse Than You Think)

Every ERP system accumulates customization over time. Sage 100 software takes this to another level entirely.

Your Sage 100 instance isn't the same as anyone else's. Over the years, someone configured custom modules. Someone set up specific general ledger account structures. Someone built custom Crystal Reports. Someone created workarounds for that one thing the software doesn't handle natively. And someone wrote notes on a sticky note about the exact sequence of steps for period-end closing that avoids that weird rounding error.

All of that knowledge lives in people's heads.

This is tribal knowledge at its most dangerous. When your longtime AP clerk retires, she takes years of institutional knowledge about your specific Sage 100 setup with her. When your controller moves to another company, the custom report templates he built might as well not exist -- nobody else knows how to modify them.

The hidden cost of undocumented processes is brutal with ERP systems. We're not talking about things just taking a little longer. We're talking about invoices going out wrong, inventory counts being off, purchase orders stuck in limbo, and period-end close taking three times longer because the new person is basically reverse-engineering the system from scratch.

I've talked to companies where a single departure set their accounting team back six months. Six months of confusion, workarounds, and errors -- all because the knowledge of how to run their Sage 100 instance walked out the door.

Why Traditional Documentation Fails for Sage 100 Training

Legacy ERP software is uniquely hostile to traditional documentation methods. Here's where each approach falls apart.

Written SOPs Don't Capture the Interface

Sage 100's interface has layers. Desktop modules that open sub-windows. Tab structures within those windows. Right-click menus with options that change based on context. Toolbar buttons that look similar but do very different things. Trying to capture all of that in a text document is like trying to describe a maze with words alone. Technically possible. Practically useless.

Someone writes "Navigate to Accounts Payable > Invoice Data Entry" and the new hire spends ten minutes staring at the screen because the module launcher looks different on their machine.

Screen Recordings Alone Aren't Enough

A raw screen recording of someone doing a 45-minute bank reconciliation in Sage 100 is overwhelming. Nobody's going to scrub through a long video to find the one step they're stuck on. They need the video for context, sure, but they also need screenshots to glance at and written steps to follow along with.

Vendor Documentation Is Generic

Sage provides documentation for Sage 100 ERP features. But your company doesn't use generic Sage 100 software. You use a heavily customized instance with specific chart of accounts structures, custom report layouts, particular vendor setups, and workflows that have evolved over years. Generic docs don't know about any of that.

What you actually need is documentation that captures your Sage 100 -- the way your team uses it, with all the quirks and customizations included. And it needs to combine visual and written formats because this software is too complex for any single format to cover.

How Glitter Works for Sage 100 Training

Here's the approach I've seen work for teams running Sage 100.

Instead of writing documentation or scheduling week-long shadowing sessions, you just do the task. Open Sage 100, start a Glitter recording, and walk through the process while narrating what you're doing and why. Mention the things that trip people up. Point out which fields matter and which ones you can skip. Explain why you chose that specific GL account code.

When you stop recording, Glitter generates a complete training guide with:

• Video of the full walkthrough so people can see the flow
• Annotated screenshots of each key step and screen
• Written instructions pulled from what you said and did
• Voiceover preserving your verbal explanations and warnings

One recording. Four formats. Every learning style covered.

This matters more for Sage 100 than for simpler software because the interface is dense. People need screenshots to confirm they're on the right screen. They need video to see the rhythm of a workflow. They need written steps for reference while doing it themselves. And they need voiceover for the context that text alone can't convey.

I've written more about this multi-format approach in my post on visual work instructions.

8 Sage 100 ERP Workflows You Should Document First

Not every workflow needs a guide on day one. Start with the ones that generate the most questions and carry the highest risk of error. Here's what I'd prioritize.

1. General Ledger Journal Entries

This is foundational. Walk through creating a standard journal entry -- selecting the journal type, entering account numbers, adding debits and credits, writing descriptions, and posting. Cover your company's conventions: which GL accounts map to which expense categories, how you handle intercompany entries, and what the review process looks like before posting.

Pro tip: Record yourself fixing a common mistake, like a journal entry that's out of balance. Showing error correction is way more valuable than a perfect walkthrough.

2. Accounts Payable Processing

AP in Sage 100 is multi-step: entering vendor invoices, matching to purchase orders, coding to the right GL accounts, routing for approval, selecting invoices for payment, and printing or sending checks. Walk through the entire lifecycle from invoice receipt to payment.

If your team uses three-way matching (purchase order, receipt, invoice), make sure to show that flow. It's one of the most complex AP tasks in Sage 100 and the one most likely to go sideways without proper training.

For more on documenting AP workflows, see my accounting SOP guide.

3. Inventory Management

Sage 100's inventory module handles item maintenance, quantity adjustments, physical counts, lot and serial tracking, and warehouse transfers. If your company runs on inventory, this module is critical and the cost of errors is high.

Record the workflows your warehouse and inventory teams use daily: receiving inventory, adjusting quantities, running inventory reports, and handling discrepancies. Show how Sage 100's barcode validation works if you're using it -- it's a newer feature that a lot of teams underutilize.

4. Purchase Order Processing

Walk through creating a purchase order from scratch: selecting the vendor, adding line items, setting quantities and prices, and sending the PO. Then show the receiving process -- how to receive against a PO, handle partial receipts, and deal with over-shipments or back-orders.

If you use the Request for Quote feature, document that workflow separately. It involves sending POs to multiple vendors and comparing responses, and the steps aren't exactly obvious to someone new.

5. Bank Reconciliation

Bank reconciliation in Sage 100 involves matching cleared transactions, handling outstanding checks, dealing with bank fees and adjustments, and balancing the statement. Record yourself working through an actual reconciliation -- the messier the better. Clean examples don't teach anyone how to handle the real-world transactions that refuse to match neatly.

6. Period-End Closing

This is the workflow most likely to live entirely in one person's head. Period-end close in Sage 100 involves a specific sequence: verify all transactions are posted, run trial balance, make adjusting entries, run final reports, close the period in each module, and advance to the next period.

The order matters. Closing modules in the wrong sequence can cause real problems. Record the exact sequence your team follows, including any manual verification steps between modules.

7. Custom Report Generation

If your team has built custom Crystal Reports or uses Sage 100's built-in report writer, document how to run, modify, and interpret those reports. Custom reports are probably the highest-value pieces of tribal knowledge in any Sage 100 installation because they represent years of accumulated business intelligence. When the person who built them leaves, the reports become black boxes.

8. Bill of Materials

For manufacturing companies and Sage 100 contractor users, the Bill of Materials module is essential. Walk through creating and maintaining BOMs, showing how parent items relate to components, how quantity calculations work, and how BOMs connect to work orders and inventory. Even small errors in BOM setup cascade into production and costing problems.

Structuring Your Sage 100 Training Program

Once you have the core workflows recorded, you need a Sage 100 training plan for how people actually work through them. Sage 100 ERP is too complex to learn all at once, so break it into phases.

Phase 1: Navigation and Basics (Week 1)

Start with the fundamentals. How to launch modules from the desktop. How the menu structure works. How to use the toolbar. How to search for records. How to use date fields and lookup windows. Sage 100's interface conventions are different from modern software, and people need to feel comfortable with the basics before tackling real tasks.

Phase 2: Core Financial Workflows (Weeks 2-3)

Move into GL journal entries, AP invoice processing, and AR invoicing. These are the daily tasks that keep the books running. Have the new person work through your Glitter guides, then practice with supervision on real transactions.

Phase 3: Module-Specific Training (Weeks 3-4)

Depending on the person's role, go deeper into their specific modules. Inventory management for warehouse staff. Purchase orders for procurement. Custom reports for analysts. Not everyone needs to know every module -- focus on what they'll actually touch day to day.

Phase 4: Period-End and Advanced Tasks (Month 2)

Have them shadow a period-end close first while following along with the recorded guide. Then have them lead the next close with someone available for questions. By the third close, they should be able to handle it independently.

This phased approach is really just training documentation applied to a specific system. The guides do the heavy lifting. Your experienced people provide context and handle questions. Nobody burns a full month on live training.

Tips for Recording Better Sage 100 Training Guides

Slow Down at the Dense Screens

Sage 100 has screens packed with fields, tabs, and options. When you hit one of these screens, pause your mouse movement and verbally explain the layout before you start clicking. "Okay, you'll see three tabs at the top -- we only use the first two. And the grid in the middle is where the line items go."

Explain the Why, Not Just the What

"Click the Distributions button" is less useful than "Click the Distributions button to verify the GL accounts are correct -- sometimes Sage defaults to the wrong account when you change the vendor, and if you don't catch it here, you'll find it during reconciliation." The reasoning is what turns a step into actual knowledge.

Record Edge Cases Separately

Don't try to cover every scenario in one recording. Do a standard invoice entry as one guide. Do a credit memo as another. Do a voided check as another. Short, focused guides are easier to find and easier to update when things change.

I've talked about this in train employees faster with documentation -- modular guides beat thick manuals every time.

Name Your Guides Clearly

"Sage 100 - AP Invoice Entry (Standard)" is a good title. "Training Video 7" is not. When someone's stuck in the middle of processing payables, they need to find the right guide in seconds.

Building a Complete Sage 100 Knowledge Base

As someone who built Glitter, I've seen our best teams document 5+ different operational workflows. The ones who stick aren't creating one guide -- they're building an entire knowledge base.

Your Sage 100 training library is the foundation, but it grows from there. How you handle year-end close. How you set up new vendors with specific tax configurations. How you process returns. How you run the custom reports your CFO needs every Monday morning.

Every one of these workflows is a recording away from being documented. And every one of them is currently at risk of disappearing when someone leaves.

The goal isn't perfect documentation. It's to capture the knowledge that exists in your team's heads before it's gone. Start with the workflow that causes the most questions, record it today, and build from there. Within a couple months, you'll have a training library that makes onboarding faster, reduces errors, and lets your experienced team members get back to their actual work instead of repeating the same explanations over and over.

Why Video Plus Screenshots Plus Written Steps Win

Let me be direct about this. For software as complex as Sage 100, no single training format is enough.

Video captures the flow and rhythm. People see how you navigate between modules, how fast you move through familiar steps, and where you slow down because something needs attention.

Screenshots capture the details. When someone is mid-task and needs to verify they're looking at the right field in a screen full of fields, they don't want to scrub through video. They want a quick visual check.

Written steps capture the logic. Why that GL account. What the approval threshold is. Which vendor terms to use. Text is searchable and scannable in ways video and screenshots aren't.

Voiceover captures the nuance. The warnings, the context, the "I know this looks weird but here's why we do it this way" explanations that make the difference between someone who can follow steps and someone who actually understands the process.

When all four come from a single recording, they stay in sync. The screenshot matches the video frame matches the written step matches the spoken explanation. That consistency is what makes training on a system as complex as Sage 100 actually work.

Getting Started Today

You don't need to document everything at once. Here's the practical first step.

1. Identify the workflow that generates the most questions. For most Sage 100 teams, it's AP invoice processing or period-end close.
2. Open Sage 100, start a Glitter recording, and do the task. Narrate as you go. Don't script it.
3. Review the generated guide. Make quick edits if needed.
4. Share it with your team. Next time someone asks, send the guide instead of walking over to their desk.
5. Record one more workflow next week. In two months, you'll have a complete Sage 100 training library.

The companies that handle Sage 100 transitions well aren't the ones with the fanciest documentation. They're the ones that have documentation at all. Start today. Your next new hire will thank you.

Frequently Asked Questions

How long does Sage 100 training take for a new hire?

Sage 100 training timelines vary a lot based on the person's role and how customized your instance is. For core financial workflows like AP, AR, and GL, expect 4-6 weeks before someone is comfortable working independently. More complex areas like inventory management, custom reporting, and period-end close tend to take 2-3 months. With documented training guides that combine video, screenshots, and written steps, you can cut these timelines by roughly 40% because new team members can learn at their own pace and revisit guides whenever they need a refresher.

What is Sage 100 and why is it harder to train on than other accounting software?

Sage 100 ERP is a desktop-based system with a legacy interface that's fundamentally different from modern cloud software. It uses module-based navigation, multi-window workflows, and dense data entry screens that aren't intuitive for people used to web applications. On top of that, every Sage 100 instance gets heavily customized over time with specific chart of accounts structures, custom reports, and configured modules. That means generic training materials don't really apply -- your team needs to learn your specific setup, not Sage 100 in general.

Can I use Sage's built-in help documentation for training?

Sage provides general documentation for Sage 100 features, but it won't cover your company's specific configuration. Your chart of accounts, vendor setups, custom Crystal Reports, approval workflows, and period-end procedures are all unique to your instance. Sage's documentation is helpful for understanding what a feature does in theory, but your team needs guides that show exactly how your company uses each module in practice.

What's the best way to document Sage 100 period-end close?

Record your period-end close as a series of focused guides rather than one long video. Break it into stages: verify all transactions are posted, run trial balance, make adjusting entries, close individual modules in the correct sequence, run final reports, and advance to the next period. The module closing sequence is critical in Sage 100 because closing modules in the wrong order can cause data issues. Each guide should show the exact steps in your instance with narration explaining the reasoning behind each one.

How do I train my team on Sage 100 inventory management?

Start with the basics of item maintenance -- how to look up items, understand quantity fields, and navigate the inventory module. Then move to daily tasks like receiving inventory, processing adjustments, and running inventory reports. If you use lot or serial tracking, create separate guides for those workflows. Record yourself handling common scenarios like physical count discrepancies, warehouse transfers, and quantity adjustments. Visual guides with screenshots are especially important for inventory because the screens are so data-dense.

How do I handle Sage 100 training for remote employees?

Screen-recorded training guides work really well for remote Sage 100 training because the software is visual and complex. Record each workflow with narration and let Glitter generate video, screenshots, and written steps automatically. Remote employees can work through guides at their own pace, pause and rewind as needed, and revisit them whenever they get stuck. This eliminates the need to schedule live screen-sharing sessions across time zones and keeps training consistent regardless of location.

How often should I update my Sage 100 training guides?

Update guides whenever your Sage 100 configuration changes -- new GL accounts, updated vendor terms, modified approval workflows, or changes to your period-end procedures. Also update when Sage releases version updates that change the interface or add new features (like the barcode validation and extended invoice numbers in recent versions). A general quarterly review is a good idea. With a tool like Glitter, re-recording a workflow takes just a few minutes, so regular updates stay practical.

What Sage 100 modules should I prioritize for Sage 100 training?

Prioritize based on daily usage and error risk. For most companies, start with General Ledger, Accounts Payable, and Accounts Receivable since those are used most frequently. Then add Inventory Management and Purchase Orders if your company handles physical goods. Bank Reconciliation and Period-End Close should be documented early because they're high-stakes processes that are often known by only one or two people. Custom Report Generation is also worth prioritizing because custom reports represent years of accumulated business intelligence.

How many training guides does a typical Sage 100 team need?

Most mid-market companies running Sage 100 need somewhere around 15-25 core guides to cover their essential workflows. This typically breaks down to 3-4 guides each for AP, AR, GL, and inventory, plus guides for bank reconciliation, period-end close, purchase orders, custom reports, and system navigation basics. Manufacturing companies using Bill of Materials and work order modules will need more. Start with 5-7 guides covering the most frequently used workflows and expand from there based on what your team actually asks about.

What's the biggest mistake teams make when training on Sage 100?

The biggest mistake is relying entirely on one experienced person to train everyone through live shadowing sessions. This doesn't scale, produces inconsistent training, and creates a single point of failure. When that person leaves, all their knowledge about your Sage 100 setup goes with them. The second biggest mistake is creating text-only documentation for a system that's inherently visual. Sage 100's dense screens and multi-step workflows need screenshots and video to be genuinely useful as training materials.