In-progress accounting workflow
Reviewed September 4, 2026 · Disbo product and content team
Answer first
A Filevine-to-Sage Intacct workflow through Disbo is in progress and implementation-dependent, not universally live. The intended design uses Disbo as the intermediary: supported Filevine matter context informs a controlled Disbo workflow, while scoped Sage Intacct API access may support configured records, dimensions, Other Receipts, and attachments. Every entity, field, dimension, attachment, posting trigger, permission, and response must be confirmed in the implementation before use.
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.
Intended configurable flow: supported Filevine matter context enters Disbo, the firm completes the controlled workflow, and Disbo may use scoped Sage Intacct API access to submit configured records such as Other Receipts, dimensions, or attachments for accounting review.
Supported source context, subject to configuration
Matter match, review, approval, and payment history
Entity, dimensions, receipt model, and files are validated
Configured request only where implemented and authorized
Firm verifies response, books, and exceptions
Sage Intacct supports configurable accounting structures, including dimensions and web-services access. Those platform concepts do not themselves establish a finished Disbo integration. The record model and authorization must be scoped for each implementation.
A scoped implementation may use supported Sage Intacct dimensions to preserve useful matter or organizational context. Which standard or user-defined dimensions apply, whether they are required, and how values are resolved must be validated.
Other Receipts may be considered for a configured receipt workflow where appropriate. Record type, bank account, payment method, posting date, line detail, references, and lifecycle behavior are implementation decisions—not universal defaults.
A scoped workflow may associate supported attachments with an Intacct record where API behavior, file requirements, retention expectations, and permissions permit. Source documents should not be assumed to transfer merely because the accounting record does.
Web-services credentials, sender authorization, company and entity access, roles, subscriptions, endpoint behavior, and environment readiness can affect feasibility. Access must be approved and tested before production reliance.
Filevine remains the source for supported case data and documents maintained by the case team.
Disbo is intended to control the applicable matter-linked workflow and coordinate only the Sage Intacct exchange that is expressly scoped and implemented.
Sage Intacct remains the accounting system of record for entities, dimensions, periods, books, corrections, and reporting.
Inventory the required Filevine inputs and intended Intacct entity, record type, dimensions, attachments, permissions, and review outcomes before confirming implementation.
Where appropriate, validate a configured Other Receipts or other supported model, required dimension values, attachment behavior, idempotency, response identifiers, and error handling in the authorized environment.
Document posting gates, credential ownership, exception queues, corrections, period controls, reconciliation, monitoring, and the manual path before any production use.
No. It is in progress and implementation-dependent. Availability must be confirmed after the required records, API access, permissions, and workflow are scoped and validated.
A scoped implementation may use supported dimensions, but the exact standard or user-defined dimensions and values depend on the organization's configuration.
Other Receipts are a possible configurable posting model, not a universal promise. The appropriate record type and fields must be approved and tested for the implementation.
They are implementation-dependent. File types, record associations, credentials, subscriptions, roles, entity access, and endpoint support must be confirmed.
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 for API concepts. Access and Disbo support remain subject to a scoped implementation.
Public vendor help for dimension concepts; it does not define which dimensions a Disbo implementation would use.
Public vendor reference for Other Receipts. Use in a Disbo workflow is only a possible scoped model.
Public vendor reference for attachment objects. Actual file support and association behavior require implementation validation.
Review connection availability, record coverage, ownership, mappings, approvals, posting behavior, and exceptions with Disbo.
Book a Demo