01
Cloud project records
Use available hub, project, company, file metadata, and cost-management tables from the Autodesk cloud connection.
Integrations · Construction
Autodesk project data with financial context.
Read authorized Autodesk cloud project and cost records into Permute. Align them with finance exports or connected sources to build reports around a declared project, cost scope, and cutoff.
Read-only APS connector
Autodesk
Construction data
Permute financial intelligence layer
Connected, reconciled, and ready for use
ReportingAnalyticsAI
What this connection unlocks
Put Autodesk into the same trusted layer as the rest of your business.
02
Cost definitions
Keep budgets, contracts, expenses, and payments distinct. Define which records contribute to each report before summing them.
03
Permissions and evidence
Review authorized hub access and Permute workspace access, then retain source references for the figures a report exposes.
Data, setup, and reporting scope
| Source records | Reporting use |
|---|---|
| Hubs, projects, and companies | Establish the project and organization identifiers for cross-source mapping. |
| Folders, items, and versions | Add cloud file metadata and version context to project records. |
| Budgets, change orders, cost items, and contracts | Compare the approved budget and commitment definitions for a project. |
| Expenses, expense items, and payments | Inspect available cost records while keeping expenses and payment timing separate. |
Before connecting
A hub administrator registers the Permute APS client ID as a custom integration, then an authorized Autodesk user completes the connection. Our setup guide names the current product Autodesk Forma; teams may still search for Autodesk Construction Cloud or Autodesk Build.
Confirm the hub, projects, licensed tools, and user entitlements before relying on a table. Review the hub-level integration grant with your administrator (including any Full Hub Access grant). An empty response can mean missing entitlement or no records; it is not proof of zero cost.
Freshness and limits
Use the latest successful sync and the source record dates to define report freshness. A downloaded finance file and a cloud project table may cover different cutoffs even when their imports complete together.
The connection reads Autodesk cloud data through APS. It does not read local desktop files, write records back to Autodesk or an ERP, or guarantee every tool and table in every tenant. Validate the reporting scope using the authorized customer account.
Synthetic worked example
Separate an expense from its payment
Synthetic project A100: an approved report counts a $12,000 expense dated September 30 as cost. A related $8,000 payment occurs October 2. These are different measures, with different dates.
| Record | Effective date | Amount |
|---|---|---|
| Expense E100 | September 30 | $12,000 |
| Related payment PAY100 | October 2 | $8,000 |
A September expense report includes $12,000 under this illustrative definition; a September payment report includes none of the October payment. Do not add the payment to the expense and report $20,000 as cost. Keep the relationship and finance-approved treatment explicit.
One connected workflow
From Autodesk data to trusted business answers.
01
Connect
Bring Autodesk data into Permute.
02
Reconcile
Align records, fields, and definitions.
03
Use
Power reporting, analytics, and AI.
Start with one workflow
Scope your Autodesk project report
Bring the project tools, finance source, and report definition you need. Review available records and access before choosing the workflow.