Set the automatic pull cadence

Minutes between automatic pulls: 10 (the shortest cadence Finero commits to) to 1440 (24 hours). Required even when enabled is false — it is the cadence kept for when automatic syncing is switched back on.

Whether automatic pulls run at all.

ERP connection id — use as connection_id when starting a sync run.

ERP system this connection syncs from: oracle_fusion (Oracle Fusion Cloud ERP) or xero (a Xero organisation, connected by signing in to Xero).

How invoices are read from the ERP. rest_api reads the receivables REST resource with its payment schedules; publisher_report reads invoice headers from an Analytics Publisher report, so every invoice from that connection is collected as a whole — installments and contact names are never present. Both methods sync incrementally (changes since the last sync) and run a complete pass at least once a day, which is when an invoice that vanished from the ERP or from the report is marked no longer present. A xero connection always reads rest_api: Xero has no payment schedules, so its invoices are collected as a whole too. Read-only: the method is chosen when a workspace admin connects the ERP.

HOW a payment's receipt is pushed to the ERP. rest — the receivables REST resource. soap — the ERP's receipt SOAP services, offered only on a publisher_report connection, which then uses its report's SOAP user for everything and holds no OAuth client. A xero connection pushes rest: each payment is recorded in Xero against the invoice it paid. Either way an accepted receipt reads erp_push_status: posted. Read-only: the transport is chosen when a workspace admin connects the ERP.

WHEN a payment collected through Finero is pushed to the ERP as a receipt. auto — right after the payment settles, without anyone acting. manual — the receipt is created at settlement but HELD until a workspace admin releases it, one or many at a time (POST /v1/payments/erp-push); a held payment reads erp_push_status: held. Releasing pushes each receipt on its own, so one failure never affects another. Switching from manual to auto releases everything held on the connection. Set with POST /v1/erp-connections/{connectionId}/payment-push-mode.

Connection health, and therefore whether the invoice data you are reading is CURRENT. connected means pulls are working. requires_reauthentication means the credential is missing, expired or revoked: scheduled pulls pause until a workspace admin reconnects it in the Finero app, so nothing new arrives and every figure is only as fresh as last_successful_sync_at - say so when you report numbers. temporarily_unavailable is the ERP being unreachable and usually clears itself. disconnected means the connection is switched off. In any state but connected, compare last_successful_sync_at against last_sync_at: a LATER last_sync_at means runs are still happening and not completing.

When a sync run last finished, whatever its outcome. Use last_successful_sync_at to judge freshness (ISO 8601 UTC).

When a sync run last completed its walk of the ERP: a success run, or a partial one that only skipped invoices (its error_summary is null). Freshness of the imported data (ISO 8601 UTC).

Whether scheduled auto-sync is on. False is the workspace's "off" choice - manual pulls still work, and auto_sync_interval_minutes keeps the cadence that applies when it is turned back on. True still requires connected health and a stored credential; reconnection restores the retained schedule after a missing-credential failure.

How often Finero pulls this connection automatically, in minutes. A workspace admin chooses it: 10 to 1440 (24 hours). Read it together with auto_sync_enabled - when that is false there is no automatic pull at all and this value is simply the setting kept for when it is turned back on. It is a FLOOR rather than an appointment: a connection is pulled on the first scheduled check after this much time has passed, typically within a minute of it.

Oldest invoice date this connection imports, inclusive. null means no limit. This is why an invoice that exists in the ERP may be absent here: it is dated before the limit. Changing it never deletes invoices already imported (YYYY-MM-DD).

Creation time (ISO 8601 UTC).