These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect project documents, site evidence and finance through agreed sources.
Bring the estimate, contract documents, site evidence and financial records into the same operating flow. Agree which source owns each fact and how updates preserve its identity. Connections are selected and verified during implementation.
- Estimates, contracts and project work
- Estimating inputsin
- Contract documents and changesin
- Field effort and equipment usagein and out
- Customer progress evidencein and out
- Materials, production and subcontractors
- Receiving and site stockin and out
- Prefabrication capturein and out
- Subcontract applicationsInvoices, SubcontractApplications · in and out
- Returns and correctionsReturns · in and out
- Finance and reporting
- Bank and cash evidencein and out
- Accounting treatmentAccounts, Invoices, ProgressApplications · in and out
- Financial exportsin and out
- Opening datain
- Agents
- Your agentWorks within the permissions you assign
Estimates, contracts and project work
- Estimating inputs. Map quantities, units, component costs, pricing assumptions and offered revisions. Preserve unknown values for review and carry the accepted version into the agreed contract and budget.
- Contract documents and changes. Retain the actual agreement, variation, approval and effectiveness evidence. An imported document or external status does not grant internal spending or billing authority.
- Field effort and equipment usage. Match actual dates, people, quantities and reviewed cost rates to the project and cost code. Preserve the required independent acceptance before the eligible cost effect. Source capture does not imply payroll processing or fleet dispatch.
- Customer progress evidence. Preserve application, certification, stored-material and prior-billing identities. A repeated certificate update cannot create another eligible billing amount. Actual certification remains distinct from a local draft or transmission acknowledgment.
Materials, production and subcontractors
- Receiving and site stock. Separate actual arrival, accepted goods, custody, owned stock and consumption. Canonical units and retained conversions keep quantities comparable across purchasing, warehouse and site records.
- Prefabrication capture. Link issued material, work performed and accepted output to the released order and approved build basis. Historical imports and repeated operation updates cannot create another finished assembly.
- Subcontract applications. Retain approved scope, cumulative work, accepted increments and matching references. Supplier invoices use eligible accepted work; they cannot create a site acceptance or charge the job again.
- Returns and corrections. Preserve the original physical and financial source, remaining quantities and reviewed correction. Uncertain execution stays visible until the actual outcome is established.
Finance and reporting
- Bank and cash evidence. Match actual economic events to the company, counterparty and currency. Retain gross amounts, fees and settlement details before applying cash to an eligible balance.
- Accounting treatment. Agree the contract obligations, recognition evidence, accounts and currency policies before enabling postings. Progress applications, invoices and cash remain distinct sources.
- Financial exports. Preserve company, period, account and posting identity. Exporting the local books does not post the same journal again or establish a statutory filing.
- Opening data. Reconcile a single opening ledger with nonposting detail for stock, work in progress, contracts, accepted work, billing, retention, advances and settlements. Imported history cannot become new operational work.
How connections are governed
service accounts, audit, pausingUse restricted service identities, stable economic keys and retained content revisions. Recheck current action and sensitive-field permissions when work executes. Distinguish a repeated event from a conflicting revision, preserve actual external evidence, and keep uncertain outcomes for reconciliation. Verify partial work, corrections, delayed updates and opening balances before enabling a connection. Installed endpoints and external services require their own confirmed implementation scope.
The API is one more client of the same interface. AI assistants and API →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Compare this accepted estimate with the current project budget.
› Show the contract changes awaiting Commercial Manager review.
› Explain the movement in this job's forecast to complete.
› List unused material still held at this site.
› Trace accepted subcontract work to its bill and remaining retention.
› Compare this progress application with prior certified and billed work.
› Explain the difference between recognized revenue and customer billing.
› Show the material and cost still outstanding on this prefabrication order.