Import or capture statements
Bring in bank statement lines or other external records using supported methods.
- Statement date, reference and amount
- Opening and closing balance checks
- File format and mapping validation
Connect bank activity, payment records, customer receipts, supplier payments and ledger balances in a disciplined reconciliation workflow. Help finance teams identify unmatched transactions, investigate differences and document resolution before period close.
Use a consistent process to compare external records with internal transactions and account balances, rather than relying on unexplained adjustments.
Bring in bank statement lines or other external records using supported methods.
Compare statement lines with receipts, payments and ledger activity.
Identify items that do not agree and assign a clear resolution path.
Compare supporting records with general ledger balances.
Keep corrections and write-offs under controlled authorization.
Track outstanding items and confirm reconciliations are complete.
Reconciliation is complete when balances agree or every remaining difference is documented, supported and assigned for resolution. Keep the original records intact and make corrections through approved, traceable transactions.
Select the account and verify statement coverage.
Validate totals, references and transaction dates.
Identify matched lines and unresolved exceptions.
Gather evidence and obtain approval for corrections.
Confirm balances, document outstanding items and sign off.
Financial reconciliation is most useful when the source modules and general ledger share consistent references and posting rules.
Compare statement lines with cashbook activity, transfers, receipts and payments.
Compare customer invoices and receipts with receivables control balances and investigate unapplied cash.
Compare supplier invoices, credit notes and payments with supplier statements and ledger balances.
Compare stock movement and valuation records with inventory control accounts.
Where integrated, compare approved payroll registers, payment totals and related ledger postings.
Maintain reconciliation status, unresolved item lists and reviewer evidence for close procedures.
Use clear ownership and separation of duties for statement preparation, matching, adjustment approval and final sign-off. Avoid silently editing posted transactions to force a balance.
Assign account owners and limit who can approve adjustments.
Verify statement ranges, opening balances and imported totals.
Require explanations and supporting documents for corrections.
Keep timing differences visible until they clear.
Review material exceptions and confirm period-end sign-off.
Review statement imports, matching rules, control accounts, exception approvals and period-end reporting with the LaraOffice team.
Common questions about matching transactions and closing accounts.
It is the process of comparing internal accounting records with independent records or supporting schedules, explaining differences and confirming that balances are supported.
Automatic matching depends on available features and the quality of imported statement data. Confirm supported formats, matching rules, tolerance settings and the review process for ambiguous matches.
They should remain visible in an exception queue with an owner, reason and next action. Timing differences should be tracked until cleared; errors should be corrected through authorized transactions.
Those reconciliations require supporting reports and control-account postings to be available and consistent. Confirm the reports, references and ledger mappings in your implementation.
It should not silently alter posted records. Any adjustment, write-off or reversal should follow the organization's approval policy and preserve an audit trail.
No. Bank feeds, statement imports, automated matching and integration availability depend on the deployed LaraOffice edition, supported bank formats and implementation configuration.
Chat with LaraOffice
Tell us a little about you, then continue on WhatsApp.