POs, invoices, pay applications, RFIs, submittals and schedules move between your systems and your partners' without shared logins, portals or re-keying. Exchange stands on its own: your Procore or ERP on one side, your partner's system on the other, and no Aquifer app required. If you run the apps, they send and receive through it too.
RFIs, submittals, purchase orders, invoices, pay applications, change orders, schedules, daily reports, as-builts, project cost data and attachments. Each one leaves your system and arrives in your partner's.
Owner and contractor. Contractor and sub. Contractor and supplier. Each company keeps its own systems and its own logins.
A purchase order approved in your ERP becomes a sales order in your supplier's. A pay application leaves the contractor's system and arrives coded in the owner's AP.
No app is needed on either side. If you do run them, a pay application built in Accounting arrives coded in the owner's payables, an RFI raised in Coordination reaches the architect's system and the answer comes back, and a schedule from Scheduling is shared with every sub.
Pay applications, invoices and schedules go toward the owner. Approvals, change orders and purchase orders come back the other way. Each company keeps the system it runs, and each decides what it shares.
Exchange connects the companies on a project, whether each runs Aquifer or its own systems. Each side keeps full control of its own systems and credentials. Data is mapped and transformed as it crosses the boundary. No portals, no re-entry.
The same part of the platform, used by the owner, the general contractor and the subcontractor. One example each.
Receive pay applications, invoices and schedules from every contractor into your own systems. Send approvals and change orders back the same way.
Send pay applications and schedules up to the owner. Send POs and subcontracts down to the subs and receive their invoices without a portal.
Receive purchase orders in the system you already use. Send invoices and pay applications back without another portal login.
Share project cost data with an owner without exposing internal markup. Receive submittals without opening your whole project. Each company sets its own sharing rules.
Nobody can pull data from a partner. A partner pushes what it chooses to share, and each side keeps its own logins.
Your cost codes map to their cost codes and your project structure maps to theirs. Mappings are written in SQL, reviewable and under version control.
Configure the route once. Send a PO and it arrives in the right partner's system, whatever they run.
Owners see one view across all their contractors. GCs track sub progress without chasing updates. The same data, where it is needed.
Every record is traced from sender to receiver with a complete log. No disputes over what was sent, when, or by whom.
A partner without an Aquifer account joins as a guest. Start the flow with a vendor or an owner before they buy anything.
Connect over API, EDI, AS2 or SFTP. Aquifer handles the protocol so your partner's system and yours do not have to match.
Exchange connects the systems you already run to the systems your partners run, with nothing else from Aquifer needed. If you run Accounting, Scheduling or Coordination, they send and receive through it too, so a pay application, an RFI or a schedule crosses the company line without leaving the app.
Each company connects its Aquifer account or its own system and approves the partnership. Each side keeps full control of its own systems and credentials.
Configure which data types flow between the companies. Share RFIs and submittals but not internal memos. Exchange invoices and POs but not cost breakdowns.
Data transforms as it crosses from one company to the other. Your cost codes map to their cost codes. Your schema maps to theirs. No manual reconciliation required.
Once configured, data moves between the companies without manual intervention. Updates sync as they happen with full audit trails.
Pricing follows what you use. Every part of the platform can be taken on its own and kept in sync with the systems you already run. Talk to us about pricing for your company.
Talk to us →Do both companies need Aquifer accounts?
At least one party needs a paid Aquifer account. A partner without one joins as a guest, so you can start exchanging data with vendors and partners without requiring them to purchase Aquifer.
Do I need the Aquifer apps to use Exchange?
No. Exchange works between the systems you and your partners already run. If you do run Accounting, Scheduling or Coordination, they send and receive through it as well: a pay application to an owner, an RFI to an architect, a schedule to a sub, each arriving in whatever the partner runs.
What if my partner uses different software than we do?
That is the point. Exchange transforms data between different systems. Your Procore connects to their Autodesk. Your Sage connects to their Oracle. The systems don't need to match.
Who controls what data is shared?
Each company controls what it shares. You cannot pull data from a partner; they have to push it to you. Both sides configure their own sharing rules.
Can I share data with multiple partners?
Yes. Configure a different Exchange flow for each partner relationship. Share different data sets with different partners.
How is this different from Integrations?
Integrations connects systems within your company. Exchange connects systems across companies. Most customers use both: Integrations to sync their internal systems and Exchange to share data with partners.
We use analytics cookies to see which pages are useful, and LinkedIn and Google tags to measure our ads and show them to past visitors on LinkedIn. Privacy notice
