8 min guideUpdated August 2026App review required

Reconcile accounting sync state

Trace queued, synced or failed invoices, bills, payments and supported timesheets between SignBas3 and the selected accounting provider.

Best forAccounts · Owner / Admin
Before you beginUse a representative record and confirm you have the permissions required for this area.

Step by step

  1. Open the affected invoice, supplier bill, payment or supported timesheet and note its SignBas3 status and reference.
  2. Review the Sync area and distinguish queued, in progress, synced, failed and reconciliation states.
  3. Open the selected provider and compare organisation, contact, reference, amount, tax, currency and current status.
  4. Check the accounting settings and activity log for a mapping, connection or validation event.
  5. Use only the supported retry or reconciliation action after confirming it will not create a duplicate.
  6. If the mismatch remains, raise a support ticket with safe references, timestamps, expected state and observed state.

Good practice

Do not delete and recreate a financial record merely to clear a sync label. Preserve both identities and reconcile the event history first.

When you are finishedYou can distinguish pending work from a real mismatch and identify the supported next action without duplicating the record.

Before you begin

  • The accounting connection and mappings have been tested.
  • You have the safe SignBas3 and provider references for the affected record.

Setup dependency

Settings that change this workflow

The same task can behave differently between organisations. Check these settings before treating a different result as an error.

Accounting mappings/settings/accounting

Controls how operational identities and financial values are represented in the provider.

Open in SignBas3 →
Activity Logs/settings/logs

Provides the event sequence needed to investigate a failed or repeated handoff.

Open in SignBas3 →

If your workspace behaves differently, record the relevant job, client or record number and raise a support ticket so the team can investigate the exact context.