How do I automate employee reimbursements in Sage 100?

What makes reimbursements and expense reports AI-native?

AI-native reimbursement removes the expense report rather than speeding it up. The employee texts a photo of the receipt, Vergo reads it line by line, infers the coding from what was bought and from your accounting structure, and chases anything missing itself — no form, no app to download, no portal to log into. The difference shows up on the first transaction from a supplier nobody has set up. A rules engine has no pattern for it, so it queues the item and waits for a person. Vergo proposes the coding from the main accounts and subaccount segments already in Sage 100, then shows why it chose it — so review is a confirmation, not a re-coding. More on the category in reimbursements and expense reports.

How does Vergo work with Sage 100?

Vergo reads your Sage 100 general ledger — the main account and the subaccount segments your account structure defines, up to ten segments in all — along with your vendor list and A/P divisions, through the Business Object Interface Sage includes with every Sage 100 activation. It codes against that structure, then produces entries in the import format Sage 100 expects: Visual Integrator jobs that load A/P Invoice Data Entry batches (vendor, invoice number, GL account and distribution amount on every line) and General Ledger journal entries. Sage 100's own update process then posts them, which is the route Sage itself recommends for keeping the ledger in balance. Whether Sage 100 runs on your own servers or with a hosting provider, your IT enables access once and Vergo does the rest; the full spec sheet lives on the Sage 100 integration page.

What does this look like day to day?

Someone buys something and texts a photo of the receipt, or a supplier emails an invoice. Vergo reads the lines — not just the total — and proposes the account from your own history with that vendor. The reviewer sees the proposal and the reason for it, confirms, and the entry lands in A/P Invoice Data Entry or the General Ledger journal file ready for Sage 100's update. Nobody types an account number, and nothing waits for a month-end scramble.

What does the employee have to do?

Text a photo of the receipt. There is no app to download and no portal to log into, and Vergo chases a missing receipt itself instead of waiting for an expense report. Mileage runs through the same coding model, so a drive and a receipt from the same trip are coded the same way and reconcile together. That matters most for the people least likely to install anything: someone who will never open an expense app will reply to a text.

What changes at month end?

The work moves from the end of the month to the moment of spend. Because coding happens at capture, close in Sage 100 becomes a review of exceptions rather than a backlog of uncoded transactions. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.

Is this the same as expense management?

No — the difference is whose money was spent. Reimbursement handles an employee's own card or cash; expense management handles the company card. The same coding model runs both against the same Sage 100 structure, which is why one reconciliation covers them. See expense management and AP invoice automation.

Who runs Sage 100?

Sage 100, from Sage, is the mid-market ERP run by distributors, manufacturers and service businesses — the system many finance teams still call by its former names, MAS 90 and MAS 200, which Sage retired in 2012. It is a different product from Sage 100 Contractor, Sage's construction package; if that is the one you run, see expense management for Sage 100 Contractor. Wherever your finance team lives, the expense layer should adapt to it — not the other way round.