LoopfourReconcile bank transactions
Build a workflow that syncs bank transactions into a table each day, matches them against your ledger, and lists the items left to explain.
The job
Each day or each month, someone exports bank activity and ticks it off against the ledger. Deposits are matched to invoices and payments out to bills. What is left becomes the list of reconciling items to explain.
By hand
With Loopfour
How the workflow runs
- TriggerEach morningA schedule you choose, in your time zone.
- StepSync bank transactions into a tableFinances (Plaid) adds new transactions and updates changed ones in your table.
- StepGet open invoices and billsFrom your ledger, such as QuickBooks.
- StepMatch transactionsThe AI Agent step pairs bank lines with invoices and bills by amount, date and payee.
- DecisionAnything left unmatched?
- OutputItems to explain sent to your teamA Slack message lists them. You can also save them to a table.
What you need
- Template: Studio has no ready-made template you can run for this job. You build it by describing it in chat.
- Systems to connect: Finances (Plaid) for your bank and card accounts, your ledger (for example QuickBooks), and Slack for the exceptions message.
- A table: a table in Loopfour that receives the bank transactions. See Tables.
- Who reviews: the person who owns the bank reconciliation. If the workflow will post adjustments, name an approver too.
Set it up
Link your bank accounts
Go to Integrations and connect Finances (Plaid). You sign in to your bank through a bank link. See Finances (Plaid).
Create the transactions table
Go to Tables and create a table for bank transactions. It needs the columns Finances (Plaid) writes to; the Finances (Plaid) guide lists them.
Describe the workflow in chat
On Home, describe the job. For example: "Each weekday at 7am Pacific, sync transactions from my operating account into the Bank transactions table. Then get open invoices and bills from QuickBooks, match each new bank transaction to one of them, and post the unmatched transactions in #close." See Build a workflow by describing it.
Check the sync step
Open the Finances (Plaid) step. Action should be Sync transactions. Check Institution connection, Accounts and Data Table. One step reads from one bank connection only.
Deploy, then test
Select Deploy, then Run and read the result. Compare the matches with your bank statement before relying on them. See Deploy, test and change a workflow.
Run works only when the workflow is Active. Deploying also switches on its trigger; choose a safe schedule or test source before deploying. Runs make real changes in connected systems.
What you review
- The transactions table: it holds the synced bank lines, so you can sort, filter and keep it as support for the reconciliation.
- Items to explain: the Slack message lists the unmatched transactions for your team to clear.
- Each run: under Runs, each run shows what was synced, the matches proposed and what was left. See Read a run.
- Who did what: the Audit trail tab under Runs records workflow changes and any approvals.
Adapt it
- Write the matches back: save each match and its invoice or bill to a second table, so you have a matched-items listing for month end.
- Several bank accounts: add a sync step for each bank connection, each writing to the same table.
- Book bank fees: add an Approval step, then a step that posts recurring items such as bank fees to your ledger after approval.
Match purchase orders, receipts and invoices
Set up a three-way match that checks each vendor invoice against its purchase order and goods receipt in NetSuite and sends mismatches for a decision.
Reconcile intercompany balances
Build a workflow that compares both sides of each intercompany balance in NetSuite at month end and lists the differences for your team to resolve.