Live API integration
+ 
3988 connects Cubby to NetSuite with a live API integration. Revenue by stream, deferred rent, tenant deposits and merchant settlements post per facility, entity by entity, so the close stops depending on exports and re-keying.
The Cubby integration, at a glance.
- Integration
- Cubby to NetSuite, built and supported by 3988.
- Connection type
- Live API integration. Not a CSV export or file upload.
- Cadence
- Posts per facility, daily or per defined period.
- System of record
- Cubby keeps the tenant ledger. NetSuite owns the financials.
- NetSuite edition
- NetSuite OneWorld, so every legal entity is its own subsidiary. CAD and USD entities consolidate together.
- Built for
- Operators running multiple legal entities. No upper size limit; clients can run well over 500 locations.
Cubby runs the facility. NetSuite runs the enterprise.
Cubby is cloud-based self storage management software. It runs rentals, tenant accounts, payments and day-to-day site operations at each facility.
It isn't built to consolidate dozens of legal entities, tie out intercompany, or produce a different statement for every owner. That is a general ledger job. The integration lets each system do its own job, without a lump journal per site or a CSV dump at month end.
Three problems that live between Cubby and the books.
| Problem | Without the integration | With it |
|---|---|---|
| Cubby-to-GL is a re-key or a CSV dump | One lump journal per site per month, or manual entry. Revenue-stream analysis is lost and errors surface a quarter later. | Revenue posts to NetSuite by stream, per facility, without anyone re-keying it. |
| Merchant settlement never reconciles | Gross charges in Cubby, net deposits in the bank, processor fees somewhere in between. | Gross charges, processor fees and the net deposit post separately, so the bank reconciles. |
| Facility P&L doesn’t tie to operations | Cubby says one revenue number, the general ledger says another. NOI per facility is a guess. | Facility revenue in NetSuite comes from the same Cubby data, facility by facility and entity by entity. |
Six data flows, Cubby into NetSuite.
| Data from Cubby | How it lands in NetSuite |
|---|---|
| Rental revenue, by revenue stream | Rent, tenant protection / insurance, late fees, admin fees, merchandise and auction proceeds each post to their own line, by facility and legal entity. No single lump "storage income" journal. |
| Deferred and prepaid rent | Held as a liability and recognised as it is earned. This is the accrual most operators get wrong. |
| Tenant deposits | Booked as a liability, not revenue. |
| Merchant settlement clearing | Gross charges, processor fees and the net deposit post separately, so the bank actually reconciles. |
| Write-offs and credits | Posted to the facility and entity they belong to, instead of surfacing a quarter later. |
| Operational statistics (optional) | Physical and economic occupancy, square feet, unit counts, move-ins and move-outs as statistical accounts, so NOI and revenue per occupied square foot run live in NetSuite. |
The boundary
Cubby stays the system of record for the tenant ledger. NetSuite owns the financials. Tenant-level detail does not migrate.
Operators with multiple legal entities on Cubby.
A storage or multi-asset real estate operator running multiple legal entities, with Cubby for site operations and QuickBooks plus Excel for the books, reporting to more than one owner group, with a close that takes more than two weeks.
There is no upper size limit. 3988 supports portfolios well over 500 locations.
NetSuite + Cubby: common questions.
Is there a NetSuite integration for Cubby?
Yes. 3988 has built a live API integration between Cubby and NetSuite. It posts rental revenue by stream, deferred and prepaid rent, tenant deposits, merchant settlement clearing and write-offs to NetSuite per facility, with optional operational statistics such as occupancy.
Is the Cubby integration an API or a CSV import?
It is a live API integration. Data moves from Cubby to NetSuite without anyone exporting or uploading a file.
Does NetSuite replace Cubby?
No. Cubby stays the system of record for the tenant ledger and site operations, and tenant-level detail does not migrate into NetSuite. NetSuite owns the financials: the general ledger, intercompany, consolidation and owner reporting across entities.
What does the Cubby integration not do?
It does not move tenant records or lease administration into NetSuite, replace Cubby, manage unit-level rates, or handle tenant-facing payment processing. Those stay in Cubby and with your payment provider. The integration carries financial data only.
We already run NetSuite. Can we add the Cubby integration on its own?
Yes. The Cubby integration is available to any Cubby operator, either on its own for an existing NetSuite customer or as part of a 3988 implementation. It requires NetSuite OneWorld.
Which other self storage platforms does 3988 integrate with NetSuite?
SiteLink / Storable Edge, storEDGE, Storable Easy, Yardi Breeze, AppFolio, Tenant Inc and Easy Storage Solutions connect through CSV or file exchange today, and 3988 can build a live API integration for any of them as part of an engagement, using the same pattern as Cubby.
Who is the Cubby integration built for?
Self storage and multi-asset real estate operators with multiple legal entities who report to more than one owner group. There is no upper size limit: 3988 supports portfolios well over 500 locations.
Running Cubby across multiple locations?
We'll walk you through the integration against a real multi-entity chart of accounts.