Property payments, Xero contacts and reconciliation

Xero was accessed through Integromat’s connector while Building Stack required custom API requests. The configured flow retrieves transactions and filters for recent payments entered by tenants. The walkthrough describes a daily lookback, rather than proving continuous unattended operation.

The flow searches for an accounting contact and branches between using an existing record or creating a new one, followed by a bank-transaction step. Final categorization still required input from the client’s accounting team.

The systems represented contacts differently. Xero could contain a household as one free-text contact, while Building Stack represented individual tenants associated with a lease. Missing names and inconsistent formats made a simple text match unreliable.

Noah prepared a comparison spreadsheet to examine candidate matches and missing equivalents. A successful test in his own account did not resolve the discrepancies found with other records.

The work identified a need to associate Xero account codes with the relevant Building Stack categories. Balance-tracking settings also affected whether particular charges could be added.

Those issues depend on accounting semantics and account configuration, not only the API connection. The recordings document the questions and a mapping approach; they do not establish that the categories or balances were reconciled.

A two-way integration can copy its own newly created record back into the originating system. The handover discusses corresponding record IDs as a way to recognize linked records and avoid that loop.

The reverse-sync control remained in development. The work covered integration analysis, mapping and troubleshooting rather than a finished two-way service.

The integration reached configuration and debugging. Contact matching, category mappings, balance tracking and reverse-sync loop prevention remained development work before a complete two-way rollout.