Finance & ERP · Integration
Estate Master
Add Estate Master to your product for your customers, and give your AI agents governed access to it.
Embed an Estate Master integration so your customers can bring their own property development feasibility and cashflow models into your product, reading the cost and revenue lines, timing assumptions, and forecast outputs they already maintain. Every customer structures its models to its own business, so line structures, required fields, and reporting periods are mapped per tenant as configuration rather than hard-coded. fastn handles per-customer authorisation and API upkeep, and writes are idempotent so a retry after a timeout does not post the same figures twice.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Estate Master data so development appraisals sit alongside the rest of their workflow in your product.
Read cost and revenue lines per project so your product reports on the numbers the team already models.
Pull cashflow forecast outputs into your product's reporting instead of exporting a spreadsheet each month.
Refresh reads on a schedule so dashboards in your product stay aligned with the latest model version.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a project's cost and revenue lines before answering a question about the appraisal.
An agent compares two scenarios and drafts a summary of what changed, with every read logged.
An agent pulls updated forecasts on a schedule and posts the notable movements to the team.
Example prompt
Compare the current and previous version of this development appraisal and list the cost lines that moved most.
Set up Estate Master in 4 steps
- 01Open the Estate Master connector from your fastn dashboard.
- 02Have each customer authenticate their own Estate Master account.
- 03Map the projects, line structures, and reporting periods your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Estate Master integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Estate Master integration without building it. Your customers connect their own Estate Master account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Estate Master update is not your on-call problem.
- One integration serves your product and your agents. The same governed Estate Master connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
NetSuiteWorks well with
Anaplan
Workday Adaptive PlanningOften used alongside
Tools the same teams tend to run next to Estate Master, across other categories.
Shopify
Stripe
BigCommerce
AfterShipEstate Master integration FAQ
How do I add an Estate Master integration to my product?
Enable the Estate Master connector in your fastn dashboard, then let each customer authenticate their own Estate Master account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Estate Master client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Estate Master account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Estate Master account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Estate Master integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a project's cost and revenue lines before answering a question about the appraisal.
Who maintains the Estate Master integration?
fastn does. When Estate Master changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Estate Master integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about Estate Master rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the Estate Master integration?
A common starting point: connect their own Estate Master data so development appraisals sit alongside the rest of their workflow in your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Estate Master integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Estate Master does not change your per-connector cost. You can start free with 3 connected accounts.
Add Estate Master to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.