Connectors and exports
Integrations, listed honestly
This page lists every external system Real Estate Management connects to today. There is no logo wall. If a connector is not on this page, it does not exist yet, and we will say so.
- Invoicing platform integration, including document types, numbering scheme prefixes and suffixes, and VAT on payment
- Accounting connector over GraphQL, authenticated with client SSL certificates
- Per-user credentials for external platforms, so documents are issued under the right person's account
- Documents stored on S3-compatible object storage; outbound mail sent through each account's own SMTP server
The current list
What Real Estate Management connects to today
Six integration points, all in production use. Each one is described in detail further down the page.
Invoicing platform connector
Invoices and rebilling invoices are issued directly on the connected invoicing platform. Document type, series numbering, due days and VAT-on-payment handling are configured per set of credentials, not hard-coded.
Accounting connector
A GraphQL connector that reads expense and revenue positions from the connected accounting system by period and by building, authenticated with client SSL certificates and cached for large portfolios.
CSV export
Contract data and supplier invoice data can be exported as CSV straight from the list screens, for spreadsheets, auditors, or loading into any system that has no connector.
Branded PDF generation
Per-client rebilling sheets are generated as PDFs showing how each figure was derived, carrying the account's own logo, colour scheme and font sizes rather than ours.
S3-compatible document storage
Documents and assets attached to properties, units, contracts and technical assets are held in S3-compatible object storage, in an EU region, separate from the application database.
Per-account SMTP
Each account configures its own outgoing mail server, so contract reminders and tenant correspondence arrive from the landlord's own domain, with the landlord's own deliverability record.
Invoicing platform
Issuing documents under your own numbering scheme
Invoices produced from portfolio and utility data are pushed to the connected invoicing platform through its API. The point is not to move a PDF around. The point is that the document exists in the platform your accountant already reconciles against, under the series and number it is supposed to carry.
What is configurable per credential set: the document type, the numbering scheme prefix and suffix, the document title, the seller and client titles printed on the document, the number of due days, and whether a client reference is required before a document may be issued. VAT on payment is a supported flag, so accounts on that regime issue documents that state it correctly.
Credentials are stored per user, not per account. When several people in a company issue documents, each one issues under their own platform account, and the audit trail reflects who did it. Stored credential values are encrypted at rest.
Once a document is issued, the system keeps the external reference and can fetch back the series and document date, produce a direct view link to the document on the platform, and send the document to a recipient by email with an optional BCC for your own records.
The invoicing platform connected today serves the Romanian market. If you need documents issued into a different platform, that is a connector request rather than an existing feature — see the section on the connector layer below.
Accounting connector
Reading the ledger back into the portfolio
The invoicing integration pushes documents out. The accounting connector pulls figures in. Together they close the loop between what you billed and what the books actually recorded.
The connector queries the connected accounting system over GraphQL for a date range, either across all buildings for a period or narrowed to a specific building through its operating unit code. Returned positions are separated into expenses and revenue by accounting category and normalised into comparable money values, so a property group's totals can sit next to the revenue timelines the reporting module already draws.
Authentication uses client SSL certificates rather than a shared API key alone, with the bearer token held in per-user credentials. Requests are serialised through a distributed lock and results are cached, so a dashboard refresh on a large portfolio does not turn into a burst of traffic against your accounting system.
This matters most where utility rebilling is involved. Supplier costs, allocated shares and issued rebilling invoices all become comparable against the ledger without anyone retyping a figure.
End to end
How a meter reading becomes a ledger entry
The integrations are not standalone add-ons. They are the last two steps of a chain that starts at a physical meter on a wall.
-
Readings and supplier invoices are captured
Meters and sub-meters are read, on batch screens that let you walk a building meter by meter. Supplier invoices and supplier meter readings are recorded against the relevant utility supply contract.
-
Costs are allocated
Rebilling entries group consumption by utility type and rebilling mode, then apply an allocation key — per square metre, per person, per unit, per consumption share, or a custom formula evaluated by the formula engine.
-
Invoices are previewed
The rebilling dashboard shows what will be issued before anything is issued. Each client's rebilling sheet PDF sets out how the figure was derived, line by line, so a query can be answered without opening the software.
-
Documents are issued to the platform
Approved invoices are issued in batch to the invoicing platform under the configured document type and numbering scheme, from the credentials of the user issuing them, and can be emailed to the recipient directly.
-
The ledger is read back
The accounting connector returns booked expenses and revenue for the same period and buildings, so reconciliation compares issued documents against recorded figures instead of against a memory of what was sent.
Getting data out
Export formats and file handling
An integration you do not have is survivable if the export is honest. These are the routes out of the system that do not require a connector.
- Contract CSV export — rental contracts, bailment agreements and early termination contracts export to CSV from their list screens, filters applied, for auditors, spreadsheets and systems that will never have a connector
- Supplier invoice CSV export — supplier invoices export to CSV as well, which is usually the fastest way to hand a bookkeeper a period's utility costs when no accounting connector is in place
- Per-client rebilling sheet PDF — a branded PDF per client showing consumption, allocation key, share and resulting amount — the document you send when a tenant asks how their ancillary cost statement was calculated
- Account-level PDF branding — logo, colour scheme and font sizes on generated PDFs are set per account; on Private Cloud, the interface can be white labelled as well, so nothing carries our name
- Document attachments — any portfolio entity, contract or technical asset can carry attached documents and assets, held in S3-compatible object storage, so land registry extracts, supplier contracts and maintenance records stay with the record they belong to
- Outbound mail on your own domain — per-account SMTP means contract end reminders and renewal notices leave from your mail server, not ours, and every issued notification is recorded with what was sent and to whom
Scope, stated plainly
What is built, what is not
We would rather lose an evaluation on this table than win one and disappoint you in month two.
| Integration point | Status | What that means in practice |
|---|---|---|
| Invoicing platform connector | Built, in production | Documents issued to the platform with configurable document type, numbering prefix and suffix, due days and VAT on payment |
| Accounting connector | Built, in production | GraphQL reads of expenses and revenue by period and building, client SSL certificate authentication |
| CSV export | Built | Contracts and supplier invoices export from their list screens |
| PDF generation | Built | Per-client rebilling sheets, branded per account |
| S3-compatible document storage | Built | Attachments on portfolio entities, contracts and technical assets |
| Per-account SMTP | Built | Tenant and reminder email sent from the account's own mail server |
| Other invoicing platforms | Not built | Available as a connector project — talk to us about the platform you use |
| Other accounting packages | Not built | Same: the connector layer is designed for this, but the work has to be done and paid for |
| Public REST or GraphQL API | Not offered | The product surface is the administration interface; there is no self-service API to build against today |
| Banking feeds and payment reconciliation | Not built | Payments are not matched automatically; the accounting system remains the system of record for cash |
| Maintenance ticketing and mobile apps | Not built | The facility management module is a technical asset register and service partner list, not a ticketing system |
Anything not named on this page is not connected. If a vendor list or an RFP asks about a system that does not appear here, the accurate answer is that it is not built.
On request and on the roadmap
The connector layer is built to be extended
Invoicing platforms and accounting connectors sit behind their own abstractions in the codebase. An invoicing app declares which credential keys it accepts, how it persists a document, how it builds an external view link and how it delivers a document by email. An accounting connector declares its authentication and its endpoints, and returns normalised expense and revenue positions. Adding a second one of either is a defined piece of work, not an architectural change.
That is the honest version of "extensible". It does not mean a new connector appears the week you ask. It means the shape of the work is known, it can be estimated, and it does not destabilise what already runs.
We do not publish a roadmap of connector names we have not committed to, because a name on a roadmap page reads like a promise. What we will do is tell you, in a first conversation, whether the system you run has an API we can work with, roughly what the integration would take, and whether an export route would serve you better in the meantime.
If you are evaluating the product and a specific platform is the deciding factor, write to us with the platform name and what you need to move in each direction. You will get a direct answer from someone who would do the work.
Connector work is quoted separately. Consulting and development time after onboarding is charged at the published hourly rate on a best-effort basis, and a larger connector project would be scoped and quoted before it starts. All prices exclude VAT.
Not built today
On request and on the roadmap
The requests we receive most often, and where each one stands. None of these exists today: some are connector projects that can be scoped and quoted, others are routes we have deliberately not taken.
Other invoicing platforms
One invoicing platform is integrated today. Issuing into a different one is a connector project behind the invoicing app abstraction, scoped and quoted before it starts.
Other accounting packages
One accounting system is connected today. A second package is a defined piece of work behind the accounting connector abstraction, and existing customers can commission one.
Public REST or GraphQL API
There is no self-service API for customers to build against. Data leaves the system through the built connectors, through CSV export and through generated PDFs.
Banking feeds and payment reconciliation
Payments are not matched automatically inside the system. Your accounting package remains the system of record for cash.
Maintenance ticketing and mobile apps
The facility management module is a technical asset register and a service partner list. It is not a ticketing system, and there is no mobile application.
Named roadmap dates
We do not publish connector names we have not committed to, because a name on a roadmap page reads like a promise. Ask, and you will get an assessment of your platform instead.
Before you decide
Tell us which systems have to talk to each other
Send the name of your invoicing platform and your accounting package. We will tell you whether it is built, whether it is buildable, and what the export route looks like if neither answer is yes.
Questions
Asked in every integration review
Which accounting software does Real Estate Management integrate with?
One accounting system is connected today, through a GraphQL connector authenticated with client SSL certificates. It reads booked expenses and revenue for a period, either across the whole portfolio or for a single building. Other accounting packages are not connected out of the box, but the connector layer was built to take further systems, and existing customers can commission one.
Can I issue invoices to my own invoicing platform?
One invoicing platform is integrated today. Document type, numbering scheme prefix and suffix, due days, document and party titles, and VAT on payment are all configured per credential set, and credentials are held per user so each person issues under their own platform account. Other platforms require a connector project rather than configuration.
Is there an API I can build against?
Not today. The product surface is the administration interface, and there is no public REST or GraphQL API offered for customers to integrate with directly. Data leaves the system through the built connectors, through CSV export on contract and supplier invoice screens, and through generated PDFs. A dedicated integration can be built as a project.
Where are documents and attachments stored?
Attachments on properties, housing units, contracts and technical assets are held in S3-compatible object storage in an EU region, separate from the application database. On Private Cloud, storage and database backups are additionally mirrored to the client's own site or office, alongside dedicated backup and failover infrastructure.
Will tenant emails come from my domain or yours?
From yours. Each account configures its own SMTP server, so contract end reminders, renewal notices and tenant correspondence are sent through your mail infrastructure and carry your sending reputation. Every notification issued is recorded with its recipient and content, giving an audit trail of what left the system and when.
Next step
A short answer beats a long evaluation
Name the invoicing platform and accounting system you run today. We will tell you exactly where you stand, including when the answer is that we have not built it.