What Current writes back to Rev.io (and when)

Reading from Rev.io is always on once you connect. Writing is the part with gates, and this page is the full list: what has to be open, what sets a write off, and what Current will not write at all.

1. 1
   The project has to be a Rev.io project

   A Current-native project never calls Rev.io, whatever else is switched on. Building a native project into Rev.io is a one-way conversion and asks you to confirm it first.
2. 2
   Two-way sync has to be on

   The switch in the Rev.io card's Manage drawer. It is on by default and covers task, project, ticket, customer, contact and note writes. Off stops those. Time entries are gated by CRM write mode alone.
3. 3
   CRM write mode decides which customers can be written to

   Off by default, and it gates every write, time included: with it off Current writes nothing to Rev.io. Test mode writes only to records whose Rev.io customer's name starts with ZZ-Current Test. Each write checks the record's own customer as Rev.io holds it, read live from Rev.io at the moment of the write, never Current's copy. Live mode writes to real customers.
4. 4
   The person has to be allowed

   Project writes need a project manager or above; a task's assignee can also change that task. An account executive can push their own book's companies and contacts, checked against their ownership in the database rather than in the interface.
5. 5
   The key's role has to carry the permission

   A Rev.io key can do only what the user who created it can. A missing permission comes back as a named refusal rather than a silent no-op.

Rev.io does not document whether an update leaves the fields you didn't send alone. So every update reads the record first, changes only the field you changed, sends the full record back once, and reads it again to confirm Rev.io stored what it was given. If Rev.io kept a different value, for example because a workflow rule changed the status, that becomes a visible conflict on the record rather than a second write that fights with your team.

When a write fails without a clear answer, a timeout or a server error, Current does not send it again on its own. A retried create is a duplicate: a second project, a second customer, or a second time log billing the same hour twice. Instead Current reads back to see whether the first one landed. If it did, Current links to it. If Current can't find it, it does not send it again on its own: the entry is flagged with the reason for a person to check Rev.io first, so the same hour is never logged twice.

• ＋Before creating a time log, Current marks the entry as being sent, then looks for a time log it may already have created for it and adopts that instead of adding another.
• ＋Current never sends a billing rate. Rev.io bills at its own rate for the time log reason you picked.
• ＋Only the entry's summary is sent. Your internal notes on a time entry stay in Current.
• ＋Time on a project task reaches Rev.io only when the task's work item is a ticket. A calendar task can't take time through Rev.io's API, so the entry stays in Current with that reason on it.
• ＋Current sends a time entry once. Editing it afterwards in Current does not change the Rev.io time log, so make corrections in Rev.io.
• ＋Once Rev.io locks a time log, for example after it is invoiced, Current marks the entry approved.

• ＋Deleting records. Current never deletes a customer, contact, ticket, project, task or time log in Rev.io. The one exception is a customer note deleted in Current: that note is deleted in Rev.io too, when CRM write mode allows it.
• ＋Opportunities and quotes. They are read-only in this release.
• ＋Customer email. A ticket note is an activity note; Current never sends the customer a message through Rev.io. Whether Rev.io shows an activity note to the customer is still being confirmed.
• ＋Cost, invoices and rates. Money is Rev.io's.
• ＋Attachments, which are not available for Rev.io yet.