Bill.com
Building the JDBC URL
After installing the license, access the connection management page by executing the command java -jar kingswaysoft.jdbc.jar. Enter the necessary details, and the program will automatically generate the JDBC connection URL. Users can click Test Connection to test the generated URL and Copy to Clipboard to copy the connection string for use within the application where the JDBC driver is being used.
Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the 'Test Connection' feature will be disabled.
General Page
The General page of the Bill.com Connection Manager allows you to specify the general settings of the connection:

General Settings
- General Settings
-
- API
-
Choose between the below APIAPI
- AP & AR
- SPEND & EXPENSE
- Instance Type
-
Choose between the below instances
- Production
- Sandbox
- API Throttling Rate
-
The API Throttling Rate will limit the number of requests that can be sent per second. Set this value to 0 to disable API throttling.
Authentication
- Authentication
-
- User Name
-
The User Name to use when accessing Bill.com service.
- Password
-
The Password to use when accessing Bill.com service.
- Developer Key
-
The Developer Key to use when accessing Bill.com service.
- Organization ID
-
The Organization ID to use when accessing Bill.com service.
- API Token
-
The API Token to use when accessing Bill.com service.
MFA
Some endpoints in the Bill.com API require the use of an MFA authenticated session. MFA configuration is optional and can be ignored if you do not intend to interact with any endpoints that require MFA.
After entering valid values for fields in the Authentication section, click on 'Get Token'. This will send a one-time code to the phone number configured on Bill.com for MFA. Enter the code in the 'MFA Token' field. Afterwards, input the device name and click 'Validate MFA'.
If the MFA Token was correct, a trusted session ID will be stored in the connection string and will allow the driver to make requests to endpoints that require MFA.
By default, Bill.com expires a session after 35 minutes of inactivity, this would typically require you to redo the MFA authentication process.
Instead, you can enable 'Remember Me' which will allow the MFA authentication to persist for 30 days rather than 35 minutes.
- MFA Token
-
The six-digit MFA token that is sent to the phone number registered during the MFA setup.
- Remember Me
-
Enable Remember Me for the generated MFA ID to expire in 30 days.
- Device
-
The Device is a nickname for your device.
Advanced Settings Page
The Advanced Settings page allows you to specify advanced settings for the connection.

Proxy Server Settings
- Proxy Mode
-
The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.
- No Proxy
- Auto-detect (Use system configured proxy)
- Manual
- Proxy Server
-
Using the Proxy Server option allows you to specify the name of the proxy server for the connection.
- Port
-
The Port option allows you to specify the port number of the proxy server for the connection.
- Username (Proxy Server Authentication)
-
The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.
- Password (Proxy Server Authentication)
-
The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.
Miscellaneous Settings
- Timeout (secs)
-
The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for infinite timeout.
- Retry on Intermittent Errors
-
The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked requests will be retried up to 3 times.
- Ignore Certificate Errors
-
This option can be used to ignore those SSL certificate errors when connecting to the target server.
Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.
Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.
- Concurrent Writing Threads
-
This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.
- Bulk Polling Interval (secs)
-
This value controls how often (in seconds) the driver polls Bill.com to check the status of bulk operations.
Using the JDBC Driver
Explore detailed examples in this section that demonstrate the application of JDBC classes such as Connection, Statement, and ResultSet to effectively manage interactions with Bill.com data. This section covers the use of regular statements and prepared statements for executing complex or frequently executed queries.
Executing Statements
Once you've connected from your code (see Connecting with DriverManager and Connecting with DataSource), you can execute SQL statements using the Statement class. Refer to the Executing Prepared Statements section for information on how to execute parameterized statements.
SELECT
Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data.
To retrieve the results of a query, you would then call the getResultSet method of the Statement.
String sql = "SELECT * FROM roles"; try { ResultSet resultSet = statement.executeQuery(sql); LOGGER.info(resultSet.toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "INSERT INTO users (firstName, lastName, email, acceptTermsOfService, roleId) VALUES ('John', 'Doe', '[email protected]', true, '0po02YYUHPUADTP1120k')"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
00602KTUCVMOCKTJun30,null,null,{"firstName":"John","lastName":"Doe","email":"[email protected]","acceptTermsOfService":true,"roleId":"0po02YYUHPUADTP1120k"},false
UPDATE
Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.
String sql = "UPDATE users SET firstName = 'John', lastName = 'Smith' WHERE userId = '00602KTUCVMOCKTJun30'"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
00602KTUCVMOCKTJun30,null,null,{"firstName":"John","lastName":"Smith"},false
DELETE
Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM bill-approvals/policies WHERE policyId = '00802CSBFHJUWKPS62yx-iByxGtJeVI'"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Executing Prepared Statements
Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general class, Statement.
Below are the steps outlining how to execute a prepared statement:
Creating and Executing a Prepared Statement
- Create a PreparedStatement
-
Use the
prepareStatementmethod of theConnectionclass to instantiate aPreparedStatement.Refer to Connecting with DriverManager or Connecting with DataSource for information related to establishing connections.
- Set Parameters
- Declare parameters by calling the corresponding setter method of the
PreparedStatement. - NOTE: The parameter indices start at 1.
- Execute the PreparedStatement
- Use the generic
executeorexecuteUpdatemethod of thePreparedStatement. - Retrieve Results
- Call the
getResultSetmethod of thePreparedStatementto obtain the query results, which will be returned as a ResultSet. - Iterate Over the Result Set
- Use the
nextmethod of the ResultSet to iterate through the results. To obtain column information, utilize theResultSetMetaDataclass. Instantiate aResultSetMetaDataobject by calling thegetMetaDatamethod of the ResultSet.
SELECT
Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.
String sql = "SELECT * FROM roles WHERE roleId = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "0po02ATCNMKFWKL1120l"); ps.executeQuery(); while (ps.getResultSet().next()) { for (int i = 1; i <= ps.getResultSet().getMetaData().getColumnCount(); i++) { LOGGER.info(ps.getResultSet().getMetaData().getColumnLabel(i) + "=" + ps.getResultSet().getString(i)); } } } catch (SQLException e) { LOGGER.error(e); }
INSERT
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.
String sql = "INSERT INTO users (firstName, lastName, email, acceptTermsOfService, roleId) VALUES (?, ?, ?, ?, ?)"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "John"); ps.setString(2, "Doe"); ps.setString(3, "[email protected]"); ps.setBoolean(4, true); ps.setString(5, "0po02YYUHPUADTP1120k"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors
00602KTUCVMOCKTJun30,null,null,{"firstName":"John","lastName":"Doe","email":"[email protected]","acceptTermsOfService":true,"roleId":"0po02YYUHPUADTP1120k"},false
UPDATE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.
String sql = "UPDATE users SET firstName = ?, lastName = ? WHERE userId = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "John"); ps.setString(2, "Smith"); ps.setString(3, "00602KTUCVMOCKTJun30"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors
00602KTUCVMOCKTJun30,null,null,{"firstName":"John","lastName":"Smith"},false
DELETE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM bill-approvals/policies WHERE policyId = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "00802CSBFHJUWKPS62yx-iByxGtJeVI"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.error(e); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Metadata Discovery
This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.
Tables
The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.
This method only retrieves tables that are not write-only.
To get a list of tables which include write-only tables, query the table system.tables.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getTables(null, null, null, null); LOGGER.info("\r\n" + rs.toString()); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS null,null,attachments,Table,null null,null,attachments/customers,Table,null null,null,attachments/invoices,Table,null null,null,attachments/vendors,Table,null ......
The getTables method returns the following metadata columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The catalog that contains the table. |
| TABLE_SCHEM | String | The schema of the table. |
| TABLE_NAME | String | The name of the table. |
| TABLE_TYPE | String | The type of the table (e.g., TABLE or VIEW). |
| REMARKS | String | An optional description of the table. |
Columns
Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns. To narrow the results to a specific table, specify the table name using the parameter table_name.
This method returns columns only for tables that are not write-only.
To get columns for tables which are write-only, query the table system.columns.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getColumns(null, null, "roles", null); LOGGER.info(rs.toString()); } catch (SQLException e) { e.printStackTrace(); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE null,null,roles,createdTime,93,TIMESTAMP,null,null,0,0,null,null,null,93,null,null,null,null,null,null,null,null,null,null,DT_DBTIMESTAMP null,null,roles,description,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,roles,id,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,roles,results,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR ......
The getColumns method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The database name. |
| TABLE_SCHEM | String | The table schema. |
| TABLE_NAME | String | The table name. |
| COLUMN_NAME | String | The column name. |
| DATA_TYPE | Integer | The data type represented by a constant value from java.sql.Types. |
| TYPE_NAME | String | The data type name used by the driver. |
| COLUMN_SIZE | Integer | The length in characters of the column or the numeric precision. |
| BUFFER_LENGTH | Integer | The buffer length. |
| DECIMAL_DIGITS | Integer | The column scale or number of digits to the right of the decimal point. |
| NUM_PREC_RADIX | Integer | The radix, or base. |
| NULLABLE | Integer | Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1). |
| REMARKS | String | The comment or note associated with the object. |
| COLUMN_DEF | String | The default value for the column. |
| SQL_DATA_TYPE | Integer | Reserved by the specification. |
| SQL_DATETIME_SUB | Integer | Reserved by the specification. |
| CHAR_OCTET_LENGTH | Integer | The maximum length of binary and character-based columns. |
| ORDINAL_POSITION | Integer | The position of the column in the table, starting at 1. |
| IS_NULLABLE | String | Whether a null value is allowed: YES or NO. |
| SCOPE_CATALOG | String | The catalog of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_SCHEMA | String | The schema of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_TABLE | String | The name of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SOURCE_DATA_TYPE | Short | The source type of a distinct type or user-defined REF type (null if DATA_TYPE is neither DISTINCT nor a user-defined REF). |
| IS_AUTOINCREMENT | String | Whether the column value is assigned by Bill.com in fixed increments. |
| IS_GENERATEDCOLUMN | String | Whether the column is generated: YES or NO. |
| DTS_TYPE | String | Object DTS attribute type. |
Primary Keys
The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in Bill.com.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "risk-verifications"); LOGGER.info("\r\n" + resultSet.toString()); Assertions.assertNotNull(resultSet); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME null,null,risk-verifications,referenceId,1,null
The getPrimaryKeys method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The catalog name. |
| TABLE_SCHEM | String | The schema name. |
| TABLE_NAME | String | The name of the table that contains the primary key. |
| COLUMN_NAME | String | The name of the column that serves as the primary key for the table. |
| KEY_SEQ | Short | The sequence number within the primary key. |
| PK_NAME | String | The primary key name. |
Connection Settings
| Connection Setting | Type | Default Value | Description |
|---|---|---|---|
| API | String | "AP & AR" | The API to use when accessing Bill.com service, the supported APIs include AP & AR and Spend & Expense |
| ApiThrottleRate | Integer | 10 | The maximum number of API requests a client can make to the server within a specific time period, defined in requests per second. |
| ApiToken | String | "" | The Api Token to use when accessing Bill.com service. |
| AuthenticationMode | String | "OAuth" | Method used to retrieve an authentication token from the server. |
| BulkPollingInterval | Integer | 5 | Controls how often (in seconds) the driver polls Bill.com to check bulk operation status. |
| CacheExpirationTime | Integer | 30 | Defines the expiration time for cache. A value of 0 disables caching. |
| ConcurrentWritingThreads | Integer | 1 | The number of threads for executing operations in parallel. A value of 0 will disable multi threading. |
| ConnectionTimeout | Integer | 30 | ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the Bill.com API. |
| DeveloperToken | String | "" | The Developer Key to use when accessing Bill.com service. |
| Device | String | "" | The nickname for your device. |
| IgnoreCertificateErrors | Boolean | false | Specifies whether to verify the certificate when connecting to Bill.com. If no certificate verification is required, you can set this value to 'true'. |
| IgnoreError | Boolean | false | Determines if the program continues executing SQL statements after encountering an error. |
| InstanceType | String | Production | Instance Type selects whether the Bill.com connection uses the real Production environment or the safe Sandbox test environment. |
| LogFileSize | String | "10485760" | A string specifying the maximum size in bytes for a log file. |
| LogLevel | String | "INFO" | The logging level for the JDBC driver. |
| LogPath | String | "./jdbcLogs" | The directory where log files are stored. |
| OemKey | String | "" | The OEM license key. |
| OrganizationId | String | "" | The Organization ID to use when accessing Bill.com service. |
| Password | String | "" | The Password of the Bill.com account used to authenticate requests to the Bill.com API. |
| ProxyMode | String | "NoProxy" | This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual". |
| ProxyPassword | String | "" | The password to be used to authenticate to the proxy. |
| ProxyServer | String | "" | The host of the proxy server. |
| ProxyServerPort | Integer | 0 | The port of the proxy server. |
| ProxyUsername | String | "" | The username to be used to authenticate to the proxy. |
| ReadBatchSize | Integer | 100 | ReadBatchSize is used to set how many records can be read from Bill.com in a single call. Bill.com has a maximum ReadBatchSize of 100. |
| RememberMe | Boolean | false | Set as true for the generated MFA ID to expire in 30 days |
| RememberMeId | String | "" | This is a persistent token used to skip MFA verification during subsequent logins. |
| ResultPath | String | "" | The path where the execution result files are saved. |
| RetryOnIntermittentErrors | Boolean | true | The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues. |
| SaveResult | Boolean | false | The SaveResult parameter indicates whether to save the execution results to a file. |
| ServiceName | String | "" | The ServiceName refers to the name of the service API selected by the user. |
| ServiceTimeout | Integer | 120 | The ServiceTimeout is the timeout to receive the full response from Bill.com API. |
| Suppress404NotFoundError | Boolean | true | When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created. |
| TrustedSessionId | String | "" | After MFA verification succeeds, the current sessionId is saved as the trusted session ID. This ID can be used during the current session to avoid repeating the MFA verification. |
| Username | String | "" | The user name of the Bill.com account that will be used to authenticate requests to the Bill.com API. |
| WriteBatchSize | Integer | 1 | WriteBatchSize is used to set how many records can be written to Bill.com in a single call. At this time, Bill.com does not support batch writing. As such, the value of this property should be kept at 1. |