Campfire

Campfire combines core accounting and consolidation with close checklists, account reconciliations and analysis of period-to-period changes. Bank matching, accruals and prepaid schedules help maintain the ledger, while reports can drill down to the transactions behind a total.

Set the review controls

To stop an administrator from posting a journal they created, edit that person on the Team page and select Approval Required. Other roles, policies and permissions determine access across the organisation.

Ember, the accounting assistant, can bring proposed matches into its conversation for review. Accept, reject or rematch the transaction there before it posts. Its activity record identifies the person or agent responsible and links to the bill or invoice involved.

Open a journal's detail page to see the invoice, bill or credit/debit memo associated with it. If you delete a linked journal, the confirmation identifies the related items that will also be removed. This gives the reviewer useful context before changing the books.

For a group with an intermediate parent, an Elimination task in the Close Checklist can be scoped to that entity. Each parent can have its own elimination entity and consolidated statements in its functional currency.

Moving the books into Campfire

Migration starts with the chart of accounts, vendors, departments and entities. Journal entries are mapped into Campfire's format, with conflicts flagged for review. Balance and format checks precede posting, which requires human approval.

The migration workbook compares the old and new balance sheets account by account and month by month. Campfire also offers a sandbox using the customer's own data before a purchase commitment.

Commercial setup

Pricing is quoted after a demonstration and depends on factors such as entity count, transaction volume, revenue complexity and integrations. It is not charged per seat. Campfire's implementation team handles onboarding, and the published pricing overview includes standard integrations and ongoing support.

Agree whether the project includes full transaction history or a cutover date that leaves earlier records in the old system. That choice determines where staff will look for historical accounting detail after the move.