What this reconciliation agent handles
Bank reconciliation slows down when someone has to match large volumes of transactions by hand. A QuickBooks reconciliation agent proposes the likely match, surfaces exceptions, and keeps a person in control of the final commit.
This setup is especially useful in three situations:
- Exact matches. The agent can surface the clearest matches for quick review when the amount, date, and context line up.
- Near matches. Transactions with small timing or amount differences can be surfaced with the variance clearly shown.
- Unmatched items. Items that do not line up with QuickBooks can be flagged so finance can investigate before anything is posted.
How the agent works
With Pinksheep, you can build this agent in plain English. The table below shows how it moves from raw transaction data to an approved reconciliation update.
| Agent stage | What happens | Output | Approval |
|---|---|---|---|
| Trigger | Scheduled run (daily, weekly, or monthly) or manual trigger | Matching run starts | No approval for read phase |
| Gather context | The agent reads bank transactions, QuickBooks entries, matching rules, and the relevant date range | Ranked match proposals | No approval for read phase |
| Proposed matches | The agent prepares matches, flags discrepancies, and surfaces any items that need closer review | Ready-to-review reconciliation batch | Approval before any write |
| Operator review | Reviewer checks match confidence, variance amounts, and unmatched items | Approve, reject, or edit | Explicit approval required |
| Write to QuickBooks | Approved matches or related updates are written to the record | Live reconciliation history with full activity visibility | Only after approval |
How to set up reconciliation
Describe your matching rules in plain English, including exact match criteria, tolerance for date or amount variance, and any vendor context the agent should use.
Connect QuickBooks with access to bank feeds, transaction history, and the reconciliation records the agent should read.
Decide which transactions need the closest review, especially discrepancies, timing gaps, or unmatched items.
Keep approval on before posting so someone can confirm the match before it lands in QuickBooks.
Permissions and approval checks
- Read access should cover bank transactions, QuickBooks transaction history, and the vendor or customer context needed for matching.
- Write scope should be limited to reconciliation marks, match confirmations, and the exact updates the agent is allowed to propose.
- Unmatched items should be surfaced clearly so the accounting team can investigate before anything is committed.
- Approval views should show both the bank record and the QuickBooks record side by side before commit.
Frequently asked questions
Does reconciliation happen automatically or does it require approval?
By default, matching proposals should be reviewed before anything is written to QuickBooks.
How does the agent decide which transactions to match?
It can use amount, date proximity, vendor context, and transaction type to propose the most likely match, then show that proposal for review.
What happens if there's a discrepancy?
It should flag the discrepancy for review so someone can investigate or approve the right next step before the match is committed.
Can the agent handle multiple bank accounts?
Yes. It can work across multiple bank accounts as long as the matching rules and access scope are defined for each one.