Operator field note refined 2026-10-19.
When a contractor asks whether their software is “AI-ready,” they usually mean “does it have an API.” We used to think so too. In implementation work, we compare the records available through each permitted route before building a financial view across systems. The lesson was humbling: the presence of an API alone never proves it supplies the records needed for month-end close or job costing.
Even mature REST APIs have operational blind spots. In BuildOps, for example, API invoice PDF URLs only populate when an invoice is emailed to a customer, and list-endpoint job statuses can lag detail-endpoint statuses until a job is edited. In Viewpoint Spectrum, web-service access (Data Exchange / SOAP) is licensed module by module, and teams using an authorized SQL replica must verify refresh timestamps across job, cost and payroll table groups independently.
Identifier gaps also show up between field systems and accounting ledgers. In Jobber, customer work-order numbers stored in custom fields do not flow into QuickBooks Online invoice descriptions by default, breaking automated remittance matching for commercial property managers unless bridged into line items.
And then there are the systems with no public pull API at all. In LMN (Granum), legacy Job History time and service exports enforce a hard 100-day date window per pull, Report #7 (Job List) exports in a non-dated form layout, and the GoodData BI “Job Cost Analysis” dashboard is charts-only. In MarketSharp, complete revenue and job-cost tie-out requires pulling a five-report bundle (Production Status, Balance Due, Job Cost, Sales, Payment) across full history because backdated cost or payment edits mutate older jobs, and native CSVs interleave detail rows with group headers and footers.
Materials procurement platforms show the same split between live ERP connections and manual file exports. SubBase, which runs commercial construction materials purchasing from field request through RFQ, cost-coded purchase order, delivery ticket and line-by-line three-way invoice match, supports eight live ERP connections (QuickBooks Online, QuickBooks Desktop, Procore, Sage 300, Foundation, CMiC, Viewpoint Spectrum and Acumatica) while relying on one-way file exports for Sage 100, Sage 100 Contractor, Viewpoint Vista, ComputerEase and TCM. In its file-export workflow, clicking Download TCM or Download Foundation immediately marks the included orders as Synced in the browser whether or not the file has been imported into the ERP, active screen filters restrict which rows export, and Download Foundation silently omits partially shipped and partially delivered orders.
So the real ingestion picture across contractor software is a pragmatic mix: REST API where endpoint coverage is complete, direct database reads where supported, scheduled CSV delivery where the API omits fields or requires an enterprise tier upgrade, and browser report collection where no API exists. A reliable finance data layer uses whichever route returns the complete population and reconciles between them.
This is why we score a system’s AI-readiness by a different question than most buyers ask. Not “does it have an API,” and definitely not “does it have an AI feature.” The question is: how cleanly can a practitioner get complete, trustworthy data out of it, by any method? Answer that, and you know whether AI can ever do anything useful on top.
Official product documentation
Use this in an implementation review
- Choose the required record and field population before choosing API, export or browser access.
- Compare a permitted extraction with the native report, including date filters, totals and identifiers.
- Retain the original export and distinguish detail, repeated headers and subtotal rows.
Specific systems to inspect
Operator analysis informed by scoped implementation workflows. See the full software index.