Skip to main content

​
Overview

Bridge lets you connect an external database so Recital can read data directly for reconciliation. After a connection is configured, you can preview available database tables or collections, choose the dataset Recital should use, and make that data available during reconciliation. This is useful when your reconciliation source already exists in a database and you want Recital to read it directly instead of uploading files manually.

​
Supported Database Types

Recital supports common relational databases, including:
  • PostgreSQL
  • MySQL
  • SQL Server
  • Oracle
  • MariaDB
  • DB2
  • Redshift
  • Snowflake
  • SQLite
  • H2
Recital also supports MongoDB for collection-based connections.

​
Required Connection Details

To connect a database through Bridge, provide the connection details for the database source you want Recital to read from:
  • Database type
  • Host or connection URL
  • Port
  • Database name
  • Username
  • Password
  • Provider or database option selected in Bridge
Use a read-only database user with access only to the required tables, views, or collections. This keeps the connection focused on the data Recital needs for reconciliation.

​
Connection Test and Schema Preview

After entering the connection details, test the connection in Bridge. If the test is successful, Recital displays the available tables or collections and their columns or fields. Review the preview to confirm that you are selecting the correct dataset before saving the connection.

​
Table or Collection Selection

You can select a table or collection and choose the columns or fields Recital should import. If the data should be filtered by reconciliation date, also select the date column Recital should use. This allows Recital to fetch only the records that match the reconciliation date range.

​
Custom Query Option

Instead of selecting a single table, you can provide a custom SQL query. Custom queries are useful when you need to join multiple tables, rename columns, add computed fields, filter records, or shape the dataset before Recital reads it. For example:
:startDate and :endDate are the default date placeholders. Recital uses them to apply the reconciliation date range when fetching data. Custom queries should be read-only SELECT queries and should return clear column names. Use column aliases when needed so the previewed fields are easy to identify during reconciliation setup.

​
Saving the Connection

Once the table, collection, or custom query is confirmed, save the connection. Recital returns a connection ID for the saved database connection. You can select this connection later during reconciliation setup.

​
Using the Connection in Reconciliation

When the saved database connection is selected during reconciliation, Recital fetches the relevant data from the configured table, collection, or custom query. If a date column or date placeholders are configured, Recital applies the reconciliation date range when fetching data. The returned records are then available like any other reconciliation source.

​
Best Practices

  • Use a read-only database user
  • Grant access only to required tables, views, or collections
  • Use clear column aliases in custom queries
  • Include a date column or date placeholders when reconciliation should be date-bound
  • Test the connection before saving
  • Preview returned data before using it in reconciliation
  • Keep query output focused on the fields needed for matching