The close in SAGE
How a close goes to SAGE as a till close document, what each status means, sending it again, and why a past day goes into the next close.
At a store that sends its closes to SAGE (Settings › Stores, the store's page, Send closes to SAGE? · Yes, the default once it has a SAGE till), each close closes that till's session in SAGE, the same till its sales and returns go to. SAGE builds the till close document itself, as its own POS does, in the store's série. The counted cash stays in zrsPOS.
Where it stands
A close's SAGE section, field Till close document, says one of:
- Sent: "… on Caixa 1 (001)", read back: zrsPOS read SAGE's lines and compared them. "It was already in SAGE: zrsPOS linked it, nothing was sent twice." when SAGE had it already.
- Pending: "SAGE didn't take it yet; zrsPOS tries again at 20:40."
- Not in SAGE, with SAGE's reason. zrsPOS tries again by itself, a few minutes apart at first and at most an hour apart later, for a week.
- Goes into SAGE's next close on Caixa 1 (001): "SAGE refuses a close after midnight; it goes in the next one. Nothing to do." Once that close exists: "In SAGE's next close, …".
- Not sent, by design: "Not sent: Loja Funchal is closed in SAGE", "Not sent: paused by zrsPOS support", "Not sent: the final close sends it" (a partial close), "Not sent: … had no SAGE till", "Not sent: no série for till close documents", "Not sent: … had no open session in SAGE" ("Nothing to do: SAGE had nothing open to close."), "Not sent: per-tablet closes stay in zrsPOS".
Send it again

- Open the close and tap Send Loja Chiado's close to SAGE again (or … to SAGE now while pending).
- Confirm: "zrsPOS first looks for it in SAGE, and sends it only if it isn't there. A till close document can't be changed."
- The steps show "Looking for it in SAGE", "Sending to SAGE", "Reading back from SAGE", then "Sent again and read back: … on Caixa 1 (001)."
At the till: tap Close not sent, then Send to SAGE again.
There is never a duplicate. Before every post zrsPOS checks whether SAGE already closed that session, and links it if so. After a post that got no answer, it waits ten minutes before posting again: "SAGE may still be closing this till — try again in a few minutes."
A past day goes into the next close

SAGE only takes a close for the current day. A close made after midnight, or a forgotten day closed the next morning, sends nothing for that day: its money goes into that till's next close, because every till close document takes the till's whole balance. The tile says Yesterday's close · "Goes into the next close (till 001)". Nothing to do.
Edge cases
- Sending paused by zrsPOS support: Till close says "Paused by zrsPOS support. Closes stay in zrsPOS; none go to SAGE.", with Resume sending closes to SAGE. Resuming first checks that every store that sends its closes has a SAGE till; if one hasn't: "Not resumed: … sends closes but has no SAGE till."
- One per till: each close sends at most one till close document per SAGE till, on the day's latest open session.
- Several SAGE tills in one period (the store changed tills that day): each till the period's documents went to is closed, unless another store has that till now.
- SAGE recorded other totals: the close's By SAGE payment method shows SAGE's figure; check that close in SAGE with your accountant.
- A read-only plan still sends a close again, and resumes sending.