Key takeaways
- JobBOSS² is ECI's job-shop ERP for small and mid-sized make-to-order manufacturers, available as SaaS, hosted or on-premise.
- It offers built-in accounting (GL, AP, AR) or a sync to QuickBooks.
- ECI does not describe an expense report, receipt capture or card feed feature, so card spend is usually keyed from statements.
- Vergo proposes GL codes, texts for receipts and posts coded AP checks to JobBOSS² after ECI activates API access.
Where should you go next?
- Vergo's JobBOSS² integration
- What expense management software integrates with JobBOSS²?
- Get started with Vergo
How do you automate expense management in JobBOSS², step by step?
- Ask ECI to activate API access. This happens once for your account; Vergo does the rest.
- Connect the cards the shop already uses. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Collect receipts from the floor. A machinist or maintenance lead replies to a text with a photo. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
- Code each line to a GL code. Vergo proposes the GL code for every receipt line, with the reason.
- Hand off to JobBOSS². Once ECI activates API access for your account, Vergo reads your GL codes and vendors and posts coded card spend as AP checks through the JobBOSS² API.
What does JobBOSS² need on each card purchase?
- GL code: shop supplies, perishable tooling, repairs and maintenance, freight.
- Vendor: the supplier record the check is written against.
- Receipt: kept with the transaction for audit and warranty claims.
Where does JobBOSS² stop and automation start?
JobBOSS² is strong where a job shop lives: quoting, scheduling, job costing and shipping. Card spend sits outside that flow. A card swipe produces no purchase order and no supplier invoice, so the cost waits until someone reconciles the statement and keys it. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, not just the vendor name on the header. That is how an end mill and a box of shop rags on one receipt end up on two different GL codes.
A practical example
A 40-person machine shop on JobBOSS² gives cards to its maintenance lead and two leads on second shift. A spindle belt fails at night and the lead buys a replacement at a local supplier. Vergo texts for the receipt, proposes the machine repairs GL code from how the last belt was coded, and the controller confirms the next morning. The entry is posted to JobBOSS² as an AP check instead of waiting for month-end.
How Vergo handles this
Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. In a job shop that means the codes your controller already uses for tooling, repairs and freight. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule.
Frequently Asked Questions
How does Vergo get spend into JobBOSS²?
Vergo posts coded spend as AP checks through the JobBOSS² API. ECI must activate API access for your account first.
Why AP checks?
The JobBOSS² API exposes GL codes, vendors and AP checks, so a card purchase is recorded as an AP check against the vendor.
What if we use QuickBooks for accounting?
JobBOSS² can sync to QuickBooks instead of using its built-in accounting. Talk to us about which system should receive card spend.
Can reimbursements run the same way?
Yes. 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.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
