—
statement months imported
—
stays agreeing penny-clean
—
stays with a difference
—
outstanding to clients
Month by month — Guesty's statements vs the ledger
Matched booking by booking on confirmation code. Click a month to open its differences. "Guesty-only" = Guesty told the owner about a stay the ledger doesn't hold. "Unread" = the ledger row exists but Guesty's API money couldn't be read.
| Statement month | Stays | Matched | Agreeing | Different | Σ |diff| | Guesty-only | Unread | Verdict |
|---|
Business models vs Guesty — lean on Guesty
Each client's model as Guesty actually billed it (fitted from their statement stays) held against their tally model. differs is a flag, never an auto-change — you decide which is the real deal. Mint draft creates a reviewable draft from Guesty's behaviour; it never activates and never touches an existing model.
| Client | Guesty billed | Evidence | tally model | Verdict | |
|---|---|---|---|---|---|
| Loading… | |||||
Statement readiness — who tally can speak for today
Ready = an active model, no invisible units, nothing missing from the ledger. Cancellation lines never block — the cancellation policy machinery handles them. The coverage guard below catches Guesty billing units no listing anpacken can see (how Redgate's 30-block hid).
Loading…
Paid & outstanding — every approved client-month
Due comes from the locked statement snapshot; paid from recorded payments. Recording a payment here is the same act as on the Statements console — one write-path for money.
| Client | Month | Due | Paid | Outstanding | Status |
|---|
Guest debt — the chase list
The other side of cash: what guests still owe on direct and manually-created bookings.
OTA balances are the platform's remittance timing and are stated separately — never chase a guest for those.
Departed stays sort first, biggest debt on top.
Ledger integrity — the API's own gaps
Independent of statements: bookings whose money Guesty's API refused to yield, missing totals, missing codes. These rows can hide real income — they re-sweep hourly, so persistent ones need eyes.
| Check-in month | Bookings | Money unread | No total | No currency | No conf. code |
|---|
Cross-check a Guesty export
The independent surface: export reservations from Guesty's own UI (CSV) and drop it here.
Every confirmation code gets a stated fate — on the ledger, captured as a cancellation, a code-less block —
and anything the ledger has never seen is named UNEXPLAINED, loudly. This is how the hidden A302A unit and
three API-invisible bookings were caught.
or paste below, then