Resources
Data Flow
How data moves between Xero and RecHound — what we read, what we write, and how your data stays secure.
RecHound is a read-firstintegration. We pull data from Xero to power your reconciliation workflow, and almost nothing is written back. The exceptions are specific journal postings (prepayments and revenue recognition) that you explicitly trigger — and those are always visible in Xero's audit log.
Xero
Source of truth
RecHound
Reconciliation layer
Xero → RecHound
Chart of accounts
All accounts from your Xero organisation, synced on connection.
Trial balance
Current and prior period balances, updated on each sync.
Transactions
Individual journal lines for each balance sheet account.
Organisation settings
Financial year, currency, and period configuration.
RecHound (internal)
Reconciliation status
Which accounts are unstarted, in progress, or approved.
Transaction matching
Cleared transaction pairs stored within RecHound only.
Workpapers
Supporting documentation, notes, and file attachments.
Approvals & audit trail
Who approved what, and when — timestamped and locked.
RecHound → Xero
Prepayment journals
Amortisation journals posted back to Xero via the API.
Revenue recognition journals
Deferred revenue release journals posted to Xero.
Nothing else
RecHound does not modify your transactions, balances, or settings in Xero.
Security
OAuth authentication
RecHound never sees or stores your Xero password. Authentication uses Xero's standard OAuth 2.0 flow.
Encrypted in transit & at rest
All data is encrypted using TLS in transit and AES-256 at rest. We follow industry-standard security practices.
Revoke access anytime
You can disconnect RecHound from Xero at any time from your Xero organisation settings — no data is retained.
Questions about data security? Get in touch— we're happy to walk you through our practices.