Integrations
QuickBooks data for covenant monitoring.
Why borrower accounting data matters
The change
When a borrower authorises a read-only accounting connection, interim financial data reaches the lender without anyone exporting a statement to PDF and emailing it, which removes the single largest source of delay in the covenant monitoring cycle.
Most of the elapsed time in covenant monitoring is not calculation. It is waiting: for the borrower's bookkeeper to close the period, produce statements, and send them. A connection does not make the borrower close their books faster, but it removes every step after that.
CovenantFlow reaches QuickBooks two ways. Codat provides broad coverage across small-business accounting systems, and a direct QuickBooks Online integration serves as a backstop where Codat is not available for a given tenant. Both are read-only and borrower authorised.
Being precise
What connected data is, and is not
This distinction is worth getting right, because overstating it is how a lender ends up testing an audited-financials covenant against management accounts.
| Dimension | Connected general ledger data | Audited or reviewed financial statements |
|---|---|---|
| What it reflects | What the borrower has recorded in its accounting system as of the moment of extraction. | Financial position after year-end adjustments, accruals, reclassifications, and, where applicable, auditor changes. |
| Timeliness | Available as soon as the borrower closes the period, with no submission step. | Typically 30 to 45 days after period end for interim statements, 90 to 120 days for annual audited statements. |
| Assurance | None. It is the borrower's own bookkeeping, unreviewed. | Compilation, review, or audit, depending on what the agreement requires. |
| Covenant use | Well suited to interim testing, trend monitoring, and early warning between reporting dates. | Required where the credit agreement specifies audited or reviewed statements as the basis for a test. |
| Consistency | High. The same extraction runs each period, so period-over-period comparison is not affected by presentation changes. | Presentation can change between periods and between preparers, which is part of why spreading exists. |
What it reflects
Connected general ledger data
Audited or reviewed financial statements
Timeliness
Connected general ledger data
Audited or reviewed financial statements
Assurance
Connected general ledger data
Audited or reviewed financial statements
Covenant use
Connected general ledger data
Audited or reviewed financial statements
Consistency
Connected general ledger data
Audited or reviewed financial statements
The right way to use both: connected data for continuous visibility and interim testing, prepared statements for the tests the agreement ties to them. A monitoring system should label which basis a given determination used, because the two are not interchangeable evidence. See commercial loan compliance.
What it can reasonably support
- Interim covenant testing between formal reporting dates, labelled as management-basis, giving an earlier read on where a ratio is heading.
- Trend monitoring on covenant inputs, which is often more informative than the quarter-end value itself.
- Pre-filling compliance certificates, so the borrower is confirming figures rather than assembling them.
- Reducing reporting delinquency, because a connected borrower has less to do each period. Lowering borrower effort is a more reliable mechanism than escalation.
- Cross-checking submitted statements against the underlying ledger, which occasionally surfaces presentation differences worth a conversation.
What it cannot do
- Satisfy a covenant that specifies audited or reviewed financials.
- Resolve definitional questions, whether a given expense qualifies as a permitted add-back is a judgment the ledger will not answer.
- Cover every borrower. Older systems, bespoke ledgers, and borrowers who decline all remain on document submission.
- Replace the compliance certificate, which carries an officer certification that a data feed does not.
Asking a borrower for the connection
This is a relationship request as much as a technical one, and it is worth handling as such.
The three properties that make it reasonable: access is read-only, it is scoped to the financial data needed rather than the whole system, and the borrower can revoke it at any time. Those should be stated plainly when the request is made. Borrowers who decline should stay on document submission without friction, and the lender should not treat the connection as a condition it never negotiated in the credit agreement.
The reciprocal argument, which is the one that actually persuades borrowers, is that connecting once replaces producing and emailing statements every period for the life of the loan. For a small finance team that is a real saving.
For borrowers on other systems, see NetSuite data for covenant monitoring, and the full collection workflow on borrower reporting automation.
FAQ
Frequently asked questions
- How can QuickBooks data support covenant monitoring?
- When a borrower authorises a read-only connection, general ledger data flows to the lender without the borrower exporting statements to PDF and emailing them. That removes the round trip on interim reporting, delivers structured data that needs no spreading, and makes period-over-period comparison consistent because the extraction is identical each time.
- Does CovenantFlow connect to QuickBooks?
- Yes, two ways. Codat provides broad coverage across small-business accounting systems including QuickBooks, and a direct QuickBooks Online integration serves as a backstop where Codat is not available for a given tenant. Both are read-only and authorised by the borrower.
- Can accounting data replace audited financial statements?
- No. General ledger data reflects what the borrower has recorded, before year-end adjustments, accruals, reclassifications, and auditor changes. Where a credit agreement requires audited or reviewed statements, a live accounting connection does not satisfy that requirement. It is valuable as an interim signal and for removing friction on internally prepared reporting.
- Is the connection read-only and can the borrower revoke it?
- Yes. Access is read-only and revocable by the borrower at any time. Those two properties are what make the request reasonable to put to a commercial customer, and they should be stated plainly when it is made rather than buried in terms.
- What if a borrower will not connect their accounting system?
- They stay on document submission, which has to be a fully supported path rather than a degraded one. Some borrowers have legitimate reasons to decline, and some run systems with no connector available. Treating the connection as mandatory converts a convenience into a relationship problem.
Keep going
Related reading
Solution
Borrower Reporting Automation
Chasing quarterly financials is a workflow problem. This is the workflow.
Integration
NetSuite
Middle-market borrowers on NetSuite, reached through the accounting aggregation layer.
Topic
Borrower Reporting
Financial statements, compliance certificates, borrowing base certificates, and everything else the agreement asks for.
Solution
Covenant Compliance Automation
Deterministic math on top of AI-extracted definitions, so a compliance status can be explained line by line.
Back to Integrations.
See how CovenantFlow automates covenant monitoring
Move from loan documents and borrower reporting requirements to structured covenant intelligence, compliance workflows, and portfolio visibility.