Platform · Integrations
It has to reconcile to your general ledger.
That is the finance director's first question and it deserves a straight answer rather than the phrase open API. Below is what is in production today, and what is scoped per deployment, named system by system.
Integrations are scoped and priced openly, per named system, before you commit.
What we connect to
- Finance and ERP
- General ledger, receivables, receipting and reconciliation
- Identity
- Microsoft Entra ID, Azure AD, ADFS, SAML 2.0 for staff single sign-on
- Records and content
- SharePoint, Microsoft 365, HPE Content Manager, TechnologyOne ECM
- GIS and analytics
- Esri ArcGIS, Microsoft Power BI, open REST API, DocuSign, Boomi
- Approach
- Open REST API plus named integrations
- Identity
- Single sign-on for staff, separate resident accounts
- Honesty
- We name what is production and what is scoped
- Pricing
- Per named system, agreed before you sign
Finance and ERP
The systems we post to, and how honest we are about each.
A production integration means it is running for a customer today. Scoped per deployment means we build it against your instance through the open API and middleware layer, and we price it before you commit rather than after.
| System | Status | What it does |
|---|---|---|
| Oracle | Production integration | General ledger, accounts receivable and receipting. In production with a council running Oracle ERP. |
| SAP | Production integration | General ledger and receivables posting. |
| TechnologyOne | Production integration | Finance and ECM. In production with councils reconciling rental revenue automatically. |
| Civica Authority | Production integration | Financial management and receipting. In production. |
| Microsoft Dynamics 365 | Production integration | Finance and CRM. |
| Sage, Xero, MYOB, Infor Pathway | Production integration | General ledger posting and reconciliation. |
| Tyler, OpenGov, Springbrook, CentralSquare, BS&A, Caselle | Scoped per deployment | North American finance stacks, delivered through the open REST API and middleware layer. Scoped and priced openly, per named system, before you commit. |
If your finance system is not listed, ask about it on the demo. We will tell you whether it is an API integration, a middleware integration, or a file-based reconciliation, and roughly what it costs, in the same conversation.
Identity and the rest of the stack
Staff sign in with your credentials. Residents do not.
Staff single sign-on runs through Microsoft Entra ID, Azure AD, ADFS or SAML 2.0, with role-based permissions down to facility and function level. Resident accounts are a separate population by design, which is both a security position and a privacy one.
- Identity and single sign-on. Microsoft Entra ID, Azure AD, ADFS and SAML 2.0. In production with councils using Azure single sign-on for staff access.
- Records and content. SharePoint, Microsoft 365, HPE Content Manager and TechnologyOne ECM, so permits and agreements land in the record system your retention policy names.
- GIS. Esri ArcGIS, used for jurisdiction boundary tests, park and facility mapping, and collection route visualization.
- E-signature. DocuSign, for permits, agreements and waivers where your process requires a countersigned document.
- Middleware. Boomi and equivalent layers, which is usually how a North American finance stack gets connected cleanly.
- Notifications. Email through your own tenant and SMS, so confirmations come from your city rather than from a vendor domain.
Questions
Asked on most calls.
If your panel needs an answer that is not here, send the question and we will publish it.
Our finance system is not on the list. Is that a problem?
Not usually. It is a scoping question rather than a blocker. The open REST API plus a middleware layer covers most North American stacks, and we will price it per named system before you sign rather than discovering it during implementation.
Do you charge for integrations?
Integrations beyond those scoped in your quote are priced per named system. What is in your quote is in your fixed implementation fee.
Can we start without a finance integration?
Yes, and some agencies do, reconciling by export for the first season. It is a legitimate way to get live faster, and it does not change the price of adding the integration later.
Tell us your finance system on the demo.
We will say plainly whether it is a production integration, a scoped build, or a file-based reconciliation, and what that means for your timeline.