Invisible when it works. Clear errors when it does not.
Two-way QuickBooks Online sync. DCAA cost accounting on top of your existing GL. FieldLedger handles the layer QBO does not: indirect rates, timekeeping, equipment, and federal invoicing.
What syncs. Which direction.
Explicit about depth. Two-way where it makes sense. One-way where QBO is the source of truth. Zero-sync for the DCAA layer that only exists in FieldLedger.
Chart of accounts
Pulled from QBO on connect and on demand. Your allowable/unallowable classification lives in FieldLedger; the account structure lives in QBO.
Employees
Pulled from QBO including active status, employment type, and pay info. Wage classifications and DCAA labor category assignments layered on in FieldLedger.
Customers
Pulled from QBO for invoice addressing. Contract records in FieldLedger link to customers 1:1.
Invoices (planned)
FieldLedger generates the FAR 52.212-4 certified invoice with per-CLIN cost breakdown. Push to QBO as invoice + line items. Keeps the signed certified PDF in FieldLedger for the audit trail.
Bills (planned)
Subcontractor invoices approved in FieldLedger push to QBO as bills against the vendor record, with DCAA cost categorization applied.
Indirect rate pools
Defined and allocated in FieldLedger under FAR 31.2. QBO is not aware of pools.
Signed timesheets
Signed periods, electronic signatures, admin-reopen log. Retained in FieldLedger. QBO stores only hour totals.
Equipment costing
USACE EP 1110-1-8 predetermined rates. Live in FieldLedger; not in QBO.
What is not synced
Being explicit about what FieldLedger is not, so you do not buy it for the wrong job.
Bank transactions
FieldLedger is not a bookkeeping tool. Bank feed and reconciliation stay in QBO.
Inventory
QBO Inventory and product catalog are not pulled. FieldLedger materials are contract-job-costed, not SKU-tracked.
Payroll
Timesheets in FieldLedger drive DCAA labor distribution. Actual payroll processing and tax filing remain with your payroll provider.
Full journal entries
FieldLedger does not post GL journal entries. Your indirect cost allocation is documented in FieldLedger and booked in QBO through your existing accountant workflow.
Security posture
Intuit OAuth handled the way DCAA and your prime contractor expect.
Tokens encrypted at rest
QBO OAuth refresh tokens encrypted with AES-256 in Azure Key Vault. Never stored in plain text.
Audit trail on every sync
Every pull and push logged: who, when, what changed. 7-year retention to match DCAA recordkeeping.
Automatic token refresh
Long-lived tokens refreshed before expiry. If Intuit invalidates a token, we surface a clear reconnect prompt on the pages where sync matters, not everywhere.
When sync breaks
No blinking indicators. No constant status messages. Sync status only appears on pages where it matters: invoices, bills, customer records. When something fails, the error tells you what to do next.
- Token expired or invalidated: reconnect prompt at Settings → Integrations. No blocked workflows in the meantime.
- QBO down: cached chart of accounts and employees continue to work. Pushes queue and retry when QBO is back.
- Data conflict: row-level error with the specific account/employee/customer and the conflicting field. One click to resolve.
Questions
Is FieldLedger on the QuickBooks App Store?+
App Store listing submitted. We run parallel direct-signup in the meantime so customers are not blocked. If you are on QuickBooks Online, the integration works today — the App Store listing is the discovery path.
Does it work with QuickBooks Desktop?+
Not currently. QuickBooks Online only. Desktop uses a different API and is not on our roadmap for Phase 1.
Will this replace my bookkeeper?+
No. QuickBooks and your bookkeeper handle the GL, bank recon, and month-close. FieldLedger handles the DCAA layer on top: indirect rates, timekeeping, equipment, federal invoicing, audit reports.
What happens if QBO sync breaks?+
Clear error with next steps surfaced on the page where the data matters (invoices, bills, customer records). Not a blinking badge on every screen. Reconnect in Settings. Your FieldLedger data is not dependent on QBO being online.
How long is initial sync?+
First pull of chart of accounts and employees typically runs in under a minute for firms under 100 employees. Customers pulled on demand. No daily full-resync — we pull diffs.
Can I disconnect and keep my data?+
Yes. Disconnect at any time from Settings. Everything FieldLedger has is yours and exports as CSV. Disconnecting does not delete data.
Connect QuickBooks in under a minute.
OAuth flow, cached pull, DCAA layer live. No implementation project. No consultant.
Start 14-day free trial