Skip to content

Daily accountant workflow ​

Follow this order for a clear audit trail. Your role and the current safety gates determine which buttons are available.

1. Import a bank statement ​

  1. Open Bank statements.
  2. Confirm the active organization/outlet.
  3. Upload the bank file and wait for the import result.
  4. Open the import to review its transactions, warnings, and any duplicates.

Bank statement import

2. Review matching ​

  1. Open the imported statement or Name matching.
  2. Review suggested counterparties and the explanation shown for a match.
  3. Correct, exclude, or create a matching rule only when the source information supports the decision.
  4. Leave uncertain items for review; do not force a guess.

Name matching

3. Check documents ​

  1. Open Syrve documents.
  2. Review payment status separately from processing status. A payable target must be Processed and not Deleted.
  3. If the page shows Not processed or Status unknown, refresh documents and do not confirm payment.
  4. Refresh or synchronize only when your permissions allow it and the page requests it.

Syrve documents

4. Allocate and prepare posting ​

  1. Open Payment allocations or the payment posting flow for the transaction.
  2. Compare the bank transaction, selected documents, and allocation total.
  3. Confirm or approve only after the information is complete and consistent.
  4. Follow the visible preflight and approval steps. A successful queue action is not the same as a completed external posting.
  5. Processing-state blocks cannot be bypassed by manually entering a document id.

Payment allocations

5. Resolve anomalies ​

  1. Open Payment anomalies when a warning, failed action, or unresolved item appears.
  2. Read the reason and related payment evidence.
  3. Correct the underlying data or follow your organization procedure.
  4. Retry or reconcile only when the page allows it and you understand the result.

Payment anomalies

End of day ​

Return to the dashboard or workbench, make sure attention items have an owner, and use the audit log when you need to confirm what happened.