Reference · built on requestOperator by FibricFinance & billing

Bank Reconciliation

Bank statement lines matched to ledger entries and processor payouts, with matches, missing entries, and unexplained items proposed.

Request accessPricing ↗

About

A bank statement and a ledger describe the same money in different words. This operator reads both. Statement lines come from the ledger's bank feed or from files the bank drops on a server you name. Ledger entries come from the same ledger: payments received, bills paid, and money spent or received without a document. Processor payouts come from Stripe, Adyen, PayPal, or Square, with their fees and refunds.

It proposes three kinds of result. A match, where a line and one or more entries agree on amount, date, and reference. A missing entry, where a line has nothing to match and an entry should be created. An unexplained item, where it found candidates and rejected them, with the reason shown.

This is a reference listing. It documents what Fibric would read from Bank Reconciliation and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Spent and received money transactions in Xero: BankTransactions with Type, Reference, and IsReconciled, and the Bank Summary report
  • Payments and bill payments in the ledger: QuickBooks Online Payment and BillPayment, Xero Payments, Prepayments, and Overpayments
  • Bank feed transactions in Sage Intacct cash-management, and journals posted against the bank account
  • Statement files the bank drops on an SFTP server, noticed by comparing directory listings and modification times between polls
  • Stripe payouts and the balance transactions inside each, listed by payout id with type charge, refund, stripe_fee, or payout
  • Payout events from Adyen (PAYOUT_THIRDPARTY, PAYOUT_DECLINE) and Square (payout.sent, payout.paid, payout.failed)
  • Lines already marked reconciled in the ledger, which it skips

Proposed actions

  • Target capability: propose a match between one statement line and the ledger entries it agrees with on amount, date, and reference
  • Target capability: propose a spend or receive money transaction for a statement line with no ledger entry, coded to the account you choose
  • Target capability: propose a payout split: one deposit explained by the charges, refunds, and fees the processor reports for that payout
  • Target capability: propose a bank transfer between two accounts where a line on each side agrees in amount and date
  • Target capability: propose a list of unexplained items, each with the closest candidates and why each was rejected

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Explain every processor deposit

    Each Stripe payout that lands in the bank is split into the balance transactions it settles, charges less refunds and fees, and matched to the Xero bank line. One approval per payout.

    With Stripe, Xero

  • Reconcile from a statement file

    The bank drops a statement on your SFTP server. Each line is matched to QuickBooks Online payments and bill payments; lines with nothing to match become proposed entries for you to code.

    With SFTP, QuickBooks Online

  • Work exceptions in a sheet

    Unexplained items are appended to a Google Sheet the controller already keeps, with candidates and reasons. Sage Intacct bank feed lines that later match are cleared from it on approval.

    With Google Sheets, Sage Intacct

  • Card payouts from more than one processor

    Adyen and Square payout events are held until the bank line arrives, then matched to Business Central customer payment journals in one proposal per payout.

    With Adyen, Square, Microsoft Dynamics 365 Business Central

Requirements

  • A ledger connector exposing bank transactions and the entries to match: Xero, QuickBooks Online, or Sage Intacct
  • A payment processor connector with payout records: Stripe, Adyen, PayPal, or Square
  • A file connector where statements land when the ledger has no bank feed: SFTP, Amazon S3, or Google Sheets
  • A mapping from each bank account to its ledger account, and a suspense account for lines you cannot yet explain
  • A date window and a tolerance for the match rule, agreed before it runs
Authentication
It carries no bank login. Statement lines arrive through the ledger's own feed or through a file server you control; ledger and processor reads use the connectors you attach and the scopes on them.

Limits

  • It matches on amount, date window, and reference. It does not read remittance PDFs or log in to a bank portal.
  • Xero exposes IsReconciled as a status to read. The match lives in this operator's receipt; a person completes the reconciliation in the ledger.
  • Stripe cannot say which transactions a manual or instant payout contains. Those payouts are matched by amount alone and flagged as such.
  • Foreign-currency lines are matched in the statement's currency. Gains and losses on translation stay with the ledger.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Bank Reconciliation ↗

Questions and answers

What do I approve, and what can I change?
Each match, each missing entry, and each payout split is its own proposal. You see the statement line, the candidate entries, and the fields they agree on. Approve it, pick a different candidate, or send it to the unexplained list.
What is left on the record?
One receipt per statement line: what it matched or created, who approved it, when, and the entry that reverses it. Unexplained items keep the candidates it rejected and the reason for each.
Does it reconcile anything on its own?
No. A statement line is matched or an entry created only after approval, and only once. Where the ledger has no reconcile action, a person completes that step in the ledger and the receipt records the match.
Ask about Bank Reconciliation

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy