Filevine + accounting architecture
Reviewed September 4, 2026 · Disbo product and content team
Answer first
Disbo is the workflow and synchronization layer between Filevine and a supported accounting product; this is not a direct Filevine-to-accounting integration. For applicable configured workflows, the live Filevine connection supplies supported matter context to Disbo, authorized users review and approve the disbursement in Disbo, and supported records are posted or synchronized through the selected accounting connection. Exact fields, record types, direction, and timing depend on both connections and the firm's configuration.
System flow
Each arrow represents a controlled, supported handoff. It does not mean every record automatically moves or that one system can overwrite another without the configured rules and permissions.
Configured Filevine matter context moves into Disbo, where the firm reviews and approves the settlement workflow. Disbo then sends supported accounting records through a separately configured accounting connection, after which the firm reviews its books.
Case system of record and supported matter context
Configured records are associated with the matter workflow
Preparation, separate approval, payment history, and review
Supported posting through its own configured connection
Accounting team reviews posting and reconciliation exceptions
A three-system design works only when the implementation defines the handoff at record level. The useful question is not whether “Filevine syncs to accounting,” but which source owns each value and what Disbo is configured to read, create, update, or preserve.
The configured Filevine connection can make supported matter context available to Disbo. The firm should define the matching key, required source fields, and treatment of closed, duplicate, merged, or corrected matters before relying on automation.
Disbo assembles the applicable matter-linked workflow, records preparation and approval events, and preserves available payment status. The firm—not synchronization—determines whether the underlying settlement calculation and recipients are correct.
A separate supported accounting connection can create or update configured records after the applicable workflow event. Account selection, class or dimension treatment, payee matching, attachments, and posting date rules must be scoped for the selected product.
Filevine remains the case-management system of record for matter data, case documents, and case-team permissions maintained there.
Disbo is the intermediary workflow and synchronization layer for applicable matter-linked preparation, approvals, payments, status, and available reconciliation evidence.
The connected accounting product remains the accounting system of record. The firm and its accounting professionals own classifications, period controls, corrections, and financial reporting.
Document required Filevine fields, matter matching, permitted updates, user access, and the event that makes a matter eligible for the Disbo workflow.
Specify the supported accounting record, accounts, payee behavior, memo or matter reference, posting trigger, duplicate handling, and whether a draft or completed workflow state is required.
Test representative workflows, corrections, rejected approvals, duplicate source records, closed periods, and connection failures; then assign owners to review exceptions in every system.
No. Disbo is the workflow and synchronization layer. Filevine and the selected accounting product each connect according to the supported, configured implementation.
Yes, for applicable configured workflows. Exact Filevine records, permissions, update direction, and timing depend on the customer's supported configuration.
Filevine remains the case-management source of truth, Disbo owns the applicable controlled disbursement workflow, and the connected accounting product remains the accounting source of truth.
No. The firm must review mappings, synchronized records, exceptions, reconciliations, and corrections with its accounting professionals.
These primary-source vendor pages explain general platform concepts. They are provided cautiously for background and do not establish that every feature or record is available in a Disbo implementation.
Public vendor documentation for Filevine platform and API concepts. Available endpoints and permissions depend on the authorized environment.
Public vendor documentation describing QuickBooks Online API concepts; it does not define Disbo-specific record coverage.
Public vendor documentation for Desktop integration concepts and local company-file access.
Public vendor documentation for Sage Intacct integration concepts. Any Disbo implementation is scoped and implementation-dependent.
Review connection availability, record coverage, ownership, mappings, approvals, posting behavior, and exceptions with Disbo.
Book a Demo