FAQ
Questions about merchant statement reconciliation, setup, and review.
Answers to the questions finance teams ask before changing how they reconcile processor statements, bank deposits, fees, and related payment activity.
Product + reconciliation
What does FeeSuite reconcile?
FeeSuite reconciles processor and merchant statement activity against bank deposits and related payment records. It keeps fees, reserves, chargebacks, adjustments, offsets, exceptions, and supporting detail connected in the same workflow.
How does FeeSuite match processor statements to bank deposits?
FeeSuite compares statement activity against the bank activity for the same period, then reports each item as matched, offset, or an exception.
How long does reconciliation take?
Routine reconciliation processes in seconds, so your team starts review with matches, offsets, exceptions, and supporting data already organized.
What happens when something does not reconcile?
FeeSuite separates the activity that still requires review and keeps the supporting data with the reconciliation record. Your team reviews the issue, resolves what needs attention, and approves the result.
What are matches, offsets, and exceptions?
A match is activity that reconciles directly. An offset accounts for related activity that explains the difference between records. An exception is activity that still requires review before the reconciliation is approved.
Review + control
Does FeeSuite replace the finance team’s review?
No. FeeSuite runs the repeatable reconciliation work and organizes the result. Your team reviews the financial outcome, resolves what needs attention, and approves the record.
What happens after a reconciliation is approved?
The underlying statement activity, bank activity, fees, reserves, chargebacks, adjustments, review states, and approvals remain connected. Your team can return to the record for month-end close, reporting, and future review without rebuilding prior work.
Does FeeSuite use the same reconciliation logic across accounts?
Yes. FeeSuite uses fixed reconciliation rules so the same inputs produce the same result. That gives teams a repeatable process across merchant accounts and entities.
Setup + positioning
What records does FeeSuite need to start reconciliation?
FeeSuite uses processor or merchant statements, bank activity and deposits, and the related payment records needed to explain the reconciliation. Depending on the workflow, that can include fees, contracted rate schedules, reserves, chargebacks, and adjustments.
How is FeeSuite different from a merchant statement analysis or fee-audit tool?
FeeSuite is built for ongoing reconciliation. It matches processor statements to bank deposits, organizes the result for review, verifies fees, and maintains the reconciliation history. Fee analysis is one part of the workflow, not the entire product.
How is FeeSuite different from spreadsheets or general accounting software?
Spreadsheets and general accounting platforms can hold reconciliation data, but the matching and investigation still have to be built and repeated by the team using them. FeeSuite is purpose-built for merchant payment reconciliation: it runs the repeatable matching work, organizes exceptions and supporting detail, verifies fees, and gives the team a structured result to review.
Who should attend a FeeSuite demo?
FeeSuite is built for the people responsible for payment reconciliation and close, including CFOs, controllers, accounting operations teams, and other finance leaders managing merchant payment portfolios.
Still have a question about your reconciliation process?
See how FeeSuite handles the routine reconciliation work and surfaces what needs your team’s attention.