ALL KLEER / INSIGHTS
Practical guidance for Sage 100 users, controllers, administrators, IT teams, and businesses that need their systems to keep working. Upgrades, reporting, data, payroll, integrations, troubleshooting, and the strange little things you only learn by doing this for decades.
BROWSE BY TOPIC
KNOWLEDGE BASE
74 articles
Sage 100 Purchase Order connects purchasing, receiving, inventory, vendors, and Accounts Payable so the business can follow what was ordered, what arrived, and what is still open.
Follow Sage 100 purchasing from PO to receipt to Accounts Payable and understand why ordered, received, and invoiced quantities or costs may legitimately differ.
Partial receipts and backorders preserve remaining purchasing commitments. When a PO stays open unexpectedly, identify the remaining quantity and status before closing it.
Purchase Order receipts can affect both inventory quantity and valuation. Separate quantity from cost, confirm the warehouse and costing method, and follow the receipt history.
Drop ships and special orders let purchasing respond to specific customer demand without forcing every purchase through normal stocked-inventory handling.
RFQ means Request for Quote. Sage 100 2025 added RFQ functionality so purchasing teams can request vendor pricing through Paperless Office and retain quote history inside Sage.
PO cleanup works best by classifying each open condition, proving the correction method with trusted accounting users, and then training internal staff to handle repetitive cleanup safely.
Barcode forms and handheld scanning can simplify Purchase Order receiving when the form, identifier, warehouse workflow, and Sage transaction all agree about what is being received.
Sage 100 2025 added optional Purchase Order audit tracking so changes, additions, and deletions can be retained and reviewed through the Audit Viewer and PO Audit Report.
Sage 100 Sales Order connects the customer promise to pricing, inventory, shipping, tax, invoicing, and Accounts Receivable across standard, master, repeating, and quote workflows.
Price levels, customer-specific pricing, discounts, quantity rules, and durable pricing programs let Sage remember the customer relationship instead of relying on manual order-entry memory.
Master orders handle long-running quantity commitments, repeating orders reduce repetitive entry, and quotes let pricing conversations exist before standard orders commit inventory.
Custom Sage 100 Sales Order forms can support acknowledgements, pick sheets, packing lists, invoices, barcodes, Crystal layouts, and Paperless Office delivery for different users in the same workflow.
Shipping integrations connect Sage 100 order data with warehouse and carrier workflows so rates, freight, tracking, packages, labels, and shipment information do not have to be re-entered manually.
When a Sage 100 Sales Order does not invoice as expected, start with the specific order, status, fulfillment, pricing, tax, freight, forms, and connected workflows before recreating the transaction.
Sales tax inside Sage 100 Sales Order depends on transaction context such as customer, ship-to, item, tax setup, jurisdiction, and any integrated tax-calculation workflow.
Sage 100 RMA gives customer returns a controlled path for reasons, receipts, replacements, credits, and other outcomes without turning the return into an unstructured exception.
Sage 100 2025 added optional Sales Order audit tracking so additions, changes, and deletions can be retained and reviewed when troubleshooting how an order reached its current state.
When Sage quantity-on-hand and the warehouse disagree, start with the exact item and warehouse, then follow the transactions and count timing before posting an adjustment.
Negative inventory means Sage shows more quantity leaving a warehouse than currently available there. The cause varies, so keep the diagnosis specific to the item, warehouse, timing, and transactions.
Purchase Order represents incoming supply, Sales Order represents demand, and Inventory provides the shared item-and-warehouse context across Sage 100's distribution workflow.
Sage 100 supports standard, average, FIFO, LIFO, lot, and serial costing. Quantity and valuation are separate questions, and inventory-value problems reach financial reporting quickly.
Warehouse workflows are where Sage 100 meets physical inventory. Barcode, receiving, shipping, lot/serial, and scanner processes have to capture what actually happens on the floor.
Physical and cycle counts are opportunities to improve inventory accuracy. Review timing and variances before adjustments so the count explains the process instead of hiding it.
When Sage 100 inventory valuation looks wrong, confirm the costing method, separate quantity from unit cost, isolate the warehouse, and follow the transactions that built the value.
Inventory cleanup should preserve history while making active items, warehouses, aliases, product lines, costing, and future item-entry rules easier to understand and maintain.
Barcode forms and handheld scanning can make Sage 100 physical counts faster and more accurate without requiring an enormous warehouse project. The scanner, identifier, form, and Sage workflow must agree.
If GL detail and the trial balance are meant to describe the same activity, they should reconcile. We start by validating the comparison and then isolate the account, period, source, or posting path behind the difference.
When two Sage 100 financial reports do not tie, the difference is evidence. Define what should match, narrow the scope, and follow the first place the stories diverge.
The chart of accounts is the language of the financial system. Good Sage 100 GL structure supports reporting, budgeting, analysis, and management understanding without unnecessary fragmentation.
A financial report begins with the way the accounting system captures activity. Clean reporting depends on account structure, transaction design, posting rules, and the data model underneath the report.
A Sage journal can post successfully and still represent the wrong accounting intent. Technical validity is not the same thing as financial meaning.
Follow Sage 100 AP activity from vendor invoice and distribution through posting into the General Ledger so the financial result can be explained instead of merely observed.
Follow Sage 100 AR activity from customer transactions through posting into the General Ledger and understand how timing, scope, and transaction flow affect reconciliation.
Bank Reconciliation is about explaining differences between the books and the bank until the two legitimately reconcile—not simply forcing the totals to match.
If users continue working in Excel after a Sage report runs, export behavior is part of the design. We aim for cleaner rows, simpler structures, and fewer obstacles between Sage and usable spreadsheets.
Subreports are powerful but can complicate maintenance, performance, parameters, and Excel export. We use them when they solve a real problem and prefer simpler architecture when it can do the job.
A useful Sage 100 financial report answers the decision behind the request, uses the right level of detail, reconciles, and fits the way the client needs to print, export, or distribute it.
Investigating a Sage 100 GL reconciliation difference is controlled narrowing: validate the comparison, isolate the first point of divergence, trace the source, and fix the cause.
When an old Sage report no longer answers the client's question, we may rewrite or recreate it. The goal is not to preserve the report—it is to preserve the business answer.
A business can modernize the infrastructure underneath Sage 100 without replacing the ERP. Hosted migrations change where Sage runs while preserving the workflows the business already knows.
Your IT team understands the infrastructure. We understand Sage. The best migrations and support relationships happen when those two specialties cooperate instead of pointing at each other.
Before moving Sage 100, identify what depends on the old server: reports, Paperless Office, ODBC, VI, integrations, Payroll, workstations, backups, printing, and historical systems.
Remote Sage 100 is more than a login screen. Server architecture affects users, printing, Paperless Office, reporting, integrations, ODBC, and the workflows that still need to work remotely.
The best Sage server migration is technical on the weekend and boring on Monday. Users log in, workflows work, reports run, integrations connect, Paperless Office sends, and the recovery plan stays unused.
Sage 100 Bill of Materials defines the product structure behind assembled and manufactured items, including standard, engineering, inactive, kit, and phantom bills.
Bills with options handle valid product variations. Engineering Change Control handles how the product itself evolves. Sage 100 gives each problem its own structure.
Not every manufacturer needs full work-in-process tracking. Sage 100 Production Entry offers a lighter one-step finished-goods and component-consumption workflow, while Production Management goes deeper.
Job Cost gives project activity a structure so labor, billing, reporting, and other project-related costs can be understood by job and cost code instead of disappearing into general accounting totals.
Payroll and Job Cost share the same labor story. Time Track can capture job and cost-code information, update Job Cost before payroll runs, and support certified payroll reporting.
A Job Cost report is only useful if it answers the management question behind it. Start with the decision, then decide which job, cost-code, labor, billing, and reporting details actually belong in the view.
A Job Cost and Payroll difference does not automatically mean one side is wrong. Timing, report scope, job and cost-code assignments, and whether Time Track updated Job Cost before payroll can all change the comparison.
Sage Intelligence is more than exporting Sage data to Excel. It provides reusable reporting models, financial report design, drill-down, automation, distribution, and multi-source consolidation.
Crystal Reports and Sage Intelligence both report on Sage 100 data, but they solve different problems: formatted reports and forms versus Excel-based financial and management analysis.
A Sage Intelligence workbook is only the visible end of the reporting chain. When reports stop working, we isolate whether the problem is the report, licensing, access, Excel, Sage connectivity, upgrades, or the surrounding environment.
Excel is not the problem. Rebuilding the same reporting workbook by hand every month is. Sage Intelligence can turn recurring Sage 100 financial reporting into a controlled, reusable process.
Paperless Office is more than a PDF button. It can archive reports and forms, preserve documents for later retrieval, electronically deliver business documents, and support workflows across AR, Sales Order, Purchase Order, Job Cost, Payroll, and more.
“Paperless Office stopped emailing” describes the symptom, not the cause. We follow the document from generation and archive through delivery to isolate where the process actually failed.
A Sage upgrade is not complete because the program opens. If the business relies on Paperless Office, document generation, archives, forms, users, delivery, and Payroll output belong in the upgrade test plan.
Production Management connects work tickets, work in process, labor, materials, scheduling, and costing so Sage 100 can follow what happens while a manufacturer turns inventory into a finished good.
A Sage 100 work ticket does not live alone. Production Management connects manufacturing activity with Inventory, Bill of Materials, Purchase Order, Accounts Payable, Payroll, scheduling, and costing.
A Sage 100 upgrade is more than installing a new version. A successful project starts with the current Sage version and server, then accounts for backups, testing, data conversion, customizations, reports, integrations, and workstation rollout.
Sage 100 has continued to evolve through practical improvements to audit tracking, purchasing, inventory, reporting, search, automation, security, and platform architecture. Here’s what has changed since the 2024 release and why those changes may matter to existing Sage 100 users.
Sage 100 2025.0 introduced more than 25 enhancements across purchasing, Accounts Payable, Sales Order, inventory, Production Management, and audit tracking. Here are the changes most likely to matter to day-to-day users.
Sage’s 2026 product direction centers on practical modernization: better search, more automation, stronger inventory visibility, expanded audit controls, connected services, and a modern 64-bit architecture.
Crystal Reports is Sage 100’s primary report writer and form builder. Here’s what that means, what it is best suited for, and how it differs from other reporting tools in the Sage 100 ecosystem.
Visual Integrator is Sage 100’s flexible import and export tool for moving data between Sage and other business systems. Here’s how jobs, mappings, testing, scheduling, chaining, and automation fit together.
ODBC provides the connection; Visual Integrator provides the Sage-oriented job, mapping, validation, scheduling, and workflow around moving data between systems.
Sage 100 Payroll connects employee time, job costing, production labor, banking, General Ledger posting, benefits, direct deposit, and reporting into one broader Sage 100 workflow.
Crystal Reports, Business Insights, and Sage Intelligence all report on Sage 100 data, but they solve different problems. Here’s how to choose the right tool for the job.
Sage Intelligence Unlimited is no longer available under Sage 100 subscription plans in 2026. Here’s what changed, what did not, and what customers should review before licensing is adjusted.
Warehouse activity in Sage 100 can connect purchasing, receiving, inventory, barcode mobility, picking, packing, shipping, replenishment, and returns into one broader distribution workflow.
Shipping in Sage 100 connects Sales Order, warehouse fulfillment, package information, barcode processes, carrier integrations, tracking, and invoicing.
NOTES FROM THE FIELD
Product documentation tells you what Sage is designed to do. Field experience tells you what to look at when the server is old, the integration has no documentation, somebody is mysteriously logged in, or a report that worked yesterday suddenly does not.
As this library grows, we’ll add practical troubleshooting and technical articles built from decades of Sage work—not generic ERP advice.
NEED A HUMAN?
If your Sage 100 system needs an upgrade, report, integration, repair, or somebody willing to actually figure out what is happening, talk with All Kleer.
Explore Sage 100 ConsultingNeed to talk now? Contact All Kleer directly →