When you need this
You need Greentree Reference values to stay unique and traceable to Sprintsuite document numbers (invoice numbers / PO numbers from Sprintsuite sequences).
Before you start
Know where your tenant configures document numbering (invoice sequences; PO numbering under Job/Project Settings when custom PO numbers are enabled).
Greentree References for pushes use the Sprintsuite document number (within Greentree length limits).
Steps
Confirm Sprintsuite invoice numbering (and PO numbering, if used) produces unique values per Greentree company.
Keep numbers within Greentree’s reference length limits before first push.
Push the invoice/bill once; store the returned Greentree Reference on the Sprintsuite document.
For re-push after Greentree already accepted a Reference, amend the Sprintsuite number (new sequence value) before resync — do not reuse the same Reference for a new create.
Treat Greentree as system of record for the posted Reference; don’t manually invent a second conflicting Reference in Sprintsuite.
[Screenshot: Invoice number field used as Greentree Reference source]
[Screenshot: Document showing Greentree Reference after push]
What success looks like
Each posted document has one clear SS number → one GT Reference.
Re-posts after correction use a new number/Reference path, not a silent overwrite.
If it fails
Too long / already in use → amend SS number, resync.
Custom PO sequences colliding → fix prefix/sequence under PO numbering settings before further Greentree-bound documents.
PO sync to Greentree itself is WIP in this pack — numbering guidance still applies to LIVE invoice/bill References.