Sitelink
Each facility's daily activity arrives as one balanced journal entry per location per day, posted to the company that owns it.
Overview
SiteLink runs the self-storage facilities. DualEntry keeps the books for them, without anyone rekeying a daily activity report.
DualEntry imports SiteLink's general journal lines and groups them by date and location into one balanced journal entry per location per day, posted to the company you mapped that location to. Locations come from a DualEntry classification whose line names start with the SiteLink location code; accounts are discovered from the journal lines in your backfill window, identified by account code plus sub-account name, and mapped independently.
Data flows one way. SiteLink stays the source of truth for facility operations, DualEntry for the accounting.
Locations
Accounts
General journal lines
Data synced
The integration syncs the following data types:
Key Features
- One entry per location per day
General journal lines are grouped by date and location into a single balanced journal entry, posted to the mapped company.
- Locations mapped to companies
Each SiteLink location code maps to the DualEntry company that should hold its activity, so multi-facility operators keep entities clean.
- Accounts discovered, then mapped
An initial backfill discovers the accounts in use by code and sub-account name, and each one maps independently to a GL account.
- Debits and credits preserved
Every line keeps its debit and credit amounts, with transaction types — income, credits, refunds, NSF — retained as codes.
- Backfill in windows
A single sync spans up to 90 days, so historical loads run in controlled chunks rather than one open-ended pull.
- Pull-only by design
DualEntry never writes back to SiteLink. Facility operations stay untouched.
.avif)