LarchManual
Manual · 03

Connections: every source Larch reads from

One connected data layer. Every connector is read-only — Larch never writes back to a source system.

Xero

The original Larch connector, for clients whose books live in Xero. OAuth authorization against the client's organisation, a currency guard that blocks sync when the Xero currency disagrees with the client record, and a nightly sync of trial balance and P&L. The full walkthrough lives on its own page: Connecting Xero.

Business Central

For clients on Microsoft Dynamics 365 Business Central. Larch reads the complete standard ledger — no custom objects in the client's tenant, nothing installed on their side.

  1. What syncs. General ledger entries with the Department dimension on every posting, month-end balance snapshots for the balance sheet, and the customer and vendor open-item ledgers that drive the A/R and A/P reports.
  2. How it refreshes. Engagement → Data → Business Central panel → refresh. The panel reports exactly what was written: P&L months, balance snapshots, dimension slices, and A/R / A/P open items — with any failures shown, never swallowed.
  3. The snapshot timestamp. Every report and pack renders from the committed snapshot and shows when it was taken. If the timestamp predates the month close, refresh again — the reports say so rather than guessing.
  4. As-of restatement. A/R and A/P can be aged at any historical date: entries closed after the chosen date are re-included at their original amounts. Partial applications in the gap are not reconstructed, and the report notes this.

Business Central is read-only to Larch. Statements reconcile to the BC trial balance at each month-end, and the coverage warnings in the product tell you when a period is not yet complete.

Aimsio

Field operations — tickets, invoices, labour hours, equipment — via a read-only connector synced daily. It powers the Lookout operational workspace; job-level financial overlays combine Aimsio with the accounting source above.

One habit worth keeping: after any month-end close in the source system, run a refresh before reading reports for that month. The data layer is honest about what it has, but it cannot know about postings it has not been asked to read.

Larch · This manual describes the platform as deployed; when in doubt, the live preview and coverage warnings in the product are authoritative.