Loading Optiviera...

Core accounting: journals and other postings, period control, bank and tax masters, and sometimes AP/AR documents. The flow is: only post in open periods, keep chart and dimensions clean, and reconcile cash and sub-ledgers regularly.

End-to-end workflow

  1. Period discipline

    Open a fiscal period, post normal activity, then run review reports. Close the period to block accidental backdating when your policy says so.

  2. Journals and adjustments

    Create journal entries with balanced debit/credit lines, references, and dimensions. Use recurring templates where your org defines them, and mark accruals and reversals clearly.

  3. Bank and reconciliation

    Import or enter bank lines, match to open items, and post small differences to defined accounts. Reconcile to the sub-ledger and GL before you sign the month.

Common use cases

  • Month-end accrual

    Post an accrual in the right period with a reversal date, then reverse in the new period on the planned day.

  • Bank fee or FX difference

    Reconcile, post to bank fee or round-off accounts with documentation, and keep audit note in the line text.

  • Year-end close and carry-forward

    Run closing procedures your auditor agreed: retain earnings, open new year, and archive reports.

Practical tips

  • No posting in closed periods without a written exception path—controls beat clever fixes every time.

  • Use consistent dimension codes (cost center, project) or reporting will be wrong even when the GL balances.

  • Reconcile intercompany and clearing accounts before you lock the year.

Screens and confirmations

  • Journals, periods, master data

    Journals and similar screens use full-screen forms to capture lines. Periods and bank pages may show read overlays first, then edit where allowed.

  • Reversal and delete on posted data

    Reversing a journal or removing a line usually opens confirm with a warning, sometimes two steps, before a write to the ledger.

  • Tax and currency setup

    Master screens follow the same overlay or inline form pattern; invalid combinations fail on save with field-level errors.