Financial workflow

Reconcile bank and ledger exports. See which transactions need review.

Compare transaction exports using reference, amount, currency and date rules you confirm. Inspect matches, tolerance outcomes and unresolved exceptions before finalizing and exporting a result.

What you can investigate

  • Find unmatched entries. Surface records present in only one financial export.
  • Inspect amount differences. Apply confirmed sign, date and tolerance rules.
  • Review before finalizing. Investigate exceptions instead of guessing matches.

Financial journey

  1. Import.Bring in supported CSV, XLS or XLSX files from both sides.
  2. Understand.Inspect headers, row counts and source shape locally before choosing reconciliation semantics.
  3. Map & Configure.Map reference and other matching fields, amount, currency and date, then set sign, exact-match rules, amount/date tolerances and normalization. Exact matching and amount/date tolerances are available on Free; optional 1:N, N:1 and bounded N:N group matching is available with Pro and during the Pro trial.
  4. Match.Run deterministic reconciliation: exact rules first, then configured tolerances and, with Pro or the Pro trial, group logic. Non-unique candidates remain unresolved.
  5. Explain.See exact, tolerance, group, conflict, invalid and unmatched outcomes with source provenance.
  6. Review.Inspect unresolved records and record supported link, unlink or ignore decisions with reasons.
  7. Verify.Resolve or explicitly ignore remaining exceptions and finalize the conserved reviewed result before export. This is workflow confirmation, not independent accounting or audit certification.
  8. Export.Download the appropriate local CSV, Basic XLSX or eligible Professional XLSX report from the finalized Financial result.

Synthetic example

A bank-to-ledger comparison you can inspect.

Matched

Bank REF-101 and ledger REF-101 both show USD 125.00 on the same date under the confirmed rules.

Amount difference

Bank REF-102 shows USD 80.00; ledger REF-102 shows USD 82.00. A configured amount tolerance determines whether this is within tolerance or needs review.

Missing record

Bank REF-103 has no corresponding ledger record and remains visible as a one-sided exception.

These invented rows illustrate possible outcomes, not an automatic accounting judgment. Review supported exceptions and finalize the Financial result before export.

Financial use cases

Start from a specific reconciliation problem.

See how the existing Financial workflow applies to payment reconciliation and bank and ledger reconciliation. Optional group matching is available with Pro and during the Pro trial.

For advertising costs, see ad spend reconciliation using exported platform and finance files.

A practical business question

A month-end question worth answering

Does transaction REF-202 differ by USD 5 between the bank and ledger exports? Configure your amount tolerance and sign convention, then review the outcome before finalizing. Timing, fees, reversals and grouping may need additional configuration; a matched row is not an audited account.

Try with synthetic sample exports or review the related workflow before using business-sensitive data.