How do I set up reconciliation software for bank reconciliations across multiple entities with bank feeds?

Here’s a practical way to set up reconciliation software for bank reconciliations across multiple entities with bank feeds.

1) Define the operating model first

Before configuring software, decide:

• Which entities need to be reconciled
• Which bank accounts belong to each entity
• Whether you need one global instance with multiple entities, or separate workspaces/tenants
• Who will prepare, review, and approve reconciliations
• Whether you want daily, weekly, or monthly reconciliation

This prevents configuration issues later, especially around access control and intercompany activity.

---

2) Connect each bank feed to the correct entity

For each entity:

1. Add the entity in the reconciliation software
2. Create the corresponding bank account record
3. Connect the bank feed to that account
4. Verify the feed is bringing in:
   • transaction date
   • value date
   • amount
   • description/reference
   • bank transaction ID, if available

Important:

• Make sure each feed is mapped to the correct legal entity
• If one bank account serves multiple entities, decide how transactions will be split or allocated
• If feeds are delayed or incomplete, define a fallback process for manual import

---

3) Standardize your chart of accounts and bank rules

To make matching reliable across entities:

• Use consistent chart of accounts naming
• Standardize bank transaction categories
• Set up matching rules for common items such as:
  • bank charges
  • interest
  • payroll
  • card payments
  • customer receipts
  • supplier payments
  • intercompany transfers

Good reconciliation software usually lets you create:

• auto-match rules
• bank rules
• transaction coding rules

Build these centrally, then apply them consistently by entity.

---

4) Configure opening balances and historical data

For each entity and bank account:

• Set the opening book balance
• Set the opening bank balance
• Import historical transactions if needed
• Reconcile the opening period first, then move forward

If you’re starting mid-year, be careful to:

• agree opening balances to the last closed period
• confirm prior reconciliations are complete
• ensure no duplicate imports

---

5) Set matching logic and tolerances

Configure matching criteria such as:

• exact amount
• date window, e.g. ±3 days
• reference/description match
• customer/vendor name match
• one-to-one, one-to-many, many-to-one matching

Also define tolerances for:

• minor FX differences
• bank fees
• rounding differences

Keep tolerances tight enough to avoid false matches, but flexible enough to handle real-world bank behavior.

---

6) Build workflows for multi-entity control

For each entity, define the workflow:

• Import bank feed
• Auto-match transactions
• Review exceptions
• Code unmatched items
• Prepare reconciliation statement
• Approve and lock period

If you have multiple entities, add:

• entity-level access permissions
• reviewer separation
• consolidated reporting across all entities
• period close status by entity

---

7) Handle intercompany and shared cash accounts

This is often the hardest part.

If entities share cash movements:

• define whether the transfer is a true intercompany loan, settlement, or cash sweep
• set up matching rules for both sides of the transfer
• use consistent references so the software can link both entries
• keep intercompany balances visible and reconcilable separately

If one bank account is used by several entities, you may need:

• allocation rules
• journals to move items to the right entity
• a clearing account structure

---

8) Set up exception management

Unmatched items should go to an exception queue with reasons like:

• duplicate transaction
• missing book entry
• timing difference
• unknown bank charge
• uncleared deposit/payment
• data feed error

Create a standard process:

• investigate
• code
• escalate if needed
• document the resolution

This is key for auditability.

---

9) Build reporting and audit trail

Make sure the software gives you:

• reconciliation status by entity and account
• unreconciled items aging
• auto-match rate
• exceptions by category
• approver history
• audit log of changes
• exportable reconciliation reports

For multi-entity environments, you want both:

• entity-level reconciliation packs
• group-level dashboard reporting

---

10) Test before go-live

Before using it in production:

• connect a few bank accounts first
• test auto-matching accuracy
• test intercompany scenarios
• test permissions and approvals
• test month-end close process
• compare system output with manual reconciliations

Run a parallel period, if possible.

---

11) Suggested rollout approach

A good rollout order is:

1. Set up the organizational structure
2. Configure one pilot entity
3. Connect one or two bank feeds
4. Tune matching rules
5. Add exceptions and approvals
6. Roll out to remaining entities
7. Standardize reporting and month-end close

This reduces disruption and helps refine rules early.

---

12) Best practices

• Use consistent bank account naming
• Keep one entity per legal entity wherever possible
• Review and update rules regularly
• Reconcile frequently, not just at month-end
• Keep documentation for unusual items
• Restrict manual overrides
• Use a close checklist for every entity

---

If you want, I can also give you:

1. a step-by-step implementation checklist,
2. a sample multi-entity reconciliation workflow, or
3. a recommended software setup structure for a specific system like BlackLine, FloQast, Xero, NetSuite, or Sage.