Integrations
Books integrates with multiple products in The One Stack and external services. These integrations automate financial data flow, reduce manual entry, and keep your books in sync with operations.
Books + PSA
The deepest integration in the stack. PSA billable time flows directly into Books.
| Feature | Description |
|---|---|
| Time sync | Billable hours sync automatically via The One Bus |
| Auto-invoice | Generate invoices from synced PSA time entries |
| GL posting | Time entries create GL entries based on COA mappings |
| Contract revenue | Managed services contracts with deferred revenue recognition |
| Reconciliation | Background timer verifies PSA-to-Books data consistency |
Setup: Settings > Integrations > PSA
See PSA Integration for the full guide.
Books + Hub
Hub manages organization subscriptions for The One Stack platform. Books handles the financial side.
| Feature | Description |
|---|---|
| Revenue events | Hub publishes billing events that Books records as GL entries |
| Deferred revenue | Hub subscription revenue is recognized over the service period (ASC 606/IFRS 15) |
| Revenue recognition timer | Background job processes deferred revenue schedules |
| Billing seed | Hub billing products and plans are seeded into Books |
This integration is automatic — Hub events flow through The One Bus to Books without configuration.
Books + Portal
Clients interact with Books through the client portal.
| Feature | Description |
|---|---|
| Invoice viewing | Clients see their invoices in the Portal |
| Online payment | Clients pay invoices via Stripe (card or ACH) through Portal |
| Payment history | Clients view their payment history |
| Invoice tracking | Books tracks when clients view invoices (status: Viewed) |
No separate configuration needed — invoices are automatically visible in Portal when sent.
Books + CRM
CRM deal lifecycle connects to Books billing setup.
| Feature | Description |
|---|---|
| Deal close | When a CRM deal closes, it can trigger billing setup in Books |
| Customer sync | CRM contacts sync to Books as AR customers via entity sync |
| Revenue attribution | Track revenue back to the originating deal |
Setup: Configured through The One Bus event routing.
Books + Stripe
Stripe handles all payment processing for Books.
| Feature | Description |
|---|---|
| Payment collection | Process card and ACH payments on invoices |
| Webhook processing | Automatic GL posting on payment events |
| Multi-account | Support multiple Stripe accounts (one per entity) |
| Refunds | Process refunds through Stripe with automatic GL reversal |
| Billing profiles | Map legal entities to Stripe accounts |
Stripe Event Handling
Books processes these Stripe webhook events:
| Event | GL Entry |
|---|---|
charge.succeeded | DR Undeposited Funds, CR Revenue |
payment_intent.succeeded | DR Undeposited Funds, CR Revenue |
invoice.paid | DR Undeposited Funds, CR Revenue |
charge.refunded | DR Revenue, CR Undeposited Funds |
Multi-Entity Stripe Routing
For organizations with multiple entities, Stripe events are routed by metadata.entity_id:
- Each entity has its own Stripe account (or a default)
- Stripe events include entity metadata
- Books routes the GL entry to the correct entity's ledger
Setup: Settings > Integrations > Stripe — connect your Stripe account and configure entity assignments.
Books + Relay
Relay handles email delivery for Books.
| Feature | Description |
|---|---|
| Invoice emails | Invoices sent to clients are delivered via Relay |
| Payment receipts | Payment confirmation emails via Relay |
| Report delivery | Scheduled reports emailed via Relay |
| Dunning emails | Failed payment follow-up emails via Relay |
No separate configuration needed — Books uses Relay automatically when sending emails.
Books + Defend
The One Defend can post forensic response time to Books for billing.
| Feature | Description |
|---|---|
| Time entries | Defend forensic response time posts to Books via internal API |
| Billing | Response time can be included on client invoices |
This is a service-to-service integration using internal authentication.
External Integration: Journal Entry API
External systems can post GL entries directly to Books:
- Endpoint: POST to the Journal Entry API
- Authentication: X-Integration-Key header
- Payload: Account mappings, amounts, and description
- COA lookup: Source system + source code mapped to GL accounts via COA Mappings
Supported source systems: books, psa, ams, chms, import, autotask, stripe, hub_billing.
External Integration: Entity Sync
Books can sync customer and vendor records from Hub:
- Hub company records sync to Books as AR customers
- Hub contact records sync to Books as vendor contacts
- Sync is bidirectional for shared fields
Next Steps
- PSA Integration — Detailed PSA sync guide
- Getting Started — Connect Stripe and PSA
- Troubleshooting — Integration troubleshooting