Key takeaways
- MarkSystems is ECI's ERP for production and semi-custom home builders, organised around cost codes, stage codes and a company, community and house hierarchy.
- AP invoices are distributed to GL accounts, with manual entry, web approval and import paths.
- API access sits in your environment; your IT enables it once.
- Vergo proposes job and cost code for card spend and posts entries into MarkSystems.
Where should you go next?
- Vergo's MarkSystems integration
- What expense management software integrates with MarkSystems?
- Get started with Vergo
How do you automate expense management in MarkSystems, step by step?
- Enable API access. Your IT team enables MarkSystems API access once. Vergo then reads your jobs and cost codes.
- Keep the cards supers already carry. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Receipts from the jobsite by text. 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.
- Confirm house and cost code. Vergo proposes the job and cost code for each receipt line, with the reason.
- Deliver to MarkSystems. Confirmed spend is posted as coded entries into MarkSystems, so nobody re-keys it.
What does MarkSystems need on each card purchase?
- Company and community.
- House (job): where the cost lands for house costing and closing.
- Cost code: so variance against budget is meaningful.
- GL account for overhead purchases that are not house costs.
Where does MarkSystems stop and automation start?
MarkSystems is strong on the purchase orders and variance POs that drive most house costs. Card purchases sit outside that flow: a superintendent buys caulk, fasteners and a replacement part to close out a punch list, and the charge shows only the store name. Someone must work out which house and cost code it belongs to. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — house and cost code — not just the store.
A practical example
A production builder on MarkSystems has a superintendent covering two communities. On one receipt, the super buys door hardware for a house in the first community and landscaping stakes for a model in the second. Vergo asks for the receipt by text, then suggests the finish hardware cost code on the first house and the landscaping cost code on the model, citing earlier purchases. The accountant confirms, and both lines are posted to MarkSystems.
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. For builders, that includes the house, because a cost on the wrong house skews margin at closing. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. 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.
Frequently Asked Questions
What does our IT team need to do?
Enable MarkSystems API access in your environment once. Vergo handles the rest.
Does Vergo post directly into MarkSystems?
Yes. Vergo posts coded entries into MarkSystems, using your jobs and cost codes.
Can Vergo split a receipt across houses?
Yes. Vergo reads each receipt line and proposes the house and cost code for each.
Do supers need a MarkSystems login?
No. They reply to text messages with a photo.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
